Files
nick-doc/Issues/ISSUE-132-scanner-evm-checkpoint-saved-every-2000-block-chunk.md
Siavash Sameni dceaf82934 audit: 2026-05-30 full-codebase audit — report, issues, docs, runbooks
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>
2026-05-30 18:48:04 +04:00

39 lines
1.1 KiB
Markdown

---
issue: 132
title: "Scanner: EVM checkpoint saved every 2000-block chunk — write amplification during catch-up"
severity: low
domain: Scanner
labels: [performance, scanner]
status: open
created: 2026-05-30
source: 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
1. Save checkpoint only at end of a successful scan cycle.
2. Save every N chunks (larger N) during catch-up.
3. 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](../09%20-%20Audits/Full%20Codebase%20Audit%20-%202026-05-30.md) — DEC-71