Bitcoin’s BIP-110 minority branch has effectively stalled after producing only two blocks, while the U.S. Digital Asset Market Clarity Act has moved toward a September Senate procedural vote. The systems are fundamentally different, but both show that proposed rules have limited practical force until enough participants coordinate around them.
For exchanges, custodians and institutional operators, the uncertainty is different on each side. Bitcoin infrastructure providers must identify the economically relevant chain during a split, while U.S. crypto businesses still cannot treat CLARITY’s proposed framework as law. Operational planning must account for rules that exist on paper or in software without yet commanding broad authority.
BIP-110 Branch Stalls After Two Blocks
BIP-110, formally titled the Reduced Data Temporary Softfork, proposes temporary consensus restrictions on several methods of embedding arbitrary data in Bitcoin transactions. Its deployment uses a 55% signaling threshold and mandatory signaling between blocks 961,632 and 963,647. When that window began, enforcing nodes rejected non-signaling blocks. The resulting BIP-110 branch produced blocks 961,632 and 961,633 before effectively stopping.
Miner backing had remained far below the proposal’s threshold before the split. The dominant Bitcoin chain continued advancing while the BIP-110 branch stayed at height 961,633, showing that the new rules had not attracted enough mining support to maintain normal block production. Pre-fork signaling and sustained support for an alternative ledger proved to be very different measures of adoption.
The branch has not formally reached BIP-110’s specified expiration state. The proposal sets mandatory signaling through block 963,647, lock-in no later than 963,648 and activation at 965,664 for nodes continuing to enforce its rules, followed by an active period of 52,416 blocks. The formal mechanism is based on block height even though the minority branch currently has little capacity to progress through those milestones.
For exchanges and custodians, the episode highlights practical fork-management questions, including ticker assignment, deposit confirmations, minority-chain support and node-software approval. A consensus dispute becomes operational risk once different rule sets produce competing transaction histories.
CLARITY Faces a September Senate Test
The legislative process remains unresolved for different reasons. The House passed H.R. 3633 on July 17, 2025, by a 294-134 vote, and the Senate Banking Committee advanced the CLARITY Act in May 2026. Before the August recess, Senate leadership filed cloture on the motion to proceed. The Senate schedule says the cloture motion will ripen on September 15 at 2:15 p.m.
That step does not make CLARITY law or guarantee final passage. It creates the next procedural test for legislation intended to establish a federal digital-asset market structure involving both the SEC and CFTC. Senate negotiations have also addressed stablecoin yield and ethics safeguards for elected officials. Compliance teams therefore still need to treat CLARITY as a legislative scenario rather than an operative regulatory framework.
The comparison between BIP-110 and CLARITY has clear limits, but the governance lesson is useful. Bitcoin rules acquire practical relevance through adoption by miners, nodes and economic actors, while federal legislation must survive congressional procedure before becoming binding law. For institutional operators, both episodes reinforce the need for documented change controls, contingency plans and clear thresholds for recognizing when proposed rules become operationally authoritative.
