From 3b085911fac7f4c883e54bb716538e2acd9af297 Mon Sep 17 00:00:00 2001 From: Aere Network Date: Fri, 11 Sep 2026 12:39:33 +0300 Subject: [PATCH] RUN-A-NODE.md: dated note (2026-09-11) on the bootnodes: the second accepts only its configured peers; a node behind NAT keeps one peer and Besu does not fetch transaction-bearing bodies from a single busy peer; forward the P2P port and set --p2p-host --- RUN-A-NODE.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/RUN-A-NODE.md b/RUN-A-NODE.md index 0a8bf24..c24e3c7 100644 --- a/RUN-A-NODE.md +++ b/RUN-A-NODE.md @@ -306,6 +306,16 @@ enode://a4b90d4f5fc7758814d41acfe00f6a2516683f3d3052410091b894d014dbb2184d6158da live address: only your own `net_peerCount` proves they are up. If both are unreachable, write to office@aere.network with the subject "bootnode" for a current enode by return. +Measured 2026-09-11: the second bootnode currently accepts connections only from its own configured +peers, so in practice your first peer is the first bootnode. A node that cannot receive inbound +connections (behind NAT without a forwarded port) keeps that single peer, and Besu does not fetch the +bodies of blocks that carry transactions from a single busy peer: the log repeats +`Unable to retrieve blocks for block numbers ... Restarting after short delay` and the import crawls. +Forward your P2P port (30303 by default) and, when you run the manual command below, add +`--p2p-host=` so that peers can bond with you; once discovery works the node reaches the +rest of the network on its own (measured the same day with ten peers: about 1,300 blocks per second +from genesis, no body failures). + `--sync-mode=FULL` is deliberate. Chain 2800 runs QBFT with a half second block period, so the head 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