Logo
Workspace

Proxy Pools

Save, merge, tag, and reuse proxy collections across tools and runtimes.

Proxy pools are reusable collections of proxy entries. They are the main way to turn one-off task results into repeatable workflows.

Proxy Pools

What a Pool Stores

FieldMeaning
NameHuman-readable pool name.
DescriptionOptional context for the pool.
EntriesSaved proxy strings.
TagsLowercase labels for filtering and workflow stage.
Source toolTool that created the entry.
Source taskTask ID and task name where the entry came from.
Added atTimestamp for entry creation or merge freshness.

Pools are capped at 100 saved pools.

Save Modes

ModeUse when
Create newBuilding a new candidate set or final list.
Save to existingAdding results into an established pool.
MergePreserving existing entries while adding new rows.
ReplaceRebuilding a pool from a known-clean current result set.

Dedupe and Tags

ZeroTrace Proxy dedupes pool entries by exact proxy string. When an incoming proxy already exists, it merges useful metadata and tags instead of creating a duplicate row.

Tiny merge behaviors:

  • tags normalize to lowercase
  • tags dedupe and sort
  • source metadata merges when entries collide
  • newest added timestamp is kept during merge
  • legacy single-file pool storage can migrate into the index/detail format
  • orphaned pool detail files can be trimmed

Recommended tag families:

Tag typeExamples
Workflowchecked, benchmarked, leak-clean
Protocolhttp, https, socks5
Qualityhigh, stable, low-latency
Sourcecloud, html-source, manual
Use caserotation, chain, export

Maintenance Routine

  1. Re-check older pools before using them.
  2. Benchmark pools that will feed rotators.
  3. Leak-test pools that will be exported or used for anonymity-sensitive work.
  4. Remove repeatedly dead, leaked, or unstable entries.
  5. Keep final pools separate from raw or experimental pools.

Use separate pools for workflow stages. For example: raw extracted, checked alive, benchmark winners, and leak clean.

On this page