Skip to main content
On-chain CLOB trading is coming soon. Today’s production API still uses HMAC-only ledger settlement. This page describes the builder flow so you can prepare.
Futuur is adding Polymarket-shaped on-chain settlement. The book still matches off-chain. Collateral (OOM or USDC) moves on-chain at match. HMAC authenticates HTTP. A wallet signature authorizes every create.

​
How a bot trade works

  1. Get HMAC keys from Settings or wallet derive.
  2. Enable trading once per token (standing approve of OOM or USDC to the pool).
  3. Ask the API for a signing context, sign LimitOrderIntent with the owner EOA, then create the order.
  4. The CLOB matches. Settlement transferFroms run before share balances update.
See Place an on-chain order for the step-by-step request flow.

​
Matching

The matching engine is a CLOB. User orders match each other first. The platform AMM is backup liquidity — it does not jump a better-priced user order. Complementary both-buy is a first-class match. If you bid long at 0.55 and someone else bids short at 0.45, the prices sum to 1 and the orders can match without an ask on the book. On a binary event, that is Yes vs No of the same event. On an exclusive event with three or more markets, it is Yes vs No of the same market — not Yes on one market vs Yes on another. See Conditional tokens. A filled on-chain order without a collateral Transfer is a failure. The API does not credit positions until collateral has moved.

​
Settlement at match

The first on-chain cutover moves collateral (OOM or USDC) and keeps share balances in the Futuur database. A later cutover mints those positions as ERC-1155 outcome tokens. Matching stays the same CLOB either way.

​
Two-layer auth

HMAC never replaces the wallet signature. Get both credentials from Get your API keys.

​
What stays the same

  • Events, markets, and the existing order and wager resources
  • Play money (OOM) and real money (USDC) as currencies
  • HMAC signing for every authenticated request — see Authentication

​
Not in this release

These are not live on https://api.futuur.com:
  • Conditional / outcome tokens (ERC-1155 Yes/No positions; binaries and exclusive N≥3)
  • A dedicated exchange contract (settlement uses the pool Safe; operator fills come later)
  • An official TypeScript or Python SDK
  • Separate CLOB, Gamma, or Relayer hosts — you still call https://api.futuur.com