EYWA
  • Eywa v2
    • πŸ’₯Eywa v2: new era of Web3 interoperability
  • Eywa token
    • πŸ’ŽTokenomics Eywa/CrossCurve
    • πŸ“ˆEywa token utility
    • ⚑Eywa NFT Collection
      • Eywa NFT Bridge from Aurora to Arbitrum
      • Merge interface in the Arbitrum chain
      • EYWA NFT Manager interface
      • Dashboard interface
    • 🏒Eywa DAO
      • Overview of EYWA DAO
      • Voting
      • Obtaining veEYWA and Calculating the Boost
      • Staking
  • EYWA Ecosystem
    • πŸ’‘Vision
    • πŸ—ΊοΈProduct & EYWA token Roadmap
    • πŸ—οΈProducts
      • Eywa v1
        • Cross-chain Liquidity Protocol
          • Cross-chain DEX v1
          • Eywa Token Bridge
          • Gasless transactions
        • Cross-chain Data Protocol
          • Eywa CDP Introduction
          • Eywa Oracle Network
          • Data transfer flow
      • Eywa v2
        • πŸŒ‰Consensus Bridge
        • ⚑CrossCurve
    • πŸ›‘οΈSecurity audits
    • 🧠Team
    • πŸ¦„Project History
    • πŸ”—External Links
    • ❓FAQ
  • User documentation
    • πŸ’ΈEywa DEX
      • About EYWA Cross-chain DEX
      • Interface Eywa WebApp
      • How to trade
      • Slippage settings
      • Routing
      • Operation Interruption
        • Slippage condition
        • Data transfer error
    • 🏒DAO
      • EYWA Locker Interface
      • Working with the EYWA Locker contract in Arbiscan.
      • EYWA Vote Interface
      • EYWA Incentives Interface
    • πŸ”—Contracts addresses
      • Cross-chain Liquidity Protocol
        • CLP smart-contracts
        • Supported stablecoins
        • Addresses of Eywa stableswap pools
        • Addresses of s-tokens
        • Addresses of e-tokens
      • Cross-chain Data Protocol
        • Governance of Eywa Oracle network
        • Cross-chain messaging
  • DEVELOPER DOCUMENTATION
    • πŸ’»Guide for Developers
      • Technical Documentation for EYWA DAO Smart Contracts
        • EmissionManagerV1
        • EscrowManager
        • EscrowVoteManagerV1
        • GaugeFactoryV1
        • GaugeV1
        • IncentiveRewardsDistributor
        • ProposalManager
        • RebaseRewardsDistributorV1
        • RewardsDistributorFactoryV1
        • CalldataHelperV1
        • Treasury
        • DelegationManagerV1
        • DelegationConditionValidatorV1
        • LockHolderFactoryV1
        • LockHolderV1
  • Eywa Oracle Network - will be ENDED in April 2024
    • πŸ₯‡Validators token distribution
    • Incentivised PoA mainnet
      • General information
      • Application for participation in PoA mainnet
      • Requirements for PoA mainnet validators
      • Rewards for PoA mainnet
      • Instruction for node operators
    • FAQ
  • βš–οΈLEGAL INFORMATION
    • Terms of Service
    • Protocol Disclaimer
    • Cookies Policy
    • Risk of using Eywa
Powered by GitBook
On this page
  • Eywa DAO Security Audit Report by MixBytes
  • EYWA CLP security audit by MixBytes
  • EYWA CDP security audit by Smartstate
  • EYWA CLP security audit by Smartstate
  • Security audits by Hexens
  1. EYWA Ecosystem

Security audits

Eywa DAO Security Audit Report by MixBytes

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.

EYWA CLP security audit by MixBytes

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.

EYWA CDP security audit by Smartstate

The core architectural element of the EYWA ecosystem is the EYWA Cross-chain Data Protocol, which is a transport layer between blockchains. All EYWA products for DeFi users are based on this protocol.

Although at the time of this audit the core of EYWA multisig is represented by a trusted group of projects, EYWA aims for DAO, as reflected in EYWA 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

EYWA CLP security audit by Smartstate

EYWA 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

Security audits by Hexens

PreviousCrossCurveNextTeam

Last updated 4 months ago

πŸ”— to MixBytes EYWA reports.

πŸ”— to SmartState EYWA reports.

The Hexens team of EYWA, such as the BLS cryptography module in EYWA CDP as well as EYWA NFT.

πŸ›‘οΈ
Link
Link
audited various components
5MB
Eywa DAO Security Audit Report.pdf
pdf
3MB
Eywa CLP Security Audit Report.pdf
pdf
5MB
05062305_EYWA_CDP_SΠ‘_report.pdf
pdf
CDP report from SmartState
10MB
05062302_EYWA_CLP_SΠ‘_report.pdf
pdf
CLP report from SmartState