Asset sweeping moves funds from multiple source wallets to a single destination wallet on a schedule. As an owner or administrator, you configure sweep workflows to consolidate funds, simplify treasury management, and reduce the number of wallets that hold active balances.
Sweeps create on-chain transactions and incur network fees.
A sweep configuration defines:
- Which blockchain to sweep
- Which assets to include and the minimum amount that triggers a sweep
- Which wallet receives swept funds (Deposit wallet)
- Which wallet pays transaction fees (Fees wallet)
- How often the sweep runs (hourly or daily)
You don't select source wallets in the sweep configuration. Instead, each wallet has a Sweeping toggle in its settings. When the sweep runs, Palisade checks sweep-enabled wallets that are eligible for the sweep blockchain. If a source wallet's available balance meets the minimum amount for a configured asset, Palisade creates a transaction to move those funds to the destination wallet. Pending or frozen balances don't count toward the sweep amount.
You can create only one sweep configuration per blockchain. Add all assets that you want to sweep on that blockchain to the same configuration.
Use the blockchain dropdown in Settings > Workflows to see supported sweep chains in your organization. The sweep workflow supports the blockchains shown in that dropdown, including Bitcoin, Ethereum, Solana, Tron, and XRP Ledger when they 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, and the fee wallet must hold the blockchain's native asset. How the fee wallet 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, Tron, and XRP Ledger | Palisade uses just-in-time fee funding. |
For a source wallet on a just-in-time fee-funded blockchain, Palisade:
- Calculates the native asset amount the source wallet needs. On Ethereum and other EVM chains, and on Tron, this is about three times the estimated network fee, to account for fee changes before the transaction confirms. On the XRP Ledger, it's the amount the account needs to send the sweep, pay the buffered network fee, and keep its reserve, minus what the account already holds.
- Transfers that native asset from the fee wallet to the source wallet.
- Creates the sweep transactions from the source wallet to the destination wallet. The source wallet pays its own network fees.
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 set a sweep to pre-fund enough native asset for several future sweeps.
If the fee wallet can't cover the fee funding for a run, Palisade records a failed sweep instance and checks the configuration again on the next scheduled 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 described in Fee funding.
On the XRP Ledger, sweeps never touch the account reserve — the base reserve plus the owner reserve for each object the account owns. The source account keeps its reserve and stays activated, and Palisade accounts for the reserve when it calculates fee funding.
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.
After Palisade completes a just-in-time fee-funded sweep, unused fee funding remains in the source wallet. Palisade tracks this balance as its own fee funding, doesn't reclaim it or return it to the fee wallet automatically, and never sweeps it to your destination wallet.
For token sweeps and XRP Ledger sweeps, Palisade offsets the wallet's existing native 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. If you create a new receive wallet for each deposit and sweep each wallet only once, each wallet may retain a small fee-funding balance after its sweep. On the XRP Ledger, the account also keeps its reserve.
Enable sweeping on each wallet that acts as a source. The sweep configuration applies to every enabled source wallet on the selected blockchain.
- Open the wallet and select the Settings gear icon.
- Go to the Sweeping tab.
- Turn on Sweeping.
- Turn on Outgoing transactions for the wallet.
Before you create a sweep configuration:
- For each source wallet, turn on Sweeping and Outgoing transactions.
- You must provision the Deposit wallet on the sweep blockchain.
- You must enable the wallet that you select in Fees wallet on the sweep blockchain. For blockchains that use native asset for fees, this wallet must hold enough native asset to pay transaction fees.
- Palisade can sweep only source wallets that are eligible for the sweep blockchain.
Asset sweeping bypasses transaction policies. Palisade can sweep a source wallet without a transaction policy, and existing transaction policies don't block sweep transactions. To restrict sweeping, manage the wallet's Sweeping setting and the sweep configurations in Settings > Workflows.
- Go to Settings > Workflows.
- Select Create sweep.
- Enter a name (5 to 50 characters) that describes the sweep.
- Enter an optional description (5 to 100 characters).
- Select the blockchain for this sweep. Palisade marks blockchains that already have a sweep configuration and prevents you from selecting them.
- Add one or more assets to sweep:
- Select a standard asset from the Asset dropdown, or select Switch to non-standard asset to enter a symbol and contract manually.
- To sweep the blockchain's native asset, select it from the standard Asset dropdown — for example, BTC, ETH, TRX, or XRP. Palisade doesn't support non-standard Bitcoin assets for sweeping.
- Set the minimum sweep amount - the smallest balance that triggers a sweep from a source wallet.
- Select the Deposit wallet - the wallet that receives swept funds. The list groups wallets by vault.
- Select the Fees wallet - the wallet that pays transaction fees. You must enable this wallet. For blockchains that use native asset for fees, fund it with the blockchain's native asset.
- Set the frequency:
- Hourly - the sweep runs every hour.
- Daily - the sweep runs once per day.
- Select Create.
You can create only one sweep configuration per blockchain. If you need to sweep multiple assets on the same blockchain, add them all to the same configuration.
Each sweep triggers automated transactions on your behalf. Make sure the sweep settings, wallet settings, and Deposit wallet are correct before you enable a sweep.
After creating a sweep, you can manage it from Settings > Workflows:
Toggle the sweep on or off. A disabled sweep doesn't run on its schedule but retains its configuration.
Select Manual sweep to run the sweep immediately outside its normal schedule. Use this to test the configuration or to sweep funds on demand.
Select the sweep configuration, then select Update to change the name, description, assets, wallets, or frequency.
Select the sweep configuration, then select Delete. Deleting a sweep stops all future runs and removes the configuration.
Each time a sweep runs, Palisade creates a sweep instance that records the results.
- Go to Settings > Workflows.
- Select the sweep configuration.
- View the list of sweep instances with their status, timestamp, and transaction details.
- Select an individual instance to see which wallets Palisade swept and which transactions Palisade created.
If the fee wallet doesn't have enough native asset, Palisade can't fund source wallets that need fee funding for that run. Palisade records a failed sweep instance and checks the configuration again on the next selected cadence, either hourly or daily. You can also top up the fee wallet and run a manual sweep.
Palisade doesn't send a dedicated webhook when the fee wallet balance is low or empty. Transaction webhooks notify you about status changes for transactions that Palisade creates, but they don't replace fee wallet balance monitoring.
| 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 configuration. |
| Palisade doesn't sweep a wallet | Make sure the wallet is eligible for the sweep blockchain, has Sweeping enabled, has Outgoing transactions enabled, and has an available balance that meets the minimum sweep amount. |
| A sweep keeps retrying without creating sweep transactions | Make sure the fee wallet holds enough native asset to pay sweep transaction fees or fund source wallets, depending on the blockchain. |
| Small native asset balances remain in source wallets | Expect this behavior on just-in-time fee-funded chains. Palisade leaves unused fee funding in the source wallet and considers it on 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. |
- Monitor fee wallet balances - keep enough native asset in each fee wallet for scheduled sweeps. For Bitcoin and Solana, the fee wallet pays sweep transaction fees directly. For just-in-time fee-funded chains, the fee wallet funds source wallets before the sweep transaction.
- Test in sandbox first - create and run a sweep in sandbox before you configure production sweeps.
- Set appropriate minimum amounts - set minimum sweep amounts high enough to avoid creating many small transactions that cost more in fees than they consolidate.
- Account for remaining native asset - if you use one-time receive wallets, plan for small native asset balances to remain after just-in-time fee-funded sweeps.
- Monitor sweep execution - review sweep instances, use audit logging to track sweep activity, and use webhooks for transaction status changes when Palisade creates sweep transactions.
- Asset sweeping - Reference documentation
- Configure wallets and vaults - Enable sweeping on individual wallets
- Policy concepts - Understand why sweep transactions bypass policies