diff --git a/RUN-A-NODE.md b/RUN-A-NODE.md
index cce6df5..93e2318 100644
--- a/RUN-A-NODE.md
+++ b/RUN-A-NODE.md
@@ -132,7 +132,8 @@ enode by return. Everything else on this page works without one; discovery is th
 that needs it.
 
 `--sync-mode=FULL` is deliberate. Chain 2800 runs QBFT with a half second block period, so the head
-is around twelve million blocks and climbing by two per second. Full sync from block 0 is the mode
+was about 12.2 million blocks when this was written (2026-08-03), passed 14.6 million on 2026-08-19,
+and climbs by roughly two per second; read the live height with eth_blockNumber. Full sync from block 0 is the mode
 that actually verifies the history we publish, which is the point of this repository. Snap sync
 against a QBFT chain trusts a peer for the state and verifies far less.
 
@@ -193,8 +194,8 @@ the two.
 
 ## What the two bootnodes are, and what they are not
 
-They are two full nodes that are **not** in the validator set. Chain 2800 seals blocks with seven
-QBFT validators, and none of the seven is listed here, on purpose. Publishing a validator's p2p
+They are two full nodes that are **not** in the validator set. Chain 2800 seals blocks with nine
+QBFT validators (seven until 2026-08-09), and none of the nine is listed here, on purpose. Publishing a validator's p2p
 address hands an attacker a target whose downtime costs the network consensus headroom, which is why
 sentry style architectures exist. The two nodes above carry no consensus responsibility: if both are
 taken down, new nodes cannot bootstrap until they are replaced, and block production is unaffected.