A reviewed sweep rule for one chain and asset.
1. Start with one tested asset
Back up the wallet, enable the asset in an enabled store and make a small manual transfer first. Verify the receiving network and destination yourself. Automatic rules authorize real, irreversible transfers.
Native sending covers 29 chains; Monero stays view-only. Token sending covers supported ERC-20 and classic SPL. Lightning spending is managed outside this sweep system.
2. Choose the destination
Open Project → Sweep → Automatic Sweep Setup. Find the chain/token and click Setup. Choose an address-book entry or enter a wallet address.
Alternatively, connect Kraken, Binance or Coinbase in Settings → Exchanges and add a compatible route under Exchange destinations. One asset can sweep to a wallet or an exchange, not both at once.
Do not use a destination requiring a memo, tag or comment. Outgoing reference destinations are not supported. Use a compatible wallet instead. Exchange deposit minimums apply to each transaction, not the combined sweep total. Confirm the exact deposit network and any restrictions.
Optional market conversion starts only after a matched deposit is credited. Exchange fees, slippage, custody and account restrictions apply; fiat remains at the exchange. Exchange setup →
3. Set trigger, reserve and fees
The sweep minimum decides when there is enough to send. Keep minimum amount sets what remains across the project’s wallets for that asset.
Trigger at 100 USDC and keep 20 USDC: send up to 80 USDC. Native gas is separate. This is a project-wide reserve, not 20 USDC at every address.
Choose a fee level and review the maximum network fee limit. A small balance may not be worth moving yet. Reserves, actual fees and provider readiness can reduce or pause a transfer.
4. Give tokens native gas
USDC/USDT on Ethereum need ETH at each token-holding address. ETH at another project address must be transferred there first. Other EVM networks need their own native coin; Solana tokens need SOL.
Keep Use project ETH for gas (or the matching native coin) enabled if you want Wholly Crypto to fund missing fees from the same project and chain. Only eligible token-holding addresses are funded, not empty unpaid invoice addresses.
Set a Daily funding limit in the displayed reporting currency. It caps native funds allocated by this token rule over a rolling 24 hours. €1 can be a starting point for light use, not a guaranteed cost or a daily charge. More addresses or higher fees may need more. Funding transactions have their own fees.
Unused funded coins stay in your own addresses. This does not spend all project ETH or make network fees disappear. Understand address-level gas →
5. Save and enable the rule
Review the full destination, network, asset, retained amount and fee/funding limits. Turn on Auto sweep, save and confirm. Opening Setup alone does not enable a rule.
Keep native funds available, providers usable and processing credit healthy. Checks run in the background; you do not need to keep the page open or repeatedly click Check gas.
If server-wide sending is disabled, inspect whollycrypto transfers status. Review all enabled rules before an administrator enables transfers: saved rules may start immediately. Sending safety →
6. Follow Transfer activity
Actual work appears under Transfer activity: gas funding, waiting for confirmations and then token sending. Open Details for amounts, limits and transaction explorer links. A broadcast is not yet a confirmation.
If a plan pauses, inspect its reason and refresh that existing transfer. Do not create a replacement while a broadcast is uncertain. Disabling a rule stops future work; it cannot reverse a transaction already sent.
Low credits pause new sending and gas funding. Once credit recovers, enabled rules can resume. Keep unwanted rules off. Idle assets with nothing to send are not an ongoing transfer.