nick-doc/Issues/ISSUE-131-scanner-tron-ton-workers-dont-share-http-transport.md at aac297d2417c7b0f02fbfcf8278163bb4b4abd99

Files

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

1.1 KiB

Raw Blame History

issue, title, severity, domain, labels, status, created, source

issue

title

severity

domain

labels

status

created

source

131

Scanner: Tron/TON workers don't share HTTP transport — no connection reuse

low

Scanner

performance

scanner

open

2026-05-30

Full Codebase Audit 2026-05-30

Severity: low Domain: Scanner Labels: performance, scanner

Description

scanner/tron_chain.go:38 creates separate http.Client instances per worker without a shared http.Transport. This means TCP connections to the same host are not reused across workers, increasing latency and connection overhead.

Options

Use a shared http.Client/Transport with MaxIdleConnsPerHost set.
Per-worker clients but with explicit transport tuning.
Leave as-is.

Recommendation

Share a single tuned transport across workers for connection reuse.

Affected Files

scanner/tron_chain.go:38
scanner/ton_chain.go — similar pattern

References

Full Codebase Audit 2026-05-30 — DEC-70

1.1 KiB Raw Blame History