Bitcoin Enchancment Proposal 110 entered its mandatory-signaling part at block 961,632 on Saturday, with miners signaling assist in simply 51 of the previous 2,016 blocks, or 2.53%, effectively under the 55% threshold required for early activation, in response to the BIP-110 monitor.
Beginning at block 961,632, nodes implementing BIP-110 started rejecting blocks that didn’t set model bit 4, whereas unusual Bitcoin nodes continued accepting each signaling and non-signaling blocks. A minority BIP-110 department subsequently emerged, however shortly fell behind the dominant chain.
The low signaling price makes a sustained rival chain unlikely with out considerably better miner participation. With comparatively little mining assist, a BIP-110 department may advance slowly or cease producing blocks altogether.
The milestone exams whether or not supporters can advance a contentious consensus change with out broad miner backing, probably separating implementing nodes from the dominant chain and escalating a dispute over how Bitcoin’s block house must be used.
BIP-110 seeks short-term limits on Bitcoin knowledge
Written by pseudonymous developer Dathon Ohm, BIP-110 proposes further consensus restrictions lasting roughly one yr.
It will restrict most new output scripts to 34 bytes, cap OP_RETURN outputs at 83 bytes, prohibit sure knowledge pushes and witness parts to 256 bytes, and quickly restrict a number of Taproot options. Unspent transaction outputs created earlier than activation can be exempt.
Supporters stated the restrictions would discourage inscriptions and different non-monetary knowledge that enhance storage and bandwidth prices for node operators.
The proposal’s critics, together with Technique Govt Chairman Michael Saylor and Blockstream CEO Adam Again, have argued that the proposal could divide Bitcoin and trigger nodes to reject transactions permitted underneath the community’s current guidelines.
Associated: Bitcoin nodes running BIP-110 crosses 2% as spam wars heat up
The proposal uses model bit 4 for miner signaling. Its deployment schedule units blocks 961,632 via 963,647 as a mandatory-signaling window, throughout which nodes implementing BIP-110 reject blocks that don’t carry the sign.
The specification defines block 963,648 as the start of its locked-in state and block 965,664 as the purpose when its transaction restrictions take impact.
BIP-110 proponents have additionally mentioned a extra intensive fallback. On Aug. 1, Bitcoin developer Chris Guida rebased preliminary code for a proof-of-work change initially written by Bitcoin Knots maintainer Luke Dashjr.
Guida described the code on the time as a contingency if miners opposed BIP-110, however stated no activation date had been set.
