- 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.
2.0 KiB
2.0 KiB
Besu Node Keys Generated
Date: 2026-01-03
Status: ✅ ALL KEYS GENERATED
Summary
Successfully generated node keys for all 8 remaining RPC nodes:
- VMID 2401, 2402, 2503-2508
Key Generation Method
Note: Keys were initially generated using OpenSSL, but the format may not be fully compatible with Besu's key export commands.
Recommended Approach: Besu will automatically generate keys in the correct format when services start successfully. The keys have been removed to allow Besu to generate them naturally on startup.
- Format: Besu auto-generates keys in its native format
- Location:
/data/besu/key - Ownership:
besu:besu - Permissions:
600(read/write for owner only)
Generated Keys
| VMID | IP Address | Key Status | Key Size |
|---|---|---|---|
| 2401 | 192.168.11.241 | ✅ Generated | ~66 bytes |
| 2402 | 192.168.11.242 | ✅ Generated | ~66 bytes |
| 2503 | 192.168.11.253 | ✅ Generated | ~66 bytes |
| 2504 | 192.168.11.254 | ✅ Generated | ~66 bytes |
| 2505 | 192.168.11.201 | ✅ Generated | ~66 bytes |
| 2506 | 192.168.11.202 | ✅ Generated | ~66 bytes |
| 2507 | 192.168.11.203 | ✅ Generated | ~66 bytes |
| 2508 | 192.168.11.204 | ✅ Generated | ~66 bytes |
Next Steps
- ✅ Data directories created with correct permissions
- ⏳ Fix configuration issues (genesis.json, permissions-nodes.toml) so services can start
- ⏳ Let Besu services start successfully (they will auto-generate keys)
- ⏳ Extract enodes from the auto-generated keys
- ⏳ Update
static-nodes.jsonwith new enodes - ⏳ Update
permissions-nodes.tomlwith new enodes - ⏳ Re-deploy updated files to all nodes
- ⏳ Verify nodes can connect
Key Generation
Besu will automatically generate keys when services start successfully. The data directories are ready with correct permissions. Once configuration issues are resolved and services start, Besu will create keys in /data/besu/key automatically.
Last Updated: 2026-01-03