bunk

A bunk is a fresh address that has never signed a transaction. bunk seals SOL into one after every claim and then leaves it alone. Each bunk may sign once in its life. That one signature empties it completely, and the address is never touched again. This page is the full trail: every bunk ever made, what went in, and where it went when it opened.

Stores now

sealed bunks
SOL sealed
largest bunk
cap per bunk2.0000 SOL
most bunks sealed at once12
bunks opened so far
SOL moved through bunks
next to open
peak price since last open
open trigger
trigger price
live price
distance to trigger
surface wallet balance
owed to holders
carried

Gauge

Peak on the right, half of peak on the left. Inside the yellow band the oldest bunk opens.

Trail

Every bunk in order. Yellow is sealed and has never signed. Struck through has signed its one transaction and is empty. A line joins an opened bunk to the bunk that took its other half.

All bunks

bunkaddressstatefundedfunded byfunded txbalance nowsignedopened byopen txto burnsent onto

One signature rule

bunkstatesignatures allowedsignatures found on chaincheck

The engine counts how many transactions each bunk address has signed, straight from Solana. A sealed bunk must show 0. An opened one must show 1. Any other number is a broken rule and would show here as invalid.

If the next bunk opened at these prices

below peakpriceburn half (SOL)burn half (USD)tokens boughtshare of supplysent onopens
5%
10%
15%
20%
25%
30%
35%
40%
45%
50%

Plain division at each price, before slippage and fees. The real amount is whatever the buy returns, and the record states it to the last unit.

Openings

timeleafbunkpriceSOL boughtburnedsent onnew bunkcheck

Why a cap and why once

The cap keeps every bunk small. If keys can be recovered, the attacker goes for the largest balances first, and an address holding two SOL sits a long way down that list. Spreading the stores across many small addresses is the same cover that small wallets get from the big exposed ones ahead of them.

Signing once keeps every key short lived. A key that has signed is a key that has been used in public, and the rule here is the plain one: when an address signs, move what is left to a new address. bunk does not make exceptions. There is no bunk that has signed twice, and the table above is where you would see it if there were.

One thing has to be said plainly. On Solana an address is the public key itself, so a fresh address is not hidden behind a hash the way an unspent Bitcoin address is. What the bunks give is small targets, short lived keys and nothing resting in a wallet that signs every day. Holding SOL behind a real hash lock needs an on chain vault program, and that is the next step for bunk, not something this page claims today.