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.
How a bot trade works
- Get HMAC keys from Settings or wallet derive.
- Enable trading once per token (standing
approveof OOM or USDC to the pool). - Ask the API for a signing context, sign
LimitOrderIntentwith the owner EOA, then create the order. - The CLOB matches. Settlement
transferFroms run before share balances update.
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 on binary markets. 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.
A filled on-chain order without an ERC-20
Transfer is a failure. The API does not credit shares until collateral has moved.
Settlement at match
Shares stay in the Futuur database. Only the collateral token moves on-chain.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 part of the first on-chain cutover:- Conditional / outcome tokens on-chain (positions stay in the database)
- A dedicated exchange contract (settlement uses the pool Safe + ERC-20
transferFrom) - An official TypeScript or Python SDK
- Separate CLOB, Gamma, or Relayer hosts — you still call
https://api.futuur.com