Somewhere on Solana there is an address that bunk keeps paying and that no one can spend from, because no one has ever known its key. It was made by hashing, not by choosing a secret. The only way SOL ever leaves it is for someone to recover a private key from a public one. If that happens, the curve under every Solana wallet is broken, and this address is how bunk finds out.
The canary
address
status
balance
paid in by bunk
waiting to be sent
deposits
last deposit
counter
hash
recomputed here
spent by
How the address was made
y = SHA-256( "bunk/canary/v1" ‖ mint ‖ counter )
try y as a compressed ed25519 point
if it is a point: multiply by 8, encode, done
if it is not: counter + 1, try again
mint
counter
address
Attempts
counter
hash
result
Flow
Where each claim goes. The dashed line is the tripwire: it carries nothing until the day the canary is spent.
Deposits
time
leaf
amount
running total
check
What changes if it trips
rule
nominal
bunker mode
holder share
40% to 60%, set by the last digest
0%
bunk share
35% to 55%
0%
canary share
5%
0%
each claim
paid, sealed and fed to the canary
bought and burned in full
sealed bunks
opened one at a time on drawdowns
opened one after another and burned in full
amounts owed to holders
paid once they reach 0.001 SOL
burned
way back
none needed
none. the mode is permanent
What survives a break
thing
before a break
after a break
SOL in any wallet, including the surface wallet
safe
exposed
SOL sealed in bunks
safe
exposed, which is why each is capped and all are drained on a trip
SOL already paid to holders
theirs
exposed like any wallet
the canary balance
safe
taken by whoever breaks the curve first
tokens already burned
gone
gone
the record of what bunk did
wallet signature and hash signature
hash signature and the anchored root
bunk's hash keys
never derived from a curve
unaffected
The canary is small on purpose and it grows with every action. It is a standing reward for the first proof that the curve has fallen, paid automatically, to whoever can show it. A trip is confirmed only when the balance has dropped below what bunk paid in and a transaction signed by the canary address itself is found on chain. bunk then records that transaction's hash with its next leaf and never leaves bunker mode.
