Scope
What part of codebase is being audited and what is it being audited for? Examples: software bugs, game theory, cryptography, economics, etc.
- Ensure either Spigot or IDLE Finance governance MUST own the FeeCollector contract after migration script ends
- Spigot operates as expected over course of Line lifecycle and returns to IDLE Finance after they repay their debt
- Mainnet fork tests simulating onchain governance vote outcomes
Spec
What is the intended functionality for the code being audited
N/A testing suite
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.
High Severity Issues
Mirrored PDF of audit report found at link in headers.
N/A nothing found
Medium Severity Issues
MirroredIssues identified by auditors that are high risk / low value or low risk / high value that we resolved.
N/A nothing found
Acknowledged Severity Issues
Issues that Debt DAO team deemed as invalid or or risks worth accepting
N/A nothing found
