Files
proxmox/docs/06-besu/NODE_LIST_FIX_COMPLETE.md
defiQUG fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands
- CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround
- CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check
- NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere
- MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates
- LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-12 15:46:57 -08:00

2.6 KiB

Node List Fix - Complete

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation


Date: 2025-01-18
Status: RECONCILIATION AND CLEANUP COMPLETE


Issues Found and Fixed

1. Old/Migrated Nodes Removed

Removed 8 old/migrated enodes:

  • 192.168.11.221 (old 2201, migrated from 2501)
  • 192.168.11.232 (old 2301, migrated from 2502)
  • 192.168.11.233 (old 2303, migrated from 2503)
  • 192.168.11.234 (old 2304, migrated from 2504)
  • 192.168.11.235 (old 2305, migrated from 2505)
  • 192.168.11.236 (old 2306, migrated from 2506)
  • 192.168.11.237 (old 2307, migrated from 2507)
  • 192.168.11.238 (old 2308, migrated from 2508)

Reason: These VMIDs (2201, 2301, 2303-2308) do not exist in current Proxmox. They were from an old migration plan that was not completed or was reverted. Current configuration uses original 2500s VMIDs.


2. Current Valid Nodes Kept

Kept valid enodes:

  • Validators: 1000-1004 (5 nodes)
  • RPC: 2101, 2401 (2 nodes)

Total kept: 7 enodes


3. Missing Nodes

Missing from file (expected but not present):

  • Sentries: 1500-1503 (4 nodes) - Need enodes
  • RPC: 2400, 2402, 2500-2508 (11 nodes) - Some stopped, need enodes from running

Note: These will need enodes collected when nodes are running or can be added when started.


Files Updated

static-nodes.json

Before: 15 enodes (7 valid + 8 old/migrated) After: 7 enodes (all valid, old entries removed)

Contents: Only current valid nodes with matching IPs from current VMID configuration.

permissioned-nodes.json

Status: Synchronized with static-nodes.json


Current File Contents

static-nodes.json contains:

  • 5 Validator enodes (100-104)
  • 2 RPC enodes (2101, 2401)

Total: 7 enodes


Next Steps

To Complete Node List

  1. Collect Missing Sentry Enodes:

    • Query sentries 1500-1503 when running
    • Add their enodes to the file
  2. Collect Missing RPC Enodes:

    • Query running RPC nodes (2400, 2402, etc.)
    • Add their enodes to the file
  3. Update When Stopped Nodes Start:

    • When nodes 2500-2508 are started, collect their enodes
    • Add to both static-nodes.json and permissioned-nodes.json

Reconciliation Summary

Removed: 8 old/migrated entries (221, 232-238)
Kept: 7 valid entries (validators + RPC nodes 2101, 2401)
Cleaned: No duplicates, no errors
Synchronized: Both files match

Result: Clean, accurate node list with only current valid entries.


Status: FILES CLEANED AND RECONCILED