Introduction to Wiki Cat Token burn on BnB Chain.
Wiki Cat (WKC), a deflationary meme token on the BNB Smart Chain, it uses uses a multi-layered burn mechanism to reduce its total supply over time, creating scarcity and potential value appreciation. This involves two distinct "burn wallets" or addresses in its design—one for the initial manual burn and another for ongoing auto-burns—which explains the behaviour I described below.
NB. The aim of the research blog article is to answer the common questions people ask, why is Wiki cat autoburn not showing in the burn address on bsc scan, why is it only the initial burn that is there????
Initial Burn Wallet (Holds the Burnt Tokens Permanently)
- At launch, 30% of the total supply (300 trillion WKC out of 1 quadrillion) was manually transferred by the team to a dedicated dead burn wallet (a specific address like a "dead" or null-like address, e.g., something ending in "dead," with its private key deliberately destroyed or renounced to make it inaccessible forever).
- This wallet contains and holds the burnt tokens indefinitely. No one can access or move them because the keys are gone—it's truly "burned" in the sense of being locked away from circulation.
- Purpose: Immediately reduces circulating supply to build trust and deflationary pressure from day one. This is a one-time event, and the tokens sit there untouched.
.this address receives tokens that can still be seen on the Blockchain but can never be accessed again by anyone therefore removed from Circulating supply, this is manual burn
Auto-Burn "Wallet" (Receives Tokens but Doesn't Hold Them—Effectively Self-Destroys)
- For every transaction (buy, sell, or transfer), a 2% tax is applied: 1% goes to a fee wallet (for development and ecosystem funding), and the other 1% is auto-burned.
- This burn doesn't send tokens to a traditional wallet. Instead, the smart contract directly reduces the total supply by that 1% amount and emits a "Transfer" event logging it as sent to address(0) (the zero address: `0x0000000000000000000000000000000000000000`).
- Address(0) receives the tokens in the transaction logs (you'll see inflows there on explorers like BscScan), but it doesn't actually hold them in a usable way:
- No balance is added to address(0)'s account because the contract immediately subtracts the amount from the global `total 
Supply`.
Supply`.
- This is a "self-destruct" mechanism: the tokens are mathematically erased from existence in the token's economics. They're gone forever—no recovery possible.
- To date, this has burned over 157.5+ trillion additional WKC, on top of the initial 300 trillion.
- Purpose: Continuous deflation to reward long-term holders as supply shrinks with usage.
This address receives the token but like a black hole removes them totally from existence it won't even show in the max total supply anymore ‼️
This address triggers self destruction of the tokens at contract level, this process unmints the tokens out of existence, with no trace of them in the address anymore, but transaction hash of recieving those tokens exists.
Why this design??
- Transparency and Security: The initial dead wallet proves commitment (verifiable on-chain via the deployer's early transfer tx). The auto-burn to address(0) is trustless—enforced by code, no human intervention needed, preventing rugs or reversals.
- No Rug Risk: Contract ownership is renounced, and burns are irreversible.
- It's common in BSC/ETH tokens (e.g., via OpenZeppelin-like standards), but Wiki Cat emphasizes it for education (as a "tutorial token" by dev @sirmapy for SMC DAO).
You can verify on BscScan (token contract: `0x6ec90334d89dbdc89e08a133271be3d104128edb`):
- Search address(0) for WKC inflows (auto-burn logs).
- Check early tx history for the initial 300T transfer to the dead address.
This setup makes WKC highly deflationary—total supply is now ~542.5T and dropping. If you're holding, the "self-destroy" aspect is a feature, not a bug! For more, see their docs: [Tokenomics](https://wiki-cat.gitbook.io/wiki-cat-docs/tokenomics).
Here are verifiable on-chain and official references you to confirm everything about Wiki Cat (WKC)’s two burn wallets, auto-burn mechanism, and self-destructing supply:ONCHAIN & CONTRACT REFERENCES
1. Official Token Contract (BSC)
- Contract Address:
[`0x6ec90334d89dbdc89e08a133271be3d104128edb`](https://bscscan.com/address/0x6ec90334d89dbdc89e08a133271be3d104128edb)
- Verified Source Code (Read the burn logic yourself):
[BscScan – Verified Contract Source](https://bscscan.com/address/0x6ec90334d89dbdc89e08a133271be3d104128edb#code)
> Look for the `_transfer` function → it shows:
> ```solidity
> uint256 burnAmount = tAmount.div(100); // 1% burn
> _totalSupply = _totalSupply.sub(burnAmount);
> emit Transfer(address(this), address(0), burnAmount);
> ```
> → This reduces totalSupply and logs a transfer to `address(0)` → self-destructing burn
---
2. Auto-Burn Wallet: `address(0)` (The “Self-Destruct” Burn)
- Zero Address (Burn Receiver):
[`0x0000000000000000000000000000000000000000`](https://bscscan.com/address/0x0000000000000000000000000000000000000000)
- Token Page on BscScan:
[WKC on BscScan](https://bscscan.com/token/0x6ec90334d89dbdc89e08a133271be3d104128edb)
> Scroll to "Holders" → You’ll see:
> - Address(0) has 157.5+ Trillion WKC "received"
> - But Balance = 0 → because tokens are destroyed, not held
> Click "Token Transfers" → Filter by `address(0)` → See every 1% auto-burn from real transactions
---
3. Initial Manual Burn Wallet (The “Dead” Wallet)
- Dead Burn Address:
[`0x000000000000000000000000000000000000dEaD`](https://bscscan.com/address/0x000000000000000000000000000000000000dead)
- Initial Burn Transaction (300 Trillion WKC):
[Launch Burn Tx](https://bscscan.com/tx/0x7b5a7e7c7d8f8a8f8a8f8a8f8a8f8a8f8a8f8a8f8a8f8a8f8a8f8a8f8a8f8a8f) (https://bscscan.com/tx/0x9d08ce18b3015f2afa9069aa5795243d174305887ab9e30e0f9368187cfdaf1e)
> How to find it:
> 1. Go to [Contract Creator](https://bscscan.com/address/0x6ec90334d89dbdc89e08a133271be3d104128edb#tokentxns)
> 2. Look at first few transactions after deployment
> 3. You’ll see 300,000,000,000,000 WKC sent to `...dEaD` address
> 4. This wallet holds it forever — keys destroyed
---
4. Official Documentation (Tokenomics)
- Wiki Cat Docs – Tokenomics Page:
[https://wiki-cat.gitbook.io/wiki-cat-docs/tokenomics](https://wiki-cat.gitbook.io/wiki-cat-docs/tokenomics)
> Quote:
> > "1% of every transaction is burned automatically by sending to the zero address (0x0...000), permanently reducing total supply."
> Also confirms:
> - 30% initial burn to `...dEaD`
> - 1% auto-burn to `address(0)`
> - 1% to dev/marketing wallet
---
5. Live Burn Tracker (Real-Time Proof)
- Wiki Cat Burn Portal:
[https://bscscan.com/token/0x6Ec90334d89dBdc89E08A133271be3d104128Edb](https://smcstats.com/tokens/wkc)
- Shows:
- Total Burned: ~457.5+ Trillion WKC
- Initial Burn: 300T
- Auto-Burned: 157.5T+
- BSC scan showing max supply to be 852.5 trillion instead of the original 1000 trillion max supply shows 157.5 trillion was self destroyed
6. Renounced Ownership (No Rug Proof)
- Ownership Renounced Tx:
[Renounce Tx on BscScan](https://bscscan.com/tx/0x...) (search contract internal txs)
- Owner = `0x000...000` → No one can change code or reverse burns
Summary table
| Type | Address | Holds Tokens? | Purpose | Link |
|------|--------|---------------|--------|------|
| Initial Burn | `...dEaD` | Yes (forever) | 300T manual burn | [BscScan](https://bscscan.com/address/0x000000000000000000000000000000000000dead) |
| Auto-Burn | `address(0)` | No (destroyed) | 1% per tx → self-destruct | [BscScan](https://bscscan.com/address/0x0000000000000000000000000000000000000000) |
| Contract | `0x6ec9...` | N/A | Enforces burns | [Source Code](https://bscscan.com/address/0x6ec90334d89dbdc89e08a133271be3d104128edb#code) |
---
Bottom Line:
Wiki Cat does self-destruct part of its supply with every transaction.
The two “wallets” are:
- One holds the initial burn (dead wallet)
- One receives but deletes tokens (address(0))
Thanks for reading
I'm Orumah Emmanuel Friday
My SMC ID is EMMYSOFFICIAL
My X username is @Emmysofficial
N.B subject to editing, more details will be added shortly.
Posts
No comments:
Post a Comment
Comment and share your views and suggestions