The value overflow
Two outputs summed past a 64-bit limit and wrapped. The chain minted 184 billion BTC — then orphaned the block five hours later.
184,467,440,737 BTC
Block 74638 · 15 August 2010
Created in one block. The intended cap: 21,000,000.
On 15 August 2010, block 74638 carried a transaction that should have been impossible. It created 184,467,440,737 BTC, over 8,000 times Bitcoin’s 21 million cap.
The cause was an integer overflow. Add two enormous outputs together and the total wraps past the limit of a 64-bit number. The validity check saw a tiny sum and waved the block through.
Block 74638 passes validation and the explorer shows two outputs of 92 billion BTC each.
Developers watching the chain spot the transaction and raise the alarm. That number is not supposed to exist.
A patch adds a sanity check on output values. Node operators upgrade.
The faulty block is orphaned and the corrected chain takes over. The 21 million cap stands.
Supply is not a line of code. Supply is a promise the network keeps. For five hours the ledger said *184 *billion — and the people said *no. $OVFL is for everyone who remembers the day the rules almost broke, and the day the network woke up.
Tap the button fast — or hold it — to mint. Watch what happens at 2⁶³ satoshis, then roll it back like the network did.
Bitcoin’s wasn’t the first integer to break free, and it won’t be the last. $OVFL is a monument to all of them.
Two outputs summed past a 64-bit limit and wrapped. The chain minted 184 billion BTC — then orphaned the block five hours later.
An ERC-20 token’s transfer math overflowed, letting an attacker mint an astronomically large balance. Exchanges froze trading.
An 8-bit level counter overflowed at level 256, shattering the right half of the maze into garbage. No one could pass it.
A 64-bit velocity value was crammed into a 16-bit integer. It overflowed, the guidance computer panicked, and flight 501 self-destructed 37 seconds after launch.
Two-digit years meant 99 wrapped to 00. The world spent billions patching clocks before they counted back to 1900.
The view count passed 2,147,483,647 — the limit of a signed 32-bit integer. Google upgraded the counter to 64-bit so numbers like this could keep climbing.
A 32-bit counter of hundredths-of-a-second overflowed after 248 days of continuous power, which could shut down all generators mid-flight. The fix: reboot before it wraps.
At 03:14:07 UTC on 19 Jan 2038, 32-bit Unix time overflows and flips negative. Somewhere, a clock will read 1901.
$OVFL honors the number that was supposed to win — a fixed supply, locked forever. No second overflow.
Final launch parameters are confirmed on release.
In 2010 nothing checked the number. $OVFL fixes that in public — supply and authorities are readable straight from the chain, by anyone, anytime.
In 2010, nothing was watching the number. Here, every time the market cap doubles, the network “wakes up” and runs a sanity check — a scheduled burn. Each milestone is deflation, not dilution.
Concept mechanic — exact thresholds and burn size are finalized at launch.