dceaf82934
Full-codebase-audit 2026-05-30 outputs: - Audit report: 09 - Audits/Full Codebase Audit - 2026-05-30.md - 81 issue files ISSUE-055..135 (decisions + 1 skipped no-brainer). - Scanner docs from scratch (was zero): architecture, data model, API ref, payment flow, operations runbook + repo README. - Doc-sync updates across API reference, data models, flows, design system. - Secret Rotation Runbook (08 - Operations) for the exposed credentials. - Reusable workflow guide (07 - Development) + .claude/workflows/full-codebase-audit.js. Issues remain status:open intentionally — the code fixes are uncommitted-then-committed working-tree changes per repo and aren't "resolved" until merged/deployed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
issue, title, severity, domain, labels, status, created, source
| issue | title | severity | domain | labels | status | created | source | ||
|---|---|---|---|---|---|---|---|---|---|
| 132 | Scanner: EVM checkpoint saved every 2000-block chunk — write amplification during catch-up | low | Scanner |
|
open | 2026-05-30 | Full Codebase Audit 2026-05-30 |
Scanner: EVM checkpoint saved every 2000-block chunk — write amplification during catch-up
Severity: low Domain: Scanner Labels: performance, scanner
Description
scanner/chain.go:260 saves the checkpoint to SQLite after every 2000-block chunk during catch-up. For a scanner catching up thousands of blocks, this means many small writes per cycle. Saving once per successful scan cycle (or every large N during deep catch-up) would reduce write load.
Options
- Save checkpoint only at end of a successful scan cycle.
- Save every N chunks (larger N) during catch-up.
- Leave as-is (SQLite WAL is efficient).
Recommendation
Persist the checkpoint once per successful cycle (or every large N during deep catch-up).
Affected Files
scanner/chain.go:260
References
- Full Codebase Audit 2026-05-30 — DEC-71