Monad Bootstrap Peers Update - Required After Authenticated UDP Activation
Overview
Following Authenticated UDP activation, Monad Foundation announced that bootstrap peers must be updated on all nodes so they can join and remain connected. Operators should replace existing [[bootstrap.peers]] entries with the latest signed records from Foundation-published configs.
Updated records are published separately for validators and full nodes on both mainnet and testnet. A critical requirement is to avoid duplicate entries for the same secp256k1_pubkey, because duplicates can create inconsistent peering behavior and complicate post-restart troubleshooting.
Context
Operationally, only a service restart is required and no hard reset is needed. Hard reset workflows wipe peers.toml through reset-workspace behavior, forcing peer cache rebuild and raising reconnection risk when bootstrap signatures are outdated.
Update bootstrap peers, restart services, and verify the node rejoins with stable connectivity and healthy participation on the target network.
- Authenticated UDP activation required refreshed bootstrap peers for network connectivity
- Replace all existing [[bootstrap.peers]] entries; do not keep duplicates per pubkey
- Restart is enough; hard reset is discouraged because it wipes the peering cache
- After any reset, outdated peer signatures can cause join failures until corrected