Shibainu burns: dead addresses and token supply

Dead-address transfers and the SHIB burn function

Dead-address transfers and direct contract burns remove access to SHIB through different changes to the token ledger. A transfer credits a destination with no known usable spending key, while a contract burn destroys units within the token’s accounting. A dormant wallet does not qualify as a dead address merely because it has stopped transacting; its owner may still hold a usable key.

SHIB balances at dead addresses

An ordinary transfer subtracts SHIB from the sender and adds it to the dead address, where the balance remains visible. A supply tracker can exclude that recipient’s balance from circulation without changing the underlying contract. A dead address can therefore appear among the largest holders without representing a trader capable of selling its balance.

Destruction through the token contract

The SHIB contract’s burn function reduces its recorded total supply. The function destroys the caller’s tokens and emits a Transfer event naming the zero address as recipient, without crediting that address with spendable SHIB. An ordinary SHIB transfer to the zero address reverts; the burn function performs a separate operation.

What confirms a completed SHIB burn?

A completed SHIB burn requires a successful transaction involving the genuine token contract, with a transfer or destruction record matching the intended removal. A transaction hash identifies an attempt; a pending transaction has not established its token changes. For a dead-address transfer, the relevant record is the SHIB Transfer event naming that recipient. For direct destruction, the event points to the zero address. An approval grants spending permission and establishes no removal by itself. A zero-value Transfer event moves no SHIB and adds nothing to the burned amount.

The transaction’s top-level recipient may be the SHIB contract, while its decoded Transfer event identifies the actual token recipient. Token identity includes the blockchain and contract address. A matching ticker on another contract does not establish a SHIB burn. Destination balances can corroborate completed transfers, while supply queries help distinguish contract-level destruction. Other transactions can change balances between observations, so an event identifies the individual amount more precisely than a later balance difference.

Shibarium fees and the ShibTorch conversion

ShibTorch funds SHIB removal using BONE accumulated from Shibarium transaction fees. Holding SHIB, or moving it between ordinary Ethereum wallets, does not automatically invoke this fee-funded mechanism.

BONE fee collection

The fee-funded process starts with BONE collected in a burn contract on Shibarium. Burn initiation requires accumulated BONE to meet the configured threshold; a lower balance cannot trigger it. The configuration also governs the portion allocated to SHIB conversion. Base fees and validator priority fees have different recipients, so the entire gas charge cannot automatically count as a SHIB burn contribution. Fee collection establishes funding; the subsequent conversion determines the SHIB quantity available for removal.

Open full-size image

Conversion and the final SHIB transfer

ShibTorch converts accumulated BONE into SHIB for burning on Ethereum. Moving the funding between networks and exchanging it precedes the final SHIB removal. Exchange execution, liquidity, and applicable fees affect the conversion output. An estimated SHIB amount can differ from the amount the final transfer records. The burn tracker distinguishes in-progress operations from completed burns. A collected BONE balance measures the funding asset, while the final SHIB transfer measures token removal. Their amounts use different token units.

A failed bridge or swap stage can leave the SHIB burn unfinished even when the funding balance exists.

Why can SHIB burn totals disagree?

SHIB burn totals can differ because trackers use different destination lists, accounting methods, reporting periods, and definitions of circulating supply. The contract’s totalSupply value counts units remaining in its accounting, including balances at ordinary dead addresses. Circulating-supply estimates can exclude those balances. Subtracting them again from an already adjusted figure counts the same removal twice. A cumulative calculation needs a clear starting supply and separate adjustments for transfers into dead addresses and contract-level destruction.

Address classification also changes the interpretation of holder statistics. An inactive wallet, exchange reserve, or liquidity pool has a different role from an inaccessible burn destination. Large balances do not establish large individual ownership. A pooled address can represent many users, and one holder can control several addresses. Including burned balances among potential sellers overstates the supply those addresses can trade.

Burn-rate percentages describe changes in burning activity across stated periods. A large increase from a small earlier amount can still remove a small fraction of circulating SHIB. If the earlier period records no burning, the usual percentage-change calculation has a zero denominator. Absolute SHIB quantities, matching reporting windows, and the circulating-supply basis explain the scale without relying on the percentage headline.

Permanent SHIB removal and burns with retained claims

A burn can cancel a token representing another asset or claim, with the underlying assets remaining accessible through a withdrawal. The affected contract and receiving asset determine whether an operation removes SHIB permanently, changes its representation, or returns pool holdings. These operations have different consequences despite sharing the word burn.

ShibaSwap v1 burns liquidity tokens when withdrawing underlying pool assets. If the pool holds SHIB, that withdrawal returns SHIB instead of destroying it. A supported bridge withdrawal similarly cancels a mapped representation to permit movement back to Ethereum. Neither record should automatically enter a total for permanent SHIB removal.

Do SHIB burns raise the token price?

SHIB burns do not guarantee a higher price, because demand and market liquidity also determine the prices buyers and sellers accept. Removing tokens changes available supply, and its economic significance depends on the amount removed relative to circulation. An impressive activity percentage can describe a small change in available units. A price move around the same time does not establish the burn caused it.

Remaining holders keep their existing SHIB quantities after someone else’s burn. The transaction creates no automatic payout to their wallets.

Fee-funded conversion can involve buying SHIB before removal, whereas burning tokens already held requires no new market purchase. Those mechanisms create different immediate trading activity without determining the next market price. Burning your own tokens also leaves you with fewer SHIB, so any later price change applies only to the balance you retain.