Processing

Sweep Deposits to a Treasury

Deposits land on many per-user addresses; treasury operations need them in one place. This guide sweeps balances into a treasury address, simulating first so a fee shortfall never leaves a stuck sweep. Works across eth, btc and tron.

Before you start
  • Funded deposit addresses derived from a wallet.
  • A treasury address and an API key with C2 access.

1Simulate the sweep before signing

Build or request the sweep, then simulate it. On TRON confirm the source has energy; on EVM confirm gas is covered before you sign.

curl -X POST https://api.1st-node.com/v1/tx/eth/simulate \
  -H "Authorization: Bearer sk_live_..." \
  -d '{"raw":"0x02f8..."}'
> {"success":true,"revert_reason":null}

2Issue the sweep

Call /v1/tx/{chain}/sweep with the source addresses and the treasury destination. The endpoint consolidates balances into the treasury.

curl -X POST https://api.1st-node.com/v1/tx/tron/sweep \
  -H "Authorization: Bearer sk_live_..." \
  -d '{"from":["TQ1n7...","TR8h2..."],"to":"TTreas..."}'
> {"hash":"7c9f...","swept":2}

3Confirm settlement

Poll the returned hash or wait on your webhook. Reconcile the treasury balance against the sum of swept deposits.

Frequently asked

How do I avoid stuck sweeps on TRON?

TRC-20 sweeps consume energy. Stake, delegate or rent energy to the source address first, and simulate the sweep to confirm the energy budget is met.

Can I sweep several addresses at once?

Yes. Pass multiple source addresses in the sweep body; balances consolidate into the single treasury destination in one call.

Keep reading

Top up, get a key, ship.

Self-serve. Pay in crypto or card. Metered by credits — heavy primitives cost more, simple ones are cheap.

Get API key