Phase 28 mainnet deployment: what's live and what isn't
The UsdcSettlementEscrow contract is deployed and verified on Base Mainnet. Here's the precise status — what's working, what's gated, and what comes next.
The Phase 28 deployment represents the production-shaped v1 of Onchain Rail. The UsdcSettlementEscrow contract is deployed at 0x15E3...44d0 on Base Mainnet (block 45,167,721) and source-verified on Basescan. The sidecar Python client is integrated, the ABI is stable, and the deployment manifest is fully documented.
What is live: the contract itself, the on-chain verification, the sidecar integration, and the full deployment tooling. What is not live: real user funds. The system is explicitly not approved to accept live settlements until all external security reviews complete and the operator key management process is hardened.
The Phase 28 review identified one critical finding: the operator private key was temporarily exposed in a plaintext .env file during the deployment process. That key has been rotated. A hardened key management process — using a dedicated secrets manager and never writing keys to disk — is a pre-requisite for enabling live funds.
The timeline to live funds is gated on three things: completion of the external security review, implementation of the hardened key management process, and a successful end-to-end fund-path exercise on a test deployment. No user capital is at risk while those gates are open.