Check it yourself.
Everywhere worth looking, labelled by how far it sits from the chain itself. This list grows. If something here goes stale or wrong, that is worth knowing about.
How to read the labels
A site publishing chain data is not automatically a source of it. Most are repeating something they read somewhere else, and the further a number travels the more chances it has to go wrong. So each entry says where its data actually comes from.
- Chain
- Runs a node. The number comes off the chain itself.
- One hop
- Reads someone else's node or API and presents it.
- Primary
- The document, the code, or the person's own words.
- Commentary
- Interpretation. Useful, but check it against the rows above.
Live chain status
Note that a normal block explorer cannot help you here. Explorers running Bitcoin Core rules follow the most-work chain and will not show you the RDTS tip at all. You need something reading a node that enforces consensusrules=rdts.
-
110explorer.comChain
Self-describes as a read-only explorer over a local Bitcoin Knots RDTS node, with the mainnet tip pulled from public APIs for comparison only. That is the provenance statement you want to see. It was still completing initial block download when we last checked, so it may show no data yet.
-
bip110.runChain
Dashboard, timeline, consensus, node, blockspam, library, coalition, census and equipment. The most complete picture of what is happening anywhere, and the reason this site does not build a dashboard.
-
bip110.org/monitorChain
Live miner signaling status, difficulty period progress, and historical signaling rates, on the site attached to the BIP's own author.
-
BIP-110 Fork MonitorOne hop
Side-by-side Core versus Knots comparison, reading from mempool.space and bip110.run.
-
BIP-110 CountdownOne hop
Countdown and status view.
Primary sources
If a claim on this site is wrong, one of these is where you prove it.
-
BIP-110, the text itselfPrimary
Reduced Data Temporary Softfork, authored by Dathon Ohm,
Layer: Consensus (soft fork), status Closed. Reading the header alone settles most of what gets argued about. There is no mention of proof-of-work or BLAKE2b anywhere in it.
-
bip110.orgPrimary
The proposal's own site, including a guide for switching chains. Distinct from bip110.run, and easy to confuse.
-
Bitcoin Knots releasesPrimary
Release notes and binaries.
29.3.knots20260508 and newer ship RDTS directly; 29.3.knots20260507 is the same release without it. Running it is not enough on its own, you also set consensusrules=rdts in bitcoin.conf.
-
Start9 on navigating RDTS activationCommentary
Practical operator-facing writeup from a node vendor.
People worth reading directly
Their own words, not somebody's summary of them. Listing someone is not agreement with everything they say, and it is certainly not their endorsement of this site.
- @LukeDashjrPrimaryWrote the 2017 proof-of-work change code the current contingency is rebased from. Removed as BIP editor on 10 August over conflict-of-interest concerns tied to BIP-110, which he did not author.
- @cguida6PrimaryChris Guida. Rebased the proof-of-work code onto a recent Knots codebase. The clearest public statements on what is and is not scheduled come from here.
- @mattkratterCommentaryBitcoin University. Takes no sponsorships. A model for how to do this without becoming an influencer.
- @hodlonautCommentary
- @GrassFedBitcoinCommentary
- @Roughnecks110PrimaryMined the first BIP-110 signaling block at 961,632, and the blocks that extended the RDTS chain afterward.
Models we are learning from
-
SeedSignerPrimary
Publishes the design and a parts list instead of selling hardware, and keeps a list of community vendors with no official endorsement, no preloaded software, and a voluntary expectation that sellers give something back. The clearest working example of building something useful in Bitcoin without becoming a shop or a shill. Their own writing is also candid that donations alone have not made the project sustainable.