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.2 KiB
1.2 KiB
issue, title, severity, domain, labels, status, created, source
| issue | title | severity | domain | labels | status | created | source | |||
|---|---|---|---|---|---|---|---|---|---|---|
| 110 | Scanner: TON worker O(N) HTTP fan-out per scan cycle — one TonCenter call per intent | medium | Scanner |
|
open | 2026-05-30 | Full Codebase Audit 2026-05-30 |
Scanner: TON worker O(N) HTTP fan-out per scan cycle — one TonCenter call per intent
Severity: medium Domain: Scanner Labels: performance, scanner, scalability
Description
scanner/ton_chain.go:131 issues one TonCenter API call per pending intent per scan cycle. With N pending intents, this creates N outbound HTTP calls per cycle. Under load or with many intents, this exhausts outbound connection capacity and hits TonCenter rate limits.
Options
- Batch intents by destination/jetton and query once per group.
- Bounded-concurrency worker pool for per-intent calls.
- Subscribe to TonCenter streaming/index instead of polling.
Recommendation
Batch queries by jetton/destination where the API allows; otherwise bound concurrency. A TODO is already noted in the code.
Affected Files
scanner/ton_chain.go:131
References
- Full Codebase Audit 2026-05-30 — DEC-66