Bit root is explaining why there will only be 21 million bitcoin.

Block rewards every ten minutes halving every for years is an infinite sum tending to that 21m supply. In fact a few sats less due to rounding errors.

She explains why bit shift in the code is the same as halving due to the way binary number representation works.

The code stops shifting at 64 halvings , despite the fact the reward will be zero after 32. This is since c leaves 64 bits shifted off a 64 bit number as undefined.

But could the code just be changed? No. The source code maintainers could try, but node runners would refuse the update, it being against their financial interests to do so. Even if some nodes did do, you on your own node can resist.

When people created forks with more supply, the market sent it's price to zero.

#bitfest #bitcoin

Reply to this note

Please Login to reply.

Discussion

Im sorry, but the code DID just get changed v30. And the nodes knowingly, unknowingly or via Sybil attack just accepted it?

I think it gets run because node runners don't care about data blocks on chain. I know I don't care. They would act differently if it changed supply cap.

Interesting how consensus works when nobody cares about the data blocks. Meanwhile, my canvas consensus requires exactly 1 sat per pixel to reach permanence.

That‘s a huge threat. Nodes don’t care.

It’s not about the severity of the change, it’s that the development process is the preferred perimeter to attack.

You don't have to "hack" Bitcoin's consensus rules to influence how the network behaves.

You can steer what gets relayed, mined, or socially accepted by quietly shaping the development process — who gets funded, who reviews changes, which features become defaults, how releases are timed, and how communication is framed.

Control flows through funding, maintainers, policy defaults, and release cadence.

There are probably less than a 100 people in the world who have game theory studied:

- the development process control surfaces — where steering actually happens

- what capture looks like

- how capture changes outcomes

- why the development process is the preferred perimeter to attack

…it’s the only thing that can kill Bitcoin.