69 lines
2.7 KiB
Markdown
69 lines
2.7 KiB
Markdown
# Key Deployment Complete
|
|
|
|
**Date**: 2025-12-20
|
|
**Status**: ✅ Keys Deployed, ⚠️ Block Production Pending
|
|
|
|
## Summary
|
|
|
|
Successfully deployed all new keys and configuration files to the running nodes. The network is now using the new validator and node identities, but blocks are not yet being produced.
|
|
|
|
## Deployment Status
|
|
|
|
### ✅ Completed Steps
|
|
|
|
1. **Services Stopped**: All Besu services stopped successfully
|
|
2. **New genesis.json Deployed**: All nodes updated with new extraData containing new validator addresses
|
|
3. **Validator Keys Deployed**: All 5 validator keys copied to `/keys/validators/validator-*/`
|
|
4. **Nodekeys Deployed**: All 12 nodekeys (5 validators + 4 sentries + 3 RPCs) copied to `/data/besu/key`
|
|
5. **Configuration Files Deployed**:
|
|
- `static-nodes.json` with new validator enodes
|
|
- `permissions-nodes.toml` with all 12 node enodes
|
|
6. **Databases Cleared**: All blockchain databases cleared to allow reinitialization with new genesis
|
|
7. **Services Restarted**: All services restarted and running
|
|
|
|
### ✅ Verification Results
|
|
|
|
- **New Validator Address in Use**: ✅
|
|
- Expected: `0x1c25c54bf177ecf9365445706d8b9209e8f1c39b`
|
|
- Found in logs: `0x1c25c54bf177ecf9365445706d8b9209e8f1c39b`
|
|
|
|
- **Service Status**: ✅ All services active
|
|
- Validators: Active
|
|
- Sentries: Active (5 connected peers each)
|
|
- RPC nodes: Active
|
|
|
|
- **Genesis extraData**: ✅ Contains new validator addresses
|
|
|
|
### ⚠️ Current Issue
|
|
|
|
**Block Production**: Blocks are still at 0
|
|
|
|
Despite:
|
|
- New keys deployed correctly
|
|
- New validator addresses in use
|
|
- Services running
|
|
- Peers connected
|
|
|
|
Blocks are not being produced. This is similar to the issue encountered before the key rotation.
|
|
|
|
## Next Steps for Investigation
|
|
|
|
1. **Check QBFT Consensus Configuration**: Verify that validators recognize themselves as validators
|
|
2. **Check Validator Key Usage**: Ensure validator keys are being used for block signing (not just P2P)
|
|
3. **Monitor Validator Logs**: Look for QBFT consensus messages about block proposal
|
|
4. **Verify Validator Set**: Confirm all 5 validators are in the QBFT validator set
|
|
5. **Check Network Connectivity**: Verify validators can communicate with each other through sentries
|
|
|
|
## Key Locations
|
|
|
|
- **Validator Keys**: `/keys/validators/validator-*/key.priv`
|
|
- **Nodekeys**: `/data/besu/key` (used for P2P and block signing)
|
|
- **Genesis**: `/etc/besu/genesis.json`
|
|
- **Static Nodes**: `/etc/besu/static-nodes.json`
|
|
- **Permissions**: `/etc/besu/permissions-nodes.toml`
|
|
|
|
## Notes
|
|
|
|
The deployment was successful from a configuration perspective - all files are in place and services are running with the new keys. The block production issue requires further investigation into QBFT consensus behavior.
|
|
|