bip110.run · Running BIP-110

Running BIP-110. BIP110.RUN

A free public observatory · open-source radar · BIP-110 miner-signal telemetry for the chain.

Live updated —

Support

BIP110 adoption

Live updated —

of the past ··· Bitcoin mined blocks have signaled for BIP-110

every block in that window is a real mined Bitcoin block

Mandatory signaling phase begins in

Live updated —

projected to block ···

Blocks until mandatory phase

Live updated —

until mandatory signaling

BTC_ONCHAIN_DATA:BIP110.D share of mined blocks that are signaling BIP-110

Live updated —

Signaling history

signaling not signaling

⛏️ BIP110 miner leaderboard

thank you 🥹

Recent signaling blocks

BIP-110 blocks

Peer mesh

Knots + BIP-110 peers · hub Austin

POV

from a Knots + BIP-110 node runner

Austin, Texas, USA

BIP-110 Knots — not yet BIP-110. Click here for upgrade instructions Austin hub

Public node share

Live updated —

Of publicly reachable Bitcoin nodes: who runs Core, Knots, and BIP-110 — and how that mix is moving.

Why Core is sliding · since Q3'24

The chart opens with Core dominant on the public mesh. Since then, operators have been leaving for Knots — a client with stricter default relay and filter policy.

The slide steepened around Core v30’s OP_RETURN / datacarrier sticky-default path (policy into the October train · ships Q4'25): many node runners read that as a purpose signal about large data on the main chain, not only a config knob. Knots was the ready exit. BIP-110 / RDTS culture grew inside that Knots migration — gold is nested in Knots, not a fourth client.

Not hashrate. Not private nodes. Not a single-cause proof. Directionally: Core’s share of the reachable public mesh fell while Knots (and BIP-aligned Knots) rose. Hover the dotted marks for dates.