The
Keepers.
Every Quai block lives on machines someone chose to run. Below is a live census of those nodes, and the roll of keepers who prove theirs: we check each one against the chain itself, with a Merkle state proof, every few minutes.
77
go-quai nodes keeping Quai alive right now
1 of them has stepped forward as verified keepers. Run a node? Become one ↓
p2p census as of 15:19 UTC · 54 distinct hosts · 48/77 returned the canonical header at #10,596,301
The upgrade wave
Versions as announced on the p2p network (libp2p identify), not self-reported. 23.4% of identified nodes run v0.56.1, the newest release seen.
- v0.56.1 18 · 23.4%
- v0.56.0 51 · 66.2%
- v0.55.0 3 · 3.9%
- v0.54.0 1 · 1.3%
- v0.52.0 2 · 2.6%
- v0.34.0 2 · 2.6%
The roll
Verified keepers only. Each one passed every check below in the last few minutes, including a state proof checked against the chain (◆ proof-verified). ✓ claimed means the keeper also signed with the node's own p2p key. Uptime is the share of our checks it passed over 30 days.
- mattman◆ proof-verifiedv0.56.166.7%2026-10-130 blk
Honors
- 01Oldest keeper: mattman (verified since 2026-10-13)
Become a keeper
Any go-quai node on mainnet can report here under any name. Pick a tag and a secret; the first login reserves the tag for that secret.
--node.quaistats "YourTag:a-secret-you-choose@quaination.xyz/keepers" --rpc.http-addr 0.0.0.0 --rpc.http-vhosts '*'
- Open TCP 9200 (Cyprus-1 RPC) to the internet, and port-forward it if you're behind a router. We verify you by calling it.
- Custom RPC port? Put it in the path:
@quaination.xyz/keepers/9300. - Know what you're opening. Port 9200 makes your node a public RPC: anyone can query it or send it transactions. go-quai exposes only the
net,web3andquaimodules by default (no admin or wallet access). - Your p2p port must be reachable (default 4002) so the census can see your node.
- Not showing up? Check your node's status with your tag and secret. Your node's own log only says
Stats login failed. - On the roll? Claim your node by signing a challenge with its p2p key (one openssl command, the key never leaves your machine) to add the ✓ claimed badge.
How we verify, every time
Before we accept a single stat, and again every ~10 minutes plus at random times between:
- 01A real node lives at your IP. Our crawler must have found a live go-quai node on the Quai p2p network at the address your stats come from.
- 02Your RPC answers. We call your node's own RPC directly. Nothing you report is taken on faith.
- 03Your chain is the chain. Your head must be within 10 blocks of the canonical head, and your block a couple behind it must match the canonical block.
- 04Your numbers agree. The height in your stats, your RPC, and your p2p node must all line up on the same block.
- 05Your state is real. We ask for a quai_getProof Merkle proof of a random account and storage slots at that exact block, and verify it ourselves against the block's state root. A node can't fake one.
What this can't prove: CPU, RAM and disk are whatever your node says, so we label them self-reported and never rank them. The canonical chain comes from rpc.quai.network. A node that fails a check simply leaves the roll until it passes again; we never shame a failing node publicly.
independent community project · not financial advice · not affiliated with the Quai foundation or Kipper
the creed · the burn · the last block · the keepers · the deep work · break the chain · light your ember · the armory · fire on X · scripture cards · the tip jar · the oath · soap.qu.ai · the docs