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

203 lines
7.2 KiB
Markdown

# Comprehensive Consistency Review Report
**Last Updated:** 2026-01-31
**Document Version:** 1.0
**Status:** Active Documentation
---
**Date**: $(date)
**Scope**: Full review of proxmox deployment project and source smom-dbis-138 project
## Executive Summary
This review examines consistency between:
- **Proxmox Deployment Project**: `/home/intlc/projects/proxmox/smom-dbis-138-proxmox`
- **Source Project**: `/home/intlc/projects/smom-dbis-138`
## ✅ Consistent Elements
### 1. Chain ID
- ✅ Both projects use **Chain ID 138**
- ✅ Source: `config/genesis.json`, `config/chain138.json`
- ✅ Proxmox: Referenced in documentation and configuration
### 2. Configuration Files
-**genesis.json**: Present in both projects
-**permissions-nodes.toml**: Present in both projects
-**permissions-accounts.toml**: Present in both projects
-**config-validator.toml**: Present in both projects
-**config-sentry.toml**: Present in both projects
-**RPC Config Files**:
- `config-rpc-core.toml`
- `config-rpc-perm.toml`
- `config-rpc-public.toml`
### 3. Service Structure
- ✅ Both projects have the same service structure:
- oracle-publisher
- financial-tokenization
- ccip-monitor
## ⚠️ Inconsistencies Found
### 1. IP Address References (CRITICAL)
**Issue**: Source project contains references to old IP range `10.3.1.X` instead of current `192.168.11.X`
**Files with Old IP References**:
1. `scripts/generate-static-nodes.sh` - Contains `10.3.1.4:30303` references
2. `scripts/deployment/configure-firefly-cacti.sh` - Contains `RPC_URL_CHAIN138="http://10.3.1.4:8545"`
3. `scripts/deployment/deploy-contracts-once-ready.sh` - Contains `10.3.1.4:8545` SSH tunnel
4. `scripts/deployment/DEPLOY_FROM_PROXY.md` - Contains multiple `10.3.1.4` references
5. `terraform/phases/phase2/README.md` - Contains `10.3.1.4` references
**Recommendation**: Update all `10.3.1.X` references to `192.168.11.X` in source project:
- Main RPC endpoint: `10.3.1.4``192.168.11.250` (or load-balanced endpoint)
- Static nodes generation: Update IP mappings
### 2. Validator Key Count Mismatch (HIGH PRIORITY)
**Issue**:
- **Source Project**: 4 validator keys
- **Proxmox Project**: Expects 5 validators (VMID 1000-1004)
**Impact**: Cannot deploy 5 validators without 5th validator key
**Recommendation**:
1. Generate 5th validator key in source project, OR
2. Update proxmox project to use 4 validators (VMID 1000-1003)
**Current State**:
- Proxmox config: `VALIDATOR_COUNT=5` (1000-1004)
- Source keys: 4 directories in `keys/validators/`
### 3. VMID References (EXPECTED - NO ISSUE)
**Status**: ✅ Expected
- Source project does NOT contain VMID references (deployment-specific)
- This is correct - VMIDs are only relevant for Proxmox deployment
### 4. Network Configuration Examples (INFORMATIONAL)
**Issue**: `network.conf.example` in proxmox project still uses `10.3.1.X` as example
**Status**: ⚠️ Minor - Example file only
- Active `network.conf` uses correct `192.168.11.X`
- Example file should be updated for consistency
## Detailed Findings by Category
### A. Network Configuration
| Aspect | Source Project | Proxmox Project | Status |
|--------|---------------|-----------------|--------|
| Chain ID | 138 | 138 | ✅ Match |
| Primary IP Range | 10.3.1.X (old) | 192.168.11.X (current) | ⚠️ Mismatch |
| RPC Endpoint | 10.3.1.4:8545 | 192.168.11.250:8545 | ⚠️ Mismatch |
| Gateway | Not specified | 192.168.11.1 | N/A |
### B. Node Counts
| Node Type | Source Project | Proxmox Project | Status |
|-----------|---------------|-----------------|--------|
| Validators | 4 keys | 5 nodes (1000-1004) | ⚠️ Mismatch |
| Sentries | Not specified | 4 nodes (1500-1503) | ✅ Expected |
| RPC | Not specified | 3 nodes (2500-2502) | ✅ Expected |
### C. Configuration Files
| File | Source Project | Proxmox Project | Status |
|------|---------------|-----------------|--------|
| genesis.json | ✅ Present | ✅ Referenced | ✅ Match |
| config-validator.toml | ✅ Present | ✅ Referenced | ✅ Match |
| config-sentry.toml | ✅ Present | ✅ Referenced | ✅ Match |
| config-rpc-*.toml | ✅ Present (3 files) | ✅ Referenced | ✅ Match |
| permissions-nodes.toml | ✅ Present | ✅ Referenced | ✅ Match |
| permissions-accounts.toml | ✅ Present | ✅ Referenced | ✅ Match |
### D. Services
| Service | Source Project | Proxmox Project | Status |
|---------|---------------|-----------------|--------|
| oracle-publisher | ✅ Present | ✅ Referenced | ✅ Match |
| financial-tokenization | ✅ Present | ✅ Referenced | ✅ Match |
| ccip-monitor | ✅ Present | ✅ Referenced | ✅ Match |
## Recommendations
### Immediate Actions Required
1. **Update IP Addresses in Source Project** (Priority: HIGH)
- Update all `10.3.1.4` references to `192.168.11.250` (RPC endpoint)
- Update static-nodes generation script
- Update deployment documentation
2. **Resolve Validator Key Count** (Priority: HIGH)
- Option A: Generate 5th validator key in source project
- Option B: Update proxmox config to use 4 validators
- **Recommendation**: Generate 5th key for better fault tolerance
3. **Update Network Configuration Example** (Priority: LOW)
- Update `network.conf.example` to use `192.168.11.X` as example
### Best Practices
1. **Documentation Alignment**
- Source project documentation should reference deployment-agnostic endpoints
- Use variables or configuration files for IP addresses
- Avoid hardcoding IP addresses in scripts
2. **Configuration Management**
- Use environment variables for deployment-specific values (IPs, VMIDs)
- Keep source project deployment-agnostic where possible
- Use configuration files to bridge source and deployment projects
## Files Requiring Updates
### Source Project (`smom-dbis-138`)
1. `scripts/generate-static-nodes.sh`
- Update IP addresses from `10.3.1.4` to `192.168.11.X`
2. `scripts/deployment/configure-firefly-cacti.sh`
- Update `RPC_URL_CHAIN138` from `http://10.3.1.4:8545` to `http://192.168.11.250:8545`
3. `scripts/deployment/deploy-contracts-once-ready.sh`
- Update SSH tunnel target from `10.3.1.4:8545` to `192.168.11.250:8545`
4. `scripts/deployment/DEPLOY_FROM_PROXY.md`
- Update all IP address examples from `10.3.1.X` to `192.168.11.X`
5. `terraform/phases/phase2/README.md`
- Update IP address references
6. **Generate 5th Validator Key**
- Create `keys/validators/validator-5/` directory with keys
### Proxmox Project (`smom-dbis-138-proxmox`)
1. `config/network.conf.example`
- Update example IPs from `10.3.1.X` to `192.168.11.X`
## Summary
| Category | Status | Issues Found |
|----------|--------|--------------|
| Chain ID | ✅ Consistent | 0 |
| Configuration Files | ✅ Consistent | 0 |
| Services | ✅ Consistent | 0 |
| IP Addresses | ⚠️ Inconsistent | 5 files need updates |
| Validator Count | ⚠️ Mismatch | 4 vs 5 |
| VMID References | ✅ Correct | 0 (expected) |
**Overall Status**: ⚠️ **Mostly Consistent** - 2 critical issues need resolution
## Next Steps
1. Generate 5th validator key in source project
2. Update IP addresses in source project scripts and documentation
3. Update network.conf.example in proxmox project
4. Re-run consistency check to verify fixes