The whole Bitcoin development process is so broken that non-technical plebs with full-time jobs have to try to become technical to understand how badly they've been getting fucked by Bitcoin's developers.
The only way out is to at least define:
- what it is you're changing (freedom money, distributed, permissionless database, etc),
- what is changeable on layer 1 (if anything),
- in which cases are these things changeable.
The more you change the protocol for the worse, the less of an option not changing the protocol becomes because you have to change the changes.
It's kind of funny to see people comparing Bitcoin's L1 to TCP/IP. Have you seen the Releases tab of the default implementation on GitHub (
). These guys are shipping.
Development-Process Capture = Perimeter Control
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.
Most probably know this, but governments want to maintain monopoly on force + money issuance.
Fiat is the ultimate control layer -> no major government defects from this system.
So governments don't like Bitcoin (as MoE) very much.
If you expect for governments to come out and try to ban Bitcoin, don't because that's not how the system works.
Systems don't rely on bans; they use knobs — adjustable defaults, standards, and processes that subtly guide behavior.
The Bitcoin development process is a dense cluster of such knobs.
Open source ≠ immune
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
I'll just go over the last one because it is quite short.
Why the development process is the preferred perimeter to attack:
- Cheaper than legislation: Defaults and "safety" framing do the enforcement work.
- Plausible deniability: "We're just improving performance".
- Asymmetric impact: hits sovereign users hardest; institutional wrappers unaffected.
If you require people to be technical for them to be able to protect their savings, this project fails.
From the outside looking in, this project is starting to look more and more like Ethereum.
Developers are gonna wanna develop and if they are allowed, they'll develop Bitcoin into a centralized shitcoin.
GitHub
Releases · bitcoin/bitcoin
Bitcoin Core integration/staging tree. Contribute to bitcoin/bitcoin development by creating an account on GitHub.
How crazy is it that "Bitcoin maximalists" care about this guy's opinion at all?
Scott Bessent was a partner at Soros Fund Management for most of his career (1991-2000 and again 2011-2015).
Bessent was instrumental in significant financial strategies, including a major profit during the British Pound crisis in 1992.
In 2011, he returned to Soros Fund Management, where he managed billions in assets and made a notable bet against the Japanese yen, yielding substantial profits.
Bessent chaired the investment committee and is a former member of the executive committee on the board of trustees of Rockefeller University.
Bessent is also a member of the Council on Foreign Relations.
Bessent has participated in Dialog, a secretive, invitation-only social club founded by Peter Thiel and Auren Hoffman. He is also a member of the Economic Club of New York.
As of December 28, 2024, Bessent's net worth was at least $521 million according to his financial assets disclosure by the U.S. Office of Government Ethics; his actual net worth is speculated to be around $600 million.
So, tell me, Bitcoin maximalists, do you think this guy really wants what's best for Bitcoin? 😂
It's like the Bitcoin maximalist who was calling out Jamie Dimon for being Epstein's banker and then started a company with Epstein's neighbor (Howard Lutnick).
If you blindly follow influencers, it might turn out that they don't have your best interest at heart. The only solution is to do your own research.
So why did Luke Dashjr say "Hashrate is irrelevant at this point"?
I won't pretend to know what his opinion is, I'll just give you mine.
1) Mining isn't decentralized — pools are (allegedly, not really).
Why are pools not decentralized? Because the interests of "rival" countries converge more often than most realize (More context:
My hot take is: "Just wait till Bitcoiners figure out Bitcoin".
Just wait till Bitcoiners figure out that the real speculative attack is not buying treasury companies that short the currency and allegedly buy Bitcoin, it is Bitcoiners taking self-custody and demanding proof-of-reserves from public companies.
Once that happens, gold bugs and non-gold bugs will be forced to figure out Bitcoin.
Until then, Bitcoiners still think that:
- Permissionless tech = permissionless adoption.
- Bitcoin is co-opting the state.
- You can enforce 21M by delegating to wrappers.
And until then, most gold bugs still think that Bitcoin is Ethereum is Solana.
Most people only care about Bitcoin because number goes up more than other things they can buy.
This is incompatible with on-chain BTC at the bottom, and layers of IOUs, wrappers, and derivatives on top.
The protocol can cap issuance at 21,000,000 BTC.
Markets can create claims on far more than 21,000,000 BTC.
More context: