π‘οΈSecurity audits
Last updated
Last updated
1. Project architecture review:
Build an independent view of the project's architecture.
Identifying logical flaws.
2. Checking the code in accordance with the vulnerabilities checklist:
Eliminate typical vulnerabilities (e.g. reentrancy, gas limit, flash loan attacks etc.).
3. Checking the code for compliance with the desired security model:
Detect inconsistencies with the desired model.
4. Consolidation of the auditors' interim reports into one:
Double-check all the found issues to make sure they are relevant and the determined threat level is correct.
Provide the Client with an interim report.
5. Bug fixing & re-audit:
Verify the fixed code version with all the recommendations and its statuses.
Provide the Client with a re-audited report.
6. Final code verification and issuance of a public audit report:
Conduct the final check of the code deployed on the mainnet.
Provide the Customer with a public audit report.
5MBEywa DAO Security Audit Report.pdfpdf
A group of auditors are involved in the work on the audit. Security engineers check the provided source code independently of each other in accordance with the methodology described below:
1. Project architecture review:
Build an independent view of the project's architecture.
Identifying logical flaws.
2. Checking the code in accordance with the vulnerabilities checklist: Eliminate typical vulnerabilities (e.g. reentrancy, gas limit, flash loan attacks etc.).
3. Checking the code for compliance with the desired security model:
Detect inconsistencies with the desired model.
4. Consolidation of the auditors' interim reports into one:
Double-check all the found issues to make sure they are relevant and the determined threat level is correct.
Provide the Client with an interim report.
5. Bug fixing & re-audit:
Verify the fixed code version with all the recommendations and its statuses.
Provide the Client with a re-audited report.
6. Final code verification and issuance of a public audit report:
Conduct the final check of the code deployed on the mainnet.
Provide the Customer with a public audit report.
3MBEywa CLP Security Audit Report.pdfpdf
π Link to MixBytes EYWA reports.
The core architectural element of the CrossCurve ecosystem is the CrossCurve Cross-chain Data Protocol, which is a transport layer between blockchains. All CrossCurve products for DeFi users are based on this protocol.
Although at the time of this audit the core of CrossCurve multisig is represented by a trusted group of projects, CrossCurve aims for DAO, as reflected in CrossCurve project current documentation.
CDP Smart Contracts: These smart contracts serve as a means for sending and accepting cross-chain calls. They also include a node registration contract used in the Proof of Authority (POA) consensus among oracle nodes.
Smart State evaluation: 8/10
5MB05062305_EYWA_CDP_SΠ‘_report.pdfpdfCDP report from SmartState
CrossCurve Cross-chain Liquidity Protocol ensures the operation of EYWA DEX v1
CLP smart contracts - are smart contracts for processing synth and burn operations, as well as mint and lock tokens. They are also responsible for swap processing and liquidity handling operations.
Smart State evaluation: 10/10
10MB05062302_EYWA_CLP_SΠ‘_report.pdfpdfCLP report from SmartState
π Link to SmartState CrossCurve reports.
The Hexens team audited various components of CrossCurve, such as the BLS cryptography module in CrossCurve CDP as well as EYWA NFT.