Files

Deploy to Phoenix / deploy (push) Has been cancelled

Details

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

3.3 KiB

Raw Permalink Blame History

Node List Deployment - Final Status

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation

Date: 2025-01-18
Status: ✅ DEPLOYMENT COMPLETE FOR RUNNING NODES

Deployment Summary

✅ Successfully Deployed

Validators (5 nodes):

✅ VMID 1000 (192.168.11.100) - Files deployed
✅ VMID 1001 (192.168.11.101) - Files deployed
✅ VMID 1002 (192.168.11.102) - Files deployed
✅ VMID 1003 (192.168.11.103) - Files deployed
✅ VMID 1004 (192.168.11.104) - Files deployed

Sentries (4 nodes):

✅ VMID 1500 (192.168.11.150) - Files deployed
✅ VMID 1501 (192.168.11.151) - Files deployed
✅ VMID 1502 (192.168.11.152) - Files deployed
✅ VMID 1503 (192.168.11.153) - Files deployed

RPC Nodes (4 nodes):

✅ VMID 2101 (192.168.11.211) - Files deployed
✅ VMID 2400 (192.168.11.240) - Files deployed
✅ VMID 2401 (192.168.11.241) - Files deployed
✅ VMID 2402 (192.168.11.242) - Files deployed

Total Deployed: 13/13 running nodes ✅ COMPLETE

⏸️ Nodes Not Deployed (Stopped)

The following nodes are stopped and will receive files when started:

VMID 2500 (192.168.11.250) - Stopped
VMID 2501 (192.168.11.251) - Stopped
VMID 2502 (192.168.11.252) - Stopped
VMID 2505 (192.168.11.201) - Stopped
VMID 2506 (192.168.11.202) - Stopped
VMID 2507 (192.168.11.203) - Stopped
VMID 2508 (192.168.11.204) - Stopped

Note: These nodes will need deployment when they are started.

Files Deployed

On Each Node:

/var/lib/besu/static-nodes.json (15 enodes)
/var/lib/besu/permissions/permissioned-nodes.json (15 enodes)

File Contents: Both files contain identical 15 unique enodes with matching IP addresses.

Next Steps

1. Complete RPC Node Deployment ⏳

Finish deployment to VMIDs 2400, 2401, 2402 (in progress)

2. Fix p2p-host Configuration ⚠️

VMID 2101: Update p2p-host from 0.0.0.0 to 192.168.11.211

Action:

# Edit config file
ssh root@192.168.11.10
pct exec 2101 -- sed -i 's/p2p-host="0.0.0.0"/p2p-host="192.168.11.211"/' /etc/besu/config-rpc-core.toml

Verify all nodes: Run scripts/besu/verify-p2p-host-config.sh to check all nodes

3. Restart Besu Services 🔄

After fixing p2p-host, restart services:

# For each node type
pct exec <VMID> -- systemctl restart besu-validator.service
pct exec <VMID> -- systemctl restart besu-sentry.service
pct exec <VMID> -- systemctl restart besu-rpc.service

4. Verify Peer Connections ✅

After restart, verify connections:

cast rpc admin_peers http://192.168.11.250:8545

Expected: Multiple peer connections showing all nodes from static-nodes.json

Verification Checklist

Files deployed to running validators (5/5)
Files deployed to running sentries (4/4)
Files deployed to VMID 2101
Files deployed to running RPC nodes (2400-2402) ✅
p2p-host fixed on VMID 2101
p2p-host verified on all other nodes
Services restarted on all nodes
Peer connections verified

Known Issues

p2p-host Configuration

VMID 2101: p2p-host="0.0.0.0" needs to be p2p-host="192.168.11.211"

Impact: Enode will show incorrect IP, preventing peer connections.

Status: ⚠️ Needs Fix

Status: ✅ DEPLOYMENT 100% COMPLETE FOR ALL RUNNING NODES

3.3 KiB Raw Permalink Blame History