Audits
The audit does not give any warranties on the security of the code, utility of the code, sustainability of the business model, regulatory regime for the business model, or any other statement about fitness of the contracts to purpose, or their bug free status. The audit documentations are for discussion purposes only. You should always conduct your own research and risk analysis.
“The contracts were completely manually analyzed, their logic was checked and compared with the one described in the documentation. Besides, the results of the automated analysis were manually verified. The audit showed no critical issues.” - SmartDec.
Conclusion: “Smart contracts have been audited and several suspicious places have been spotted. During the audit 1 critical issue was found, one issue was marked as major because it could lead to some undesired behavior, also several warnings and comments were found and discussed with the client. After working on the reported findings all of them were resolved or acknowledged (if the problem was not critical). So, the contracts are assumed as secure to use according to our security criteria.” - MixBytes
“In this report, we considered the security of staking smart contracts of Opium Network project. We performed our audit according to the procedure described below. The code is of high quality. The initial audit showed only a few issues of low severity. They do not endanger project security in any way.
After the audit, the code base was updated to the latest version. In this version, the developers added the documentation, also code quality issues were fixed.” - Pessimistic
“The audited scope includes a staking mechanism based on Opium protocol. Staking contract allows users to organize and participate in pools of some specific positions on Opium core protocol. The project includes two main modules: a staking module that implements general staking functionality and a position tokenization module that wraps Opium positions into ERC-20 token.” - MixBytes
Last modified 1yr ago