Before the audit
Agree the scope with the audit firm, freeze the code at a tagged commit and prepare the documentation the auditors need.
An audit report is a list of problems, not a fix. We take it from there. We coordinate with the audit firm, triage every finding, fix the ones that need fixing with regression tests, and see the changes through the auditors' fix review, with the deployment prepared. It works whether or not we wrote the code.
01 / WHO THIS IS FOR
02 / WHAT WE DO
Agree the scope with the audit firm, freeze the code at a tagged commit and prepare the documentation the auditors need.
Answer the auditors' questions quickly, so their time goes into finding issues rather than understanding the code.
Classify each finding as fix, mitigate or acknowledge, with the reasoning written down.
Fix each finding with a minimal change and a regression test that fails before the fix and passes after it.
Prepare the response to each finding and support the auditors while they review the fixes.
A deployment checklist and scripts. The mainnet deployment is done with your keys, with our support.
Every fix is new code that the auditors did not review in the first pass. A large refactor in the middle of an audit can introduce the next bug, so we keep each change as small as the finding allows, and we tell you clearly when a finding needs a deeper redesign.
03 / WHAT YOU GET
| DELIVERABLE | FORM |
|---|---|
| Each finding fixed in its own commit, with a regression test | Repository |
| A response document covering every finding, whether fixed, mitigated or acknowledged, and why | Document |
| Updated documentation and NatSpec | Repository |
| A deployment checklist and scripts | Repository |
05 / FAQ
No. The audit is done by an independent firm. We handle the work around it.
We can share what to look for and help you compare scopes and quotes. The choice is yours.
We tell you before touching the code, with the options and their cost, so you can decide whether to fix it now, mitigate it or move the launch date.
Yes. We start by reading the code, the report and the documentation, and the fixed price reflects how well documented the codebase is.
Nobody can promise that. Remediation closes the findings from the audit, but it does not prove that no other bugs exist. A second audit, a bug bounty or a staged launch can reduce the remaining risk.