BIP-110

Every number comes from our own infrastructure. External trackers are linked only for comparison.

This page no longer reports a live event. It is the closed record of the SHA-256d BIP-110 fork, from block 961,631, the last block both chains shared, to block 961,639, the last block the fork produced under Bitcoin's proof of work. Every panel is served from a committed archive rather than from a feed, nothing polls, and nothing updates.

The Stratum signalling history is a separate fixed archive covering August 4 to 30, 2026: the whole life of the fork, and the two days past it that hold the moment the last pool signalling for it moved to another chain.

Versions as they stood over the record. The fleet has not changed since.

The unpruned archival node lets us rebuild derived series from the chain. The Knots vantage enforced BIP-110, so at height 961,632 it rejected the majority chain and began following the fork as its active chain. It is the only listed node that followed that fork, and the only reason we can account for the fork block by block.

That vantage stands at 961,639 and has not moved since. The BIP-110 chain continues above it under a different proof-of-work function: the released client sets the BLAKE2b fork height to 961,640, one block above the last block this vantage accepted, and requires the first block under the new rules to carry the coinbase headline 8-30 NYPost Deride And Conquer. Following that chain would have meant upgrading this vantage to the client that validates BLAKE2b, released on 2026-09-02. We chose not to, so the record stops where the old rules do. The absence of later blocks here follows from that choice, not from anything we know about that chain.

The signalling series, pool attribution, and majority-chain ledger came from the archival node's headers and blocks. We decoded each coinbase and matched it against a pinned snapshot of the mining-pool dataset. An unmatched coinbase is labelled Unknown.

At heights 961,632 through 963,647, BIP-110 required the versionbits top pattern 001 with bit 4 set. An enforcing node rejected any other header with bad-version-reduced_data, and a later signalling block built on a rejected one also fell outside the BIP-valid branch. We applied that rule to the majority chain to produce the enforcing view.

The fork ledger comes from the Knots vantage, where the fork is still that node's active chain. We scanned its blocks and decoded their coinbases with the same pool dataset used for the majority ledger.

The archival node follows the majority chain, so it only ever knew fork headers supplied by peers. Its view stopped at height 961,633 on August 8, while the Knots vantage went on to accept eight blocks, ending at 961,639. That gap is not a fault. It is what following the other chain means. This record takes the fork from the Knots vantage throughout.

Above the window's close at 963,647 the mandatory rule constrained nothing, so the majority blocks recorded there are not marked rejected. We mark them as off the BIP-valid branch, which is a statement about what they descend from rather than a verdict any node reached. Our enforcing node never evaluated them, because it was not following that chain.

Read-only listeners collected mining.notify jobs from public pool endpoints without submitting work. Raw JSON-RPC frames were sealed daily as zstd archives with SHA-256 manifests and copied to the archive host hourly.

A job signals BIP-110 when its version field (the 6th parameter of mining.notify) carries the versionbits top pattern 001 (0x20000000) with bit 4 set (0x10), giving version 0x20000010. This shows a pool's intent, not whether it enforces BIP-110. A pool can change the bit between jobs without producing a block.

The archive covers 25 endpoints from 2026-08-04 04:50:03 UTC through 2026-08-30 23:59:57 UTC: 653 sealed archives, 2,733,928 jobs, of which 161,007 carried bit 4. Only finalised *.jsonl.zst archives with matching SHA-256 checksum files are included. Active files are excluded.

The page is served from static files under /archive/split/, built once and committed. Their manifest carries the record's bounds, a SHA-256 for every file, and the provenance of each part. The live feeds that used to drive this page have been retired.

Every one of these describes the record itself. The chain-tips panel was retired with the feeds: it showed where three nodes sit today, which is a live view rather than a fact about a closed record.