This market resolves YES if BIP-110 reaches its defined lock-in threshold before activation by achieving support in at least 55% of blocks within a single Bitcoin difficulty adjustment period on Bitcoin mainnet. Because each Bitcoin difficulty adjustment period contains 2,016 blocks, the required threshold is at least 1,109 signaling blocks out of 2,016.

For purposes of this market, “lock in” means that, during an applicable Bitcoin difficulty adjustment period, at least 1,109 blocks signal support via the designated BIP 9 version bit for BIP-110, using deployment name “reduced_data”, under BIP-110’s specified miner activation mechanism. The lock-in event must occur before the rule change becomes active/enforced.

The threshold must be achieved on the primary Bitcoin mainnet chain, defined as the chain with the most cumulative proof-of-work that is widely traded under the BTC ticker on major economic exchanges. Miner signaling achieved exclusively on a minority split chain will not count toward a YES resolution.

This market resolves NO if Bitcoin block height 965664 is reached without a valid miner lock-in event having occurred in that or any prior difficulty adjustment period.

This market also resolves NO if BIP-110 activates through its mandatory signaling or flag-day mechanism, including where the deployment bit becomes required in vbrequired, without first reaching the organic 55% miner threshold within a single difficulty adjustment period. It also resolves NO if BIP-110 is officially abandoned or superseded, or if no clear and publicly verifiable miner lock-in event occurs before block height 965664.

Resolution should be based on public Bitcoin mainnet block data, including sources such as Mempool.space, BGeometrics, BTC.com, public BIP-110 activation trackers, node/client activation status, and other credible blockchain data documenting whether the 55% threshold was reached within a single difficulty adjustment period before block height 965664.