logo
bg_imgbg_imgbg_imgbg_img
exclamation mark iconReport an issue

If you notice some outdated information please let us know!

close icon
Name
Email
Your message
arrow-left

Dopex

36%

Process Quality Review (0.8)

Dopex

Final score:36%
Date:15 Apr 2022
Audit Process:version 0.8
Author:Nick
PQR Score:36%

FAIL

Protocol Website:https://dopex.io

Scoring Appendix

The final review score is indicated as a percentage. The percentage is calculated as Achieved Points due to MAX Possible Points. For each element the answer can be either Yes/No or a percentage. For a detailed breakdown of the individual weights of each question, please consult this document.

The blockchain used by this protocol
Arbitrum
Avalanche
BnB Smart Chain
Ethereum
#QuestionAnswer
56%
1.100%
2.100%
3.No
4.0%
5.0
43%
6.Yes
7.Yes
8.0%
9.0%
10%
10.0%
11.0%
12.No
13.0%
14.No
15.Yes
65%
16.75%
17.0%
13%
18.0%
19.0%
20.0%
21.0%
22.0%
23.0%
24.0%
25.100%
25%
26.50
27.No
28.No
Total:36%

Very simply, the audit looks for the following declarations from the developer's site. With these declarations, it is reasonable to trust the smart contracts.

  • Here is my smart contract on the blockchain
  • You can see it matches a software repository used to develop the code
  • Here is the documentation that explains what my smart contract does
  • Here are the tests I ran to verify my smart contract
  • Here are the audit(s) performed to review my code by third party experts

This report is for informational purposes only and does not constitute investment advice of any kind, nor does it constitute an offer to provide investment advisory or other services. Nothing in this report shall be considered a solicitation or offer to buy or sell any security, token, future, option or other financial instrument or to offer or provide any investment advice or service to any person in any jurisdiction. Nothing contained in this report constitutes investment advice or offers any opinion with respect to the suitability of any security, and the views expressed in this report should not be taken as advice to buy, sell or hold any security. The information in this report should not be relied upon for the purpose of investing. In preparing the information contained in this report, we have not taken into account the investment needs, objectives and financial circumstances of any particular investor. This information has no regard to the specific investment objectives, financial situation and particular needs of any specific recipient of this information and investments discussed may not be suitable for all investors.

Any views expressed in this report by us were prepared based upon the information available to us at the time such views were written. The views expressed within this report are limited to DeFiSafety and the author and do not reflect those of any additional or third party and are strictly based upon DeFiSafety, its authors, interpretations and evaluation of relevant data. Changed or additional information could cause such views to change. All information is subject to possible correction. Information may quickly become unreliable for various reasons, including changes in market conditions or economic circumstances.

This completed report is copyright (c) DeFiSafety 2023. Permission is given to copy in whole, retaining this copyright label.

Smart Contracts & Team

56%

This section looks at the code deployed on the relevant chain that gets reviewed and its corresponding software repository. The document explaining these questions is here.

1. Are the smart contract addresses easy to find? (%)

Answer: 100%

They can be found at https://docs.dopex.io/contracts/arbitrum, as indicated in the Appendix.

Percentage Score Guidance:
100%
Clearly labelled and on website, documents or repository, quick to find
70%
Clearly labelled and on website, docs or repo but takes a bit of looking
40%
Addresses in mainnet.json, in discord or sub graph, etc
20%
Address found but labeling not clear or easy to find
0%
Executing addresses could not be found

2. How active is the primary contract? (%)

Answer: 100%

Contract DPX SSOV is used considerably more than 10 times a day, as indicated in the Appendix.

Percentage Score Guidance:
100%
More than 10 transactions a day
70%
More than 10 transactions a week
40%
More than 10 transactions a month
10%
Less than 10 transactions a month
0%
No activity

3. Does the protocol have a public software repository? (Y/N)

Answer: No

Location: https://github.com/dopex-io. However, their main strapiuct, SSOV, has its contracts behind a private repository. We will therefore consider Dopex to be a closed-source projects.

Score Guidance:
Yes
There is a public software repository with the code at a minimum, but also normally test and scripts. Even if the repository was created just to hold the files and has just 1 transaction.
No
For teams with private repositories.

4. Is there a development history visible? (%)

Answer: 0%

No Dopex SSOV contract repository is listed. Aside from a Uniswap-V2 Oracle, this repository contains no contracts. This renders the project closed-source. No commits to contract repositories are detailed, making us unable to award points. Indeed, an audit references contracts that were once available for viewing. The contracts are thus committed but private.

Percentage Score Guidance:
100%
Any one of 100+ commits, 10+branches
70%
Any one of 70+ commits, 7+branches
50%
Any one of 50+ commits, 5+branches
30%
Any one of 30+ commits, 3+branches
0%
Less than 2 branches or less than 30 commits

5. Is the team public (not anonymous)?

Answer: 0

Dopex's team consists of a few popular anonymous twitter personalities and others, none of which are public.

Score Guidance:
100%
At least two names can be easily found in the protocol's website, documentation or medium. These are then confirmed by the personal websites of the individuals / their linkedin / twitter.
50%
At least one public name can be found to be working on the protocol.
0%
No public team members could be found.

Documentation

43%

This section looks at the software documentation. The document explaining these questions is here.

6. Is there a whitepaper? (Y/N)

Answer: Yes

Location: https://docs.dopex.io/

7. Is the protocol's software architecture documented? (Y/N)

Answer: Yes

This protocol's software architecture is documented in great detail.

Score Guidance:
Yes
The documents identify software architecture and contract interaction through any of the following: diagrams, arrows, specific reference to software functions or a written explanation on how smart contracts interact.
No
Protocols receive a "no" if none of these are included.

8. Does the software documentation fully cover the deployed contracts' source code? (%)

Answer: 0%

There is no coverage of deployed contracts by software function documentation.

Percentage Score Guidance:
100%
All contracts and functions documented
80%
Only the major functions documented
79 - 1%
Estimate of the level of software documentation
0%
No software documentation

9. Is it possible to trace the documented software to its implementation in the protocol's source code? (%)

Answer: 0%

There is no traceability between software documentation and implemented code. No functions are listed and no code is available to cross reference this with.

Percentage Score Guidance:
100%
Clear explicit traceability between code and documentation at a requirement level for all code
60%
Clear association between code and documents via non explicit traceability
40%
Documentation lists all the functions and describes their functions
0%
No connection between documentation and code

Testing

10%

10. Has the protocol tested their deployed code? (%)

Answer: 0%

It is impossible to verify code testing at this moment without any documented public contracts or indeed testing of said contracts.

Percentage Score Guidance:
100%
TtC > 120% Both unit and system test visible
80%
TtC > 80% Both unit and system test visible
40%
TtC < 80% Some tests visible
0%
No tests obvious

11. How covered is the protocol's code? (%)

Answer: 0%

No tests for code coverage are identified.

Percentage Score Guidance:
100%
Documented full coverage
99 - 51%
Value of test coverage from documented results
50%
No indication of code coverage but clearly there is a complete set of tests
30%
Some tests evident but not complete
0%
No test for coverage seen

12. Does the protocol provide scripts and instructions to run their tests? (Y/N)

Answer: No

No scripts are documented.

Score Guidance:
Yes
Scripts and/or instructions to run tests are available in the testing suite
No
Scripts and/or instructions to run tests are not available in the testing suite

13. Is there a detailed report of the protocol's test results?(%)

Answer: 0%

No test reports were documented by Dopex.

Percentage Score Guidance:
100%
Detailed test report as described below
70%
GitHub code coverage report visible
0%
No test report evident

14. Has the protocol undergone Formal Verification? (Y/N)

Answer: No

This protocol has not undergone formal verification.

Score Guidance:
Yes
Formal Verification was performed and the report is readily available
No
Formal Verification was not performed and/or the report is not readily available.

15. Were the smart contracts deployed to a testnet? (Y/N)

Answer: Yes

This protocol has been deployed to a testnet.

Score Guidance:
Yes
Protocol has proved their tesnet usage by providing the addresses
No
Protocol has not proved their testnet usage by providing the addresses

Security

65%

This section looks at the 3rd party software audits done. It is explained in this document.

16. Is the protocol sufficiently audited? (%)

Answer: 75%

Dopex has undergone multiple pre-launch audits as it developed. A final audit was completed in June 2021, long before launch. However, since Dopex is closed source and therefore renders the audited code unavailable for comparison, we will deduct 25% from the score of this question.

Percentage Score Guidance:
100%
Multiple Audits performed before deployment and the audit findings are public and implemented or not required
90%
Single audit performed before deployment and audit findings are public and implemented or not required
70%
Audit(s) performed after deployment and no changes required. The Audit report is public.
65%
Code is forked from an already audited protocol and a changelog is provided explaining why forked code was used and what changes were made. This changelog must justify why the changes made do not affect the audit.
50%
Audit(s) performed after deployment and changes are needed but not implemented.
30%
Audit(s) performed are low-quality and do not indicate proper due diligence.
20%
No audit performed
0%
Audit Performed after deployment, existence is public, report is not public OR smart contract address' not found.
Deduct 25% if the audited code is not available for comparison.

17. Is the bounty value acceptably high (%)

Answer: 0%

This protocol does not offer a bug bounty.

Percentage Score Guidance:
100%
Bounty is 10% TVL or at least $1M AND active program (see below)
90%
Bounty is 5% TVL or at least 500k AND active program
80%
Bounty is 5% TVL or at least 500k
70%
Bounty is 100k or over AND active program
60%
Bounty is 100k or over
50%
Bounty is 50k or over AND active program
40%
Bounty is 50k or over
20%
Bug bounty program bounty is less than 50k
0%
No bug bounty program offered / the bug bounty program is dead
An active program means that a third party (such as Immunefi) is actively driving hackers to the site. An inactive program would be static mentions on the docs.

Admin Controls

13%

This section covers the documentation of special access controls for a DeFi protocol. The admin access controls are the contracts that allow updating contracts or coefficients in the protocol. Since these contracts can allow the protocol admins to "change the rules", complete disclosure of capabilities is vital for user's transparency. It is explained in this document.

18. Is the protocol's admin control information easy to find?

Answer: 0%

Admin control information was not documented by Dopex.

Percentage Score Guidance:
100%
Admin Controls are clearly labelled and on website, docs or repo, quick to find
70%
Admin Controls are clearly labelled and on website, docs or repo but takes a bit of looking
40%
Admin Control docs are in multiple places and not well labelled
20%
Admin Control docs are in multiple places and not labelled
0%
Admin Control information could not be found

19. Are relevant contracts clearly labelled as upgradeable or immutable? (%)

Answer: 0%

The relevant contracts are not identified as immutable / upgradeable.

Percentage Score Guidance:
100%
Both the contract documentation and the smart contract code state that the code is not upgradeable or immutable.
80%
All Contracts are clearly labelled as upgradeable (or not)
50%
Code is immutable but not mentioned anywhere in the documentation
0%
Admin control information could not be found

20. Is the type of smart contract ownership clearly indicated? (%)

Answer: 0%

Ownership is not indicated in Dopex's documentation. There is a Multisig address, but no details exist about it.

Percentage Score Guidance:
100%
The type of ownership is clearly indicated in their documentation. (OnlyOwner / MultiSig / etc)
50%
The type of ownership is indicated, but only in the code. (OnlyOwner / MultiSig / etc)
0%
Admin Control information could not be found

21. Are the protocol's smart contract change capabilities described? (%)

Answer: 0%

Smart contract change capabilities are not identified in any contracts.

Percentage Score Guidance:
100%
The documentation covers the capabilities for change for all smart contracts
50%
The documentation covers the capabilities for change in some, but not all contracts
0%
The documentation does not cover the capabilities for change in any contract

22. Is the protocol's admin control information easy to understand? (%)

Answer: 0%

This information is not documented.

Percentage Score Guidance:
100%
All the contracts are immutable
90%
Description relates to investments safety in clear non-software language
30%
Description all in software-specific language
0%
No admin control information could be found

23. Is there sufficient Pause Control documentation? (%)

Answer: 0%

This protocol's pause control is not documented or explained.

Percentage Score Guidance:
100%
If immutable and no changes possible
100%
If admin control is fully via governance
80%
Robust transaction signing process (7 or more elements)
70%
Adequate transaction signing process (5 or more elements)
60%
Weak transaction signing process (3 or more elements)
0%
No transaction signing process evident
Evidence of audits of signers following the process add 20%

24. Is there sufficient Timelock documentation? (%)

Answer: 0%

This protocol has no timelock documentation. A timelock.sol is deployed, though this is without documentation.

Percentage Score Guidance:
100%
Documentation identifies and explains why the protocol does not need a Timelock OR Timelock documentation identifies its duration, which contracts it applies to and justifies this time period.
60%
A Timelock is identified and its duration is specified
30%
A Timelock is identified
0%
No Timelock information was documented

25. Is the Timelock of an adequate length? (Y/N)

Answer: 100%

The timelock is of a relevant length (at 3 days), as specified in this contract source code.

Percentage Score Guidance:
100%
Timelock is between 48 hours to 1 week OR justification as to why no Timelock is needed / is outside this length.
50%
Timelock is less than 48 hours or greater than 1 week.
0%
No Timelock information was documented OR no timelock length was identified.

Oracles

25%

This section goes over the documentation that a protocol may or may not supply about their Oracle usage. Oracles are a fundamental part of DeFi as they are responsible for relaying tons of price data information to thousands of protocols using blockchain technology. Not only are they important for price feeds, but they are also an essential component of transaction verification and security. These questions are explained in this document.

26. Is the protocol's Oracle sufficiently documented? (%)

Answer: 50

The protocol's oracle source is UMA. The contracts dependent are not identified. There is not relevant software function documentation.

Score Guidance:
100%
If it uses one, the Oracle is specified. The contracts dependent on the oracle are identified. Basic software functions are identified (if the protocol provides its own price feed data). Timeframe of price feeds are identified. OR The reason as to why the protocol does not use an Oracle is identified and explained.
75%
The Oracle documentation identifies both source and timeframe, but does not provide additional context regarding smart contracts.
50%
Only the Oracle source is identified.
0%
No oracle is named / no oracle information is documented.

27. Is front running mitigated by this protocol? (Y/N)

Answer: No

This protocol documents no front running mitigation techniques.

Score Guidance:
Yes
The protocol cannot be front run and there is an explanation as to why OR documented front running countermeasures are implemented.
No
The Oracle documentation identifies both source and timeframe, but does not provide additional context regarding smart contracts.

28. Can flashloan attacks be applied to the protocol, and if so, are those flashloan attack risks mitigated? (Y/N)

Answer: No

This protocol documents no flashloan countermeasures.

Score Guidance:
Yes
The protocol's documentation includes information on how they mitigate the possibilities and extents of flash loan attacks.
No
The protocol's documentation does not include any information regarding the mitigation of flash loan attacks.

Appendices

1pragma solidity ^0.8.0;
2
3/**                                                                                                 
4                                                                                
56                                       ▓▓▓                                      
7                                      ▓▓▓▓▓                                     
8                                    ▓▓▓▓▓▓▓▓▓                                   
9                                   ▓▓▓▓▓▓▓▓▓▓▓                                  
10                                  ▓▓▓▓▓▓▓▓▓▓▓▓▓                                 
11                                 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                                
12                                ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                               
13                              ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▒                             
14                             ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                            
15                            ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                           
16                           ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                          
17                          ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                         
18                        ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                       
19                       ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                      
20                      ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                     
21                     ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                    
22                    ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                   
23                  ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                 
24                    ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                   
25                        ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                       
26                   ▓       ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓       ▓                  
27                    ▓▓▓       ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▒       ▓▓▓                   
28                      ▓▓▓▓▓       ▓▓▓▓▓▓▓▓▓▓▓▓▓       ▓▓▓▓▓                     
29                       ▓▓▓▓▓▓▓       ▓▓▓▓▓▓▓       ▓▓▓▓▓▓▓                      
30                        ▓▓▓▓▓▓▓▓▓              ▓▓▓▓▓▓▓▓▓░                       
31                          ▓▓▓▓▓▓▓▓▓▓▓       ▓▓▓▓▓▓▓▓▓▓▓                         
32                           ▓▓▓▓▓▓▓▓▓▓▓▓▓ ▓▓▓▓▓▓▓▓▓▓▓▓▓                          
33                             ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                            
34                              ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                             
35                               ▒▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                               
36                                 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                                
37                                  ▓▓▓▓▓▓▓▓▓▓▓▓▓                                 
38                                    ▓▓▓▓▓▓▓▓▓                                   
39                                     ▓▓▓▓▓▓▓                                    
40                                       ▓▓▓                                      
4142
43                             ETH SINGLE STAKING OPTION VAULT V2
44            Mints covered calls while farming yield on single sided ETH staking farm                                                           
45*/
46
47// Libraries
48import {Strings} from '@openzeppelin/contracts/utils/Strings.sol';
49import {Clones} from '@openzeppelin/contracts/proxy/Clones.sol';
50import {BokkyPooBahsDateTimeLibrary} from '../../external/libraries/BokkyPooBahsDateTimeLibrary.sol';
51import {SafeERC20} from '../../external/libraries/SafeERC20.sol';
52
53// Contracts
54import {ReentrancyGuard} from '@openzeppelin/contracts/security/ReentrancyGuard.sol';
55import {ERC20PresetMinterPauserUpgradeable} from '@openzeppelin/contracts-upgradeable/token/ERC20/presets/ERC20PresetMinterPauserUpgradeable.sol';
56import {Pausable} from '@openzeppelin/contracts/security/Pausable.sol';
57import {ContractWhitelist} from '../../helper/ContractWhitelist.sol';
58
59// Interfaces
60import {IERC20} from '../../external/interfaces/IERC20.sol';
61import {IChainlinkV3Aggregator} from '../../external/interfaces/IChainlinkV3Aggregator.sol';
62import {INativeSSOV} from '../../interfaces/INativeSSOV.sol';
63import {IETHVolatilityOracle} from '../../interfaces/IETHVolatilityOracle.sol';
64import {IOptionPricing} from '../../interfaces/IOptionPricing.sol';
65import {IFeeStrategy} from '../../fees/IFeeStrategy.sol';
66
67interface IRewardsDistribution {
68    function pull(
69        uint256 epoch,
70        uint256 userDeposit,
71        uint256 totalDeposit,
72        address user
73    ) external returns (uint256, uint256);
74}
75
76contract ArbEthSSOVV2 is
77    Pausable,
78    ReentrancyGuard,
79    INativeSSOV,
80    ContractWhitelist
81{
82    using BokkyPooBahsDateTimeLibrary for uint256;
83    using Strings for uint256;
84    using SafeERC20 for IERC20;
85
86    /// @dev ERC20PresetMinterPauserUpgradeable implementation address
87    address public immutable erc20Implementation;
88
89    /// @dev Current epoch for ssov
90    uint256 public currentEpoch;
91
92    /// @dev Expire delay tolerance
93    uint256 public expireDelayTolerance = 5 minutes;
94
95    /// @dev The list of contract addresses the contract uses
96    mapping(bytes32 => address) public addresses;
97
98    /// @dev epoch => the epoch start time
99    mapping(uint256 => uint256) public epochStartTimes;
100
101    /// @notice Is epoch expired
102    /// @dev epoch => whether the epoch is expired
103    mapping(uint256 => bool) public isEpochExpired;
104
105    /// @notice Is vault ready for next epoch
106    /// @dev epoch => whether the vault is ready (boostrapped)
107    mapping(uint256 => bool) public isVaultReady;
108
109    /// @dev Mapping of strikes for each epoch
110    mapping(uint256 => uint256[]) public epochStrikes;
111
112    /// @dev Mapping of (epoch => (strike => tokens))
113    mapping(uint256 => mapping(uint256 => address)) public epochStrikeTokens;
114
115    /// @notice Total epoch deposits for specific strikes
116    /// @dev mapping (epoch => (strike => deposits))
117    mapping(uint256 => mapping(uint256 => uint256))
118        public totalEpochStrikeDeposits;
119
120    /// @notice Total epoch deposits across all strikes
121    /// @dev mapping (epoch => deposits)
122    mapping(uint256 => uint256) public totalEpochDeposits;
123
124    /// @notice Epoch deposits by user for each strike
125    /// @dev mapping (epoch => (abi.encodePacked(user, strike) => user deposits))
126    mapping(uint256 => mapping(bytes32 => uint256)) public userEpochDeposits;
127
128    /// @notice Epoch eth balance per strike after accounting for rewards
129    /// @dev mapping (epoch => (strike => balance))
130    mapping(uint256 => mapping(uint256 => uint256))
131        public totalEpochStrikeEthBalance;
132
133    // Calls purchased for each strike in an epoch
134    /// @dev mapping (epoch => (strike => calls purchased))
135    mapping(uint256 => mapping(uint256 => uint256))
136        public totalEpochCallsPurchased;
137
138    /// @notice Calls purchased by user for each strike
139    /// @dev mapping (epoch => (abi.encodePacked(user, strike) => user calls purchased))
140    mapping(uint256 => mapping(bytes32 => uint256))
141        public userEpochCallsPurchased;
142
143    /// @notice Premium collected per strike for an epoch
144    /// @dev mapping (epoch => (strike => premium))
145    mapping(uint256 => mapping(uint256 => uint256)) public totalEpochPremium;
146
147    /// @notice User premium collected per strike for an epoch
148    /// @dev mapping (epoch => (abi.encodePacked(user, strike) => user premium))
149    mapping(uint256 => mapping(bytes32 => uint256)) public userEpochPremium;
150
151    /// @dev epoch => settlement price
152    mapping(uint256 => uint256) public settlementPrices;
153
154    /*==== EVENTS ====*/
155
156    event ExpireDelayToleranceUpdate(uint256 expireDelayTolerance);
157
158    event AddressSet(bytes32 indexed name, address indexed destination);
159
160    event EmergencyWithdraw(address sender, uint256 ethWithdrawn);
161
162    event NewStrike(uint256 epoch, uint256 strike);
163
164    event Bootstrap(uint256 epoch);
165
166    event NewDeposit(
167        uint256 epoch,
168        uint256 strike,
169        uint256 amount,
170        address user,
171        address sender
172    );
173
174    event NewPurchase(
175        uint256 epoch,
176        uint256 strike,
177        uint256 amount,
178        uint256 premium,
179        uint256 fee,
180        address user,
181        address sender
182    );
183
184    event NewSettle(
185        uint256 epoch,
186        uint256 strike,
187        address user,
188        uint256 amount,
189        uint256 pnl
190    );
191
192    event NewWithdraw(
193        uint256 epoch,
194        uint256 strike,
195        address user,
196        uint256 amount,
197        uint256 ethAmount
198    );
199
N/A