Bitcoin Halving: The Lamp That Must Not Go Out

There is a lamp in the book of Exodus that is not allowed to die. Not a miraculous lamp. A maintained one. Someone has to walk into the dark tent every evening, trim the wick down to clean fiber, top up the oil, and leave before the flame is settled. The text does not say the lamp will burn forever. It says a man will keep showing up. That is a different promise, and a harder one. I have been thinking about that tent all week, because the thing I actually believe about Bitcoin is not that it is magic. It is that it has never stopped.

I. The Command to Keep It Burning

Exodus 27 gives an instruction and then a duty. Bring clear oil of beaten olives. Kindle the lamps. Aaron and his sons shall tend them from evening until morning. The Hebrew word is tamid. Regularly. Continually. Without a gap.

Read it fast and it sounds like a promise of permanence. Read it slowly and it is a labor contract.

Nobody in that passage is told the fire is self-sustaining. They are told to be there.

Bitcoin started at 02:54:25 GMT on the third of January, 2009. Since that timestamp the network has produced blocks at roughly ten minute intervals through four continents, three market collapses, one national mining ban, and every obituary anyone has ever written for it. Not because it is enchanted. Because at any given second, somewhere, someone is tending it.

II. Trimming the Wick Is Not Putting It Out

Here is the part most sermons on Exodus 27 skip.

Rashi reads the instruction differently than you would expect. Aaron does not relight the lamp each night. He nurtures it. He trims the wick and adds the oil and waits until the flame rises on its own. The fire is continuous. The maintenance is periodic.

That is the Bitcoin Halving, exactly.

Every four years or so the protocol reaches in and cuts the fuel. Fifty became twenty five in 2012. Twenty five became 12.5 in 2016. Then 6.25 in 2020, 3.125 in 2024, and 1.5625 waiting in 2028. The subsidy is trimmed. The flame is not.

Each of those cuts is a rehearsal. A small-h halving. A hand in the tent.

The Halfture is the last trim, the one near block 6,930,000 where the subsidy rounds down to nothing at all and the wick is finally short enough that only fees keep the light. That one is the terminal event. The Halfture is the Rapture, and it is still more than a century out, which means every cut you have lived through was practice for a service none of us will attend.

III. The Two Nights the Lamp Went Out

Halfture is a site about scarcity, not about pretending.

The Bitcoin network has an uptime figure of about 99.98 percent since genesis, and there is a live tracker that counts the outages so nobody has to take a maximalist’s word for it. Two events. One in 2010, an overflow bug that ate eight hours and twenty seven minutes. One in 2013, worth about six hours and twenty minutes.

Two nights in seventeen years.

I want to sit inside the second one, because it is the more instructive night and because almost nobody tells it correctly.

IV. What Actually Happened in March 2013

Block 225,430 was not an attack. It was a perfectly valid block that happened to touch more transaction inputs than any block before it.

Bitcoin 0.8 had switched from Berkeley DB to LevelDB and handled it fine. Nodes running anything older were configured with too few Berkeley DB locks to process it, so they rejected the block outright. Nobody had chosen that limit as a rule. As the post-mortem Gavin Andresen wrote afterward puts it, the lock configuration had implicitly become a consensus rule, an inconsistent and unsafe one, because the lock count depended on the arrangement of a database file on each node’s own disk. The rule was not in the code. It was in the sediment.

The chain split. About sixty percent of hashpower sat on the new chain, which meant the split was not going to resolve itself. The stronger fork simply keeps winning.

So two men fixed it by hand.

BTCGuild and Slush downgraded their pools from 0.8 back to 0.7, deliberately, so that their hashpower would also reject the larger block and push the majority back onto the older chain. The post-mortem records that they did this despite sacrificing significant amounts of money. There is no protocol reward for that. There is no line in the whitepaper about it. Two operators looked at a burning building, walked in, and took a loss to keep the light on.

The full patch did not finish landing until the sixteenth of August that year, when block 252,451 was accepted and the unpatched nodes were finally forked off the network. Five months of tending.

That is the ner tamid. Not a fire that cannot go out. A fire that people refuse to let go out.

V. The Oil Is Beaten, Not Poured

The text is specific about the oil. Clear oil of beaten olives. Crushed by hand, first pressing, no sediment, more expensive than the oil you would use for anything else.

You could light the lamp with cheaper oil. It would smoke. It would leave residue on the wick. It would need more attention and give less light.

Proof of work is beaten oil. It is the most expensive way to secure a ledger and that expense is the whole product. The energy is not a byproduct of the security, it is the security, the same way the crushing is not a byproduct of the oil. Fiat is the cheap oil. It lights fine and it smokes, and after a few decades you notice the walls are black.

This is the point where I say the doctrine plainly, once, and then leave it alone: you have to hold Bitcoin to be saved. I mean that the way a liturgy means things, not the way a prospectus means things. It is theology. It is not advice, I am not your advisor, and anyone who quotes that line at you with a referral link attached has misread both the sentence and the tradition it borrows from.

Keep the flame. Do not sell the lampstand.

VI. Two Ways to Check Whether It Is Still Lit

The lamp in the tent had one advantage over most institutions: you could see it. Walk in, look, know.

Bitcoin gives you the same privilege in two forms. The first is the heartbeat of the difficulty adjustment, which retargets every 2,016 blocks and tells you whether the network is still breathing at the pace it promised. The second is that the count is public and anyone may run it, so the supply is not a claim on a press release but an audit you can perform on a laptop in an afternoon.

Most people never check either one.

That is fine. The lamp does not require every Israelite in the camp to inspect the wick. It requires that inspection be possible, and that the people who do inspect are not asking anyone’s permission.

VII. The Counter-Sermon

Now the honest part, and it is worse than you think.

The perpetual lamp was not perpetual.

The Talmud records in Yoma 39a that for forty years before the destruction of the Second Temple, the westernmost lamp went out every single night. The sign that could not fail, failed, nightly, for four decades, while the priests kept trimming it anyway. And then the building burned and the lampstand was carried to Rome and the whole apparatus of continual flame became a story we tell about a room that no longer exists.

Uptime is a low bar dressed as a high one. A network can produce blocks on schedule for a hundred years and still fail everyone who trusted it, if the fees price ordinary people out, if custody consolidates into four institutions, if the thing that survives is the ledger and not the point of the ledger. Liveness is not health. My own tradition of writing about this stuff loves the uptime number because it is the one metric that has never embarrassed us.

And the March 2013 story cuts both ways. Two pool operators coordinating in an IRC channel saved the chain. That is competence. It is not decentralization. If the answer to the next crisis is again “the right people happened to be online,” then what we have is a very good fire brigade, not a fire that cannot spread.

Someone will trim the wick until someone does not.

VIII. What to Do About It

Nothing dramatic.

Do not treat continuity as a promise made to you. Treat it as a chore that has so far been done. Then decide whether you are in the tent or in the camp.

If you are in the camp, that is a real answer. Most people are, and the lamp burns anyway.

If you are in the tent, the work is unglamorous and always has been. Run the node. Hold the keys yourself. Learn what a difficulty retarget actually is. Do not confuse the price of the oil with the light.

The next cut is a rehearsal. So is the one after that. Somewhere out past every reader of this sentence, the last one waits.

Trim the wick.

FAQ

Has the Bitcoin network ever gone down?

Twice. A value overflow bug in August 2010 caused roughly eight hours and twenty seven minutes of disruption, and a chain split in March 2013 caused roughly six hours and twenty minutes. Both were resolved by coordinated human intervention. Total uptime since the genesis block on 3 January 2009 sits around 99.98 percent.

What caused the March 2013 Bitcoin chain fork?

A valid block, number 225,430, touched more transaction inputs than any previous block. Nodes running versions before 0.8 were configured with too few Berkeley DB locks to process it and rejected it, splitting the chain. Two mining pools downgraded their software at their own expense to restore a single chain.

Does the Bitcoin Halving stop the network?

No. The halving reduces the block subsidy paid to miners; it does not pause block production. Every cut so far has been absorbed within a difficulty epoch or two. The subsidy is the fuel, not the flame.

Is the Halfture the same as the 2028 halving?

No. 2028 is another rehearsal. The Halfture is the final cut, near block 6,930,000, when the subsidy rounds to zero and miners are paid by fees alone. Every halving before it is practice for that one.