PodPut
, WPodPut
, PodCall
, WPodCall
. It uses the "Mega Factory" pattern, where it uses auxiliary "builder" contracts (PodPutBuilder
, WPodPutBuilder
, PodCallBuilder
, WPodCallBuilder
). From the users/developer's perspective, they do not need to interact with those auxiliary contracts. OptionFactory has only one function:ERC20
pair as the strike asset and underlying asset. This contract is also compatible with aTokens on the strike asset or the underlying asset. It is possible to interact with the contract mainly using:ETH
into WETH
. The underlying asset of that contract must be the official WETH address. The only function that has a different signature is theexerciseEth.
Although the other functions work differently under the hood, they have the same signature of the PodPut
:WETH
/ ETH
conversion yourself, you can simply use PodPut with WETH
in the underlying asset parameter.ERC20
pair as the strike asset and underlying asset. This contract is also compatible with aTokens on the strike asset or the underlying asset. It is possible to interact with the contract mainly using:ETH
into WETH
. The underlying asset of that contract must be the official WETH address. The only function that has a different signature is the mintEth
. Although the other functions work differently under the hood, they have the same signature of the PodPut
:WETH
/ ETH
conversion yourself, you can use PodCall with WETH
in the underlying asset parameter.WETH
. You can check our WETH
address for testnets on our deployed contracts page.