diff --git a/RUN-A-NODE.md b/RUN-A-NODE.md
index 2a363be..3f8cf4e 100644
--- a/RUN-A-NODE.md
+++ b/RUN-A-NODE.md
@@ -302,6 +302,16 @@ address hands an attacker a target whose downtime costs the network consensus he
 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.
 
+**Update, 2026-08-28.** The first bootnode (37.27.216.110) now also serves the devp2p
+`snap/1` protocol (`SnapServer ... Bonsai full flat db` in its startup log, capability list
+`[eth/68..71], [istanbul/100], [snap/1]`). A client that chooses `--sync-mode=SNAP` against it
+downloads headers plus the state at the pivot instead of replaying every historic block body,
+which on this chain of empty blocks removes most of the multi-day full-sync cost. Honest limits,
+measured versus not: the server capability and the public endpoint answering are measured today;
+a complete stranger's snap sync to head against it has not yet been run, and the one-command
+`run-node.sh` path deliberately stays `--sync-mode=FULL`, because a validating node that replayed
+every block is a stronger statement than one that trusted a pivot.
+
 A written address is not a live address. This file cannot prove the bootnodes are up at the moment
 you read it; only your own `net_peerCount` can.