Exercise
Prepare Exercise
Generate transaction call data for exercising options positions purchased on CLAMM.
Exercising on CLAMM involves swapping of tokens. i.e if for call options, Call Asset (eg: ETH) -> Put Asset (eg: USDC) and vice versa. Currently, the API only supports swaps through DEX and aggregators as specified below:
DEX | Chains Supported | SwapperId |
---|---|---|
PancakSwap V3 | Arbitrum, Base | pancakeswap |
Uniswap V3 | Arbitrum, Base | uniswap |
Sushiswap V3 | Arbitrum, Base, Mantle, Blast | sushiswap |
Thruster V3 | Blast | thruster |
Agni V3 | Mantle | agni |
FusionX V3 | Mantle | fusionx |
Aggregator | Chains Supported | SwapperId |
---|---|---|
0x Protocol | Arbitrum, Base, Blast | 0x |
Odos SOR V2 | Arbitrum, Base, Mantle | odos |
1inch Aggregator V6 | Arbitrum, Base | 1inch |
Paraswap V6.2 | Arbitrum, Base | paraswap |
KyberSwap V1 | Arbitrum, Base, Mantle, Blast | kyberswap |
OpenOcean V4 | Arbitrum, Base, Mantle, Blast | openocean |
It is important to try and experiment with reasonable slippage percentages as CLAMM contracts always ensure the underlying collateral of the options are fulfilled before the profit is paid out to the trader when the swap takes place. To understand this concept better let's consider the example below:
As you can see with the example above, when options are exercised the slippage only affects trader's profit to ensure liquidity providers are always whole. To avoid losing much on profit it is recommended to exercise options partially similar to how one would TWAP on DEXs or use supported aggregators but it is also important to note that even aggregators are prone to slippage if the size of the swap is big enough.
Exercise History
the history endpoint can be used to retrieve the history of options exercised for a user
Last updated