Opium Network
  • Opium Documentation
  • Introduction to Opium
    • What is Opium
    • FAQs
  • Restrictions
    • Restrictions
  • Security and Audits
    • Disclaimer
    • Audits
    • Bounty program
  • Governance
    • Decentralized setup
    • Governance flow
      • Proposal creating
      • Process of voting – technical description
    • $Opium governance token
  • For users
    • Opium.Finance
    • opium.exchange
  • FOR DEVELOPERS
    • Deployment Addresses
      • Opium Protocol v2
      • Opium Protocol v1
    • High-level overview
    • Opium Protocol V2
      • Core
      • Registry
      • SyntheticAggregator
      • OracleAggregator
      • OpiumProxyFactory
      • OpiumPositionToken
    • Opium Protocol V1
      • Core
      • Registry
      • TokenMinter
      • TokenSpender
      • SyntheticAggregator
      • OracleAggregator
      • Helpers
      • Interfaces
      • Common Errors
        • OracleAggregator Errors
        • Core Errors
      • oID - Oracle recipe
      • sID - Derivative recipe
      • EIP-2547: Composable Multiclass Token
    • Tutorials
      • OracleId examples
      • SyntheticId examples
      • End-to-end tutorial
    • Opium API
      • Subgraph V2
      • Subgraph V1
    • SDK
      • Opium V2 SDK
      • Opium Finance Pools SDK
      • Swap Rate SDK/API
  • Complex description
    • Glossary
    • Opium derivatives
    • Oracle and derivative recipes
    • Oracle and derivative registers
    • Opium margin
    • Opium swaps (TMtm)
    • Opium order books
Powered by GitBook
On this page
  • Disclaimer
  • Audits
  • Audit of Opium Protocol V2 done by Pessimistic
  • Audit of Opium Protocol V2 done by Igor Gulamov
  • Audit of Opium Protocol V1 done by SmartDec
  • Audit of Opium Protocol V1 done by MixBytes
  • Audit of staking smart contracts of Opium Network done by Pessimistic
  • Audit of staking smart contracts of Opium Network done by MixBytes

Was this helpful?

  1. Security and Audits

Audits

PreviousDisclaimerNextBounty program

Last updated 3 years ago

Was this helpful?

Disclaimer

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.

Audits

Audit of Opium Protocol V2 done by Pessimistic

Audit of Opium Protocol V2 done by Igor Gulamov

Audit of Opium Protocol V1 done by SmartDec

“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.

Audit of Opium Protocol V1 done by MixBytes

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

Audit of staking smart contracts of Opium Network done by Pessimistic

“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

Audit of staking smart contracts of Opium Network done by MixBytes

“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

Read the full report here
Read the full report here
Read the full report here
Read the full report here
Read the full report here
Read the full report here