Bitcoin has 185 blocks left before BIP-110 rules begin rejecting blocks
Bitcoin nears the deadline for BIP-110, a proposed non permanent gentle fork that will shrink block knowledge. Once the present signaling interval ends, nodes implementing it is 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 before the interval closes.
BIP-110 requires 1,109 signaling blocks in a 2,016-block interval to fulfill its 55% threshold. Even if each a type of 185 remaining blocks signaled, the interval would end at 233 of two,016, or about 11.56%.
Different rules at top 961,632
From top 961,632, repeatedly enforcing BIP-110 nodes reject blocks that don’t sign bit 4. Nodes following existing Bitcoin rules might settle for the identical blocks in the event that they in any other case fulfill these rules.
The outcome could be divergent block acceptance, whereas any sustained implementing department relies on miners producing BIP-110-valid work after the boundary.
Under the proposal, obligatory signaling runs by way of block 963,647, lock-in will not occur as soon as the peak reaches 963,648, and the reduced-data rules activate at 965,664. That schedule governs BIP-110-enforcing nodes with out binding each Bitcoin participant.
The 2.62% studying measures model bits in noticed blocks, and the monitor says it sources block knowledge from mempool.house 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 swap truly came about and that each miner utilizing the pool now enforces BIP-110 would require unbiased verification.
Alternative 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 totally validating BIP-110 rules 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 downside on regtest utilizing implementing and non-enforcing Knots builds. An information listing might retain a block accepted beneath the previous rules after the operator switched builds as a result of regular startup didn’t reconnect the inherited historical past. The take a look at left out 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 first blocks after top 961,631 will reveal which miners change signaling and whether or not an implementing chain accumulates work. Measuring financial help would take separate proof, comparable to trade listings, node adoption knowledge, or holder habits.
The put up Bitcoin has 185 blocks left before BIP-110 rules begin rejecting blocks appeared first on CryptoSlate.
