Smart Contracts
Last updated
Was this helpful?
Last updated
Was this helpful?
All those contracts are the direct factories of the Option contracts. We will not cover them in our documentation, but you can check directly on our code. Check our Github. They all have the same function and parameters used to deploy a new option contract:
buildOption()
Contract responsible for creating/deploying new option contracts. This contract can create four different option's contracts: PodPut, WPodPut, PodCall, WPodCall. It uses the "" 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:
()
The contract for American or European Put options. It works with any ERC20 pair as the strike asset and underlying asset. This contract is also compatible with on the strike asset or the underlying asset. It is possible to interact with the contract mainly using:
Same logic as the PodPut, but with some special function to convert ETH into WETH. The underlying asset of that contract must be the . 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:
If you are using WPodPut on a testnet, you should use a contract address for the underlying asset with the same interface of the mainnet WETH. You can check our WETH address for testnets on our .
The contract for American or European Call options. It works with any ERC20 pair as the strike asset and underlying asset. This contract is also compatible with on the strike asset or the underlying asset. It is possible to interact with the contract mainly using:
)
()
Same logic as the PodCall, but with some special function to convert ETH into WETH. The underlying asset of that contract must be the . 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:
)
If you are using WPodCall on a testnet, you should use a contract address for the underlying asset with the same interface of the mainnet WETH. You can check our WETH address for testnets on our .
