Hall of ashes
Leaderboard.
Every legendary certificate is a monument. Every certificate earns. Every certificate will one day walk into Zcash's shielded pool.
Certificates
—
ETH distributed
—
$SIGIL burned
—
Next flush
10 min
Dividends. Every trade on the SIGIL launchpad pays a 1% fee. 100% of that fee flows to the Dividend Router — a smart contract, not a wallet. Every 10 minutes the router splits accumulated ETH: 50% buys back $SIGIL and burns it into a permanent protocol-owned certificate, and 50% is deposited as an ETH dividend to every certificate holder pro-rata. The protocol's own certificates earn too, and their dividend flows back into the next flush — a flywheel that compounds itself.
Top burners
Loading…
The endgame
Every certificate can walk into Zcash.
When Zcash mainnet activates OrchardZSA (ZIP-226 + ZIP-227), every SIGIL certificate and every user-launched token migrates 1:1 into a real shielded custom asset.
What's already on-chain
Every certificate stores a real ZIP-227 IssueBundle — canonical asset base (BLAKE2b), issuer (BIP-340 x-only), and a Schnorr signature over a finalized bundle. Not a SHA-256 placeholder. Not a mock. The exact bytes ZSA mainnet will accept.
Why nobody can rug the migration
Because the signature is already signed and immutable. When ZSA ships, anyone with public on-chain data can broadcast the migration tx. Our team can vanish and the migration still happens.
What triggers the migration
A single mainnet activation date — announced by the Zcash Foundation once NU8 or later carries the transaction format. On that block, a permissionless migrator script sweeps every certificate → real shielded asset.
What holders need to do
Register a Zcash z-address ahead of time. That's it. No re-signing, no re-approving, no gas on Zcash. The certificate you already own becomes a shielded custom asset with the same amount, in your Zcash wallet.
Read the algorithm: MIGRATION.md · Reference migrator stub: migrator/