# Upload CW Burner Admin Contract

**URL:** https://forum.osmosis.zone/t/upload-cw-burner-admin-contract/3434
**Category:** DApps / Tooling
**Tags:** withdrawn
**Created:** [January 23, 2025, 10:40pm UTC](https://forum.osmosis.zone/t/upload-cw-burner-admin-contract/3434 "2025-01-23T22:40:38Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![temporalkaku](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/temporalkaku/32/2712_2.png) [@temporalkaku](https://forum.osmosis.zone/u/temporalkaku)
#### Post date: [January 23, 2025, 10:40pm UTC](https://forum.osmosis.zone/t/upload-cw-burner-admin-contract/3434/1 "2025-01-23T22:40:38Z")

</div>

**Description:**  
Passing this proposal will upload the CW Burner Admin contract to the Osmosis chain.

## Details

The CW Burner Admin is a CosmWasm contract designed to serve as a tokenfactory admin that exclusively allows burning tokens, while preventing any minting operations. This smart contract provides a secure and controlled mechanism for implementing token burning strategies on the Osmosis blockchain in a decentralized manner.

Key features of the contract include:

- Restricted administrative capabilities that only allow token burning operations while ensuring an accurate token supply count in the Bank module
- Complete prevention of token minting or further change of admin rights, ensuring a strictly deflationary mechanism
- Compatible with IBC-Hooks for burning from other IBC connectedchains
- Exhaustive testing utilizing Osmosis Test-Tube

## Contract Information

- Release: V1.0.0
- Code repository: [GitHub - kakucodes/cw\_burner\_admin](https://github.com/kakucodes/cw_burner_admin)
- Checksum: 4f380e1d087ad368e5ce817679c2de7db15557067b0ad4b7fb4e2fb884d03dd9
- Compiler Version: cosmwasm/optimizer:0.16.0
- Commit ID: 234bf576147f08e3684c435b68546cb107eba16f

---

<div class="post-metadata">

### Author: ![LeonoorsCryptoman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/leonoorscryptoman/32/208_2.png) [@LeonoorsCryptoman](https://forum.osmosis.zone/u/LeonoorsCryptoman)
#### Post date: [February 4, 2025, 6:26pm UTC](https://forum.osmosis.zone/t/upload-cw-burner-admin-contract/3434/2 "2025-02-04T18:26:50Z")

</div>

There is a similar feature on the Chihuahua-chain.

Did you investigate that one as a basis or did you start from zero?

---

<div class="post-metadata">

### Author: ![temporalkaku](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/temporalkaku/32/2712_2.png) [@temporalkaku](https://forum.osmosis.zone/u/temporalkaku)
#### Post date: [February 19, 2025, 2:53pm UTC](https://forum.osmosis.zone/t/upload-cw-burner-admin-contract/3434/3 "2025-02-19T14:53:36Z")

</div>

I asked Mr Wyles and Mr Powers in the Osmosis Technical TG if they were aware of a contract that does this currently and none of us were familiar with one so this is an independent attempt at a solution.

---

<div class="post-metadata">

### Author: ![LeonoorsCryptoman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/leonoorscryptoman/32/208_2.png) [@LeonoorsCryptoman](https://forum.osmosis.zone/u/LeonoorsCryptoman)
#### Post date: [February 20, 2025, 7:48pm UTC](https://forum.osmosis.zone/t/upload-cw-burner-admin-contract/3434/4 "2025-02-20T19:48:55Z")

</div>

Now knowing the alternative on Chihuahua, are you open for a comparison?

I rather have the best solution in the market already if we can choose from 2 solutions; maybe yours is better, but I don’t know ^^

---

<div class="post-metadata">

### Author: ![temporalkaku](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/temporalkaku/32/2712_2.png) [@temporalkaku](https://forum.osmosis.zone/u/temporalkaku)
#### Post date: [February 24, 2025, 9:55pm UTC](https://forum.osmosis.zone/t/upload-cw-burner-admin-contract/3434/5 "2025-02-24T21:55:18Z")

</div>

absolutely but I could use a hand locating their repo as google isn’t uncovering anything.

---

<div class="post-metadata">

### Author: ![LeonoorsCryptoman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/leonoorscryptoman/32/208_2.png) [@LeonoorsCryptoman](https://forum.osmosis.zone/u/LeonoorsCryptoman)
#### Post date: [February 26, 2025, 7:32pm UTC](https://forum.osmosis.zone/t/upload-cw-burner-admin-contract/3434/6 "2025-02-26T19:32:51Z")

</div>

> **[GitHub - ChihuahuaChain/chihuahua: chihuahuad binary repository](https://github.com/ChihuahuaChain/chihuahua)**
>
> chihuahuad binary repository

---

<div class="post-metadata">

### Author: ![temporalkaku](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/temporalkaku/32/2712_2.png) [@temporalkaku](https://forum.osmosis.zone/u/temporalkaku)
#### Post date: [February 28, 2025, 3:26pm UTC](https://forum.osmosis.zone/t/upload-cw-burner-admin-contract/3434/7 "2025-02-28T15:26:10Z")

</div>

sorry i dont think i quite understand. this is the chihuahua chain repo? do they have a contract for tokenfactory ownership that disallows mints but continues to allow burns? i dont think i’m the right person to champion an update to Osmosis’ tokenfactory module itself.

---

<div class="post-metadata">

### Author: ![LeonoorsCryptoman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/leonoorscryptoman/32/208_2.png) [@LeonoorsCryptoman](https://forum.osmosis.zone/u/LeonoorsCryptoman)
#### Post date: [March 5, 2025, 7:27pm UTC](https://forum.osmosis.zone/t/upload-cw-burner-admin-contract/3434/8 "2025-03-05T19:27:34Z")

</div>

What is the difference between burning a native asset and a tokenfactory asset?  
In both cases they need to be removed, right?
