All articles
on-chain api bitcoin-protocol miners

BIP-110 Signaling Has Begun: Track It Daily with BGeometrics

Bitcoin is approaching what could be a significant inflection point. A contested soft fork proposal — BIP-110 — has a UASF flag day approaching around August 2026. Miner signaling, nearly absent until late May, is beginning to appear in the data. BGeometrics now publishes daily block counts for BIP-110 signaling so analysts can follow whether support moves toward the 55% threshold required for miner-driven lock-in.

What Is BIP-110?

BIP-110 proposes a temporary set of consensus rule changes intended to limit how much arbitrary data can be stored inside Bitcoin transactions. The proposal is closely associated with an earlier concept known as RDTS (Reduced Data Temporary Softfork), sometimes referred to as BIP-444, though the exact lineage and authorship remain a subject of dispute within the community. It was formally assigned the BIP-110 number after circulating under the pseudonym “Dathon Ohm”.

The proposal takes aim at a specific class of activity: Ordinals inscriptions, BRC-20 tokens, Runes, and oversized OP_RETURN payloads — uses that embed data into the blockchain primarily to leverage its immutability rather than to transfer value.

If activated, BIP-110 would introduce seven consensus-level restrictions:

  1. New transaction outputs limited to 34 bytes (except OP_RETURN)
  2. OP_RETURN outputs capped at 83 bytes, restoring the historical limit
  3. Data pushes within scripts capped at 256 bytes
  4. Spending from undefined Taproot witness versions becomes invalid
  5. Taproot annex fields prohibited entirely
  6. Taproot control blocks capped at 257 bytes
  7. OP_IF disabled within Tapscripts

Crucially, BIP-110 is designed to be temporary: the rules expire automatically after approximately one year, at which point the community would need to actively extend, modify, or let them lapse.

How Activation Works

BIP-110 uses a User-Activated Soft Fork (UASF) mechanism — the same model used for the SegWit activation debate in 2017. Under UASF, a flag day is set: if the reference implementation running it is adopted by enough economic nodes, those nodes begin enforcing the new rules on that date regardless of miner support.

The flag day for BIP-110 falls approximately in August 2026.

However, there is also a miner-driven fast-track path. If 55% of blocks within any single 2,016-block difficulty adjustment period signal support (version bit 4 set in the block header), the proposal locks in early and activates one difficulty period later. That threshold is 1,109 out of 2,016 blocks — or roughly 110 blocks per day.

The reference implementation is Bitcoin Knots 29.2. Bitcoin Core, the dominant implementation with the largest developer and node share, has not endorsed BIP-110.

According to public reports, the first block to signal BIP-110 was mined on March 1, 2026 by Barefoot Mining, operating through Ocean Pool.

Why It Is Controversial

The debate around BIP-110 cuts to a foundational question about what Bitcoin is for.

Supporters argue that Ordinals and similar uses impose externalities on the entire network: increased node storage requirements, higher bandwidth costs, and elevated transaction fees that crowd out ordinary payments. Limiting arbitrary data at the consensus level, they say, is a legitimate defense of Bitcoin’s core utility as a monetary network.

Opponents push back on multiple fronts. Introducing consensus rules that restrict how people use the scripting system sets a precedent for content-level censorship — a line many Bitcoiners consider uncrossable. There is also the practical risk: if UASF-ready nodes and non-upgraded nodes diverge on what constitutes a valid block, the network could temporarily split. Without Bitcoin Core endorsement and without broad mining support, critics argue BIP-110 lacks the legitimacy required for a safe consensus change, and some prominent voices in the community have called it an “illegitimate soft fork.”

There have also been public allegations — notably from Greg Maxwell — that Ocean Mining was the true author of the proposal, claims that Dathon Ohm has denied. Whether or not those allegations are accurate, they have added a layer of reputational complexity to an already fractious debate.

What the Data Shows So Far

BGeometrics has been collecting daily signaling data since May 2026. The picture as of June 9, 2026 is one of early activity — still far from any critical mass.

DateTotal BlocksBIP-110 BlocksSignal %
2026-05-0115800.0%
2026-05-2114310.7%
2026-05-2813621.5%
2026-06-0413121.5%
2026-06-0714842.7%
2026-06-0912732.4%

Zero signaling blocks were recorded from May 1 through approximately May 20. The first signals appeared around May 21, and activity has been marginally increasing in early June, peaking at 4 blocks in a single day on June 7.

The current daily signal rate of 2–4 blocks represents roughly 2–3% of daily blocks — well below the ~110 per day (55%) needed for miner lock-in. As of writing, no major mining pool (Foundry USA, Antpool, ViaBTC, or F2Pool) has publicly committed to signaling. The volumes observed so far appear consistent with individual miners or small operations, though attributing specific blocks to specific pools requires independent verification.

Track It with the BGeometrics API

The daily BIP-110 signaling data is available via the BGeometrics API:

GET https://api.bitcoin-data.com/v1/bip-110-day

Each record in the response contains three fields:

[
  { "theDate": "2026-06-09", "totalBlocks": 127, "bip110Blocks": 3 },
  { "theDate": "2026-06-08", "totalBlocks": 144, "bip110Blocks": 1 },
  { "theDate": "2026-06-07", "totalBlocks": 148, "bip110Blocks": 4 }
]
  • theDate — calendar date (YYYY-MM-DD)
  • totalBlocks — total blocks mined that day
  • bip110Blocks — blocks with the BIP-110 signal bit set

The endpoint is available to all API subscribers. Full documentation at bitcoin-data.com/scalar.html.

What to Watch

The August 2026 UASF date is a hard deadline in the sense that UASF-ready nodes will begin enforcing BIP-110 rules on that date with or without miner support. Whether that enforcement has any economic consequence depends entirely on how many nodes and wallets have actually upgraded — a number that is difficult to measure in advance.

The more decisive signal to watch for is whether any large mining pool begins signaling. Foundry USA and Antpool together account for a substantial share of global hashrate; a decision by either to signal would move the daily percentage from low single digits into meaningful territory within days. Conversely, explicit public statements from major pools against signaling would effectively end the miner lock-in path, leaving the UASF mechanism as the only route to activation — and dramatically raising the stakes of the August deadline.

BGeometrics will continue updating this data daily. The coming weeks will be telling — whether signaling accelerates toward the lock-in threshold, stalls at current levels, or draws explicit rejections from major pools will shape how the August deadline plays out.