How-to guide

Configure the Trading UI

The standalone Trading UI runs in one of two modes and verifies its contracts before it lets you trade. This guide shows how to pick the mode and network you need.

Choose a mode

Simulation mode is labeled as such and is never evidence of live chain state. Set up Trading development lists the commands and URLs.

Select a network and RPC

The build copies the canonical mainnet and Sepolia core factory and deterministic proxy addresses from the root deployment manifests, together with a default public RPC URL for each network. When you open the live UI it derives the fixed-fee trading factory and router addresses with CREATE2 and checks whether both contracts are deployed. If either is missing, the deployment screen opens automatically; Deploy the Trading contracts covers that flow. The UI verifies the RPC chain and core bytecode and lists each deterministic contract's deployment status. After both contracts are verified, live trading opens without saving a separate trading deployment configuration.

Use Settings beside the wallet to select another supported network or override its RPC URL. A custom RPC must use HTTPS or loopback HTTP and match the selected chain. Browser-led deployment uses a fixed 0.30% trading fee, and every trading and pool-deployment surface shows the deployed immutable fee as a percentage. Share, complete-set, and LP amounts are shown as their settlement-collateral value in ETH at the pool's current rate.

What you will see the client verify

Every workflow starts from a SecurityPool address: #/market opens a market by address or from the Markets list, and #/create-market opens a security pool that has no trading market yet so you can deploy its pair and seed liquidity. Before any submission the client checks that the wallet reports the selected network, then simulates the entry, exit, liquidity, settlement, or fork-migration call through the actual contracts. A new block does not invalidate a quote; the client simulates again at submission and stops if the result falls outside your approved bounds. The configuration reference describes the client's discovery and verification behavior in full.

Serve built assets from the same origin. Production code may connect only to the configured RPC, the wallet provider, and explicit explorer links. Simulation mode is unmistakably labeled and must never be presented as live state.