Pick a date. Prove your coins are older.
An event is a block height that matters: where a hack's coins first arrived, a tax cutoff, the start of a bug. A Vintage proof says one thing about it: every coin in this transaction was already in the shielded pool before that block.
Three steps, one block height.
An event gets a block height H: the first block where it matters. The Bitget hack's coins first entered the shielded pool at block 3,501,240.
You send with an anchor from before H. Coins that arrived after H aren't in that snapshot, so your wallet can't include them, and consensus checks it.
The txid and H are all a checker needs: our verifier, the API, or vintage verify on their own machine.
Ironwood so far.
Not to scale. Coins untouched since before an event clear it, and every later event, with one proof.
The signed list of dates.
The registry labels block heights, with the transactions and public sources behind each. It names no people and no addresses, and nothing in it marks a coin as bad. You can always check against a height of your own.
| Type | Event | Block | ID | |
|---|---|---|---|---|
| hack | Bitget hot-wallet exploit: first shielding into Ironwood | 3,501,240 | bitget-2026-09 | Check a deposit |
| custom | Vintage demo: simulated event (not a real hack) | 3,525,709 | vintage-demo-2026-10 | Check a deposit |
ed25519-signed · public key d36b99d8…4376
New events are added only with primary-source transaction ids. Propose one on GitHub.
One proof, any dated event.
Exploit inflows
- When
- Stolen coins first enter the shielded pool.
- You prove
- Your deposit can't contain them.
- Who asks
- Exchanges, bridges, swap services.
Bought before a date
- When
- A legal cutoff. A German draft, not yet law, would keep the one-year exemption only for coins bought before 2027.
- You prove
- You've held these exact coins since before the cutoff: a coin can't change hands without being spent.
- Who asks
- You, your accountant, a platform.
Pre-bug coins
- When
- A bug that could create or move coins becomes possible.
- You prove
- Your coins are older than the window, so they weren't made through it.
- Who asks
- Exchanges, auditors.
Held a year
- When
- One year before you sell.
- You prove
- The exact coins you sell are over a year old. Ironwood launched in July 2026, so full-year proofs start in July 2027.
- Who asks
- Tax rules with a holding period.
Your own date
- When
- Any block you name: before a contract, a job, a dispute.
- You prove
- Your coins existed before it.
- Who asks
- Whoever you're dealing with. Use Custom height in the verifier.
Airdrops and votes
- When
- A balance snapshot for an airdrop or a vote.
- You prove
- It works, but snapshots need "unspent at the snapshot", which ZAIR and coinholder voting prove directly. Use them.