Files
proxmox/docs/06-besu/RPC_NODES_COMPLETE_INFO.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

3.0 KiB

RPC Nodes - Complete Enode and IP Address Information

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


Date: 2025-01-18
Proxmox Host: ml110 (192.168.11.10)


IP Addresses (Verified from Container Configs)

VMID IP Address Hostname Status
2101 192.168.11.211 besu-rpc-core-1 Running
2201 192.168.11.221 besu-rpc-public-1 Running
2301 192.168.11.232 besu-rpc-private-1 ⏸️ Stopped
2303 192.168.11.233 besu-rpc-ali-0x8a Running
2304 192.168.11.234 besu-rpc-ali-0x1 Running
2305 192.168.11.235 besu-rpc-luis-0x8a Running
2306 192.168.11.236 besu-rpc-luis-0x1 Running
2307 192.168.11.237 besu-rpc-putu-0x8a Running
2308 192.168.11.238 besu-rpc-putu-0x1 Running
2400 192.168.11.240 thirdweb-rpc-1 Running
2401 192.168.11.241 besu-rpc-thirdweb-0x8a-1 Running
2402 192.168.11.242 besu-rpc-thirdweb-0x8a-2 Running
2403 192.168.11.243 besu-rpc-thirdweb-0x8a-3 Running

Enodes (From static-nodes.json and Collection)

Confirmed Enodes

VMID 2101 (besu-rpc-core-1)

enode://6cdc892fa09afa2b05c21cc9a1193a86cf0d195ce81b02a270d8bb987f78ca98ad90d907670796c90fc6e4eaf3b4cae6c0c15871e2564de063beceb4bbfc6532@192.168.11.211:30303

VMID 2401 (besu-rpc-thirdweb-0x8a-1)

enode://38e138ea5a4b0b244e4484b5c327631b5d3c849dcb188ff3d9ff0a8b6ad7edb738303a1a948888c269aa7555e5ff47d75b7b63dbd579d05580b5442b3fa0ebfc@192.168.11.241:30303

Pending Collection

The following nodes need enodes collected (admin RPC API was not accessible via external calls):

  • 2201 (192.168.11.221)
  • 2303-2308 (192.168.11.233-238)
  • 2400 (192.168.11.240)
  • 2402-2403 (192.168.11.242-243)

How to Collect Remaining Enodes

Method 1: Via pct exec (from Proxmox host)

PROXMOX_HOST="192.168.11.10"

for vmid in 2201 2303 2304 2305 2306 2307 2308 2400 2402 2403; do
    echo "VMID $vmid:"
    ssh root@$PROXMOX_HOST "pct exec $vmid -- curl -s -X POST -H 'Content-Type: application/json' --data '{\"jsonrpc\":\"2.0\",\"method\":\"admin_nodeInfo\",\"params\":[],\"id\":1}' http://localhost:8545 | jq -r '.result.enode'"
done

Method 2: Check Besu Config/Logs

# Check Besu config for enode
ssh root@192.168.11.10 "pct exec <VMID> -- cat /etc/besu/config*.toml | grep -i enode"

# Check Besu logs for enode at startup
ssh root@192.168.11.10 "pct exec <VMID> -- journalctl -u besu -n 100 | grep -i enode"

Method 3: Enable Admin API (if disabled)

If admin API is disabled in Besu config, enable it:

rpc-http-enabled=true
rpc-http-api=["ADMIN","ETH","NET","WEB3"]

Then query:

cast rpc admin_nodeInfo http://<IP>:8545 | jq -r '.enode'

Summary

IPs: All 13 IP addresses collected and verified
Enodes: 2 confirmed (2101, 2401), ⏸️ 10 pending collection


Last Updated: 2025-01-18