A time-boxed security review of the protocol name protocol was done by CD Security, with a focus on the security aspects of the application's implementation.
A smart contract security review can never verify the complete absence of vulnerabilities. This is a time, resource, and expertise-bound effort where we try to find as many vulnerabilities as possible. We can not guarantee 100% security after the review or even if the review will find any problems with your smart contracts. Subsequent security reviews, bug bounty programs, and on-chain monitoring are strongly recommended.
explanation of what the protocol does, some architectural comments, technical documentation
| Severity | Impact: High | Impact: Medium | Impact: Low |
|---|---|---|---|
| Likelihood: High | Critical | High | Medium |
| Likelihood: Medium | High | Medium | Low |
| Likelihood: Low | Medium | Low | Low |
Impact - the technical, economic, and reputation damage of a successful attack
Likelihood - the chance that a particular vulnerability gets discovered and exploited
Severity - the overall criticality of the risk
review commit hash - fffffffff
The following smart contracts were in scope of the audit:
SmartContractNameSmartContractName
The following number of issues were found, categorized by their severity:
- Critical & High: x issues
- Medium: x issues
- Low: x issues
| ID | Title | Severity |
|---|---|---|
| [C-01] | Any Critical Title Here | Critical |
| [H-01] | Any High Title Here | High |
| [M-01] | Any Medium Title Here | Medium |
| [L-01] | Any Low Title Here | Low |
Impact:
Likelihood: