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. A wallet doesn't need a transaction policy to be swept, 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 destination wallet that receives swept funds.
- The fee wallet that pays transaction fees.
- 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. This includes Ethereum, Solana, and Tron when those blockchains are available to your organization.
Palisade uses just-in-time fee funding for sweeps. When a source wallet needs native asset to pay the network fee, Palisade estimates the fee, transfers native asset from the fee wallet to the source wallet, and then creates the sweep transaction.
Palisade currently transfers about 3 times the estimated network fee to help account for fee changes before confirmation. You can't currently configure this multiplier or pre-fund enough native asset for several future sweeps through the sweep configuration.
After the sweep, any unused native asset remains in the source wallet. Palisade doesn't currently reclaim this remaining balance automatically. If the same source wallet qualifies for a later sweep, Palisade considers the existing native asset balance before it sends more native asset from the fee wallet.
- 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.
- Set the minimum amount that triggers a sweep for each asset.
- Select the destination wallet.
- Select the fee wallet. You must enable the fee wallet on the same blockchain as the sweep. For blockchains that use native asset for fees, the fee 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.
- Trigger the sweep manually.
- 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 fund source wallets, checks the configuration again on the next hourly or daily run, and lets you trigger the sweep manually after funding the fee wallet. |
| Small native asset balances remain after a sweep | Expect this behavior. Palisade leaves unused native asset in source wallets and considers it during later sweeps. |
Palisade doesn't currently 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 and fee-funding transfers.
- 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 sweeps.
- Test the sweep in sandbox before you configure it in production.