TLDR
- Luke Dashjr stated that Bitcoin cannot depend on one developer for its survival.
- He expressed frustration over repeatedly stepping in to save Bitcoin during crises.
- Dashjr helped fix the 2013 inflation bug that once split the Bitcoin network.
- He strongly opposed the SegWit2x hard fork and prevented major protocol changes.
- Dashjr also criticized Ordinals and inscriptions for causing unnecessary network issues.
Luke Dashjr, a long-time Bitcoin developer, expressed frustration over his recurring role in crisis moments. In a recent statement, he warned that Bitcoin’s future is uncertain if it relies on a single individual. “Even if we survive this attack by Core30,” he said, “this situation… needs to stop.”
Dashjr’s Historic Role in Bitcoin
Dashjr has played a critical role in several key Bitcoin incidents since 2013. That year, he helped patch a severe inflation bug that split the blockchain into two chains. The bug could have caused lasting damage to Bitcoin’s credibility, but developers, including Dashjr, quickly responded.
In 2017, he strongly opposed the controversial SegWit2x hard fork proposal. The proposal aimed to double Bitcoin’s block size and had broad support from miners and exchanges. However, Dashjr’s resistance contributed to its failure, preserving Bitcoin’s original path.
Even if we survive this attack by Core30, this situation where I personally have to save Bitcoin every few years needs to stop. Bitcoin cannot survive if it's dependent on one man. Others need to step up more. https://t.co/86mx2MNcQE
— Luke Dashjr (@LukeDashjr) October 8, 2025
He also warned against Ordinals and inscriptions, citing risks to Bitcoin’s UTXO set. Dashjr claimed he attempted mitigation before a spike in outputs but faced personal setbacks due to a hack.
Internal Conflict Over OP_RETURN and Hard Fork Allegations
Dashjr recently opposed the removal of the OP_RETURN data limit, calling it a harmful change to Bitcoin’s structure. He clashed with Bitcoin Core developers, maintaining his conservative stance on protocol integrity. His disagreement highlights ongoing tensions within the Bitcoin development community.
Leaked messages allegedly showed Dashjr discussing a hard fork proposal using a multisig committee. Critics accused him of attempting to centralize control of Bitcoin, contrary to its decentralized ethos. In response, Dashjr labeled the messages as “fabricated nonsense.”
Dashjr emphasized that relying on one developer places Bitcoin at significant risk. “Bitcoin will not survive if it depends on one man,” he said, urging other developers to step in. He emphasized that community-wide responsibility is crucial for the long-term stability of Bitcoin.
Despite controversies, Dashjr’s influence on Bitcoin development remains significant. His repeated involvement in crisis resolution has significantly contributed to Bitcoin’s technical resilience. However, he insists that the burden must now be shared.
