BIP-110 nodes fork from main chain after rejecting
The fork highlights the challenges of achieving consensus in decentralized networks, potentially leading to isolated, economically weak chains.
TL;DR
On Aug 8, 2026, Bitcoin nodes enforced BIP‑110 via a UASF, rejecting blocks from miners who did not signal support. With only 2.53% miner backing, the move tests Bitcoin’s governance and could lead to a parallel chain if it gains traction.
Key facts
- BIP‑110 UASF began at block 961,632 on Aug 8, 2026.
- Only 51 of 2,016 pre‑UASF blocks signaled miner support, about 2.53%.
- The activation threshold for non‑contentious rollout is 55% miner support.
On August 8, 2026, a subset of Bitcoin nodes activated a user‑activated soft fork (UASF) for BIP‑110 at block 961,632, rejecting blocks from miners that did not signal support via version‑bit 4. The move, tracked by the BIP‑110 Situation Monitor, came after only 2.53% of miners indicated backing during the preceding mandatory‑signaling phase. Proponents argue the fork will curb non‑financial data on the chain, while critics, including Michael Saylor, contend it threatens Bitcoin’s open‑access ethos.
Background
BIP‑110 is a proposed temporary amendment to Bitcoin’s consensus rules intended to make it harder to embed non‑financial data—such as text, images, and inscriptions—into block space. Its supporters claim that limiting such data will reduce storage and bandwidth demands, preserving Bitcoin’s focus on monetary transactions. The proposal would restrict certain Taproot features, data pushes, witness elements, and OP_RETURN outputs for roughly a year. Activation of a soft fork in Bitcoin traditionally requires a 55% miner signaling threshold to avoid a contentious split. However, the BIP‑110 supporters chose to enforce the change via a user‑activated soft fork, a mechanism that allows node operators to reject blocks that do not meet the new criteria, regardless of miner support. This approach raises a fundamental governance question: who holds the authority to set Bitcoin’s rules—miners, developers, node operators, or users? The debate echoes earlier governance tests in Bitcoin’s history, but the current scenario is notable for its low miner backing and the potential for a lasting chain split if the minority fork gains traction.
What happened
According to the BIP‑110 Situation Monitor, Bitcoin reached block 961,632 on August 8, 2026, marking the point where nodes running modified software began enforcing BIP‑110’s new regulations. The enforcement rule requires miners to set version‑bit 4 to signal support; otherwise, their blocks are rejected by these enforcing nodes. Prior to this mandatory‑signaling phase, miners had 2,016 blocks to indicate support, and only 51 of those blocks—approximately 2.53%—did so, far below the 55% threshold needed for activation without a split. The low signaling rate meant that the majority of mining power continued to produce blocks that the BIP‑110‑enforcing nodes considered invalid. As a result, two parallel chains could emerge: the legacy chain following existing Bitcoin rules and the minority chain adhering to BIP‑110’s temporary restrictions. Proponents of the fork argue that the minority chain could attract enough support to become viable, while opponents warn that the lack of miner backing makes the fork unlikely to compete effectively. Michael Saylor publicly listed 110 reasons to oppose BIP‑110, underscoring the contentious nature of the proposal.
Market impact
The immediate market impact is limited, as the fork has not yet caused a noticeable shift in Bitcoin’s price or trading volume. The primary quantitative signal is the miner support figure of 2.53% for BIP‑110, derived from 51 supportive blocks out of 2,016 in the pre‑UASF period. The activation threshold remains at 55% for a non‑contentious rollout, highlighting the gap between current miner sentiment and the level required for smooth adoption. No additional price data or transaction flow metrics were provided in the source, indicating that the event’s financial repercussions are still unfolding and may depend on whether the minority chain gains sufficient hash power to challenge the main network.
Why it matters
The BIP‑110 UASF represents a live test of Bitcoin’s decentralized governance model, exposing the tension between miner dominance and node operator autonomy. If the minority fork persists, it could force miners to reconsider their stance on data‑heavy transactions or risk being sidelined by a growing community of nodes enforcing stricter rules. Conversely, a failure of the fork would reaffirm miner control over consensus changes, potentially discouraging future UASF attempts. The debate also touches on broader questions about Bitcoin’s role: whether it should remain a pure monetary system or continue to support a wider range of data applications. The outcome may influence future proposals that aim to modify block space usage, as stakeholders gauge the viability of enforcing changes without broad miner consensus. Moreover, the public opposition from high‑profile figures like Michael Saylor adds a layer of reputational risk, potentially affecting community sentiment and the perceived legitimacy of governance mechanisms.
DeFi Intel’s take
Editorial analysis, not a statement of fact.
DeFi Intel's take: the BIP‑110 UASF highlights a growing willingness among node operators to challenge miner‑centric rule changes, suggesting a shift toward more diversified governance in Bitcoin. The 2.53% miner support figure indicates that the majority of hash power remains unconvinced, which could limit the fork’s ability to sustain a viable chain. We read this as a warning that without broader miner alignment, minority forks may struggle to attract sufficient security, but the experiment also serves as a proof‑of‑concept for future user‑driven upgrades. The ongoing debate may prompt developers to seek more inclusive signaling mechanisms, balancing the interests of miners, users, and the broader ecosystem.
Sources used for this analysis
DeFi Intel wrote this analysis from the reporting above. Any figure or quotation can be checked against those pages.
Frequently asked questions
What is BIP‑110 and why was it introduced?
BIP‑110 is a temporary proposal to make it harder to embed non‑financial data, such as text, images, and inscriptions, into Bitcoin block space. Its supporters say the change would lower storage and bandwidth demands, keeping Bitcoin focused on monetary use, while opponents argue it restricts legitimate use of block space.
How much miner support did BIP‑110 receive before the UASF?
During the mandatory‑signaling phase, miners indicated support for BIP‑110 in only 51 out of 2,016 blocks, which equals roughly 2.53% support—far below the 55% threshold needed for activation without a chain split.
What could happen if the BIP‑110 fork continues to run alongside the main chain?
If the fork persists, two parallel chains may exist: one following the existing Bitcoin rules and another enforcing BIP‑110’s temporary restrictions. The minority chain would need enough hash power and community backing to remain viable; otherwise, it could fade as miners continue on the main chain.
Direct answers
Short answers, written to be quoted.
- When did the BIP‑110 user‑activated soft fork start?
- The BIP‑110 UASF started at block 961,632 on August 8, 2026, when modified nodes began rejecting blocks without version‑bit 4 support.
- What percentage of miners supported BIP‑110 before the fork?
- Only about 2.53% of miners indicated support, with 51 out of 2,016 blocks signaling for BIP‑110 during the mandatory‑signaling phase.
- Why is BIP‑110 considered a governance test for Bitcoin?
- Because it pits node operators enforcing new rules against miners who largely reject them, highlighting who ultimately decides Bitcoin’s consensus changes.
DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at Crypto Briefing.
Discussion
Comments are reviewed before publication.
Want the full article?
Continue reading on Crypto Briefing →
No comments yet.