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.5 KiB

Raw Blame History

DeFi Oracle Meta Mainnet Connectivity - Issue Resolved

Date: 2026-01-09
ChainID: 138 (0x8a)
Status: ✅ ALL RPC ENDPOINTS OPERATIONAL

Summary

The DeFi Oracle Meta Mainnet (ChainID 138) is now accessible. All RPC endpoints are responding correctly.

✅ Working RPC Endpoints

Internal Network Endpoints

RPC Translator (ThirdWeb Compatible)
- URL: http://192.168.11.240:9545
- VMID: 2400
- Status: ✅ Working
- ChainID: 0x8a (138)
Core RPC
- URL: http://192.168.11.250:8545
- VMID: 2500
- Status: ✅ Working
- ChainID: 0x8a (138)
Permissioned RPC
- URL: http://192.168.11.251:8545
- VMID: 2501
- Status: ✅ Working
- ChainID: 0x8a (138)
Public RPC
- URL: http://192.168.11.252:8545
- VMID: 2502
- Status: ✅ Working
- ChainID: 0x8a (138)

Service Status

Besu RPC Nodes

VMID 2500: ✅ Container running, service active
VMID 2501: ✅ Container running, service active
VMID 2502: ✅ Container running, service active

RPC Translator

VMID 2400: ✅ Container running, service active
All dependencies: ✅ Healthy (Besu, Redis, Web3Signer, Vault)

Configuration Verified

Besu RPC Configuration (VMID 2500)

RPC HTTP: Enabled on 0.0.0.0:8545
RPC WebSocket: Enabled on 0.0.0.0:8546
APIs: ETH, NET, WEB3, TXPOOL, QBFT, ADMIN, DEBUG, TRACE
Status: ✅ Properly configured

Testing Commands

Test ChainID

curl -X POST http://192.168.11.250:8545 \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
# Expected: {"jsonrpc":"2.0","result":"0x8a","id":1}

Test Block Number

curl -X POST http://192.168.11.250:8545 \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Test RPC Translator

curl -X POST http://192.168.11.240:9545 \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
# Expected: {"jsonrpc":"2.0","result":"0x8a","id":1}

Public Endpoints (via Cloudflare Tunnel)

These endpoints should also be accessible via Cloudflare tunnels:

https://rpc-core.d-bis.org
https://rpc-http-pub.d-bis.org
https://rpc-http-prv.d-bis.org
https://rpc.public-0138.defi-oracle.io

Resolution

The connectivity issue appears to have been temporary or related to network routing. All RPC endpoints are now responding correctly:

✅ All Besu RPC nodes are running and accessible
✅ RPC Translator is operational
✅ All services are healthy
✅ ChainID 138 (0x8a) confirmed on all endpoints

Recommendations

Use RPC Translator for ThirdWeb compatibility:
- Endpoint: http://192.168.11.240:9545
- Supports eth_sendTransaction with automatic signing
Use Core RPC for internal services:
- Endpoint: http://192.168.11.250:8545
- Full API access including ADMIN and DEBUG
Monitor service health:
- Check RPC Translator: curl http://192.168.11.240:9545/health
- Check Besu services: systemctl status besu-rpc on each VMID

References

RPC Node Configuration: docs/05-network/RPC_NODE_TYPES_ARCHITECTURE.md
VMID Allocation: reports/VMID_IP_ADDRESS_LIST.md
RPC Translator Status: reports/VMID2400_ALL_STEPS_COMPLETE.md

Status: ✅ RESOLVED - All endpoints operational

3.5 KiB Raw Blame History