How-to guide

Exit an insured position

Use this guide to turn Yes or No shares back into ETH while the market's trading pool is open. The exit spends one Invalid share for each complete set it redeems, so your Invalid balance limits it.

Connect your wallet and open Portfolio to discover Yes, No, Invalid and LP holdings across registered security pools in the selected universe, including pools never opened in this browser. Discovery covers the configured deployment; switch universes to inspect other branches. A failed balance read remains visible as unavailable rather than being counted as zero.

Exit in the UI

  1. Open the market, select Sell and the side you hold.
  2. Select Max to fill Shares to sell with the largest amount you can sell now, or enter a smaller amount. The hint under the field shows your holding and that limit.
  3. Check You receive ≈, Minimum received, and Invalid used, then select Sell Yes (or Sell No) and confirm.
The Trade tab with Sell and Yes selected, 0.001 Yes in Shares to sell, the hint that up to 0.0054 Yes can be sold now, 25%, 50%, and Max shortcuts, and the estimate with Invalid used, above an enabled Sell Yes button.
An insured Yes exit. The hint under the amount is the limit set by your Invalid, your Yes, and the trading pool's liquidity.

If Invalid is the binding limit and you enter more than it covers, the ticket shows Not enough Invalid shares to insure this sale. and offers Sell … instead with the largest amount. The shares you do not sell stay in your wallet. Acquiring more Invalid helps only when Invalid is the binding limit; Why early ETH exits are limited works through the bounds.

When the sale confirms, the Invalid balance under Your position has dropped by Invalid used and the ETH is in your wallet.

Exit through the SDK

  1. Call maximumInsuredExit from the SDK, a private workspace package in this repository, with your wallet balances and the trading pool's reserves and fee. It returns the largest number of complete sets q that your Invalid, your long shares, and the opposite reserve all allow. For a Yes position, q complete sets need q Invalid, q Yes to redeem, and enough extra Yes to buy exactly q No.
  2. Choose maxLongSharesIn, minEthOut, payoutRecipient, refundRecipient, and deadline explicitly, and encode the request with encodeReceiveRequest.
  3. Send a ShareToken safeBatchTransferFrom to the router carrying q Invalid and maxLongSharesIn long shares with the encoded request. Simulate it, simulate again immediately before submission, and submit only if the result still satisfies maxLongSharesIn and minEthOut.

The router reference lists the request fields, their constraints, and what the router delivers. A successful exit emits PositionExitedByTransfer with the long shares used and refunded.