Configuration reference

Public browsing needs no environment file. Connected services need specific configuration in the process that uses it. The tables below list names and behavior; they contain no credentials.

Web settings visible to the browser

Next embeds NEXT_PUBLIC_ values in the client build. Put only public configuration in these fields, and rebuild when changing a value used by the browser.

HTTP and WebSocket endpoint lists do not imply automatic runtime failover. The source currently keeps automatic rotation off.

Local contract overrides

Production normally uses the generated deployment manifest. These app overrides exist for a deliberately matched local fork:

The market package also accepts GameArena address/from-block in its programmatic configuration. The current web/src/lib/env.ts does not expose matching NEXT_PUBLIC_GAME_ARENA_* variables. Do not invent environment support from a TypeScript option name.

Shared records

DATABASE_URL is server-only. Configure it on web and the ops actors that need the same records. The driver uses a small connection pool and requires TLS for hosts other than local loopback.

Without it, public market browsing works, but X relay, stored social activity, durable agent memory, Lucky draws, arcade score posting and the duel settler worklist are unavailable or degraded.

AI on web and ops

Resolution order is custom endpoint, selected provider's direct key, Gateway, then unavailable. The checked-in default model is anthropic/claude-opus-5; this is a source default, not a claim that your account can access it.

Configure web for Sensei and Studio Dry read. Configure ops independently for AI runner execution. A credential on one host does not configure the other. Dry-run trading can still make model calls.

Strategy runner

With no key, explicit strategy ids can still be inspected and reported when the required stores are available. With neither ids nor key, the runner idles. Missing AI credentials make AI strategies hold. Missing or stale risk data and unresolved execution attempts also hold new submissions. Keep the strategy runner and X executor on distinct keys, with one process writing each key.

X: web and relay use different credentials

The callback origin must match the browser origin that writes OAuth cookies. Starting on another origin redirects to the configured canonical origin.

The relay's session credential is sensitive account access. Do not publish it or put it in a client variable. Startup resolves the session's stable account id; a configured-handle mismatch prevents the relay from starting. Turning replies off does not turn trading off.

Testnet onboarding faucet on web

Fund the dedicated wallet with Shannon STT. The address and readable balance are returned by GET /api/faucet; the API never returns its private key or signed transaction bytes. Do not use the same key for unrelated transactions: a conflicting nonce stops allocations for review.

The fixed policy tops wallets below 1 STT up to 2 STT, once per rolling 24 hours, with a 40 STT rolling global allocation and 10 STT retained reserve. The fee envelope is checked separately before signing. Limits and pending transfers are coordinated with a PostgreSQL transaction lock across web instances. A missing database or unreadable required chain state prevents a new transfer.

Production POST routes currently trust Vercel's overwritten x-forwarded-for header for an HMAC-derived connection identifier. Production outside Vercel fails closed until a trusted proxy adapter is implemented. Raw IPs are not stored. A shared connection can receive at most ten allocations per rolling 24 hours; signature challenges are also limited. These caps bound distribution but are not proof that each wallet belongs to a different person.

Only the STT leg uses this service. The tUSDC leg remains the user's transaction through the DreamDEX SDK faucet. This is independent of the older sponsorship routes below and grants no trading or deposit permission.

Sponsor and private desk on web

The sponsor declines unsupported targets, selectors, native value, gas or deadlines. It never supplies the player's deposit or pot. Sponsor counters and funded-seat tracking are process-local, not shared durable quotas.

PrivateDesk checks its named key, pause state, stake limits and gas readiness. Its open is three desk transactions, so the key must fund more than one send.

Game room and recovery

The web fallback room secret is random per process. It may support isolated development behavior, but it cannot authenticate tokens to a separate room process. Configure the shared secret for multiplayer.

Maker and leverage keeper

Maker, leverage keeper and duel settler default to dry-run. They send only when DRY_RUN is 0 or false. This differs from the strategy runner. Set it deliberately rather than relying on a shared default.

Seasons and contract tools

Share the same season rules between web and payout tools. The contract end time does not automatically authorize or trigger payout.

Contract scripts separately use settings such as DEPLOYER_PRIVATE_KEY, SHANNON_FORK_URL, FORK_MARKET_ID, FORK_RESOLVED_MARKET_ID, FORK_ASSET and SETTLED_QUESTION_ID for specific deployment/fork scenarios. Inspect the selected script: these are not web runtime variables and should not be copied wholesale into a web host.