How Swap Proceeds Can Pay for a Contract Call

A swap can fund a follow-on contract call by sending its output tokens to a contract on the destination chain, then calling that contract with instructions you set in advance. This lets an app turn one asset into another and use the result in a second action, such as adding funds to a pool. The call needs a compatible receiver and enough of the output reserved to pay the destination chain’s transaction fee.

How does a swap trigger a contract call?

The swap request includes a destination address, a message for the receiver, and a gas budget—the amount of transaction capacity set aside for the contract’s work. On supported chains, Chainflip’s cross-chain messaging feature carries that information with the swap. If you want the basics of its wallet routes first, read how Chainflip sends swaps to your wallet. The route details are separate from the contract call, which depends on the destination chain and receiver.

When the swap finishes, the destination transaction sends the output asset to the receiver and passes along your message. On EVM chains—networks that run Ethereum-style smart contracts—the receiver must support Chainflip’s cfReceive function. The function can read the token and amount received, then use them in its own logic. For example, it could pass the swapped tokens into a decentralized exchange or another supported contract.

How much of the swap output funds the call?

The output has to cover both the contract action and the network’s transaction fee. The gas budget covers the receiver’s logic; Chainflip estimates the required fee and deducts the cost from the swap output. That means the amount left for the follow-on action can be lower than the quoted swap output. A larger gas budget can allow more complex work, but it can also raise the amount set aside for fees.

Before starting the swap, work out what the receiver will do and estimate the gas for that exact call. Check these details:

• The destination chain supports cross-chain messaging.
• The receiver implements the required interface for that chain.
• The message contains the inputs the receiver needs, such as a pool or action choice.
• The gas budget covers the receiver’s logic, with room for usage to vary.

On Solana, the equivalent budget is measured in compute units, and extra account details are needed. On AssetHub, supported calls use a different format and transaction fees are deducted from the output. The implementation differs by chain, so a message built for one receiver cannot simply be reused on another.

What can go wrong with a follow-on call?

A call can fail if the message is malformed, the receiver does not accept the call, the action’s conditions are not met, or the gas budget is too small. A failed call may prevent the funds from reaching the intended destination. Some chains have a fallback route for failed calls; others handle the failure differently. Test the receiver with the expected token, amount, and message before committing funds.

There is also a practical trade-off: a direct wallet payout is simpler and leaves the next decision to you, while a follow-on call can complete several steps in one swap flow. Use the call when the next action is clear and the receiver is built to handle the incoming asset safely. Treat the gas budget as part of the amount you are swapping, since it reduces what remains for that action.