Configuration & operations
Explicit activation gates and the operational responsibilities around them.
On this page
Runtime configuration
| Variable | Purpose |
|---|---|
| DATABASE_URL | PostgreSQL connection for accounts, payments, execution and the worker |
| SIMULATION_ENABLED=true | Enable simulated execution and continuous risk processing |
| PAYMENTS_ENABLED=true | Enable checkout after a valid receiving address is configured |
| USDC_RECIPIENT / USDC_RECIPIENT_<chainId> | Shared or per-network EVM checkout recipient |
| RPC_URL_999 / RPC_URL_42161 / RPC_URL_137 | Optional HyperEVM, Arbitrum and Polygon RPC overrides |
| PAYOUT_REVIEWS_ENABLED=true | Allow the server-only approval helper with a funding reference; does not enable treasury transfers |
This documents supported variables, not the secret values or live environment of a deployment. A boolean flag does not configure custody, validate operational solvency or implement a missing transfer path.
Payout review is server-only
The operator helper validates an explicit decision, actor, reason and unique review identity. Approval additionally requires the activation flag and funding reference. There is no public approval API. Rejection and an owner’s pending-request cancellation remain possible without enabling approvals.
Approval of a credit request appends the trader allocation to the credit ledger. Approval of a wallet request records review status and leaves it Awaiting transfer. No paid transaction or receipt is manufactured.
Worker and accounting operations
Keep the risk process supervised and monitor its heartbeat, scan lag, funding backlog and stale-source errors. Missing boundary oracles require reconciliation; later prices must not be silently substituted.
New exposure is blocked when required funding or risk health is unavailable. Cancellation remains a database operation and reduce-only exits retain their protective allowance. A reached account loss floor persists before a refund or later mark recovery.
Verification before changes
The repository includes pure accounting tests, deterministic market-feed tests and isolated-database regression coverage for ownership, retries, fills, liquidity budgets, funding, margin segregation, backstops, analytics and payout accounting. Run the relevant checks when changing those paths.
Production payment activation also requires receiver validation and an end-to-end settlement check. Wallet payout activation requires its own custody, solvency, transfer and reconciliation work. Existing tests are not a blanket security or availability guarantee.