Our team of experienced auditors, researchers, and engineers will thoroughly review your project to identify code vulnerabilities and weaknesses that could compromise its security or functionality.
Before the audit starts, the Chain+ team will request access to the repository and the definition of the commit hash to be used during the audit. The audit begins with a joint meeting, during which the client walks us through the codebase and provides all available documentation, including the test suite. We recommend that tests provide code coverage above 90%. A joint communication channel is established between both teams, and the meeting dates are set.
During the audit
The Chain+ team will develop a deep understanding of the protocol's intended use cases and internal mechanics. This insight will be leveraged to identify potential issues, exploits, and attack vectors. The code will be matched against the technical specification. The client's team and our auditors will have many meetings to discuss the audit progress.
Initial report
When the review phase is complete, the client will receive an initial document listing issues and points of attention. The client will evaluate the list of findings while our team works on the audit report, which also evaluates the documentation provided by the client and the quality of the test suite. Once the initial audit report is ready, it is shipped to the client.
Reaudit
The client evaluates the report and performs the fixes in the code, and may request more information and meetings with the Chain+ team. When the client finishes, we recheck the code. This process is repeated until both teams reach a final decision — the client comments on every issue, and those comments become part of the audit report. The final report is then sent to the client for final approval.