CTF tokens
How binary AGARA outcome tokens are identified, traded, split, and merged.
AGARA outcome tokens are ERC-1155 positions issued through the Conditional
Tokens Framework. Your AGARA deposit wallet holds these positions alongside
USDC.
Every market is binary
AGARA supports binary markets only. Each market has exactly two complementary outcome tokens. They may appear as Yes and No, as two team names, or as another two-sided choice, but the underlying market still has two outcomes.
A multi-outcome event is represented as multiple binary candidate markets. It is not one condition with many outcome slots.
Neg-risk markets are binary too. A neg-risk group connects mutually exclusive binary markets and enforces that at most one member resolves to its first outcome. Each member keeps its own condition, two outcome tokens, and orderbook. Native AGARA members use the same ordinary binary CTF position operations as standalone markets.
A three-way moneyline may appear as a grouped Home / Draw / Away card. Each member still has separate first- and second-outcome controls; there is no three-token CTF condition.
Condition IDs and token IDs
| Identifier | Meaning | Format |
|---|---|---|
condition_id | The on-chain binary condition for one market | 0x-prefixed 32-byte hex |
token_id | One tradeable outcome position under that condition | Decimal-encoded ERC-1155 token ID |
The two CTF index sets are 1 and 2. AGARA maps them to the market's first
and second displayed outcomes; those labels are not always Yes and No.
Use token_id to place an order, read an orderbook, or subscribe to an
outcome stream. Use condition_id for condition-wide position operations and
market-status subscriptions.
A token ID is not an ERC-20 address. Every outcome in this environment lives in the same Conditional Tokens contract and is distinguished by its token ID. Discover both identifiers through Markets.
Token lifecycle
| Action | Standalone market | Neg-risk group member |
|---|---|---|
| Split collateral into both outcome tokens | Supported | Supported |
| Trade either outcome token | Supported | Supported |
| Merge a complete pair back into collateral | Supported | Supported |
ERC-1155 positions do not declare decimals. The API expresses share quantities
in millionths: 1000000 means one share. AGARA may also mint or merge complete
pairs while matching complementary orders; your filled size and execution
price do not depend on that settlement path.
See Positions for split and merge requests, Automatic redemption for resolved supported markets, and Inventory for market-making use.
Contracts in this environment
| Contract | Production address |
|---|---|
| Agara Account Registry | 0x92f14F46B636154F1358728A3755Ad0694371584 |
| Collateral | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
| Conditional Tokens | 0xe12D566cE5Dd8d817488E85a81386878649e3A18 |
| Standard CTF Exchange and order-signing contract | 0xD06f3fA925D35077A11dB42c6614D684f10B2aD6 |
| Automatic redemption | 0xCDA8a1De44D489070294E9A6a535555523c29e63 |
The standard CTF Exchange is the verifying contract for order signatures. For account batches, your own AGARA account address is the EIP-712 verifying contract. See Pre-signed orders and Account batches before signing.