ConditionalTokens

​

Key concepts

• Condition — an (oracle, questionId, outcomeSlotCount) tuple.
• Position — an ERC-1155 balance of a specific outcome slot within a condition.
• Redemption — once the oracle reports payouts, holders call redeemPositions to exchange winning tokens for USDC.

​

Prepare a condition

function prepareCondition(
    address oracle,
    bytes32 questionId,
    uint256 outcomeSlotCount
) external;

​

Redeem winning positions

function redeemPositions(
    IERC20 collateralToken,
    bytes32 parentCollectionId,
    bytes32 conditionId,
    uint256[] calldata indexSets
) external returns (uint256 totalPayout);

​

Redeeming your positions

• Automatic — auto-redeem is on by default. Within a few minutes of a market’s final status the platform redeems for you, and pays the gas for, the refund on a voided market and your winnings on a resolved market when they pay at least 1 USDC on that market. Smaller winnings are left for you to claim, so check redeemable on GET /api/me/positions?status=redeemable and use one of the paths below for anything still redeemable. Read or change the setting with GET / PUT /api/me/auto-redeem (body { "enabled": true | false }); details in Auto-redeem.
• Gasless API — POST /api/me/positions/redeem (vault:write scope) with the position’s { "marketId", "outcomeIndex" } as returned by GET /api/me/positions (0 = YES, 1 = NO). API-key callers must also send auth: { deadline, v, r, s }: an EIP-712 RedeemAuthorization(address owner, string marketId, uint8 outcomeIndex, uint256 deadline) signed by the wallet owner under the domain { name: "PredictStreetRedeem", version: "1", chainId } (no verifyingContract). The response is { jobId, status }; poll GET /api/me/positions/redeem/{jobId} until status is confirmed (or failed_permanent / expired).
• On-chain, from the vault-owner EOA — vault.redeemPositions(conditionId, indexSets) for binary markets, or vault.redeemPositionsNegRisk(marketId, questionIndex, amount) for neg-risk markets. No backend co-signature is needed; only the vault owner (or the platform) may call them, anyone else gets NotOwner(). See Positions → Redeeming a resolved position for which fields to pass.

​

Events

event ConditionPreparation(uint64 seq, bytes32 indexed conditionId, address indexed oracle, bytes32 indexed questionId, uint256 outcomeSlotCount);
event ConditionResolution(uint64 seq, bytes32 indexed conditionId, address indexed oracle, bytes32 indexed questionId, uint256 outcomeSlotCount, uint256[] payoutNumerators);
event PositionSplit(uint64 seq, address indexed stakeholder, IERC20 collateralToken, bytes32 indexed parentCollectionId, bytes32 indexed conditionId, uint256[] partition, uint256 amount);
event PositionsMerge(uint64 seq, address indexed stakeholder, IERC20 collateralToken, bytes32 indexed parentCollectionId, bytes32 indexed conditionId, uint256[] partition, uint256 amount);
event PayoutRedemption(uint64 seq, address indexed redeemer, IERC20 indexed collateralToken, bytes32 indexed conditionId, bytes32 parentCollectionId, uint256[] indexSets, uint256 payout);

​

Source