Files
proxmox/docs/04-configuration/verification-evidence/ENODE_IP_VERIFICATION_20260208.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.4 KiB

Enode and IP Verification — 2026-02-08

Script: scripts/verify/verify-besu-enodes-and-ips.sh
Sources: config/besu-node-lists/static-nodes.json, config/besu-node-lists/permissions-nodes.toml
IP reference: config/ip-addresses.conf, BESU_NODES_FILE_REFERENCE.md


Summary

Check Result
Static vs permissions OK — Same enodes, same IPs in both files
IP to VMID mapping OK — All 15 listed IPs match expected VMID mapping
Duplicate node IDs FAIL — Same enode key used for .240 (2400) and .241 (2401)
Missing from lists WARN — 192.168.11.154 (VMID 1504) add when enode available

Duplicate enode key (.240 and .241)

Finding: The same enode key is used for both 192.168.11.240 (VMID 2400) and 192.168.11.241 (VMID 2401). Each Besu node must have a unique node key.

Fix: Get the real enode for VMID 2401 and update both files.

  1. Get enode from VMID 2401 (from host that can reach the node). If 2401 is on ml110 (192.168.11.10):

    ssh root@192.168.11.10 "pct exec 2401 -- curl -s -X POST -H 'Content-Type: application/json' --data '{\"jsonrpc\":\"2.0\",\"method\":\"admin_nodeInfo\",\"params\":[],\"id\":1}' http://127.0.0.1:8545" | jq -r '.result.enode'
    

    If on r630-01 (192.168.11.11), use that host instead.

  2. Replace the .241 entry in both static-nodes.json and permissions-nodes.toml with the returned enode (ensure IP in enode is 192.168.11.241).

  3. Redeploy: bash scripts/fix-validator-permissioning-toml.sh and/or bash scripts/deploy-besu-node-lists-to-all.sh

  4. Re-run: bash scripts/verify/verify-besu-enodes-and-ips.sh


IP to VMID reference (verified)

IP VMID Role
192.168.11.100 1000 Validator
192.168.11.101 1001 Validator
192.168.11.102 1002 Validator
192.168.11.103 1003 Validator
192.168.11.104 1004 Validator
192.168.11.150 1500 Sentry
192.168.11.151 1501 Sentry
192.168.11.152 1502 Sentry
192.168.11.153 1503 Sentry
192.168.11.154 1504 Sentry (not in lists yet)
192.168.11.211 2101 RPC Core 1
192.168.11.212 2102 RPC Core 2
192.168.11.221 2201 RPC Public 1
192.168.11.232 2301 RPC Private 1
192.168.11.233 2303 RPC (Ali)
192.168.11.240 2400 ThirdWeb RPC primary
192.168.11.241 2401 ThirdWeb RPC 1