---
issue: 131
title: "Scanner: Tron/TON workers don't share HTTP transport — no connection reuse"
severity: low
domain: Scanner
labels: [performance, scanner]
status: open
created: 2026-05-30
source: Full Codebase Audit 2026-05-30
---

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

**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

1. Use a shared `http.Client`/`Transport` with `MaxIdleConnsPerHost` set.
2. Per-worker clients but with explicit transport tuning.
3. 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](../09%20-%20Audits/Full%20Codebase%20Audit%20-%202026-05-30.md) — DEC-70