Security
Smart contract security is a top priority for those working on Aura Finance. All reasonable precautions must be taken to ensure the protocol is safe to use. Below is a list of some of the things we believe make smart contract systems secure.
PeckShield-Audit-Report-AuraFinance-v1.0.pdf
389KB
PDF
A $150k, 2 week long audit competition ran on https://code4rena.com/ allowed anyone with knowledge of the system, or just general bug hunters, a chance to come and contribute to the security of the Aura system before launch.
Code4rena-Audit-Report-AuraFinance-v1.0.pdf
802KB
PDF
Halborn-Audit-Report-AuraFinance-v1.0.pdf
3MB
PDF
External bug bounties are essential for projects. Aura has placed a $1m critical bug bounty payout on Immunefi.
Some practices employed on Aura Finance smart contract repositories:
- protected
masterbranch with mandatory peer reviews and passing CI (including linting, compiling, and testing) - >98% code coverage (using coveralls) and comprehensive integration tests
- Strict linting rules
- Code commented using the Natspec standard
Fork testing is helps simulate contract deployments and functionality in a live environment, accounting for external dependencies. Aura comprehensively tests deployments using fork tests.
Developers know their code best, and dedicated time has been taken to manually review all code in the system.
If you have any feedback or concerns, reach out to
[email protected] or to an admin on Discord
Last modified 7mo ago