Files

defiQUG cb47cce074 Complete markdown files cleanup and organization

- Organized 252 files across project
- Root directory: 187 → 2 files (98.9% reduction)
- Moved configuration guides to docs/04-configuration/
- Moved troubleshooting guides to docs/09-troubleshooting/
- Moved quick start guides to docs/01-getting-started/
- Moved reports to reports/ directory
- Archived temporary files
- Generated comprehensive reports and documentation
- Created maintenance scripts and guides

All files organized according to established standards.

2026-01-06 01:46:25 -08:00

4.1 KiB

Raw Blame History

Besu Enode Configuration Update - Chain 138 RPC Nodes

Date: 2026-01-03
Status: ✅ UPDATE COMPLETE

Summary

Updated static-nodes.json and permissions-nodes.toml files to include all known RPC nodes (VMID 2400, 2500, 2501, 2502) for Chain 138 (Defi Oracle Meta).

Changes Applied

static-nodes.json

Previous: Only 5 validators (VMID 1000-1004)
Updated: 5 validators + 4 known RPC nodes (VMID 2400, 2500, 2501, 2502)
Total: 9 enodes

permissions-nodes.toml

Previous: 5 validators + 4 old RPC nodes (150-153) + 4 known RPC nodes (2400, 2500, 2501, 2502)
Updated: 5 validators + 4 known RPC nodes (VMID 2400, 2500, 2501, 2502)
Removed: Old RPC nodes (150-153) - no longer relevant
Total: 9 enodes

Enodes Included

Validators (5)

VMID 1000 (192.168.11.100): enode://2221dd9fc65c9082d4a937832cba9f6759981888df6798407c390bd153f4332c152ea5d03dd9d9cda74d7990fb3479a5c4ba7166269322be9790eed9ebdcfe24@192.168.11.100:30303
VMID 1001 (192.168.11.101): enode://4e358db339804914d53bec6de23a269aef7be54c2812001025e6a545398ac64b2513a418cd3e2ca06dc57daf5c0aa2fb97c9948b6d7893e2bd51bf67dae97923@192.168.11.101:30303
VMID 1002 (192.168.11.102): enode://0daef7e3041ab3a5d73646ec882410302d63ece279b781be5cfed94c1970aacb438aeafc46d63a630b4ea5f7a0572a3a7edff028b16abc4c76ee84358af8c31f@192.168.11.102:30303
VMID 1003 (192.168.11.103): enode://107e59cb6c5ddf000082ddfd925aa670cba0c6f600c8e3dc5cdd6eb4ca818e0c22e4b33ef605eb4efd76ef29177ca00fd84a79935eccdddd2addbbb26d37a4a4@192.168.11.103:30303
VMID 1004 (192.168.11.104): enode://59844ade9912cee3a609fae1719694c607b30ac60a08532e6b15592524cb5f563f32c30d63e45075e7b9c76170a604f01fc6de02e3102f0f8d1648bf23425c16@192.168.11.104:30303

RPC Nodes (4 - Known)

VMID 2400 (192.168.11.240): enode://38e138ea5a4b0b244e4484b5c327631b5d3c849dcb188ff3d9ff0a8b6ad7edb738303a1a948888c269aa7555e5ff47d75b7b63dbd579d05580b5442b3fa0ebfc@192.168.11.240:30303
VMID 2500 (192.168.11.250): enode://6cdc892fa09afa2b05c21cc9a1193a86cf0d195ce81b02a270d8bb987f78ca98ad90d907670796c90fc6e4eaf3b4cae6c0c15871e2564de063beceb4bbfc6532@192.168.11.250:30303
VMID 2501 (192.168.11.251): enode://07daf3d64079faa3982bc8be7aa86c24ef21eca4565aae4a7fd963c55c728de0639d80663834634edf113b9f047d690232ae23423c64979961db4b6449aa6dfd@192.168.11.251:30303
VMID 2502 (192.168.11.252): enode://83eb8c172034afd72846740921f748c77780c3cc0cea45604348ba859bc3a47187e24e5fad7f74e5fe353e86fd35ab7c37f02cfbb8299a850a190b40968bd8e2@192.168.11.252:30303

RPC Nodes (Pending - Missing Enodes)

VMID 2401 (192.168.11.241): ⏳ Key not generated yet
VMID 2402 (192.168.11.242): ⏳ Key not generated yet
VMID 2503 (192.168.11.253): ⏳ Key not generated yet
VMID 2504 (192.168.11.254): ⏳ Key not generated yet
VMID 2505 (192.168.11.201): ⏳ Key not generated yet
VMID 2506 (192.168.11.202): ⏳ Key not generated yet
VMID 2507 (192.168.11.203): ⏳ Key not generated yet
VMID 2508 (192.168.11.204): ⏳ Key not generated yet

Files Deployed

RPC Nodes (VMID 2400-2402, 2500-2508)

/genesis/static-nodes.json - Updated
/permissions/permissions-nodes.toml - Updated

Validators (VMID 1000-1004)

/etc/besu/permissions-nodes.toml - Updated (static-nodes.json not changed on validators)

Next Steps

Once the remaining RPC nodes (2401, 2402, 2503-2508) generate their keys and start successfully:

Extract their enodes using:

curl -X POST -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"admin_nodeInfo","params":[],"id":1}' \
  http://<NODE_IP>:8545

Add the extracted enodes to both static-nodes.json and permissions-nodes.toml
Re-deploy the updated files to all nodes
Restart Besu services to apply changes

Important Notes

All nodes in static-nodes.json MUST be in permissions-nodes.toml
With permissioning enabled, nodes can only connect to nodes listed in permissions-nodes.toml
static-nodes.json is used for initial peer discovery
permissions-nodes.toml enforces which nodes are allowed to connect

Last Updated: 2026-01-03

4.1 KiB Raw Blame History