Consolidate only the dust whose value survives two-chain execution costs. For an integrator, that means grouping small balances by source chain, quoting each route, and comparing the net destination amount with the cost of leaving or moving the assets separately.
Net destination value decides what to consolidate
Define a threshold in the portfolio’s accounting currency, then include source gas, swap fees, broker commission, and destination egress in the estimate. For example, a $12 balance may be worth sweeping when it shares a source-chain transaction with other assets; the same balance can be uneconomic when it needs its own gas-heavy deposit and payout.
Compare that with a $150 residual spread across Ethereum and Arbitrum. Combining the two into one cross-chain route may simplify the target allocation, but it does not combine their source transactions: each chain needs its own funded wallet and deposit. Chainflip can take a native asset on one supported chain and pay out a native asset on another, so it is useful when the rebalance actually crosses chains rather than merely consolidating bookkeeping entries.
Estimate with a live quote, not a spot-price conversion. The Ethereum.org glossary’s distinction between gas and execution cost is relevant: source gas is paid by the wallet sending the deposit, while the swap’s output is reduced by protocol and destination-chain costs.
The deposit, swap, and payout form one execution path
For a deposit-channel swap, the integrator opens a channel with the source asset, destination asset and address, refund address, and price limits. The user sends funds to the returned address; validators witness the deposit after the required chain confirmations, the State Chain records it, and the JIT AMM processes the trade before the network broadcasts the destination payout.
That route can pass through one or more pools, commonly via USDC when the pair has no direct pool. The Chainflip liquidity pools matter when estimating that route: each pool leg can add its liquidity fee and price impact, while the protocol network fee is charged once per swap. Current documented typical fees are 0.10%–0.15% per pool, plus a 0.10% network fee with a $0.50 minimum; source gas, destination broadcast costs, and any broker commission are additional.
Use a minimum accepted price and a retry duration so a poor quote does not silently execute. If the limit is missed until the retry window expires, funds are refunded to the source address, with refund and broadcast costs potentially still deducted. DCA can split larger trades into chunks, but it often adds delay without improving execution for dust-sized amounts; the protocol may reduce the requested chunk count when chunks fall below its per-asset minimum.
Build the sweep around explicit checks
Chainflip’s SDK exposes chain support, required confirmations, quotes, and recommended slippage parameters; fetch these at runtime because asset availability and network parameters can change. A deposit channel expires after 24 hours, so create it close to the time the user can send funds and surface the expiry with the deposit instructions.
- Enumerate residual balances by source chain and exclude assets below your configured minimum value after estimated source gas.
- Request a quote for each proposed source-to-target route, including broker commission, pool legs, estimated destination fees, and the minimum output the user will accept.
- Open one deposit channel per source asset with the correct destination address, source-chain refund address, retry duration, and slippage limits.
- Check that the channel is still open and the deposit amount meets the quoted route’s assumptions before showing the address to the user.
- Track each deposit through confirmation, swap, and egress; reconcile actual output against the quote and update the portfolio only after payout is observed.
Keep separate deposits separate in your state model: a failed or expired channel for one chain should not block successful payouts from another. The decision changes when source gas is subsidized, balances can be batched in a single source-chain transaction, or the portfolio target is on the same chain; in those cases, a local transfer or delayed sweep may preserve more value than a cross-chain swap.