​

4. Go live

In short. You connect your Polymarket account to the app, test it with real orders of the minimum size, and then turn on trading. Do the steps once, in order. Until the last step, the app cannot place a real order outside the test.

Until now the app ran with LIVE_TRADING=false and no account. This page adds a Session Key: a key that can trade for your account but is not the account’s main (owner) key. Every setting named here is explained in configuration.md.

​

Before you start

You need:

• Pages 1, 2 and 3 done, with a passed restore test.
• Your owner machine: the computer that holds the owner key of your Polymarket account. It is never the server.
• To be in a location where Polymarket permits you to trade.

WARNING: Never put the owner key on the server or in sesame.env. A person who gets the owner key controls all the money in the account.

​

Step 1. Run the security checklist

Do the security checklist on the server.

1. Do checks S1 to S9. Record the date, the release tag and the output of each check.
2. Do check S10.

Do not continue until S1 to S10 pass.

​

Step 2. Create the Session Key

Follow Session Key setup, sections 1 and 2.

• Create the key pair on the server, so the private key never leaves it.
• Authorise it from your owner machine.
• To use Combos, give the key the combos scope too (section 8).

At the end you have three values:

​

Step 3. Add the account settings

CAUTION: Cancel every open order on polymarket.com before you do this step. At its first start with the key, the app takes every open order as its own (live verification, PF3).

1. On the server, open the settings file:
   sudoedit /opt/sesame/sesame.env
   
2. Add these three lines, with your values:
   POLYMARKET_WALLET_ADDRESS=<Deposit Wallet address>
   POLYMARKET_SESSION_KEY=<Session Key private key>
   POLYMARKET_OWNER_ADDRESS=<owner address>
   
3. Add the eight RISK_CEILING_* lines with the test values from live verification, section 1.1. The app reads the ceilings only when it starts.
4. Make sure that the file still has LIVE_TRADING=false.
5. Save and close the file.
6. On your computer, in the repository folder, restart the app:
   task deploy:start
   
   Enter the security key’s PIN and touch it, or type the passphrase. The command ends with a list of the two containers, sesame-sesame-1 and sesame-caddy-1.

If the command stops with an error, the app found a wrong setting. Go to The deploy stops and the app does not start.

​

Step 4. Check the credential state

1. Log in to the app and open Settings.
2. In Account, find Credentials. It shows Connected.
3. Make sure that Signer address (Session Key) is the address of the key you created in Step 2. It must not be the owner address.
4. Make sure that Wallet address (Deposit Wallet) is your Deposit Wallet address.
5. On your computer, read the app’s log:
   task deploy:logs -- sesame
   
   Find the line with baseline orders adopted. It shows "orders":0.

​

Step 5. Run the live verification

The live verification places real orders of the minimum size and checks each result. It needs LIVE_TRADING=true, with the low test ceilings from Step 3.

1. On the server, open the settings file:
   sudoedit /opt/sesame/sesame.env
   
2. Change the LIVE_TRADING line to:
   LIVE_TRADING=true
   
3. On your computer, restart the app:
   task deploy:start
   
4. Do the live verification from its section 1 to its section 6. Use minimum sizes only.

The runbook is written for an app on your own computer. On the server, use these in its place: If a step fails, stop and do section 3 of the runbook. It turns trading off again.

​

Step 6. Turn on live trading

Do this step only when every step of the live verification passed.

1. In the app, press Cancel all. Make sure that polymarket.com shows no open order from the test.
2. Set the switch to Safe.
3. On the server, open the settings file:
   sudoedit /opt/sesame/sesame.env
   
4. Change the eight RISK_CEILING_* lines to the values you want for normal trading. To use the defaults, delete the lines.
5. Make sure that the file has LIVE_TRADING=true.
6. On your computer, restart the app:
   task deploy:start
   
7. In the app, raise your risk limits one at a time (Change a risk limit). Each raise asks for your login password. A limit cannot go above its ceiling.
8. Set your stake presets last (Change your stake presets). A preset cannot be above the maximum order notional.

​

Is it working?

If trading stays off, see The app runs but trading stays off. The Session Key expires 180 days after you authorise it. Write down the date. From 14 days before it, Settings, then Account shows Session Key expiry. Replace the key before it expires (Rotation). Previous: 3. Backups · Next: Day to day