Wallet Sweep

Overview

Sweeps consolidate deposits, migrate exposed keys, retire wallets, or transfer funds from lower-security addresses. In UTXO systems, sweeping typically creates a transaction spending available outputs, while token networks may require separate transfers and native fee assets.

Importing a private key is not the same as sweeping because the old key remains authoritative. A sweep can also miss tokens, staking positions, contract permissions, unconfirmed funds, or future deposits. Fee estimation and dust can affect the final amount.

Users should verify destination, network, asset inventory, fee funding, and confirmation state. Suspected compromise requires a trusted new wallet and rapid, prioritized execution. Organizations need approval, monitoring, and source-to-destination reconciliation. The old address should remain watched for delayed receipts or attacker activity, while related permissions and integrations are revoked or updated.

The operational record for Wallet Sweep should identify requester, source account or wallet, beneficiary, destination, asset and network, amount, fee basis, policy and limit, approvers, execution service, expected completion rule, and the business or customer obligation that caused the movement.

For Wallet Sweep, risks include unauthorized requests, address substitution, wrong networks, missing memo fields, insufficient fees, duplicate submission, nonce conflicts, provider delay, irreversible delivery, and incomplete accounting. For Wallet Sweep, automation needs balance caps, velocity limits, pause controls, and independently verified destinations.

Wallet Sweep moves through request validation, balance reservation, destination screening, approval, signing or provider submission, broadcast, execution, confirmation, recipient recognition, and ledger posting. For Wallet Sweep, idempotency keys and status queries are essential when a timeout leaves execution uncertain.

Evidence for Wallet Sweep should preserve gross and net amounts, asset, network, destination, beneficiary validation, fees, approvals, external identifiers, status history, replacements, confirmation evidence, recipient outcome, source-balance release, and final ledger entries. Failed and returned movements remain separate events.