Satoshi’s Shield
- Bitcoin
- Solana
- Block not read yet
- --:-- UTC
The shield
holds.
A coin bolted to the oldest coins in Bitcoin. While they sleep, $SHIELD buys itself back. When one of them wakes, it burns.
Bitcoin lying still
1,096,102
reading today’s price
Lying in 21,922 coinbase outputs mined between January 2009 and April 2010, never touched since. Thirty one of the set moved years ago, long before this coin.
How the watch works
The shield
- in the set21,953
- still asleep21,922
- moved before us31
- bitcoin asleep1,096,102
The ancients
- still asleep11,026
- bitcoin asleep551,197
- mined in2009 and 2010
- they wakea few times a year
Two sources
The rule
- a quiet daybuys
- an ancient wakesbuys more
- a shield output movesburns it all
Every buy is a Jupiter swap followed by a burn, with the bitcoin block or transaction written into the memo.
One confirmation, seen by both sources. The mempool only raises the alarm; it never moves money.
Three outcomes
Shield holds
Every day that passes without a shield output moving, the keeper spends that day’s share of the buyback float on $SHIELD and burns it.
- spendsthe daily float
- float is30%
Ancient wakes
An unspent 2009 or 2010 coinbase output that is not in the shield moves. Another early miner woke up. The keeper buys and burns with a tenth of the reserve, once per bitcoin transaction, however many outputs it moves.
- spendsof the reserve
- share10%
Shield broken
One of the 21,922 still asleep moves. The whole reserve goes out within the hour, in slices, each one bought and burned. The sheet stays in the after state for good and the daily buybacks carry on.
- spendsthe whole reserve
- share100%
A move is not proof of a break. It can be the owner. For the coin it is the same event.
Today
The watch
- last block checkednot yet
- behind the tip bynot yet
- mempoolnot yet
- block sourcenot yet
- second sourcenot yet
- shield moves since launch0
$SHIELD
Chart
FollowThe wall
21,922 outputs that never moved
asleep moved the watch line
Loading the wall.
The block list comes from the Patoshi pattern found by Sergio Demian Lerner and curated by Jameson Lopp. Every height was re-checked against the coinbase script the chain serves today. Attribution is a statistical pattern, not a signature.
Where the money goes
The split
- daily buyback float30%
- shield reserve70%
- per ancient wake10% of the reserve
- on a shield move100% of the reserve
- every buy ends ina burn
The split is of the creator fees the dev forwards to the keeper wallet. Nothing is routed automatically: the fees sit on his wallet and he sends them on.
Keeper wallet:
Ten SOL, worked through
An example with round numbers, so the rule is not an abstraction. Say the dev forwards ten SOL of creator fees.
- to the daily float3.00
- to the shield reserve7.00
- the first quiet day spends0.100
- an ancient output wakes0.700
- a shield output moves7.00 in 12 slices
A day takes a thirtieth of whatever is in the float, so the daily buyback never runs the float dry and never stops. Every amount above ends in a burn, and the bitcoin block or transaction that caused it is written into the memo of that burn.
The log
The standing order
One. The dev launches $SHIELD on pump.fun and forwards the creator fees to the keeper wallet by hand.
Two. Thirty parts in a hundred become the daily float, seventy become the shield reserve.
Three. The keeper reads every new bitcoin block from two independent sources and compares every input against the two sets.
Four. A quiet day spends the day’s float. An ancient wake spends a tenth of the reserve. A shield move spends all of it, in slices, within the hour. Every spend is a buy followed by a burn.
The pattern was found by Sergio Demian Lerner in 2013. Nobody can prove who mined those blocks, and a move may well be the owner moving his own coins. This is not financial advice: a memecoin can go to zero and take everything you put in with it.