Will BIP-110 signaling reach 51% of blocks during its mandatory window?
53,580 Vol.18 hours ago (Aug-25-2026 12:00:00 AM UTC)
DescriptionBIP-110 ('Reduced Data Temporary Softfork,' backed by Luke Dashjr's Knots camp) seeks to cap non-financial data on Bitcoin. Its mandatory miner signaling window runs from block 961,632 (~Aug 9, 2026) through block 963,647 (~Aug 23-24, 2026). Mining pool Foundry (~1/3 of network hashrate) publicly committed to signal 'No' until 'Yes' votes cross 51%, at which point it flips ALL its blocks to 'Yes.' As of late July 2026, bit-4 'Yes' signaling sat near ~2.64%.
- This event resolves YES if the share of blocks signaling BIP-110 version-bit 4 reaches or exceeds 51% at any point during the mandatory block window (blocks 961,632 to 963,647) on the most-work chain.
- This event resolves NO if bit-4 signaling never reaches 51% within that window.
- 1. Specificity: YES requires the publicly tracked bit-4 'Yes' share to hit >=51% of blocks during the mandatory window. Foundry's automatic flip counts once its blocks actually signal 'Yes.'
- 2. Exclusion: A share below 51% does NOT count. Node-software adoption (Knots node %), social-media pledges, and any resulting chain split are NOT this market. Foundry's internal poll metric is not used — only on-chain block share.
- 3. Source Hierarchy: bip110monitor.com priority. coin.dance secondary. Bitcoin Magazine reporting tertiary. If chains diverge, signaling is measured on the most-work (majority) chain.
- 4. Timing: Resolution is tied to the block-height window (ends at block 963,647), estimated ~Aug 23-24, 2026 UTC; the calendar date is an estimate, not a hard cutoff.
- 5. Cancellation Rule: If the mandatory window is rescheduled or block heights shift, resolution tracks the actual on-chain bit-4 signaling during the defined mandatory window.