Cold-address sized rentals
Deposit addresses rarely hold USDT, so each first-time sweep needs the larger cold pack — request it per address, on demand.
API docs live on docs.eopen.io
Use the external docs as the source of truth for endpoints, fields, auth, and migration notes. Open API docs →
EOPEN
TRON Energy API for Collection Wallets & Sweeps
Sweep USDT from many cold, low-balance deposit addresses into treasury without pre-funding TRX on each one — rent 131K Energy per address on demand and reconcile every sweep on-chain.
Plan a sweep runEnergy for Collection Sweeps, Address by Address
No TRX pre-funding across thousands of deposit addresses
EOPEN lets collection systems delegate Energy to each deposit address right before a sweep, so the treasury moves USDT without seeding TRX everywhere or burning it transfer by transfer.
131K
Energy per cold address
No pre-fund
TRX off each address
Per-address
Delegation + tx hash
Batch
Sweep windows
Sweep Workflow
No TRX seeding
Skip the operational drag of pre-funding TRX on every deposit address; delegate Energy only to the ones you are about to sweep.
Reconcilable by address
Each delegation returns a tx hash you can tie to the deposit address and sweep batch for clean financial reconciliation.
01
Why deposit addresses are the expensive case
Collection addresses are the textbook cold case: most are freshly generated, hold no USDT until a deposit lands, and have never sent a TRC-20 transfer. The first sweep from each one consumes about 130,285 Energy — roughly double a hot transfer — because a first-time sender triggers extra contract storage on chain. Burning that costs around 13 TRX per address, and at sweep scale across thousands of addresses that turns deposit collection into a recurring TRX drain.
- Cold deposit address: ~130,285 Energy per sweep (use a 131,000-Energy pack).
- Each transfer also needs ~350 Bandwidth, which a busy address may not have either.
- Pre-funding TRX on every deposit address just to sweep it later is capital and ops overhead you do not need.
02
Worked example: a 1,000-address sweep run
Take a treasury sweeping 1,000 cold deposit addresses in one window. Burning TRX at 13 TRX each costs about 13,000 TRX for the run. Renting 131,000-Energy cold packs at a typical 3.5 TRX per address brings that to about 3,500 TRX — savings of up to 80% on the Energy line — and you never had to scatter TRX across 1,000 addresses to begin with. For very large runs, a 500,000-Energy bulk pack (typical ~12 TRX) can cover several sweeps from one delegation.
- Burn path: 1,000 × 13 TRX ≈ 13,000 TRX per run.
- Rental path: 1,000 × ~3.5 TRX ≈ 3,500 TRX per run.
- Reserve a 500,000-Energy bulk pack ahead of the window for the largest sweeps.
03
How EOPEN fits a sweep pipeline
Your collection service detects funded deposit addresses, requests a cold Energy pack for each one just before sweeping, waits for the delegation, then moves USDT to treasury. Order IDs and tx hashes flow back so finance can reconcile every sweep against its address.
- REST API to delegate Energy per deposit address on demand.
- Tx hash returned for on-chain proof against each sweep.
- Bulk packs and dedicated pool options for large, scheduled windows.
Next steps
Delegate 131,000-Energy packs per deposit address at sweep time — no TRX pre-funding, just a clean ~3.5-TRX line per address you can reconcile on-chain.
Core API flow
- 1Authenticate your collection service with its API key.
- 2For each funded deposit address, request a cold Energy quote (~131,000 Energy) just before the sweep — or a 500,000-Energy bulk pack for a large window.
- 3Submit the order and delegate Energy to that deposit address; capture the tx hash.
- 4Sweep USDT to treasury at the rented rate (~3.5 TRX) instead of burning ~13 TRX, and reconcile by address and order ID.
Collection FAQ
Why do deposit-address sweeps cost more than normal transfers?
Most deposit addresses are cold — newly generated and never having sent USDT. The first sweep needs about 130,285 Energy (roughly 2x a hot transfer) because first-time senders trigger extra contract storage, so a 131,000-Energy pack is the right size.
Do we have to keep TRX on every collection address?
No. EOPEN delegates Energy to a deposit address only when you are about to sweep it, so you avoid seeding and topping up TRX across thousands of addresses.
Can we reconcile each sweep for finance?
Yes. Every delegation returns an order ID and on-chain tx hash you can tie to the deposit address and sweep batch for clean reconciliation.
Migration & verifiability
Why do I see different field names in old docs vs new docs?
Field naming and migration details are maintained on docs.eopen.io. This page keeps only the collection-wallet and sweep scenario overview.