Audit-to-deploy gap
Kamino Lend's assessment for RD-F-006 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Per-version audit model — each version has corresponding audit(s) named by version number; audit-to-deploy gap appears within days/weeks per version, well within the 60-day green threshold.
Detail #
Audit files are named kamino_lend_ottersec_1.13.0.pdf through kamino_lend_ottersec_1.16.0_and_1.17.0.pdf, indicating version-specific audits timed with releases. The per-version cadence suggests the audit was conducted alongside or immediately before each version release.
Sources #
- GitHubKamino Finance Audits RepositoryAudits repo file naming by version: kamino_lend_ottersec_1.13.0.pdf through kamino_lend_ottersec_1.16.0_and_1.17.0.pdfretrieved 2026-04-27
Methodology #
Measure the number of days between the audit report sign-off date and the mainnet deploy of the audited bytecode.
See the full factor methodology and distribution across all protocols →