fix(node): refresh mainnet bootnodes (+shellfish) and raise default runtime-cache-size to 8#1479
Merged
enthusiastmartin merged 11 commits intoJun 30, 2026
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the shipped Hydration mainnet chainspec bootnode multiaddrs so that nodes syncing from node/res/hydradx.json can successfully discover peers via the official p2p-01/02/03.hydra.hydradx.io bootnodes.
Changes:
- Replaces the
/p2p/<peer-id>segments forp2p-01,p2p-02, andp2p-03bootnodes while keeping hostnames and/tcp/30333unchanged.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…thrashes WASM cache on archive/RPC nodes)
…ation / --version)
# Conflicts: # Cargo.lock # node/Cargo.toml
00bf670
into
galacticcouncil:master
4 of 7 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bootnodes (
node/res/hydradx.json)The official mainnet bootnodes (
p2p-01/02/03.hydra.hydradx.io) advertised peer IDs of decommissioned collators and were unreachable — a node syncing from the shipped chainspec gets 0 usable peers from them. Their DNS now points at the current operator nodes; this updates the peer IDs to match (hostnames/ports unchanged, only/p2p/<peer-id>), and adds a 4th operator bootnode:p2p-01.hydra.hydradx.io12D3KooWDZvr1trejZptZq9aPYE5owDrHAwGhNivw8bpAXkxVGXXp2p-02.hydra.hydradx.io12D3KooWJchDHSvN8xuerTwJm7GEdEHQ299yGerJ4S1fud5kWUgJp2p-03.hydra.hydradx.io12D3KooWJr2g3EFNqcF6z9rUy2EeRracoWUyDUtksdv2CUVxwrqZhdx.shellfish.hydration.cloud(:30334)12D3KooWLbvUYQ2dr5uKsAZZP3FLPba1QEHfSEzsXFwsM9uH712SEach peer ID was verified against the running node (
system_localPeerId). The community bootnodes in the same list (helikon / stake.plus / dwellir / radiumblock) are currently unreachable too, but left untouched for their operators to restore.Default
--runtime-cache-size2 → 8 (node/src/service.rs)The upstream default of 2 is too small for nodes serving historical state across runtime upgrades (archive / RPC / indexer-backing): the hot working set spans several runtime versions, so a cache of 2 re-prepares a WASM runtime on nearly every cross-version query, burning CPU and exhausting the instance pool (
Ran out of free WASM instances) under load — stalling block import. This treats the upstream default (2) as "unset" and uses 8 in the executor builder; any explicit--runtime-cache-sizeis honored. Pruned/validating nodes that don't serve historical state are unaffected in practice.Version
node/Cargo.toml+Cargo.lock:hydradx15.0.2 → 15.0.3 (node-crate bump for CI's version-bump check).