Chris Guida rebases proof-of-work hard fork code for Bitcoin Knots as miner contingency plan

Bitcoin’s governance debates have a long history of producing contingency plans that everyone hopes never get used. The latest entry: developer Chris Guida has rebased Luke Dashjr’s 2017 proof-of-work hard fork code onto the current version of Bitcoin Knots, positioning it as a ready-to-deploy emergency measure if miners refuse to play along with a proposed protocol change.

The work was completed as of early August 2026, and it has already attracted significant attention from the portion of the Bitcoin community that believes node operators, not miners, should have the final word on the network’s direction.

What BIP-110 is trying to do, and why miners might resist

The soft fork at the center of all this is BIP-110, also called the Reduced Data Temporary Soft Fork, or RDTS. In plain terms, it would temporarily restrict the amount of arbitrary, non-financial data that can be embedded in Bitcoin transactions for a period of one year.

For the soft fork to activate, it needs miner signaling above 55% across a window of 2,016 blocks, which corresponds to roughly two weeks of Bitcoin block production. Early reports from around August 2026 suggest that miner signaling has been weak. That weakness is precisely the scenario Guida’s rebase is designed to address.

The proof-of-work change as a nuclear option

A proof-of-work algorithm change is, in technical terms, one of the most drastic tools available to a Bitcoin faction. It would render existing mining hardware incompatible with the new chain, effectively stripping miners of their accumulated investment in specialized equipment.

Dashjr’s original code was written in 2017 during the height of the block size wars. The fact that it is being dusted off and rebased onto current Bitcoin Knots software signals that at least some developers view miner intransigence on BIP-110 as a real possibility worth preparing for.

Dashjr himself expressed hope that the contingency would never need to be deployed, while affirming that preparation was the prudent course regardless. Bitcoin Mechanic and other stakeholders in the node-operator community have offered stronger endorsements, framing the rebase as a necessary assertion of the principle that economic nodes, not hash power, are the ultimate arbiters of Bitcoin’s rules.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.