BNB ChainCertificate of Destruction
The quantity below was irreversibly destroyed on BNB Chain. This inscription records it on Zcash and cannot be reissued.
Burn STAMP on BNB Chain. Keep a certificate on Zcash stamped with exactly what you destroyed.
One way. No escrow, no custody, nobody holding your funds. The tokens stop existing; the certificate is the only thing left.
Real, on Zcash mainnet. Inscription b2cbded5c37c2cca8918a077a73e2ca349005efba046cee0866b34dd879c5acb
Burn yoursIssue a certificate
REACT_APP_STAMP_TOKEN (the STAMP BEP-20 address on BNB Smart Chain) is filled in frontend/.env. Everything else — wallet, network, Zcash certificate — works.This cannot be undone, reversed or refunded. Your tokens stop existing the moment you sign.
Launch a coin
Create a token directly on the flap.sh bonding curve on BNB Smart Chain — no redirect. Your wallet signs the launch; the token trades on flap.sh immediately.
The token address is mined client-side to end in 8888 (flap.sh vanity rule), then created via the Portal contract. Gas + any initial buy are paid from your wallet.
Trending
Launch a coinCoins launched here trade on the flap.sh bonding curve. Live rows show real price and curve progress read from the Portal contract — buy in one click.
Leaderboard
1,500,000 tokens destroyed across 1 certificate. Live from this deployment. Read from BNB Smart Chain; a refused burn still destroyed its tokens.
| When | Coin | Destroyed | Burner | Certificate to | |
|---|---|---|---|---|---|
| 11d ago | $STAMP | 1,500,000 | 0x26aa…GtYA | t1P2GcxGhzeM5tPk3r3JsGh1tEVArD4C2fB | tx |
Why a stamp, and not a token
Zcash cannot hold assets yet
Shielded assets are specified — ZIP 226 and ZIP 227 — but they are drafts. They are not on mainnet, and the next network upgrade does not include the transaction format they need.
Zcash can hold inscriptions today
An inscription needs no new consensus rules. It is an ordinary transparent transaction carrying data, which Zcash has accepted since the beginning. Around 113,000 already exist on mainnet.
So the stamp is the asset
Not a placeholder image. A record of one specific destruction, written to the chain the asset will eventually live on. Each stamp maps to exactly one burn and can be claimed once.
Uniqueness is doing real work
A balance cannot say that this destruction happened, on this date, for this amount, to this person. Only a unique record can. When shielded assets activate, each stamp converts to the amount cut into it.
Check it yourself
A certificate counts only if it names a real burn that has not already been claimed, and is delivered to the address that burner chose. Anyone can rebuild the whole set from public data on both chains and get the same answer we do.
A certificate on Zcash mainnet
1,500,000 destroyed on BNB Chain, recorded on Zcash, delivered to the address that burned it.
A forgery the chain accepted
Signed with our own key, claiming ten times the amount, citing a burn that never happened. Zcash accepted the inscription. The rule does not: it names no real burn, so it is not a certificate and never counts.