Bitcoin Halving and Laban: Wages Changed Ten Times

A man stands in a field at night, counting sheep that are not his. He has been counting them for twenty years. He knows every ewe by her limp and every ram by his temper, and he knows something else, too, something he has told no one: the terms of his pay have changed ten times since he arrived. This is a sermon about the Bitcoin Halving and Laban, the uncle who kept moving the wage, and about the one schedule of pay in the world that was written down before anybody started work.

I. Twenty Years in Haran

Jacob came to Haran with nothing. A staff. A stolen blessing. A brother somewhere behind him who wanted him dead.

His uncle Laban took him in, and after a month of free labor asked the honest question. What shall thy wages be?

Jacob named his price. Seven years for Rachel, the younger daughter. The years went by “but a few days,” the text says, for the love he had to her.

Then came the wedding night, and in the morning it was Leah.

That was the first change. Not a refusal, which would at least have been honest. A substitution. The wage was paid, technically, in a currency Jacob had not agreed to accept.

So he served seven more.

II. The Bitcoin Halving and Laban

Read Genesis 31 slowly and you notice Jacob is not angry about the work. He is angry about the terms.

“Your father hath deceived me, and changed my wages ten times.” He says it to his wives in the field, out of earshot. He says it again to Laban’s face at Gilead, twenty years in, with the whole camp listening.

If Laban said the speckled shall be thy wages, then the flock bore speckled. If Laban said the ringstraked, then the flock bore ringstraked. And every time the flock favored Jacob, Laban rewrote the contract.

This is the oldest labor dispute in the canon, and it is not really about sheep. It is about who holds the pen.

The Bitcoin Halving is the answer to that question, stated once in code. Nobody holds the pen. The wage was set before the first block was mined, and every change to it was announced in advance, on a date anyone could calculate, down to the block.

III. Ten Times

Laban is not a villain in the cartoon sense. He is a manager. He is a reasonable man with a household to run and a flock to protect, and he responds to circumstances.

That is exactly the problem.

Every monetary authority on earth is Laban. Not because its people are wicked, but because its wage is discretionary by design. The committee meets. The circumstances are weighed. The terms change. Your savings were speckled last year and ringstraked this year, and the notice arrives after the lambing.

Nobody at the committee calls it a change of wages. They call it policy. Jacob had a word for it too, and he used it in front of witnesses.

Deceived.

IV. A Wage Written Before the Work

Here is what a Bitcoin miner is paid. A fixed subsidy per block, currently 3.125 bitcoin since the cut at block 840,000, plus whatever fees the block’s transactions carry.

The subsidy is not negotiated. It is halved every 210,000 blocks, roughly every four years, and it has been halved exactly on schedule four times now. The next halving takes it to 1.5625. Every miner who plugs in a machine today knows what the wage will be in 2028, in 2032, and in the last cut after that.

And almost the entire wage is still the subsidy. In the week of April 13, 2026, transaction fees made up only 0.58 percent of total block rewards, about 16 bitcoin out of roughly 3,166, by Hashrate Index’s count. Hashprice sat at $33.25 per petahash per day.

Sit with that number. Ninety-nine cents of every miner dollar that week came from a schedule written in 2009. The fees, the waters I wrote about at the pool by the sheep gate, are barely stirring yet.

Which means the miner lives the way Jacob lived. Paid mostly in a wage he did not choose, from a master who will cut it on a known date. The difference is that this master cannot lie about the date.

Laban changed the wage whenever it suited him. The protocol changes it only when it said it would.

V. The Laboratory Where the Wages Run Out

There is a quiet place in the Bitcoin source code where the whole story is compressed into an afternoon.

It is called regtest, the regression-test network developers use to try things without real money. In its parameters, the halving interval is not 210,000 blocks. It is 150. Every other network, main and test and signet alike, carries 210,000. Regtest carries 150.

Someone noticed in 2016 and opened an issue asking why regtest did not match. The issue was closed. The number is still 150.

Do the arithmetic. Fifty bitcoin, halved every 150 blocks, reaches a single satoshi and then zero after thirty-three cuts. That is 4,950 blocks. On mainnet the same thirty-three cuts take 6,930,000 blocks and roughly until the year 2140.

So on a developer’s laptop, the entire schedule can be walked to its end on demand. Every halving. The last one too.

I find that unbearably moving. The cuts we live through every four years are rehearsals of the Halfture, and here is a rehearsal of the rehearsals, a chapel where the whole liturgy is read aloud in one sitting so that nobody can say they were surprised by how it ends. The Halfture itself is the terminal cut on the real chain, still more than a century out, the night the subsidy rounds to nothing and the wage becomes only what the fees can bear. Halfture = Rapture, because that is the night the schedule finishes keeping its word.

Laban never let anyone read the end of his contract. Bitcoin puts the end in a test file.

VI. The Counter-Sermon

A fair reader will object, and should.

Jacob was no saint either. He peeled the rods, bred the strong ewes to his own advantage, and left Haran rich. The story does not end with an honest man and a crooked one. It ends with two schemers making a treaty over a heap of stones.

And the fixed wage is not obviously a mercy. Laban’s discretion was, at least sometimes, a response to real drought, real disease, real need. A schedule that cannot respond to anything will cut the miner’s pay in a bad year exactly as it would in a good one. When the subsidy falls and fees stay thin, the machines that cannot cover their power bills go dark, and the security of the whole network rests on a fee market that barely exists today.

The skeptic will also say that I am preaching. That a halving interval in a test file is a convenience for developers and not a chapel. That calling a monetary schedule salvation is a category error with a good soundtrack.

I hear all of it. I still say what the site says: you have to hold Bitcoin to be saved. But I say it as theology, not as a prospectus. It is a claim about what can be trusted to keep its terms, not a promise about what any coin will be worth, and nothing on this page is financial advice.

Maybe the skeptic is right and none of this saves anybody. Even then, the schedule is still the only wage I know of that was published in full before the work began.

VII. Go Home With What Is Yours

When Jacob finally left, he left at night, with his wives and his children and his flocks, and Laban chased him seven days to the hills of Gilead.

The confrontation there is almost comic. Laban searches the tents for his stolen household gods and does not find them. Jacob delivers his twenty-year grievance in one breath. And then the two men pile stones into a heap and name it, and agree that neither will cross it to do the other harm.

That heap is the first boundary in the story that Laban cannot move. It is also the last we hear of him.

Some of us are still in Haran. We are paid in terms that change after the lambing, and we have learned to call it policy. There is another wage in the world now, a stranger one, that halves on a date you can calculate and ends on a night you will not see.

Read the contract. All of it. The end is in the test file.

Amen.

FAQ

What does Laban have to do with the Bitcoin Halving?

In Genesis 31, Jacob accuses his uncle Laban of changing his wages ten times over twenty years. The Bitcoin Halving is the opposite arrangement: the miner’s wage, the block subsidy, is cut on a fixed schedule every 210,000 blocks that was published before the first block and cannot be rewritten at anyone’s discretion.

How much of a Bitcoin miner’s pay comes from the block subsidy?

Almost all of it for now. Hashrate Index reported that in the week of April 13, 2026, transaction fees were only about 0.58 percent of total block rewards, meaning the fixed subsidy of 3.125 bitcoin per block made up nearly everything miners earned.

What is the halving interval on Bitcoin’s regtest network?

Bitcoin Core’s regression-test network halves the subsidy every 150 blocks instead of every 210,000, so developers can run through the entire issuance schedule, down to a zero subsidy after 4,950 blocks, on a single machine.

When is the last Bitcoin Halving?

The thirty-third and final cut, which this site calls the Halfture, happens at block 6,930,000, expected around the year 2140. At that height the subsidy rounds to zero and miners are paid in transaction fees alone.