Files
proxmox/docs/00-meta/OPERATOR_CONTEXT_VERIFIED.md
defiQUG b3a8fe4496
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
chore: sync all changes to Gitea
- Config, docs, scripts, and backup manifests
- Submodule refs unchanged (m = modified content in submodules)

Made-with: Cursor
2026-03-02 11:37:34 -08:00

1.0 KiB

Operator context — verified (remember)

Last verified: 2026-03-01
Purpose: Record that this machine has LAN and Proxmox host access so operator scripts can be run from here.

LAN access — OK

  • Proxmox hosts (SSH 22): 192.168.11.10, 192.168.11.11, 192.168.11.12 — reachable
  • Proxmox API (8006): All three hosts — reachable
  • Chain 138 RPC (Core): 192.168.11.211:8545 — reachable, eth_chainId = 0x8a (138)
  • NPMplus: 192.168.11.167:80 — reachable
  • Blockscout API: 192.168.11.140:4000 — reachable

Proxmox host access — OK

  • SSH: Login to root@192.168.11.10 (ml110) succeeded (key-based).
  • Operator scripts that require LAN + Proxmox (e.g. run-all-operator-tasks-from-lan.sh, contract verification, backup) can be run from this machine when .env has the required secrets (e.g. NPM_PASSWORD, PRIVATE_KEY).

Re-verify anytime: From repo root, run TCP checks to the above IPs/ports or use ./scripts/verify/check-contracts-on-chain-138.sh (uses RPC 192.168.11.211:8545).