Every time bunk does something it writes down exactly what happened in 229 bytes, hashes it, and signs the hash twice: once with the surface wallet, the ordinary Solana way, and once with the next unused leaf of its hash tree. The hash goes on chain in a memo. The hash signature is stored here and checked by your browser. Each record also carries the hash of the record before it, so the whole history is one chain that cannot be reordered or trimmed without breaking a signature.
Totals
actions sealed
fees actions
bunks opened
rotations
SOL claimed
SOL paid to holders
payouts sent
SOL sealed in bunks all time
SOL sealed now
SOL bought
tokens burned
burned share of 1B
SOL to canary
signatures valid
All actions
tree
leaf
kind
time
volume seen
claimed
paid
wallets
sealed
canary
opened
bought
burned
stores after
price
digest
check
c
s
o
b
u
m
Message bytes of the latest action
offset
length
field
decoded value
0
1
kind
1
4
gen
5
4
leaf
9
32
mint
41
32
previous digest
73
8
claimed
81
8
paid to holders
89
4
wallets paid
93
8
to stores
101
8
to canary
109
8
bought
117
8
burned
125
8
stores after
133
8
supply after
141
8
price_e12
149
8
volume seen
157
4
bunk opened
161
4
bunk created
165
32
transactions hash
197
32
payload
Record chain
Each record names the hash of the one before it. Change any old record and every later signature stops verifying.
How each digest sets the next action
leaf
digest bytes 0 to 2
holder share
bunk share
action threshold
open trigger
Nobody picks these numbers. The first three bytes of an action's hash set the split, the volume threshold and the open trigger for the action after it. They cannot be known until the action has landed.
