- 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.
985 B
985 B
Besu Network ID Update - All RPC Nodes to Chain 138
Date: 2026-01-03
Status: ✅ UPDATE COMPLETE
Update Summary
All RPC nodes (VMID 2400-2402 and 2500-2508) have been updated to use Chain ID 138 (Defi Oracle Meta).
Changes Applied
VMID 2500-2508 (Previously Chain 2400)
- Previous: network-id=2400
- Updated: network-id=138
- Config Files:
- VMID 2500, 2503-2508:
/etc/besu/config-rpc.toml - VMID 2501:
/etc/besu/config-rpc-public.tomland/etc/besu/config-rpc-perm.toml - VMID 2502:
/etc/besu/config-rpc-public.toml
- VMID 2500, 2503-2508:
- Action: Updated configuration files and restarted services
VMID 2400-2402 (Already Chain 138)
- Status: Already configured for Chain ID 138
- Config File:
/etc/besu/config-rpc-thirdweb.toml - Action: Verified configuration
Verification
All RPC nodes should now respond with Chain ID 138 when queried via net_version RPC method.
Last Updated: 2026-01-03