Files
proxmox/docs/11-references/NON_EVM_NETWORK_HEALTH_AND_LANE_STATUS.md

2.1 KiB

Non-EVM Network Health And Lane Status

Purpose: Keep two different truths separate:

  • Public network health answers whether Solana, Tron, and XRPL public endpoints respond from this environment.
  • Repo lane status answers how this workspace currently models those networks from the Chain 138 side.

Current operator references

  • Live endpoint check: bash scripts/verify/check-non-evm-network-health.sh --json-out reports/status/non-evm-network-health-latest.json
  • Repo-backed lane report: python3 scripts/verify/build-non-evm-lane-status.py
  • Generated outputs:
    • reports/status/non-evm-network-health-latest.json
    • reports/status/non-evm-lane-status-latest.json
    • reports/status/non-evm-lane-status-latest.md

Repo treatment by lane

Solana

  • The repo treats Solana as the most documented non-EVM GRU lane.
  • The current source of truth is config/solana-gru-bridge-lineup.json.
  • The current recorded live proof is the cAUSDT -> cWAUSDT corridor, with send/confirm evidence and a pending SPL mint inventory follow-up.

Tron

  • The repo currently represents Tron primarily through the Chain 138 TronAdapter contract surface.
  • This is a Chain 138 adapter / relay model, not a native Tron program inventory in the unified deployment reports.
  • Remaining closure work is mainly Chain 138 Blockscout/source publication, not Tron network reachability.

XRPL

  • The repo represents XRPL through the Chain 138 XRPLAdapter, wXRP, and MintBurnController contracts, plus bridge UI and runbook material.
  • This means XRPL is more than a destination label here: the workspace contains the 138-side adapter, the wrapped bridge asset, and controller logic.
  • Remaining closure work is likewise Chain 138 Blockscout/source publication, not XRPL uptime.

Interpretation rule

If a public endpoint is healthy while reports/inventory/DEPLOYED_CONTRACTS_COMPLETION_MATRIX.md still shows NEEDS_BLOCKSCOUT_SOURCE_IMPORT, that means:

  1. the external network is up, and
  2. the repo still has explorer/source-publication work to finish for the related Chain 138 contracts.

Do not treat those as the same problem class.