Our Nodes
Why sync the honest way
Most dashboards read someone else's API. Some run nodes bootstrapped from downloaded snapshots — trusting whoever built the snapshot. Ours validated every block from each chain's genesis era forward across the P2P network, on a small server we operate. A syncing bar on this page is not a weakness; it is what verification actually looks like. When a chain shows at tip, every number derived from it on this site traces to consensus rules our own software enforced.
The nodes are pruned (they keep recent blocks plus all headers), which is why we also run a forward-only archiver: fees and block telemetry are captured live into our own database as each block arrives, because pruned history cannot be re-read later. That archive's start dates are permanent, honest facts:
| chain | fee/telemetry series starts | captured since | headers (difficulty/hashrate) history |
|---|---|---|---|
| DOGE | block 5,810,448 | 2026-09-15 | deepening toward genesis |
| LTC | block 2,385,884 (captured live during the sync itself) | 2026-09-15 | deepening toward genesis |
| BTC | block 602,342 (~Dec 2019) | 2026-09-18 | full, from headers |
What runs on top
A Rust pipeline computes the site's indicators from these nodes' headers and publishes them at /api/chain/{btc,ltc,doge} with the recipe and SHA-256 seals inside every response. It machine-checks its mathematical invariants on every start and refuses to publish if any fail. A chain in initial sync gets no indicator feed at all — we withhold rather than present historical numbers as live.
Difficulty Pressure · Kether Fast Ribbon · Hash Ribbons · Glossary