<aside> ℹ️ We aren’t picky about how you get us this information! Most clients just send us a message with everything directly in the communication channel we are using, though you are welcome to create a doc that you share with us if you prefer.
</aside>
[ ] Link to your repo/s. If your repo isn’t public, we’ll also ask you to add the auditor doing the estimate to the repo.
[ ] List of contracts and the commit hash you want us to review.
<aside> ‼️ Including interfaces and dependencies.
</aside>
[ ] Documentation for all steps needed to set-up your project and run your test suite.
[ ] All environment variables we need to run your contracts and test suite.
<aside>
👉 Ideally, a .env file with dummy values/accounts you don't mind us using. At minimum, an .env.example file we can populate with our own accounts.
</aside>
[ ] Links to existing documentation, blog posts, or other information describing what your project does, how it is architected, and any relevant set-up information.
What we need to deliver an estimate
How to get the best estimate and audit
General Security Best Practices