proxmox/docs/06-besu/UPDATES_REQUIRED_BEFORE_CONTINUING.md

Updates Required Before Continuing

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

---

Date: 2026-01-18
Status: Review Required

---

Status Changes Detected

✅ ENODE_COLLECTION_2402_2403_STATUS.md - Updated by user

• Status changed: BLOCKED → RESOLVED
• Services confirmed running on VMIDs 2402 and 2403

---

Files That Need Updates

1. ⚠️ COMPLETE_REMAINING_TASKS_LIST.md

Location: docs/06-besu/COMPLETE_REMAINING_TASKS_LIST.md

Current Status (Line 10-14):

### 1. Collect Enodes for 2402 and 2403 ⏸️

**Status**: Blocked - Besu service not installed on these containers

**Action**: Investigate container purpose and Besu installation method

Should Update To:

### 1. Collect Enodes for 2402 and 2403 ⏸️

**Status**: Services running - Enode collection pending

**Action**: Collect enodes for 2402 and 2403 (ADMIN API not enabled, need alternative method)

---

2. ⚠️ CHAT_TASKS_COMPLETE_REVIEW.md

Location: docs/06-besu/CHAT_TASKS_COMPLETE_REVIEW.md

Current Status (Line 122-128):

### 1. Collect Enodes for 2402 and 2403 ⚠️

**Task**: Collect enodes for 2402 and 2403 and add to allowlist

**Status**: ⏸️ **PENDING**

**Issue**: Besu services are inactive on VMIDs 2402 and 2403
- VMID 2402: Besu service inactive, RPC port 8545 closed
- VMID 2403: Besu service inactive, RPC port 8545 closed

Should Update To:

### 1. Collect Enodes for 2402 and 2403 ⚠️

**Task**: Collect enodes for 2402 and 2403 and add to allowlist

**Status**: ⏸️ **PENDING**

**Issue**: ADMIN API not available on ThirdWeb RPC nodes (by design)
- VMID 2402: Service running, need alternative enode collection method
- VMID 2403: Service running, need alternative enode collection method

**Solution**: Use alternative methods - DO NOT enable ADMIN API on ThirdWeb nodes
- Extract from Besu logs, or
- Check static-nodes.json on nodes, or
- Query via core RPC node admin_peers

---

3. ⚠️ permissions-nodes.toml

Location: smom-dbis-138/config/permissions-nodes.toml

Current Status:

• Has: 13 nodes (validators + RPC: 2101, 2201, 2301, 2303-2308, 2400, 2401)
• Missing: 2402, 2403

Action Required:

• Collect enodes for 2402 and 2403
• Add to nodes-allowlist array
• Will complete allowlist to 15/15 nodes (100%)

---

Investigation Findings

Admin API Status

VMID 2402: rpc-http-api=["ETH","NET","WEB3","DEBUG","TRACE"] VMID 2403: rpc-http-api=["ETH","NET","WEB3","DEBUG","TRACE"]

Issue: ADMIN API is only available on core RPC nodes (2101), not on ThirdWeb RPC nodes (2402, 2403)

Solutions (Alternative Methods):

1. Extract from Besu logs:

   pct exec 2402 -- journalctl -u besu-rpc -n 1000 | grep -i 'enode://' | head -1
   pct exec 2403 -- journalctl -u besu-rpc -n 1000 | grep -i 'enode://' | head -1
   

2. Check static-nodes.json on the node:

   pct exec 2402 -- cat /var/lib/besu/static-nodes.json | jq '.[]' | grep -i "192.168.11.242"
   pct exec 2403 -- cat /var/lib/besu/static-nodes.json | jq '.[]' | grep -i "192.168.11.243"
   

3. Query from a core RPC node (if 2402/2403 are peers):

   # Via admin_peers on core RPC node (2101)
   curl -X POST -H "Content-Type: application/json" \
     --data '{"jsonrpc":"2.0","method":"admin_peers","params":[],"id":1}' \
     http://192.168.11.211:8545 | jq '.result[] | select(.id | contains("192.168.11.242"))'
   

4. Extract from node key file (if accessible):

   pct exec 2402 -- find /var/lib/besu -name "key" -o -name "*key*"
   

---

Current Allowlist Status

Total Nodes: 15

• Validators: 5 (100-104)
• RPC Nodes: 10 (2101, 2201, 2301, 2303-2308, 2400-2403)

In Allowlist: 13/15 (87%)

• ✅ All validators (5/5)
• ✅ RPC: 2101, 2201, 2301, 2303-2308, 2400, 2401 (8/10)
• ⏸️ Missing: 2402, 2403 (2/10)

---

Recommended Actions

Priority 1: Update Documentation

1. ✅ Update COMPLETE_REMAINING_TASKS_LIST.md status
2. ✅ Update CHAT_TASKS_COMPLETE_REVIEW.md status

Priority 2: Collect Enodes

1. Use alternative method (ADMIN API not available on ThirdWeb RPC nodes)
   • Extract from Besu logs, or
   • Check static-nodes.json on nodes, or
   • Query via core RPC node admin_peers
2. Collect enodes for 2402 and 2403
3. Add to permissions-nodes.toml

Priority 3: Deploy Updated Allowlist

1. Deploy permissions-nodes.toml to all nodes
2. Verify allowlist configuration

---

Next Steps

1. Update documentation to reflect current status
2. Collect enodes for 2402 and 2403 using alternative methods:
   • Check Besu logs for enode strings
   • Check static-nodes.json on the nodes
   • Query via core RPC node admin_peers (if nodes are peers)
3. Update allowlist with collected enodes
4. Deploy and verify allowlist configuration

Note: ADMIN API is intentionally limited to core RPC nodes for security. ThirdWeb RPC nodes use standard RPC APIs only.

---

Last Updated: 2026-01-18