Eonian Docs
WebsiteBlogResources
  • ♾️Welcome to Eonian
  • Basics
    • πŸš€Get Started
      • πŸ€—How to Deposit Crypto
      • πŸ›‘οΈHow to Enable Insurance
      • 🍰How to Withdraw Crypto
    • πŸ›‘οΈThe Eonian Protocol
    • πŸ’ͺFeatures and Benefits
    • 🌴What Can I Do With Eonian?
    • βš™οΈHow Eonian Works
      • The Insurance Pool
      • Savings Premium
      • Assets Recovery
    • πŸ––Guides
      • Recovering Assets After a Wallet Hack
    • ❓FAQs
  • PROTOCOL
    • πŸ«‚Governance & DAO
      • Dispute Process
      • Founders
    • 🌾Yield Aggregator
    • ⛰️Roadmap
      • Alpha Test
      • Closed Beta Test
      • Public Beta Test
      • Release v1
    • βš–οΈEconomic Model
      • Risks and Revenue Analysis
      • Revenue Distribution
      • Future Outlook
  • Security
    • πŸ›‘οΈSecurity Overview
    • πŸ“‘Audits
      • πŸ“‹Vertical Audits
    • ⏰Intelligent Emergency Shutdown
  • Ambassador Program
    • ⭐Ambassador Program Overview
    • 🎁The Rewards for Ambassadors
    • πŸš€Onboarding Guide and Roadmap
    • πŸ’ŽReward System
    • πŸ€—The Community Roles
      • πŸ’¬Discord Discussions XP and Levels
      • πŸ’ŒDiscord Invites System
    • πŸ‘‘The Ambassador Roles
      • ❀️Community Advocate
      • πŸŽ‰Crypto Evangelist
      • πŸ–ŒοΈThe Creator
  • Resources
    • πŸ“ˆOpen Statistics
    • ❀️Marketing Collaboration Contacts
    • πŸ‘Job Opportunities
    • 🎨Brand Guide / Media Press Kit
  • Discord
  • Twitter
  • Telegram
  • Medium
  • Github
  • Zealy
  • Galxe
Powered by GitBook
On this page
  • Audits
  • Quick Check by TechRate
  • Audit by Bunzz
  • Code Analysis
  • OpenZeppling Defender Code Inspector
  • Vertical Audits

Was this helpful?

Edit on GitHub
  1. Security

Audits

This a page with audits of Eonian protocol conducted by third-party companies

PreviousSecurity OverviewNextVertical Audits

Last updated 11 months ago

Was this helpful?

Security is critical for us, which is why we need to ensure that our smart contract code doesn't contain any vulnerabilities, exploits, or security issues. We perform different automated checks through linters and code analyzers for our codebase on each update. You can read about it there:

Additionally, we plan to validate each significant smart contract protocol change through third-party audit firms. Starting from the first audit performed before our public beta release.

Audits

Quick Check by TechRate

First quick check audit of our protocol that was performed by during closed beta.

Summary

No vulnerabilities were found.

Audit by Bunzz

The first full audit was conducted by the as part of the preparation for the public beta release.

Summary

Only three low-impact potential vulnerabilities were found. All are fixed by our team.

Code Analysis

OpenZeppling Defender Code Inspector

Summary

No high or medium-impact potential vulnerabilities were found.

Vertical Audits

Our team also performs independent audits on other protocols before we integrate with them:

We conduct automated code analysis on all changes in smart contracts. You can see them in real-time in our . There we collect few latest reports.

Analysis was conducted using the Code Inspector tool.

πŸ“‘
repository
OpenZepplin Defender
πŸ“‹Vertical Audits
πŸ›‘οΈSecurity Overview
TechRate
Bunzz team
2MB
openzepplin-defender-conde-inspector-report.pdf
pdf
96KB
Quick Check Audit (TechRate).pdf
pdf
1MB
bunz_audit_final.pdf
pdf
Audit source on Bunzz site