Scope
What part of codebase is being audited and what is it being audited for? Examples: software bugs, game theory, cryptography, economics, etc.
- Verify Spigot concept can work
- financial math of Line of Credit contract
- Line status states, transitions, and logic
- Access controls on Line and Spigot
- 0x and Chainlink integrations
Spec
What is the intended functionality for the code being audited
N/A testing suite at commit freeze
Commit Freeze
Git commit hash of codebase that auditors will review and link to github/gitlab of repo where they can clone the repo.
Final Report
Mirrored PDF of audit report found at link in headers.
Debt_DAO_P2P_Loan_Smart_Contract_Security_Audit_Report_Halborn_Draft.pdf21462.8KB
High Severity Issues
Mirrored PDF of audit report found at link in headers.
- Issue Name
- Github issue # - X
- Notion ticket # - X
- Link to changes made - X
- Link to tests writen for changes showing fixes - X
- Issue Name #2
Medium Severity Issues
MirroredIssues identified by auditors that are high risk / low value or low risk / high value that we resolved.
- Issue Name
- Github issue # - X
- Notion ticket # - X
- Link to changes made - X
- Link to tests writen for changes showing fixes - X
- Issue Name #2
Acknowledged Severity Issues
Issues that Debt DAO team deemed as invalid or or risks worth accepting
