Drivechain ObservatoryConnecting…Waiting for data.
  1. 1What is a drivechain?
  2. 2Blocks: the heartbeat
  3. 3Slots and sidechains
  4. 4Creating a sidechain
  5. 5Deposits and the treasury
  6. 6Withdrawals by miner vote
  7. 7Blind merged mining
  8. 8How we know
Concept 8 of 8

How we know

Where every number on this site comes from, and how sure we are.

4 min read

Where the numbers come from

A Betanet node and the official enforcerEnforcerThe program that checks the BIP300/301 rules alongside the L1 node. The Observatory reads its official API. run side by side. A monitor asks them what is happening, block after block, and records every answer exactly as received. The Observatory keeps a checked copy of those records, and this site turns them into the lessons you have read.

From the network to this page: node and enforcer, monitor, Observatory, this siteBetanet nodeblocks, headersEnforcerBIP300/301 APIMonitorrecords readingsObservatoryverified copyThis siteexplains it
Nothing on this site queries the network directly: it reads the Observatory's copy of what the monitor recorded.

Three kinds of answer

Not every value is equally certain, so each live panel says which kind it shows:

  • Observed in a blockThe official sources reported this for a specific L1 block. A fact the sources reported for a specific block, such as a deposit or a merged-mining commitment.
  • Read at a stable tipA reading of current state, taken while the chain tip stayed the same before and after. It shows the state at that moment, not the history of how it got there. A reading of current state, such as a treasury balance or a vote count, taken while the chain tip did not move. It tells you the state at that moment, not how it got there.
  • UnknownThis value is missing, conflicting, or was read while the chain moved. Nothing is guessed to fill the gap. The reading was missing, conflicting, or taken while the chain moved. The Observatory never fills a gap by guessing or by replaying the protocol rules itself.

Every value also has See the proof: the exact evidenceEvidenceThe exact record the monitor captured from the enforcer or node, kept so anyone can check what a page shows. record behind it, which anyone can download and check.

Live on Betanet

Is the monitor keeping up?

Loading live data…

Live on Betanet

How good is the data?

Loading live data…

What we cannot see

The enforcer's official API reports current state and per-block facts, but not the full history of every vote. So the site shows vote counts as they were read, never the individual votes in between. It does not watch the sidechains themselves, so it cannot confirm that a deposit was credited on L2. And when the monitor was not looking, a missing record does not mean nothing happened: that is why coverageCoverageWhich blocks the monitor has actually recorded. Without coverage, a missing record does not mean nothing happened. matters.

Live on Betanet

Exactly which software produced this data

Loading live data…

Live on Betanet

Take the data with you

Every list on this site can be downloaded, up to 10,000 records per file. The file says if it was cut short.

Developers can use the same API directly: API reference.

Go deeper: how the chain itself is checked

The Observatory selects the chain from the enforcer's tip readings and checks it against the node's headers: each block's accumulated work must equal its parent's plus its own. If the node and the enforcer disagree, the chain is not certified and the disagreement is shown. If a record changes after it was imported, synchronization stops and says so instead of continuing silently.

Every block and event has a permanent page. Try the live activity and follow any "Proof" link.

Check yourself

The site shows no deposit into a sidechain during a period when the monitor was offline. What can you conclude?

Read the source

The rules in this lesson come from these documents and code:

Ask an AI assistant about this concept

Opens your assistant with a question about this concept and its sources already written. AI answers can be wrong: check them against the sources above. Your question goes to the assistant you choose, not to us.