Treasury should reconcile Chainflip swaps from deposit to payout

Treasury teams should reconcile each Chainflip swap by matching the source deposit to the actual destination payout and recording fees at execution. The deposit starts the swap, but it does not establish the final amount received: the protocol processes the trade through liquidity pools, then deducts destination-chain broadcast costs from the output.

That makes a swap a linked set of events across chains, rather than a single exchange entry. Record the source asset and quantity, destination asset and quantity, both transaction hashes, timestamps, fees, and the value in the company’s reporting currency under its approved valuation policy.

Route choice affects which pools and fees appear in the record. For the mechanics behind comparing paths, see how Chainflip selects a swap route; the ledger should still follow the executed transactions, not just the quoted route.

Which transactions belong in a Chainflip reconciliation?

Match the source-chain deposit, the protocol’s execution record, and the destination-chain payout using their transaction hashes and amounts. A deposit channel or direct vault call registers the intended destination asset, chain and address; the deposit alone does not prove the swap completed.

Use the protocol’s explorer or transaction records to connect the incoming transfer with its swap status and outgoing transfer. Keep the source and destination network fees distinct: the sender pays the source-chain fee, while Chainflip deducts an estimated broadcast fee from the payout for the destination chain.

How should treasury record the swap value and fees?

Record the amount actually received, then reconcile the difference from the source amount as the trade result and separately identified costs. Value both sides at the transaction times using the treasury’s established pricing source and policy; retain the rates and timestamps so a reviewer can reproduce the reporting-currency amounts.

Chainflip’s documentation lists liquidity fees of 0.10% to 0.15% per pool and a network fee of 0.10%, with a $0.50 minimum. A route through more than one pool can incur liquidity fees at each step. Source-chain gas, destination broadcast costs and any broker charge are separate lines where they apply, not unexplained reductions to the asset balance.

• Source asset, quantity, chain and deposit transaction hash.
• Destination asset, quantity, chain, recipient address and payout hash.
• Execution timestamp, reporting-currency valuation and pricing source.
• Network, liquidity, gas, broker or refund fees, recorded by type.

What should happen when a swap is delayed or refunded?

Leave an unmatched deposit in a pending reconciliation account until the protocol confirms execution, refund or another terminal status. Confirmation times vary by source chain, so a delay between deposit and payout does not by itself establish a loss or completed trade.

If slippage protection is not met within the retry period, the protocol can refund the deposit to the specified source-chain address, less applicable fees; a DCA swap can also complete in part and refund the remainder. Reconcile each payout and refund separately against the original deposit, then close the item when the chain records and treasury ledger agree.