Instant Trading

Usually, when trading on-chain, every action needs a wallet signature and a network confirmation: to open a trade, close a trade, cancel etc. That’s secure, but it can feel slow and clunky, especially if you’re used to the speed of execution on centralized exchanges. Instant Trading on SYMMIO is a way to keep the same trustless backend while making the trading experience feel almost as fast as a CEX. Instead of signing every single trade, you set up a secure “session” with a solver once, and they can then execute specific actions on your behalf, within strict limits you control.

If you've traded on one of our frontends, they will guide you to create a sub-account when you first sign up and deposit collateral into that, rather than trade directly from your wallet. From this sub-account, a a solver address can be approved to call a small set of functions for you, like opening positions, requesting closes, cancelling quotes, or allocating collateral. You do this by confirming a single on-chain transaction from your wallet that grants those permissions to the solver for your chosen sub-account. The delegation is function-level, so the solver can’t do anything outside what you’ve explicitly allowed. This access can also be revoked on-chain. See more information here.

Once delegation is in place, the frontend guides you through a one-time login. You'll sign a message that proves you control the sub-account and agree to start an instant-trading session. The solver verifies this signature and issues an access token to the frontend. That token is then attached to your API requests, so when you click “Open” or “Close” in the UI, the solver can immediately act on your behalf using its delegated access. Under the hood, the solver is still performing the usual risk checks and on-chain calls, but from your trades are confirmed almost instantly, with on-chain settlement following shortly after.

Delegation happens through the MultiAccount contract, so only the sub-account owner can grant or revoke access, and only for the exact functions you’ve chosen. There is a two-step revocation process: you first propose to revoke access, then, after a short cooldown, you complete the revocation. This gives solvers enough notice not to be rug-pulled mid-flow, while still letting you take back control whenever you want. On the solver side, access tokens have an expiration time, and every instant action still goes through balance checks, PnL checks, and normal SYMMIO risk logic before anything is sent on-chain.