Asset sweeping consolidates assets from source wallets into a destination wallet on a schedule. Use it when you receive deposits across many wallets and want Palisade to move those balances into a treasury or operations wallet.
Sweeps create on-chain transactions and incur network fees. Only owners and administrators can configure sweeping operations.
You don't select source wallets when you create a sweep configuration. Instead, you enable sweeping on each wallet that acts as a source.
When a sweep runs, Palisade checks sweep-enabled wallets that are eligible for the configured blockchain. If the wallet's available balance meets the configured minimum amount for a swept asset, Palisade creates a transaction to move that asset to the destination wallet. Pending or frozen balances don't count toward the sweep amount.
To enable a source wallet:
- Open the wallet.
- Go to Settings.
- Turn on Outgoing transactions.
- Go to the Sweeping settings.
- Turn on Sweeping.
Asset sweeping bypasses transaction policies. Palisade can sweep a wallet without a transaction policy, and existing transaction policies don't block sweep transactions.
A sweep configuration defines:
- The blockchain to sweep.
- The assets to sweep and the minimum amount that triggers a sweep.
- The wallet that receives swept funds (Deposit wallet).
- The wallet that pays transaction fees (Fees wallet).
- The sweep frequency, either hourly or daily.
You can create only one sweep configuration per blockchain. Add multiple assets to the same configuration when you need to sweep more than one asset on that blockchain.
Supported blockchains appear in the blockchain dropdown when you create the sweep. The list can include Bitcoin, Ethereum, Solana, Tron, and XRP Ledger when those blockchains are available to your organization.
You can sweep native assets — BTC, ETH, TRX, and XRP — in addition to supported tokens, and one configuration can sweep both on the same blockchain. For Bitcoin, Palisade sweeps native BTC only.
Every sweep configuration needs a fee wallet. The fee wallet pays or funds the network fees for all sweep transactions in a run. How it pays depends on the blockchain:
| Blockchain | Fee model |
|---|---|
| Bitcoin | The fee wallet pays the network fee directly inside the sweep transaction. Palisade doesn't transfer BTC to the source wallet first. |
| Solana | The fee wallet pays the network fee directly as the transaction fee payer. Palisade doesn't transfer SOL to the source wallet first. |
| Ethereum and other EVM chains, and Tron | Palisade uses just-in-time fee funding. Before the sweep transaction, Palisade estimates the network fee and transfers about three times that amount of native asset from the fee wallet to the source wallet. The source wallet then pays its own network fee. |
| XRP Ledger | Palisade uses just-in-time fee funding. The fee wallet tops up the source account with the amount it needs to send the sweep, pay the buffered network fee, and keep its reserve, minus what the account already holds. The source account then pays its own network fee. |
Just-in-time fee funding works the same way for token sweeps and native asset sweeps. When Palisade sweeps several assets from the same source wallet in one run, a single fee-funding transfer covers all of them. You can't configure the fee multiplier or pre-fund enough native asset for several future sweeps through the sweep configuration.
After a just-in-time fee-funded sweep, unused native asset remains in the source wallet. Palisade tracks this balance as fee funding and doesn't reclaim it automatically. For token sweeps and XRP Ledger sweeps, Palisade offsets the existing balance when it calculates the next run's fee funding. For native sweeps on EVM chains and Tron, Palisade funds the full buffered fee on each run.
On Ethereum and other EVM chains, a wallet can't act as both a sweep source and the fee wallet. Choose a dedicated fee wallet that doesn't have sweeping enabled.
You sweep a blockchain's native asset the same way you sweep a token: add BTC, ETH, TRX, or XRP to the sweep configuration and set a minimum amount.
For each sweep-enabled wallet, Palisade tracks native asset ownership — it separates the balance the wallet received as deposits from the native asset Palisade sent for fee funding. A native sweep moves only the deposited balance to the destination wallet, and Palisade never sweeps its own fee funding to your destination.
Palisade doesn't reduce the swept amount to pay the network fee. The fee follows the blockchain's fee model: direct payment from the fee wallet on Bitcoin and Solana, and just-in-time fee funding on Ethereum and other EVM chains, Tron, and the XRP Ledger.
Some native asset stays in the source wallet after a native sweep:
| Blockchain | What stays in the source wallet |
|---|---|
| Ethereum and other EVM chains, and Tron | Unspent fee funding. |
| XRP Ledger | The XRP Ledger reserve — the base reserve plus the owner reserve for each object the account owns. Sweeps never touch the reserve, so the account stays activated. |
If Palisade hasn't finished building a wallet's native ownership records, it skips that wallet's native asset for the run and includes the wallet again after tracking is ready.
- Go to Settings > Workflows.
- Select Create sweep.
- Enter a name for the sweep.
- Enter an optional description.
- Select the blockchain for the assets you want to sweep.
- Select one or more assets to sweep. Use the standard Asset dropdown for listed assets. To sweep the blockchain's native asset, select it from the same dropdown — for example, BTC, ETH, TRX, or XRP.
- Set the minimum amount that triggers a sweep for each asset.
- Select Switch to non-standard asset only when you need to enter an asset symbol and contract manually. Palisade doesn't support non-standard Bitcoin assets for sweeping.
- Select the Deposit wallet. This wallet receives swept funds.
- Select the Fees wallet. You must enable this wallet on the same blockchain as the sweep. For blockchains that use native asset for fees, this wallet must hold the blockchain's native asset.
- Select the sweep frequency: Hourly or Daily.
- Select Create.
- Enable Outgoing transactions and Sweeping on each source wallet.
After you create a sweep, Palisade lists it in Settings > Workflows. Use the actions menu to:
- View sweep details.
- Enable or disable the sweep.
- Run a Manual sweep.
- Delete the sweep configuration.
Open a sweep configuration to review sweep instances. Each instance shows the wallets Palisade checked, the transactions Palisade created, and the result of the run.
| Issue | What to check |
|---|---|
| The fee wallet is missing from the dropdown | Make sure you enabled the wallet and that it uses the same blockchain as the sweep. |
| Palisade doesn't sweep a wallet | Make sure the wallet is eligible for the sweep blockchain, has Outgoing transactions enabled, has Sweeping enabled, and has an available balance that meets the minimum sweep amount. |
| The fee wallet is empty | Top up the fee wallet with native asset. Palisade records a failed sweep instance when it can't pay sweep fees or fund source wallets, checks the configuration again on the next hourly or daily run, and lets you run a manual sweep after funding the fee wallet. |
| Small native asset balances remain after a sweep | Expect this behavior on just-in-time fee-funded chains. Palisade leaves unused fee funding in source wallets and considers it during later sweeps. On the XRP Ledger, the account also keeps its reserve. |
| Palisade doesn't sweep a wallet's native asset | Palisade sweeps native asset only after it finishes building the wallet's ownership records, and skips the wallet when its tracked balance diverges from the on-chain balance. Palisade includes the wallet again on a later run. |
Palisade doesn't send a dedicated webhook when the fee wallet balance is low or empty. Use transaction webhooks to monitor transactions that Palisade creates, and monitor fee wallet balances separately.
- Keep enough native asset in the fee wallet for scheduled sweeps. For Bitcoin and Solana, the fee wallet pays sweep transaction fees directly. For just-in-time fee-funded chains, it funds source wallets before the sweep transaction.
- Set minimum sweep amounts high enough to avoid moving small balances that cost more in fees than they consolidate.
- Plan for small native asset balances to remain in one-time receive wallets after just-in-time fee-funded sweeps.
- Test the sweep in sandbox before you configure it in production.