Skip to main content

​
Verify operator localnet readiness

Use this guide when you already know you are on an operator-backed localnet path and want to decide whether the environment is ready to proceed.

​
Prerequisites

  • You have already classified the task as node-operations work.
  • You know whether you are running localnet.loopback or localnet.compose.
  • You can inspect the environment that owns the operator-backed baseline.

​
1. Confirm the mode and URL pair

Do not mix loopback and Compose-network URLs in the same run.
ModeETH_RPC_URLDEPLOYMENT_SERVICE_URL
localnet.loopbackhttp://127.0.0.1:8545http://127.0.0.1:4040
localnet.composehttp://ethereum:8545http://deployment-service:4040
If the pair is mixed, fix the environment before you debug anything else.

​
2. Confirm the fixed ownership contracts

Verify these facts before you treat later state as trustworthy:
  • APP_CONFIG is /opt/dexlabs.
  • deployment metadata is read from ${APP_CONFIG}/ethereum/addresses.json.
  • deployment-service is the only writer of that file.
  • the standard localnet baseline still uses REPORT_TYPE=SELF.

​
3. Verify the shared services

Check the services that the operator-backed baseline depends on:
ServiceWhat to verify
chain + deployment-serviceboth are reachable for the mode you chose
Postgresreachable before operator and KYC startup
Redisreachable before background coordination work begins
PCCS and AESMreachable when you are validating an SGX-capable runtime
oracle sourceprovides the symbols expected by the baseline
KYC mock or release sourcereachable before KYC-backed readiness checks

​
4. Verify the node-facing endpoints

Confirm that the node-facing APIs are healthy once the environment starts them:
EndpointExpected localnet posture
operator REST APIanswers on the standard localnet port 8080
KYC REST APIanswers on the standard localnet port 8090
If those endpoints are not healthy, do not treat later request or sequencing failures as application-level bugs yet.

​
5. Verify baseline and reset posture

Make sure the environment still follows the canonical baseline model:
  • deploy created the clean baseline
  • reset returns to that deployment baseline
  • release and registration effects are applied after reset
  • you are not depending on an ad-hoc snapshot or inherited drift

​
6. Decide the next route

If you find…Use this next
a mode or contract mismatchNode Operations Reference
a public-versus-restricted surface questionOperator & Restricted APIs
a general public-docs mismatchTroubleshooting or Support Channels
a need for a private operator procedureSupport Channels
Last modified on April 12, 2026