Skip to content

cleanup: trim Level6 to Hydration, drop PAsset paseo, rename metaspan → interweb#74

Merged
hitchho merged 1 commit into
mainfrom
cleanup/level6-trim-and-metaspan-rename
May 13, 2026
Merged

cleanup: trim Level6 to Hydration, drop PAsset paseo, rename metaspan → interweb#74
hitchho merged 1 commit into
mainfrom
cleanup/level6-trim-and-metaspan-rename

Conversation

@hitchho
Copy link
Copy Markdown
Collaborator

@hitchho hitchho commented May 13, 2026

Summary

Three independent threads landing together because they touch overlapping config files.

1. Drop dead Level6 services from services_rpc.json

Every member's ServiceAssignments.Level6 already collapsed to ["Hydration"] in an earlier commit, but the service definitions for the abandoned chains stayed in services_rpc.json. Removing them:

  • Acala, Ajuna, Bifrost-Polkadot, Nexus, Kilt, Moonbeam, Mythos, Polimec, Unique, Xcavate
  • PAsset-Hub-Paseo, ETH-PAsset-Hub-Paseo

12 entries gone. Hydration is the only Level6 service that remains.

This subsumes #72 (which proposed Kilt/Mythos/Polimec/Xcavate + PAsset paseo). #72 currently conflicts against main because the member-side cleanup landed separately in between; this PR rebases that intent cleanly and goes the rest of the way.

2. Drop PAsset paseo from member Paseo assignments

PAsset-Hub-Paseo + ETH-PAsset-Hub-Paseo removed from each of the 7 members' Paseo service list to match the service-side removal.

3. Rename metaspaninterweb

Operator is continuing under the new name. The matrix room in alerts.json already had interweb set up; this catches the remaining references:

  • services.json: 6 operator-allowlist mentions
  • alerts.json telegram.members: 1
  • scripts/sync_bootnodes.py: DROP_MEMBERS list + a doc comment

Diff size

5 files changed, 16 insertions(+), 268 deletions(-)

Test plan

🤖 Generated with Claude Code

… → interweb

Three independent threads landing together because they all touch the same
config files and would otherwise interleave noisily.

**1. services_rpc.json: drop dead Level6 entries.**
Member ServiceAssignments already collapsed every operator's Level6 down to
`["Hydration"]`, but the service definitions for the now-unused chains
lingered in services_rpc.json. Removing the 10 dangling Level6 entries
(Acala, Ajuna, Bifrost-Polkadot, Nexus, Kilt, Moonbeam, Mythos, Polimec,
Unique, Xcavate) plus PAsset-Hub-Paseo and ETH-PAsset-Hub-Paseo. Hydration
stays as the only Level6 service.

This is essentially #72 (which proposed removing Kilt/Mythos/Polimec/Xcavate
+ PAsset paseo) plus the rest of the unused Level6 set. #72 currently
conflicts against main because the member-side cleanup landed separately
in between.

**2. members_professional.json: drop PAsset paseo from Paseo assignments.**
Every member's Paseo list still referenced PAsset-Hub-Paseo and
ETH-PAsset-Hub-Paseo even though those services are being removed. 7
members updated.

**3. metaspan → interweb rename.**
Operator is continuing under the new name. The matrix room in alerts.json
already had `interweb` set up; this catches the remaining references:
- services.json: 6 operator-allowlist mentions
- alerts.json telegram.members: 1
- scripts/sync_bootnodes.py: DROP_MEMBERS list + a doc comment

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@hitchho hitchho merged commit 43b8800 into main May 13, 2026
1 check passed
hitchho added a commit that referenced this pull request May 13, 2026
These are outputs of `scripts/bootnode_coverage.py` and
`scripts/probe_bootnodes.py`. Committing them means:

- they go stale the moment anyone edits bootnodes.json (PRs #73 and #74
  immediately invalidated both), and
- every regeneration produces a noisy diff against an artefact nobody
  reads from the repo.

Removing both files and adding them to `.gitignore`. Generate locally
with the scripts when you want a current snapshot.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
hitchho added a commit that referenced this pull request May 13, 2026
After landing #73 (typo / stale peer-id fixes) and #74 (Level6 / PAsset /
metaspan cleanup), bootyspector swept the current `bootnodes.json` at
60s timeout with the retry-with-jitter path; 23 multiaddrs still failed
to establish a substrate-level connection on two attempts. Removing them.

Going from **211 endpoints → 188 working** (89%).

Breakdown of what was removed:

**amforc TCP — 12 entries.** Every amforc TCP listener fails substrate
protocol negotiation with `MultistreamSelectError`. WSS works on all
amforc networks; TCP is consistently broken across all 12 networks they
serve. Likely the TCP listeners aren't running the substrate p2p stack.

**amforc/encointer-kusama — also the WSS.** Both transports failed
(`tcp/30333/wss` and `tcp/30338`). The encointer-kusama WSS was the
one I added from chainspec in #73; it's not reachable either. amforc
loses encointer-kusama coverage entirely.

**stakeplus shared-host TCP — 3 entries** on `boot.stake.plus`:
asset-hub-paseo `:44333`, encointer-kusama `:36333`, paseo `:43333`.
Time out with no specific dial-failure event.

**radiumblock/polkadot — both transports** (`:30333` tcp, `:30335` wss).
The whole `polkadot-bootnode.radiumblock.com` polkadot bootnode appears
to be down; radiumblock loses polkadot coverage entirely.

**radiumblock/coretime-polkadot WSS.** TCP variant works; WSS times out.

**radiumblock/hydration WSS, dwellir/hydration WSS.** Both were
chainspec-sourced additions (#73); both fail in practice.

**radiumblock/coretime-polkadot WSS.** Same.

Also removing 4 now-empty operator entries: amforc/asset-hub-paseo,
stakeplus/asset-hub-paseo, amforc/encointer-kusama, radiumblock/polkadot.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant