Destination calls

​

When to use

• One-click cross-chain protocol deposits (“deposit USDC into our Arbitrum vault from any chain”)
• Bridge-and-swap into a non-stable destination asset
• Pay an invoice that requires a specific contract call beyond a transfer
• Cross-chain auto-stake or auto-compound flows

​

How it works

1. The intent’s route.calls array contains one or more Call structs, { target, value, data }, to execute on the destination chain.
2. The solver fronts the destination-chain tokens to the Executor.
3. The Executor runs each call sequentially. If any call reverts, the entire intent reverts. The solver pays only gas; the user gets refunded.

struct Call {
    address target;
    uint256 value;
    bytes data;
}

​

Examples

​

Bridge and deposit

calls[0] = Call({
    target: tokenAddress,
    value: 0,
    data: abi.encodeCall(IERC20.approve, (vaultAddress, amount))
});
calls[1] = Call({
    target: vaultAddress,
    value: 0,
    data: abi.encodeCall(IVault.deposit, (amount, beneficiary))
});

​

Bridge, DEX swap, transfer

calls[0] = Call({ target: tokenIn, value: 0, data: approveCalldata });
calls[1] = Call({ target: dexRouter, value: 0, data: swapCalldata });
calls[2] = Call({ target: tokenOut, value: 0, data: transferCalldata });

​

Constraints