This is part of a series that began with Fiat Incentives Everywhere, which maps how the legacy system’s cost structures have infiltrated every layer of Bitcoin’s human infrastructure. This article goes deeper into the development department: Why the funding pipeline that sustains Bitcoin Core reproduces the very power dynamics Bitcoin was designed to make impossible, and why the community has normalised the fallout.
Note: This article references findings from hodlonaut’s investigation “The Capture,” a planned four-part series in Citadel21, which documents the consolidation of influence over Bitcoin Core development through public records.[1][2] I recommend reading it in full. This article does not retell that investigation. It examines the incentive structure underneath it.
Why This Was Inevitable
Every section of this series describes the same mechanism: Fiat funds the infrastructure, and fiat incentive structures follow. In the creator economy, sponsorship revenue creates a compounding loop. In the funding landscape, return expectations force Bitcoin companies to bolt on non-Bitcoin products. In the corporate treasury model, retail capital finances institutional Bitcoin accumulation while receiving fiat-denominated claims in return. The mechanism is always the same. Fiat capital enters a Bitcoin space, and the space begins to act like the system Bitcoin was designed to replace.
And Bitcoin Core development is not immune to this. The protocol has no treasury, no foundation, no built-in compensation mechanism but open-source developers need funding. Developers either fund themselves, receive grants from nonprofits and corporations, or eventually stop contributing. In the absence of a Bitcoin-native funding model, fiat-structured organisations filled the gap, inevitably bringing fiat incentive structures with them.
The Cost of Concentrated Funding
The past few years have demonstrated what happens to the project when funding concentrates to the point where a single organisation’s engineer merges more than half of all changes in a given year,[3] that organisation’s engineers lead every release across five maintained branches,[3] and occupy multiple maintainer seats simultaneously.[2] These are numbers from the organisation’s own public reporting, presented as achievements. Merging in Core is the final step after open review, and the merger is usually not the author of the code; defenders will rightly note that reviewer consensus decides what is ready. But when review is contested, the people with merge access have the final say, and almost all of them are funded by a single organisation. Read from a different angle, they describe a level of dependency that no decentralised protocol should have on any single entity.
When the pathway into Bitcoin Core runs through a small number of institutions, the people who advance are the ones those institutions select. hodlonaut’s investigation documents how that selection operated through social proximity and alignment rather than technical merit alone, how dissent was structurally punished, and how the governance mechanisms that were supposed to protect the project were repurposed to insulate the funding network from challenge.[1][2] It is the same selection pressure that operates in every fiat institution on Earth: Proximity to power and paper money determines advancement while independence eventually determines irrelevance.
The Subconscious Normalisation of Burnout
There is a narrative in the Bitcoin community that maintainer burnout is normal; that it is the nature of open-source work. Maintainers exhaust themselves, step down, and others take their place. The community has absorbed this as an unfortunate but inevitable feature of the landscape. The contribution histories, funding decisions, and contributors’ own public statements documented in hodlonaut’s investigation tell a consistent story: From the outside looking in, “burnout” seems to be doing a lot of heavy lifting as an explanation for what is actually happening.[1][2]
When one of the most prolific contributors in Bitcoin Core’s history, top five in the world by commit count, is rejected by the funding pipeline, then watches the reception of his work turn hostile after a technical objection that proved correct, until his contributions fall to near-silence, in his own words “an immense handicap and permanent doghouse status,” with friendly support “almost completely vanished” nearly five years on,[1][2] the word “burnout” starts to look less like a diagnosis and more like a convenient label for something the community is subconsciously dismissing.
There is also a first-hand account on the record: In a March 2026 presentation on Bitcoin Core governance, Jon Atack, a Core developer since 2019, described maintainers who “stay until they burn out” with no plan for passing the torch and the “dynastic effects” that follow, a pipeline in which “your whole life changes when you get your first serious funding,” his own year-long wait for funding while friends waited three or four years, and contributors systematically pushed away from the project after questioning maintainer nominations.[12] I cannot say with certainty what happened inside those dynamics. What I can say is that from the outside, it looks remarkably similar to what happens in every other sector covered in this series: The independent operator runs out of resources while the funded operator compounds, and the community dismisses the departure as normal.
Any single case can have a personal explanation, and the individuals involved may give their own. The structural question is the aggregate one: Across contributors, does persistence in the project track funding-pipeline approval? If independent contributors lasted at the same rate as funded ones, this thesis would be wrong. If they do not, then what the community calls “burnout” may be the predictable outcome of a funding structure that rewards compliance and makes independence unsustainable.
Whether you are a creator who spent everything producing years of educational content for little return, or a developer who spent years contributing to the most important open-source project in the world without institutional backing, the result converges on the same point. The people who care the most are the ones most likely to exhaust themselves, and the community’s response so far has been to treat that exhaustion as inevitable rather than ask why it happened in the first place, and what it would take to prevent it. Calling it burnout converts a collective failure into a personal one, and every builder who disappears becomes the justification the comfortable majority needed to never cross at all.
When independent contributors burnout and disappear, the seats do not stay empty. They fill with people the funding structure selected precisely because they will not push back. The culture shifts. Bitcoin shifts. And what changed is who’s incentives it serves.
The Deeper Problem
What makes Bitcoin Core’s capture particularly significant is that it happened to the layer of Bitcoin’s infrastructure where the protocol’s rules are literally written. Conferences can be captured by corporate sponsors and Bitcoin survives. The influencer landscape can be captured by engagement incentives and Bitcoin survives. VC-funded companies can drift from the Bitcoin-only thesis and Bitcoin survives. But if the reference implementation drifts from what Bitcoin was created for, if it eventually no longer is decentralized and secure, the protocol itself is at risk.
This is precisely what happened when Bitcoin Core v30 increased the default OP_RETURN data limit from 83 bytes to 100,000 against community pushback.[4][5] To be precise: This was a relay policy default, never a consensus rule, and Core contributors argued the old limit was already trivially bypassed through inscriptions and other encodings. The technical debate was real. But that is exactly the point. A contested judgment call about what the network should carry was settled by the maintainers of one implementation, the same implementation whose development pipeline had been consolidating for years. The decision was made.
The community was expected to accept it; but it did not.
The Immune Reaction
Over 22% of all reachable nodes have migrated to Bitcoin Knots, a compatible implementation that allowed operators to control their own mempool settings.[6][7] As of June 2026, approximately 12.44% of the network is signalling for BIP-110 (Reduce Data Temporary Soft fork).[8][9] Node counts can be inflated and Knots advocacy was loud, so the precise figures deserve scepticism; but even heavily discounted, the direction is unambiguous. Individual node operators changed software specifically to reject a default chosen for them, in a world where most Bitcoin educators and influencers stayed silent on the matter due to their own fiat incentive dependencies.
It is an echo of the immune response that defeated the corporate takeover attempt in 2017, when a coalition representing over 80% of Bitcoin’s hash power tried to force a consensus change under corporate terms and individual node operators simply refused.[10][11] The stakes differ, a hard fork then against a relay default now, but the reflex is the same. The people with the most economic weight do not determine Bitcoin’s future. The people running nodes do. That is the design, and the design still works. The Prison Door Is Open; it always was.
Bitcoin cannot end the cycle of monetary extraction if the people maintaining the reference implementation are selected by social proximity, funded by a concentrated pipeline with no functioning governance,[1] and insulated from accountability by the same mechanisms every fiat institution uses to protect its own. But Bitcoin also cannot be captured permanently, because the protocol does not require anyone’s permission to enforce its rules. The immune reaction is already underway; but what would sustain it is the subject of the companion piece: The Comfortable Trap.
This is part of a series. Read the full map or the companion piece: The Comfortable Trap, or go deeper into Marketing: How Money Shapes the Signal, Sales: The STRC Cantillon Reconstruction, Funding: Why Bitcoin Companies Drift.
Data as of mid-June 2026.
Sources
[1] hodlonaut. (2026, March 27). The capture: Article one of four – The network. Citadel21. https://www.citadel21.com/the-network
[2] hodlonaut. (2026, April 29). The capture: Article two of four – The lever. Citadel21. https://www.citadel21.com/the-lever
[3] Brink. (2026, March 26). 2025 engineering impact report. https://brink.dev/blog/2026/03/26/engineering-impact-report-2025/
[4] Bitcoin Core. (2025, October 10). Bitcoin Core 30.0 release notes. https://bitcoincore.org/en/releases/30.0/
[5] Liberati, D. (2025, September 8). Choosing Core or Knots based on first principles (Bitcoin node) [Video]. YouTube. https://youtu.be/mDTfEr2gYWo
[6] Coin Dance. (2026, June 9). Bitcoin nodes summary. https://coin.dance/nodes/knots
[7] Moody, C. (2026, June 9). Bitcoin dashboard. https://bitcoin.clarkmoody.com/dashboard/
[8] Dashjr, L. (2026, June 9). Bitcoin network statistics. https://luke.dashjr.org/programs/bitcoin/files/charts/services.html
[9] Bitcoin Improvement Proposals. (n.d.). BIP-110. GitHub. https://github.com/bitcoin/bips/blob/master/bip-0110.mediawiki
[10] Bitcoin Wiki. (2019, February 24). SegWit2x. https://en.bitcoin.it/wiki/SegWit2x
[11] River. (2021, January 7). What is SegWit? https://river.com/learn/what-is-segwit/
[12] Atack, J. (2026, March 4). Bitcoin code governance and Bitcoin Core [Video]. YouTube. https://www.youtube.com/watch?v=H9c9A2rNrFA (Maintainer burnout at 12:20 and 18:24; funding dynamics at 17:48 and 18:47; maintainer nominations at 22:25)