Polymarket CTF: Conditional Token Framework Explained

Polymarket CTF is the Conditional Token Framework Polymarket uses to represent market outcomes as ERC-1155 tokens. This guide explains what those outcome tokens are, how split / merge / redeem work, and the practical implications for traders and developers on Polymarket.

Key takeaways

• The CTF mints ERC-1155 outcome tokens that each correspond to a specific market outcome; a complete set is worth $1.00 in pUSD at fair value.
• "Split" mints a complete set from pUSD, "merge" converts a full set back to pUSD, and "redeem" burns winning tokens for $1.00 after resolution.
• You interact with CTF through Polymarket's relayer and SDKs; users never pay chain gas directly on Polygon because Polymarket sponsors it.
• The mechanics are deterministic, but practical risks exist: oracle disputes (UMA), settlement timing, slippage, fees, and smart-contract risk.
• Understanding CTF is essential for arbitrage strategies that buy full sets or individual outcomes.

Why the CTF matters

Polymarket is an exchange of outcome shares. The CTF is the smart-contract layer that makes each outcome an ERC-1155 token. Those tokens are what you buy, sell, transfer, or hold. For traders and builders, knowing how the CTF issues and reclaims tokens explains how you can create complete sets, hedge, or exit positions without going through other users.

How outcome tokens are structured

Each market outcome is represented by an ERC-1155 token minted under the CTF. For binary markets the two tokens are conventionally called YES and NO. For multi-outcome markets there is one token per mutually exclusive outcome. At theoretical fair prices the sum of all outcome token prices equals $1.00.

Important properties:

• Fungibility within an outcome: all tokens for the same outcome are equivalent.
• Non-fungibility across outcomes: an outcome token only pays if that outcome resolves YES.
• ERC-1155 semantics let the CTF manage multiple outcomes and markets efficiently.

The split / merge / redeem lifecycle

Split

• What it does: "split" mints a complete set of outcome tokens for a specific condition (market) in exchange for pUSD.
• Practical effect: you pay $1.00 in pUSD and receive one unit of every outcome token. If you want to hold a neutral position or arbitrage a mispriced market, splitting is how you create the legs on-chain.
• When traders use split: common when arbitrageurs buy a full set to lock in an edge, or when a user wants to construct bespoke exposures.

Merge

• What it does: "merge" burns a full set of outcome tokens and returns $1.00 in pUSD to the caller.
• Practical effect: merging is how you unwind a neutral complete-set position back into tradable pUSD, without relying on counterparty fills.
• Limitations: you must hold a complete set (one of every outcome token) to merge.

Redeem

• What it does: after a market resolves, "redeem" burns winning outcome tokens and pays out $1.00 per winning token in pUSD.
• Practical effect: holders of winning tokens exchange them for cash value once UMA reports the result.
• Caveat: if UMA triggers disputes, redemption can be paused until resolution is final. Redeem is therefore subject to oracle timing and dispute risk.

How these operations appear to you on Polymarket

• Polymarket exposes split/merge/redeem flows through its UI and SDKs. The Relayer handles gas and wallet deployment so users don’t pay polygon gas directly for these operations.
• Typical trader flow: use the UI to buy outcome tokens, or split a complete set; merge when you want pUSD back; redeem only after resolution.
• Developers: the CTF operations are standard on-chain calls; the Polymarket Relayer and SDKs abstract many details (wallet proxy deployment, approvals, and sponsored gas).

A simple example (conceptual)

• You see a 3-outcome market where the sum of best-ask prices is $0.92. Buying those three asks costs $0.92. You can then hold the full set and later merge it for $1.00 in pUSD, locking an edge equal to the $0.08 gap (minus fees and execution risk). This is the basis of intra-market combinatorial arbitrage.

Operational notes and UX details

• Sponsored gas: Polymarket sponsors gas through its Relayer. You interact with split/merge/redeem without sending native gas fees; the Relayer model also handles on-demand wallet proxy deployment.
• Tokens are ERC-1155: use tooling that understands ERC-1155 balances when inspecting wallets or building bots.
• Order-book vs CTF: you can acquire outcome tokens either by trading on the CLOB or by splitting a full set. Arbitrageurs often mix both to optimize execution and fees.

Risks you must consider

Never treat split/merge/redeem as mechanically "risk-free" without accounting for real-world risks. Key risks:

• Oracle and resolution risk: UMA disputes can pause redemption and change final outcomes.
• Settlement timing: the time between your trade, resolution, and redeem can expose you to price movement and funding risk.
• Slippage and partial fills: when relying on the CLOB, fills may be partial or cost more than expected; merging removes counterparty dependence but requires a complete set.
• Fees: taker fees vary by category (0%–1.8% current band) and can change; maker fees are zero. Builder fees apply if orders are routed through third parties.
• Smart-contract risk: while CTF and exchange contracts are established, all on-chain interactions carry technical risk.

How this affects your trading

• Arbitrage strategies: understanding split/merge lets you convert between on-chain complete sets and position legs efficiently. Intra-market arbitrage often exploits deviations between sum-of-asks and $1.00.
• Execution choices: if the book is shallow, splitting and placing limit sells can be cheaper than buying individual asks; conversely, buying asks may be faster when spreads are tight.
• Accounting and custody: ERC-1155 tokens are on-chain assets; track balances and approvals. If you use third-party builders, check attribution and builder-fee terms.

Developer pointers

• APIs and SDKs: use Polymarket's SDKs and the Gamma, Data, and CLOB APIs for market metadata, positions, and order-book interactions. The CTF contract calls are reflected in Polymarket's relayed flows.
• Testing: on Polygon, token behaviour follows ERC-1155 rules. Respect the Relayer model in integration tests—wallets may be auto-deployed on first use.
• Builder Program: if you route orders through the Builder Program, attribution headers and builder fees are part of the flow; check program limits by tier.

Closing summary

Polymarket CTF is the primitive that turns market outcomes into transferrable ERC-1155 tokens. Split, merge, and redeem are simple on-chain operations that enable neutral-set creation, unwind, and post-resolution settlement. Knowing these operations helps you design execution strategies and reason about arbitrage, but always balance the deterministic math with real-world risks like UMA disputes, fees, and slippage.

Frequently asked questions

What exactly is a Polymarket CTF token?

A Polymarket CTF token is an ERC-1155 outcome token minted by the Conditional Token Framework. Each token represents a claim on a single market outcome; winning tokens can be redeemed for $1.00 in pUSD after resolution.

When should I split a complete set instead of buying outcomes on the order book?

Splitting is convenient when you want a guaranteed complete set without counterparty dependence, or when the combined best asks cost more than $1.00 minus expected fees. Buying on the order book can be faster and cheaper if liquidity is deep. Consider slippage, fees, and execution time.

Can I redeem immediately after resolution?

You can redeem winning tokens after Polymarket's resolution process reports a result via UMA, but if UMA disputes occur redemption may be paused until final resolution. Redeem timing is therefore subject to oracle and dispute risk.

Do I need MATIC or POL to pay gas for CTF operations?

No. Polymarket sponsors gas via its Relayer on Polygon. Typical CTF operations—wallet proxy deployment, approvals, split/merge/redeem—are handled gaslessly for the end user.

Are split / merge / redeem operations visible in Polymarket APIs?

Yes. Market metadata and positions appear through the Gamma and Data APIs, while order-book activity is available from the CLOB API. The Relayer abstracts the underlying CTF calls in user flows.