How-to guide

Configure the Trading UI

Use this guide to choose between live and simulated mode and to point the Trading UI at the network and RPC you need.

Choose a mode

With no mode parameter, the UI reads live RPC and wallet state.
?simulate=1 boots a browser-local simulator with seeded contracts and balances. Add &simScenario=deployed for a SecurityPool with no trading pool, &simScenario=baseline for a chain without Statoblast or Trading contracts, &simScenario=trading-forked for the funded market after its universe forks, or leave it out for the default trading-funded scenario with one funded market. A banner labels the page as a simulation.

Set up Trading development lists the commands that serve the UI.

Choose the truthful universe

Choose Yes or No for the displayed Augur v2 fork question. To open that choice directly, add genesis=yes or genesis=no to the URL query, for example ?simulate=1&genesis=yes. The selected universe uses its own REP token and protocol deployment. To change the choice, open Universe under More, follow the selected root's Parent universe link to Augur v2 universe, and open the other child. Returning to the Augur v2 universe clears the previous deployment's market and fork selection.

Select a network and RPC

Open Settings in the header. Choose the RPC network, and optionally enter a Fallback RPC URL and select Save RPC. A custom RPC must use HTTPS, or HTTP on a loopback address, and must serve the selected chain. It is used only until a wallet is connected on the selected chain; after that, the wallet's own RPC serves reads and transactions.

The UI then checks the RPC chain and the core contracts, and derives the Trading factory and router addresses for that network. If either is not deployed, the deployment screen opens; Deploy the Trading contracts covers it. The configuration works when the Markets tab opens. The configuration reference describes what the client derives and checks.