Bitcoin nears the deadline for BIP-110, a proposed short-term tender fork that will shrink block information. As soon as the present signaling interval ends, nodes imposing it’s going to reject blocks that don’t sign help.
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%.
Totally different guidelines at top 961,632
From top 961,632, constantly imposing BIP-110 nodes reject blocks that don’t sign bit 4. Nodes following current Bitcoin guidelines could settle for the identical blocks in the event that they in any other case fulfill these guidelines.
The end result could be divergent block acceptance, whereas any sustained imposing department will depend on miners producing BIP-110-valid work after the boundary.
Underneath the proposal, obligatory 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.house and checks every block’s model area 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 private capability on June 4 that Core doesn’t implement the proposal.
Mining pool OCEAN introduced separate signaling and non-signaling endpoints and stated its default would change on July 15. Confirming that the change really occurred and that each miner utilizing the pool now enforces BIP-110 would require impartial verification.
Various Bitcoin node implementation Bitcoin Knots used its Aug. 7 launch to warn that older non-enforcing software program, explicitly together with present Bitcoin Core, might cease totally validating BIP-110 guidelines and depart chainstate unsafe in some eventualities.
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. An information listing might retain a block accepted beneath the outdated guidelines after the operator switched builds as a result of regular startup didn’t reconnect the inherited historical past. The take a look at unnoticed 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 might require reindexing.
The primary blocks after top 961,631 will reveal which miners change signaling and whether or not an imposing chain accumulates work. Measuring financial help would take separate proof, similar to change listings, node adoption information, or holder habits.
