📑Audits
This a page with audits of Eonian protocol conducted by third-party companies
Last updated
This a page with audits of Eonian protocol conducted by third-party companies
Last updated
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.
First quick check audit of our protocol that was performed by TechRate during closed beta.
Summary
No vulnerabilities were found.
The first full audit was conducted by the Bunzz team 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.
We conduct automated code analysis on all changes in smart contracts. You can see them in real-time in our repository. There we collect few latest reports.
Analysis was conducted using the OpenZepplin Defender Code Inspector tool.
Summary
No high or medium-impact potential vulnerabilities were found.
Our team also performs independent audits on other protocols before we integrate with them: