Deutsch
Français
Español
Português
Italiano
Русский
Türkçe
日本語
한국어
简体中文
Polski
ไทย
Tiếng Việt
Bahasa IndonesiaBTX NETWORK · BY EASYBTX
The BTX node census
A live picture of the public BTX network: how many nodes are up, where they are, how fresh they run, and how many can really serve the chain's signed history. We verify with real requests, then label. Known operators can join the node circle to see the full directory.
[ NETWORK HEALTH ]
Network health
One row per question, each with where its answer came from and when.
Every answer comes from a machine that is not yours: the census asked
and compared, and nothing on your machine checked it, which is what
ATTACHED, NOT CHECKED HERE means. A row older than one hour turns grey,
because a green that is remembered is not a green that is current.
Sources count by who runs them: api.btxscan.io, both witnesses and
this census are one operator (easyBTX/btxscan), and the Byron Bay
explorer is an independent one, so agreement needs both.
Your own node is the only source you do not have to trust. The words
follow the BTX Verdict Spec (btx-verdicts/0.1), a community draft, and
the same rows are public as JSON at /api/network-health.
Rechecked every 30 minutes. The tip is the highest block of the heaviest valid chain the reachable nodes report, read from their own block headers, not from an explorer. Nodes come and go between checks, and we do not always reach every one on a single pass, so these are a live estimate, not an exact count. The real network is larger than what any single vantage point can see at once.
[ ONE CHAIN, OR SEVERAL? ]
Every reachable node is asked for its recent block headers, and nodes are grouped by the chain those headers actually follow. One group means the network agrees. Two groups built past a common block is a split, and both are shown, with height, work since the split and how many nodes follow each, and which chain each pool is paying out on. We do not say which is right. A node's own validation decides that, and the honest number here is that a split exists at all.
[ STRANDED NODES ]
Named nodes that are not keeping up
A node that broadcasts a name is flagged here when the census has measured it more than 6 blocks behind the tip, or on a branch other than the heaviest chain, on checks that span an hour. Below 6 blocks a fork is a mining race that settles by itself, so a node on a short side branch is judged by its distance alone. A node that is closing the distance is syncing, not stuck, and is watched rather than flagged. The "since" time is the first check that saw it stranded: the census checks every 30 minutes but reaches community nodes in turns, so it can trail the real start by a check or two, and it began keeping these streaks in mid-October 2026. If one of these is yours, it is not following the rest of the network, and the chains above show where the network is.
Run BTX v0.34.14 or later. v0.34.15 (6 October) is current and fixes a 0.34.14 catch-up stall. Three consensus checks took effect at block 244,000 on 10 October, and an older node can follow a branch the rest of the network refuses. The version list further down is the live split.
[ THE NETWORK BY CLASS ]
What the reachable nodes offer
Full nodes serve the whole chain, pruned nodes only the recent blocks. An archive advertises serving signed block confirmations, the thing machines without a qualified graphics chip need to follow the chain, and the network's scarcest service today. Advertising is a claim. Serve-verified means the node answered a real request for the attestation of a recent canonical block. We measure, then label.
The only node you fully trust is your own. These are other people's machines, and connecting a light client to one shares your IP and the addresses you look up with whoever runs it. We report what we can measure, we make no promises about who is on the other end.
Run your own BTX node → Share a Mac in Keeper mode → Guard a node you already run →[ NETWORK MAP ]
Coarse locations from the node's IP, rounded on purpose, aggregate only. No addresses are shown or stored for this map. A green dot is a reachable node, red is one that did not answer the last check.
[ SOFTWARE VERSIONS ]
What the reachable nodes on the network are running
Self-reported /BTX:x.y.z/ subversion string, brighter green is a newer build.
[ THE NODES ]
| Node | Height | Chain | Software | Class |
|---|
A name is what a node broadcasts in its user agent (easyNode lets you set one under Settings, and it shows here on the next check). Unnamed nodes get a stable tag. The chain column is measured from the node's own headers; a node marked far behind is parked below the point where the census starts comparing. The letters are handed out again on every check, so a node the census last read on an earlier check shows whether it was on the heaviest chain then, not a letter. No addresses here: those stay in the member directory below.
[ THE SEEDS ]
Seeds are the addresses a new node is told to dial first. One marked shipped is compiled into easyNode's bootstrap list, so while it is down every fresh install spends its first dial on it and only then reaches a node that answers. Uptime is over the whole stored history, so a seed that flaps reads differently from one that died. The tag is the same one the node list uses; addresses stay in the member directory below.
[ THE NODE CIRCLE ]
The full directory, with per-node addresses and live status, is for known operators. A public list of the network's scarcest machines would be an attack map, so the detail view asks who you are: sign in with qID, apply, and Mende approves each member personally. No token, no payment, nothing to buy. Recognition and trust only.
Sign in with qID
Your qID address is your identity here. Private keys never touch this page: the wallet signs a challenge, the page only ever sees the proof.
Apply to join the node circle
Signed in. Tell Mende who you are, in a word or two, and which node is yours if you run one. Approval is personal, curation is the point.
Application received
Your application is in the queue. Mende approves each member personally, so this can take a moment. This page will show the directory once you are in.
This address is not approved for the member directory. The public census above stays fully visible.
Approval queue
| Address | Handle | Note | Applied | Status | Decide |
|---|
| Node | Status | Latency | Height | Class | Archive | Uptime | Last seen | Location | Software |
|---|
Latency is measured from our checker in one location, not from where you are. Archive serve-VERIFIED means the node answered a real request for a recent canonical block's attestation on the last check. Addresses are for the circle: point your own tooling at them, do not republish the list.
Add a node
Run a public BTX node and want it in the directory? Open a submission form and we will add it. We only list a node with its operator's consent, and you can ask to be removed anytime.