The Bitcoin community has placed disproportionate trust in developers while vilifying miners, creating a dangerous asymmetry where the single codebase controlling over 90% of full nodes (with the 2018 inflation bug as evidence) represents a larger attack surface than the 51% mining pool threat. Both developers and miners are humans who operate between incentives and ideals, and the solution is to build systems that don't depend on either group being angels or demons, while spreading the load across multiple implementations to prevent any single group from carrying the entire network.
Deep Dive
Prerequisite Knowledge
- No data available.
Where to go next
- No data available.
Deep Dive
Bitcoin OG Has A Confession To Make | Jimmy Song
Added:All right, so my talk is entitled, Incentives and Ideals.
So every few years, Bitcoin has some sort of panic attack, or more accurately, Bitcoiners have a panic attack.
A mining pool gets a little too big, right?
Somebody refreshes a hash rate chart, sees a slice getting a little too fat towards that magic number, 50%.
And the whole community just sort of loses its mind, right?
Twitter lights up, blog posts get written, people start using the word existential.
You all know the chart I'm talking about.
It's that big colorful pie, right?
With names like Foundry and AntPool, ViaBTC, Slush.
And a long tail of smaller pools, beautiful spread of colors, right?
A beautiful spread of choices.
And we're very proud of that pie.
And we put it on our slides, we tell people, hey look, this is how decentralized we are.
We have all of these different types of miners.
Here's the thing though, that pie, that assortment of colors didn't come for free, right?
It's the result of community engagement.
We keep it that way by essentially freaking out every single time that the percentage of a single miner gets too big.
And there's a historical event back in 2014 that illustrates this.
There was a mining pool by the name of GHash.io.
I don't know how many of you guys were around back then, but it was a pretty big pool and it kept increasing, right?
40%, 45%, people started freaking out.
And at one point it actually reached 51%.
And the community outrage was so loud that the people running the pool actually said, hey miners, can you get off of our pool so we're not above 50% so that the community doesn't freak out anymore.
In other words, we policed it and we policed it pretty hard and it worked.
It worked really well.
So hold that picture in your head for the next 15 minutes or so.
And that pie and the panic, because I want you to think about this question.
Why do we panic about that?
And only that, or not some of these other things.
To answer that, we have to sort of look at the story that we tell ourselves about miners.
And the story goes like this.
Miners are slaves of short-term economic incentives.
And that's the assumption that underneath absolutely everything.
We believe that if a miner can make an extra nickel they will do X, Y, or Z to get it.
Even if X, Y, or Z make Bitcoin worth less tomorrow.
Even if it torches the future value of their own business.
A business which they spent millions of dollars and much blood, sweat, and tears into building.
We assume that they literally cannot see past the next block.
And I have a confession to make.
I've thought this way myself.
I've sat in rooms and modeled miners as little profit-maximizing robots.
I've used the phrase incentive compatibility like it was like a law of physics.
As if no miner could possibly have Bitcoin's best interests at heart.
The moment ignoring it can earn them an extra basis point of profit.
So I'm not pointing fingers here.
This kind of thinking is the water that we swim in.
And it absolutely dominates the conversation when we talk about miner centralization.
Now listen to the story that we tell ourselves about another group.
Because the way we talk about Bitcoin developers could not be more different.
With developers the default is to assume the best.
Best intentions.
That they are always doing what's right for the network.
That at least collectively they are the long-term guardians of this community, this network of Bitcoin.
And we expect them to live up to the highest ideals that we have for Bitcoin.
And here's the almost beautiful part.
We expect them to do it even if it costs them money.
Especially when it costs them money.
In fact the more a developer appears to be sacrificing money the more we kind of tend to trust them.
So sit with that contrast for a moment.
One group assumed to be sellouts for a nickel.
And then another group assumed to be so noble that money is almost beneath them.
And here's what's really strange about that.
Both of these groups come from the exact same pool.
That pool is called humanity.
And the last time I checked very few people are so depraved that they do the selfish short-sighted thing every single time.
And very few people are so angelic that they hit the ideal every single time.
Most of us, and I definitely include myself, live somewhere in the middle between incentives and ideals.
We bounce back and forth between the things that were selfishly incentivized to do and the things that are the best for the world.
That's just what being a human is.
And yet somehow we've handed one group the role of mercenary and the other group the role of a saint.
Same species, two completely different stories that we have about them.
And that's not just a quirk of how we talk.
It has actual real consequences.
And I wanna give you two of those.
The first consequence is that we hand the developers an enormous amount of trust.
Far more than we've ever stopped to really examine.
Think about what that trust actually buys them because we've decided that developers are selfless guardians of the network, the noble ones, we don't really scrutinize them the way we'd scrutinize anyone else with that much power.
We assume the code is sound because we assume the people writing it are good.
And that one assumption quietly hands a small group of people an extraordinary amount of control over what Bitcoin even is.
And notice where we aim our suspicion instead.
A misbehaving miner, that's a bounded problem.
A 51% attacker can do some things like reorder transactions, censor things, maybe even try a double spend.
But it's really expensive.
And it's visible in real time.
And it's self-limiting because they're kind of cutting off the branch that they're standing on.
The moment they attack, the price of Bitcoin is going to be way more volatile.
And that threat though, we watch around the clock.
We reload that pie chart.
Meanwhile, the software, which has no such boundedness gets waved through on trust.
And that software is by a very large margin, the attack surface of the entire Bitcoin system.
For most of Bitcoin's history, well over 90% of full nodes have run that single implementation.
One code base effectively defining the rules for everyone.
Even today, after a real shift towards Knots, a large majority still run Core.
One implementation, one set of assumptions, a shared point of failure.
And it doesn't take a grand betrayal, like some spook that puts in some vulnerability.
It just takes a bug.
The ordinary kind that lives in all kinds of software.
When most of the network runs the same code, one bad bug doesn't just crash one node, it crashes most of them at the same time.
A single malformed message and a huge chunk of the network can go offline at once.
No 51% attack required, just a typo or a bug.
And this isn't just theoretical.
There was a bug in 2018.
I know many of you are familiar with that.
It was called the inflation bug because it introduced the possibility of inflation.
But the more serious part of that particular bug was that it would remote crash every node if a block met certain requirements.
But I don't want you to really remember the bug per se.
I want you to remember where it came from.
Wasn't a shadowy attacker, wasn't a greedy miner.
It came from the people that we put our trust in.
The careful, brilliant, well-intentioned developers that we have put on a pedestal.
Our trust didn't catch that bug.
Thankfully, that bug was fixed and despite it having been on the network for two years, we didn't suffer the consequences of that bug.
Here's the thing that we don't like to say out loud.
Developers are not infallible.
They didn't shed their humanity the day they opened the pull request.
They're not magically immune to error or to greed or to pride or to wanting to win an argument just because their work happens to be open source.
And the block size war should have taught us that much.
Years of conflict, conflicting implementations and activation fights full of conviction and ego, fighting over who gets to define the rules.
Open source doesn't sand the ego off of a human being.
Sometimes it just hands them a bigger stage.
So when I say we trust the developers too much, I'm not calling them bad people.
Most of them are doing some of the most important work on earth and saying that trust without verification is the very thing that Bitcoin was invented to destroy.
And we've quietly rebuilt it a little bit, aimed it at the people writing the code and called it a virtue.
The second consequence is the mirror image of the first.
If we trust the developers too much, we're inspiring the miners far too little.
We don't just doubt them, we vilify them.
We've cast them as people who are villains inside their own story, despite the fact that they are securing the network.
I mean, listen to the language, like we call them greedy and we talk about incentive compatibility as if it's like some iron law, as if it's simply impossible for a miner to care about anything beyond the next reward.
We describe people who have sunk hundreds of hours, millions of dollars and stake their livelihoods on Bitcoin as if they're just sitting there waiting to sell us out.
So let me ask you a genuine question.
Have you met miners?
Have you actually sat down and talked to one?
Because the ones I've met don't sound like profit maximizing robots that we make them out to be.
They're actually pretty obsessed with Bitcoin.
They've bet their entire livelihoods and careers on it.
Of course they care about the long term because the long term is all they have.
And it's not just talk.
In 2023, a firm accidentally paid a transaction fee of 20 Bitcoin to transfer like maybe half a Bitcoin or something like that.
And the pool that mined the block, F2Pool, had every legal and protocol right to keep that money.
But they didn't.
They actually gave it back.
And to be fair, it was kind of a messy situation.
And one of the founders of F2Pool later said he regretted giving that money back.
But it kind of shows they're not profit maximizing beasts.
There's a humanity about them.
And a few years before that, there was a similar incident where they also returned the money.
Now think about what that vilification actually does.
When you tell a group of people over and over that they are nothing but mercenaries, that they have no values, that they'll sell you out and betray you the instant that it pays, you are not protecting Bitcoin.
You are isolating the very people that are securing it.
You're telling them that they don't get a seat in the conversation about Bitcoin's ideals.
And then we act shocked, maybe even offended, when a few of them shrug and start behaving like the mercenaries that we always insisted they were.
And here's the part that really gets me.
We hold the developers to a towering ideal.
Now a lot of the time they rise to meet it.
In that way, it's very good.
People tend to grow into the thing that you trust them to be.
But we have never really extended that to the miners.
We never invite them into the ideals.
We never turn to them and say, "You too are guardians of this network, "and we are counting on you."
We kind of assume the worst.
And we wall them off and we call it prudence.
So we leave the single greatest source of alignment in the whole system sitting untouched on the table.
Miners are not just a security budget to be managed.
They're people, and people can be inspired.
We inspire the developers, and we vilify the miners.
And then we have the nerve to wonder why the whole relationship feels so adversarial.
All right, so to be clear about what I'm saying, I'm not saying that you should be cynical about developers and naive about miners, and that you should flip the saint and mercenary thing around.
What I'm asking cuts to the root of what centralization is.
Strip it all down, and centralization is really a question about trust.
How much we put in to how few people.
Forget pie charts and node counts for a moment.
What actually scares us about the 51% pool is that it asks us to trust one party too much.
And when we turn around and heap that same concentrated trust onto a small circle of developers, that's bad.
My admonition to you is to stop trusting people blindly.
Treat both groups as what they actually are.
They're humans.
Somewhere in that messy middle, like you, like me.
And build systems and hold opinions that don't depend on either group being angels, and that survive either group being demons.
And look, I'd rather not just stand up here and ask you to do the work.
This is exactly why I'm involved in an organization called ProductionReady, it's a nonprofit.
The whole idea is simple.
Fund a conservative Bitcoin client that's an old.
And fund developer education so that the thing I just spent 10 minutes worrying about, one code base quietly defining the rules for everyone becomes less true every year.
More implementations, more independent eyes, more builders who don't answer to the same repository.
The worry that I keep circling back to, that if we lean too hard on one set of developers and barely watch the software they ship, doesn't go away by trusting them less and stewing about it.
It goes away when we spread the load, so no single group of them ever has to carry the whole network on its shoulders.
That's better for them, and it's better for us.
If any of that resonates, if you write code, if you fund things, or if you want to understand the stakes better, come, find me afterwards, or go to productionready.org.
That's where I'm putting my own time.
I'd love to get your help.
So I wanna leave you with this one last thing.
The next time you see one of those pie charts about the different mining pools and so on, and you see one slice getting a little fatter, and you feel that familiar surge of panic in your chest, I want you to ask yourself this one question.
Have I ever looked this hard at the thing that the pie chart can't show me?
Because the people writing the code, and the people that are computing the hashes come from the same place.
They're the same flawed, brilliant, self-interested, and occasionally generous species.
And Bitcoin doesn't survive because some of us are angels.
Bitcoin survives because none of us have to be.
Thank you.
(audience applauding)
Related Videos

Multi Vendor Multisig w/ Seed Signer, Hodl Dee & QnA
BitcoinMagazine
985 views•2024-09-05

Oasis Week in Review: Latest blog articles, workshops and more
OasisFoundation
135 views•2024-10-18

Kaspa: How ZK Turn Blockchains Into Settlement Layers (Part II)
cxc
1K views•2025-12-19

以言會友 EP13|當比特幣屢破紀錄 區塊鏈技術能帶來什麼?
dotdotnews
293K views•2021-01-05

Soroban Development: Ecosystem Growth, and the Rise of 70+ Smart Contract Projects
SorobanOfficial
1K views•2023-07-19

Balaji Srinivasan I The Fiat Crisis | Pragma Tokyo 2023
ETHGlobal
37K views•2023-05-06

$22 million NFT scammers arrested (insider evidence)
coffeezillaextras
806K views•2025-02-03

SYMMETRICAL TRIANGLE HOLDS THE KEY TO NEXT MOVE" DON'T IGNORE
xrpfuturemillionaire
800 views•2026-03-15
Trending

Playstation NO DISC/NO BUY Fight Is Over...
DavidJaffeGames
4K views•2026-07-23

Americans Confused in Australia for 17 Minutes Straight
IWrocker
17K views•2026-07-23

Bitcoin Social Interest: Dozens of us Left
benjaminjcowen
12K views•2026-07-23

Tesla Profits Plunge & SpaceX Stock Continues Fall
TheJohnJohnstonLounge
6K views•2026-07-23