BETAWEB3

Core Flow (Trading)

Trading is off-chain matching with on-chain settlement. Speed comes from the off-chain orderbook; security comes from the fact that every order carries your signature and PnL settles into the on-chain vault.

This page explains the mechanics. For the full order form walkthrough, see How to Trade Perps On-Chain | Advanced.

Order lifecycle

  1. You submit an order in the browser.
  2. The browser signs it with the delegated session key — no wallet popup per click.
  3. The matching engine verifies the signature against the delegated key your main wallet authorized at login, then matches the order off-chain.
  4. PnL settles into the on-chain vault.
  5. Fills and updates stream back to your client.

What is signed

Every mutating futures action carries a delegated-signer signature:

  • Order creation (market, limit, conditional)
  • Order updates (TP/SL, leverage, margin adjustments)
  • Order cancellation (single or batch)
  • Position close (single, all, or by symbol)

The signature is verified against the delegated key that your main wallet authorized at login.

What is not signed

Read-only queries — orderbook depth, your positions, trade history — are authenticated with your session token only. They don't change state and never carry a signature.

Safety properties

  • The matching engine cannot place orders on your behalf — it holds no signing key.
  • A compromised delegated key cannot withdraw funds — withdrawals require your main wallet plus two independent validators.
  • The delegated key has a TTL and can be revoked instantly by logging out.

See the Technical Reference for how the delegated key is provisioned and scoped.