hardhat VS opium-protocol-v2

For a list of all the built-in tasks and subtasks please take a look at task-names.ts

Let’s now get the account’s balance. The Hardhat Runtime Environment will be available in the global scope. By using Hardhat’s ether.js plugin, which is included in the Hardhat Toolbox, we get access to an ethers.js instance:

Plugins can extend the HRE. For example, hardhat-ethers adds a Ethers.js instance to it, making it available to tasks, tests and scripts.

The struct above is the schema that we use in the Opium Protocol. Let’s quickly walk through it: uint256 margin: aka the reference collateral that is (usually) parsed by the IDerivativeLogic SyntheticId getMargin function to set the collateral requirements of the option contract. uint256 endTime: aka the maturity date of the contract. It is the point in time at which the buyers will have the right to exercise their contract. uint256[] params: option contracts can differ greatly in the complexity of their financial requirements, as such Opium uses a dynamic array to ensure a high degree of flexibility to the consumers of the protocol, as to enable them to encode arbitrary parameters in their LibDerivative asset definition if needed. One convention to keep in mind is that, however, the first item of the params array is always expected to be the strike price. The strike price is the value that determines the profitability of an option upon expiry: if the market price is above the strike price in case of a call option or the market price is below the strike price in the context of a put option, the option is said to be ‘in the money’ and the buyer stands to make a profit. Vice-versa, the option is said to be out of the money and the buyer stands to lose the premium or the collateral that they had to exchange for the ownership of the option contract. oracleId: oracles are the entities that inform the Opium Protocol about the value of an asset upon its maturity date. The Opium Protocol does not enforce any specification as for what can be used as an oracle, be it on-chain or off-chain. token: the address of the ERC20 token to be used as a collateral syntheticId: the address of the contract where the financial logic of the derivative is encoded. The Opium Protocol expects the syntheticId contracts to be compliant with the specifications of the IDerivativeLogic interface.