Bitcoiners love saying that Bitcoin has no leaders.
No CEO. No board. No headquarters. No foundation capable of changing the monetary policy. No committee that can wake up tomorrow morning and decide that 21 million should become 42 million.
That absence of centralized authority is one of Bitcoin’s defining properties.
Then something happened that made the slogan suddenly feel much less simple.
Luke Dashjr was removed from his position as a Bitcoin Improvement Proposal editor.
Not voted out by token holders. Not dismissed by a Bitcoin president. Not removed by shareholders. There is no Bitcoin HR department, no Bitcoin Supreme Court, and no constitution containing an impeachment clause for BIP editors.
Instead, a developer proposed his removal on the Bitcoin Development Mailing List. Other prominent contributors supported it. Dashjr rejected the accusations. A GitHub pull request was opened. His administrative permissions to the BIPs repository were removed. The repository was subsequently updated to reflect the change.
And just like that, one of the strangest governance questions in Bitcoin moved from philosophy to reality.
If Bitcoin has no leaders, who exactly had the authority to remove Luke Dashjr ?
The answer is uncomfortable because there isn’t really one.
And that may be precisely the point.
First, Luke Dashjr Wasn’t “Fired From Bitcoin”
This distinction matters enormously.
Luke Dashjr has not been expelled from Bitcoin.
Nobody can do that.
He can continue writing Bitcoin software. He can publish code. He can maintain Bitcoin Knots. He can advocate protocol changes. He can run whatever rules he wants. He can persuade miners, node operators, businesses, and users to adopt those rules.
Nobody possesses the cryptographic key that revokes someone’s membership in Bitcoin.
What Dashjr lost was a specific position of trust : his role as an editor of the Bitcoin Improvement Proposals repository and the privileged repository access associated with it.
That is much narrower than being “removed from Bitcoin.”
But it is not meaningless.
The BIP repository is where proposals intended to describe standards, protocol changes, and important technical processes are formally documented. The BIP process exists partly to bring structure to what would otherwise be chaos : proposals are discussed, formatted, reviewed, assigned numbers, and archived so that developers across the ecosystem can reason about the same technical ideas.
Importantly, BIP editors are not supposed to decide whether an idea is politically desirable.
The repository itself explicitly states that publishing a BIP does not mean the proposal has consensus, is a good idea, or will be adopted. Editors primarily administer the process ; ultimate acceptance rests elsewhere, with Bitcoin’s users and the broader ecosystem.
That sounds almost bureaucratic.
But bureaucracy inside a leaderless system is never merely bureaucracy.
Because the person controlling a gate does not need the power to decide what ultimately wins to possess influence over how ideas enter the conversation.
And this is where BIP-110 detonated something much larger than itself.
