Docs
The mechanism, the accounting, and the checks you can run yourself. Short by design — there is not much to a protocol whose guarantees are things it cannot do.
ZYNT is a token burn protocol on Robinhood Chain. It does one thing: it removes ZYNT from circulation and makes the removal verifiable by anyone, without asking them to trust a dashboard — including this one.
Supply is fixed at genesis. There is no mint function, no treasury that can issue more, and no upgrade path that could add either. Every figure this site reports is derived from two on-chain values: total supply, and the balance sitting at the burn address.
ZYNT is not deployed yet. There is no contract on Robinhood Chain, so there is nothing to burn and nothing to measure. Every burn figure on this site is empty, and none of them are estimated, projected, or simulated.
What is already fixed is the supply: 10,000,000 ZYNT, minted once in the constructor, with no mint function to raise it. The moment the contract is deployed and its address configured, supply, the ledger, analytics, and burning all switch to live chain data with no change to this interface.
A burn is an ordinary ERC-20 transfer to an address with no private key. Once tokens arrive there, no signature exists that can move them again — not the protocol’s, not a multisig’s, not yours.
Because the destination is a normal address, the accounting needs no special indexer to be trustworthy. Circulating supply is total supply minus that address’s balance, and anyone can compute it from a single RPC call.
circulating = totalSupply() - balanceOf(BURN_ADDRESS)
burnRate = balanceOf(BURN_ADDRESS) / totalSupply()The ledger tags each burn with where it came from, because the distinction matters when reading the cadence.
Protocol burns are automated reductions funded by protocol revenue. Treasury burns retire tokens the protocol itself held. Manual burns are holder-initiated — anyone can burn their own balance from the burn panel, and it counts identically.
A burn event is a reduction the protocol committed to in advance, with a target amount published before it settles. Events show progress against that commitment, so a partially filled event is visible as exactly that rather than presented as complete.
Individual transactions inside an event also appear in the main ledger. Events are a narrative layer over the ledger, never a replacement for it.
Nothing here needs to be taken on faith. Every burn row links to its transaction on the Robinhood Chain explorer, and the burn address page shows the running total this site reports as “total burned”.
If the two ever disagree, the chain is right and this interface is wrong. Treat the explorer as the source of truth.
Open the burn address on RobinhoodThe interface reads through a single data source interface rather than talking to the chain directly. That boundary is deliberate: the presentation layer is finished and the on-chain reader is a drop-in behind it.
interface ZyntDataSource {
getSupply(): Promise<TokenSupply>
getRecentBurns(limit?: number): Promise<BurnTransaction[]>
getAllBurns(): Promise<BurnTransaction[]>
getBurnEvents(): Promise<BurnEvent[]>
getAnalytics(timeframe: Timeframe): Promise<BurnAnalytics>
getWalletBalance(address: string): Promise<WalletBalance>
submitBurn(address: string, amount: number): Promise<BurnReceipt>
}No contract is configured yet, so the pre-launch source answers with the genesis supply and nothing else. It invents no burns and no history — every burn figure on the site stays empty until there is a chain to read.
Burning is irreversible. A burn submitted by mistake cannot be refunded, rolled back, or compensated, and the protocol has no mechanism to make anyone whole.
Supply reduction is not a guarantee of price, value, or return. ZYNT makes a mechanical claim about token supply and nothing else. Nothing on this site is financial advice.