Bitcoin nears the deadline for BIP-110, a proposed non permanent smooth fork that may shrink block information. As soon as the present signaling interval ends, nodes imposing it can reject blocks that don’t sign assist.
A 3rd-party monitor confirmed solely 48 of 1,831 blocks signaling as of 14:41:49 UTC on Aug. 7, simply 2.62%, with 185 blocks left earlier than the interval closes.
BIP-110 requires 1,109 signaling blocks in a 2,016-block interval to fulfill its 55% threshold. Even when each a kind of 185 remaining blocks signaled, the interval would end at 233 of two,016, or about 11.56%.
Completely different guidelines at peak 961,632
From peak 961,632, constantly enforcing BIP-110 nodes reject blocks that don’t sign bit 4. Nodes following existing Bitcoin rules could settle for the identical blocks in the event that they in any other case fulfill these guidelines.
The end result will be divergent block acceptance, whereas any sustained imposing department relies on miners producing BIP-110-valid work after the boundary.
Below the proposal, necessary signaling runs via block 963,647, lock-in will not occur as soon as the peak reaches 963,648, and the reduced-data guidelines activate at 965,664. That schedule governs BIP-110-enforcing nodes with out binding each Bitcoin participant.
The two.62% studying measures model bits in noticed blocks, and the monitor says it sources block information from mempool.area and checks every block’s model discipline for bit 4.
A BIP-110 implementation pull request within the Bitcoin Core repository closed unmerged on March 26. Core contributor Antoine Poinsot wrote in a personal capacity on June 4 that Core doesn’t implement the proposal.
Mining pool OCEAN introduced separate signaling and non-signaling endpoints and mentioned its default would switch on July 15. Confirming that the change truly passed off and that each miner utilizing the pool now enforces BIP-110 would require unbiased verification.
Various Bitcoin node implementation Bitcoin Knots used its Aug. 7 release to warn that older non-enforcing software program, explicitly together with present Bitcoin Core, might cease absolutely validating BIP-110 guidelines and depart chainstate unsafe in some situations.
Independently reproducing the Core-specific warning on Bitcoin Core or on mainnet stays excellent.
A July 17 BlockSlop technical write-up reproduced a narrower late-upgrade drawback on regtest utilizing imposing and non-enforcing Knots builds. A knowledge listing might retain a block accepted underneath the outdated guidelines after the operator switched builds as a result of regular startup didn’t reconnect the inherited historical past. The check ignored bodily database corruption or a mainnet incident.
Knots then merged a safeguard that scans inherited headers for mandatory-signaling violations, invalidates offending blocks, and reorganizes. Transaction or script violations that aren’t seen in headers nonetheless want reconnection validation and may require reindexing.
The primary blocks after peak 961,631 will reveal which miners change signaling and whether or not an imposing chain accumulates work. Measuring financial assist would take separate proof, equivalent to trade listings, node adoption information, or holder habits.
