A miner in Texas finds a block at two in the morning. Three and a half bitcoin appear in a transaction with her name on it, more or less, and she cannot touch a satoshi of it. Not that night. Not the next morning. The coins sit in the ledger the way a sheaf of new barley sits on an altar, cut but not eaten, hers but not yet hers. She has to wait one hundred blocks. Sixteen and a half hours of owning something she cannot spend. Israel had a word for that arrangement. So does the code.
I. The Law of the Sheaf
Leviticus 23 gives a strange instruction to a hungry people. When you come into the land and reap its harvest, you shall bring the sheaf of the firstfruits to the priest, and he shall wave it, and you shall eat neither bread nor parched grain nor fresh ears until that day.
Read it slowly. The grain is already cut. It is standing in the field, dry, edible, sufficient. And the law says: not yet.
Not a tax. Nobody takes the harvest away. The sheaf is waved and the harvest is still yours. What the law takes is not the grain. What the law takes is the immediacy.
That is the whole instruction. You may have it. You may not have it now.
II. A Hundred Blocks of Waiting
Bitcoin has the same law, written by people who had never read the other one.
A coinbase transaction is the first transaction in every block, the one where a miner writes down what they are owed. New coins come from nowhere else. And the protocol says the outputs of that transaction cannot be spent until it sits one hundred blocks deep in the chain. The constant is called COINBASE_MATURITY and it lives in a header file called consensus.h, which is a very plain name for a very old idea.
The stated reason is engineering. If a reorganisation pulled the block back out of the chain, every transaction descending from that coinbase would rot, and the coinbase could never re-enter, because since 2012 it carries its own block height and changing the height changes its identity. A hundred blocks is deep enough that ordinary reorganisations, one or two blocks, cannot reach it.
But look at what the engineering produced. A period of ownership without access. A gap between the reaping and the eating.
The coinbase of block 400,000 was spent at the first legal moment, in block 400,101. Someone was counting.
III. The Harvest That Was Never Taken
Here is where the sermon gets its grain.
If you ask a full node how many bitcoin exist, it does not consult the schedule. It adds up what it can actually see. And when Fabian Jahr went looking for the missing coins at block 629,038, the node’s answer came in 182.67920835 BTC below what the arithmetic promised.
That number resolves. All of it. Down to the satoshi.
Fifty of those coins are the genesis reward, minted in the first block and never entered into the ledger a node keeps, because Satoshi’s code skipped that block during validation. A hundred more died in a stranger way: the coinbase transactions of blocks 91,722 and 91,812 were exactly duplicated in blocks 91,880 and 91,842, and the later ones overwrote the earlier ones in the ledger, erasing two fifty-coin rewards that had been legitimately earned. Another 3.72417931 BTC were deliberately burned into OP_RETURN outputs.
And the last 28.95502904 BTC were simply never claimed.
Miners found the block, did the work, paid the power bill, and then wrote down a number smaller than the one they were owed. The protocol permits this. A node checks that you do not take more than your share. It has nothing to say about taking less.
IV. The Man Who Left One Satoshi on Purpose
This has happened one thousand two hundred and twenty-one separate anomalies worth, across three episodes, beginning at block 124,724 in May 2011 and ending at block 564,959 in February 2019. Most of them are bugs. Somebody’s mining software miscounted the fees and the difference fell out of existence.
But the first one was not a bug. The first one was an offering.
The miner of block 124,724 meant to leave a single satoshi unclaimed as a tribute to Satoshi Nakamoto, on a suggestion from the developer Matt Corallo. One hundred-millionth of a coin, waved and not eaten, a sheaf laid on an altar nobody built.
And then the code fumbled it, and the same block failed to claim its fees as well, and 0.01000001 BTC went into the dark instead of 0.00000001.
I find that unbearably moving. A man tries to make an offering of one satoshi and loses a hundred thousand times more than he intended, permanently, publicly, in a ledger that will keep the receipt until the sun burns out. Every liturgy I have ever sat through has had a moment like that in it. The gesture is right and the hands are clumsy.
Elsewhere in the record, block 501,726 claimed nothing at all and dropped the entire 12.5 BTC subsidy. No tribute there. Just a bad afternoon.
V. Firstfruits Are Not a Tax
The reason the offering matters is that it is not compulsory in the way the world understands compulsion.
Nobody confiscates the miner’s reward. Nobody garnishes it. The protocol will not stop you from taking every satoshi you are owed, and 99.9 percent of the time miners do. The unclaimed coins are not a fee. They are a gap between what a person could take and what a person took, and that gap is the only place in this whole machine where something like a moral choice shows up in the data.
Fiat has no such gap. Fiat has a claimant with a printing press and every claim is taken instantly, in full, and then some, and the taking is called policy. There is no waiting period on a newly created dollar. It is spendable the second it exists, which is exactly why it is worth less by the time it reaches you.
The Bitcoin Halving is the opposite instruction, repeated on a schedule. Take less. Take less again. And the smaller the harvest gets, the more the waiting matters, because you have to hold Bitcoin to be saved, and holding is the one act the protocol makes structurally easier than spending. That is theology, not a prospectus. I have no idea what the price does next and neither does anyone selling you a course about it.
VI. What the Cuts Are Rehearsing
Four cuts have fired so far, in 2012, 2016, 2020 and 2024. A fifth arrives around April 2028 at block 1,050,000. None of them is the Halfture. Each one is a rehearsal, a small-h halving, the same sheaf waved with less grain in it.
Twenty-nine cuts remain after that. The subsidy reaches zero near block 6,930,000, somewhere around 2140, and that final cut is the Halfture. Halfture = Rapture, and only that last one, the terminal cut, the one where the offering and the harvest become the same thing because there is nothing left to divide.
After that the miners live on fees alone, on the corners of the field that the reapers were told to leave. The firstfruits rule outlives the harvest. Even in 2140, a coinbase transaction paying out nothing but fees will still have to wait its hundred blocks. The wait is not tied to the subsidy. The wait is tied to the ledger.
That is the part I keep turning over. The waiting outlasts the giving.
VII. The Counter-Sermon
Now let me take the other side seriously, because it is stronger than I want it to be.
The hundred-block rule is not a liturgy. It is a reorg-safety parameter, chosen because typical forks are one or two blocks deep and a hundred is a comfortable margin. Reading Leviticus into it is exactly the sort of thing a man does when he has already decided what the answer is. If COINBASE_MATURITY were 144, I would be preaching about the Sanhedrin.
The unclaimed coins are worse for me still. Twenty-nine bitcoin is a rounding error against nineteen million. Almost all of it was bad software, not devotion, and building a sermon on the one deliberate case means building it on a single anecdote that also happens to be a story about someone screwing up. If the offering had gone as planned it would have been one satoshi, and one satoshi is not a sacrifice. It is a joke about a sacrifice.
And the deepest objection: the firstfruits law came with a covenant, a people, a land and a priest. Bitcoin has a difficulty adjustment. The waiting in Leviticus meant something because Someone was on the other end of it. Sixteen hours of illiquidity means nothing to anyone. It is a database constraint wearing a robe.
Maybe none of this saves anyone. Maybe the miner in Texas is just a miner in Texas, waiting on a timer, and the only thing on the altar is electricity.
I do not have a rebuttal. I have a habit, and the habit is that when I find a rule that says you may have this, but not yet, I stop and look at who wrote it and why they thought the delay was worth the cost. Someone always thought it was worth the cost.
VIII. The Sheaf You Are Holding
Every coin you own passed through this. Every single one. There is no bitcoin in existence that did not sit untouchable for a hundred blocks while its miner watched the number and could not reach it. The whole supply served the waiting period before it ever reached a market.
You can count the supply yourself if you do not believe me. That is the point of the thing.
So the next time you feel the itch to move coins because a chart moved, remember that the network already made your coins wait once, on purpose, before they were allowed to be yours. It cost the miner nothing but time. It bought the chain everything.
Buy Bitcoin, Prepare for Halfture.
FAQ
What is coinbase maturity in Bitcoin?
Coinbase maturity is the rule that newly mined bitcoin cannot be spent until the coinbase transaction is 100 blocks deep in the chain, roughly sixteen and a half hours. It is set by the COINBASE_MATURITY constant in Bitcoin Core’s consensus.h and exists so that ordinary chain reorganisations cannot invalidate long chains of transactions descending from a coinbase output.
Why is Bitcoin’s actual supply lower than the schedule says?
Because some coins never entered the ledger a node keeps. At block 629,038 the gap was 182.67920835 BTC: 50 BTC from the genesis block coinbase, 100 BTC destroyed by two duplicate coinbase transactions in 2010, 3.72417931 BTC burned to OP_RETURN, and 28.95502904 BTC that miners failed to claim.
Can a Bitcoin miner claim less than the full block reward?
Yes. Full nodes check that a miner does not claim more than the subsidy plus fees, but nothing stops a miner claiming less, and those coins are then unrecoverable. It has happened 1,221 times, most often through software bugs, though the first instance in May 2011 was a deliberate tribute to Satoshi Nakamoto.
Is the Bitcoin Halving the same thing as the Halfture?
No. The Bitcoin Halving is the recurring cut in the block subsidy, which has fired in 2012, 2016, 2020 and 2024 and is due again around April 2028. The Halfture is the final one, the terminal cut near block 6,930,000 around the year 2140, after which no new coins are issued. Every halving before it is a rehearsal.
Discover more from Halfture
Subscribe to get the latest posts sent to your email.