Transfer of Reserve Tokens with Arbitrary Instruction

function depositReserveTokenAndExecute(
        bool isSourceNative,
        bool isAppTokenPayer,
        bytes calldata swapData,
        bytes calldata executeData,
        bytes calldata arbitraryData,
        bytes calldata requestMetadata
    ) external payable;

The flow is just the same as that of the reserve token transfer explained before. The only difference here is the arbitrary data that you need to pass and state whether the tokens that need to be swapped are to be deducted from the user or the application.

Arbitrary Data

Arbitrary Data is the abi encoded data that comprises of:

1. destContractAddress: Address of the contract which will be called after the transfer is complete. This contract needs to implement the voyagerReceive function (details given below).
2. data: This is the abi encoded arguments that will be passed to the function that should be called on the destination contract address. The data should exclude the address and amount of tokens received as the amount may vary according to the fees. The address of the token and exact amount of tokens received by the user will be accessible into the handler function directly on the destination chain.
3. gasLimit: The gas limit required for your function to be executed on the destination chain. The fees that we deduct from you will depend on this.
4. gasPrice: Current gas price of the destination chain. The fees that we deduct from you will depend on this.

voyagerReceive

The arbitrary instruction that you provide here will be executed on the destination chain on the contract address that you specify. That contract must implement the voyagerReceive function given below.

function voyagerReceive(
        address sourceSenderAddress,
        bytes32 srcChainIdBytes,
        bytes memory data,
        address settlementToken,
        uint256 settlementAmount
    ) external;

With this function, you will receive:

1. sourceSenderAddress: the address of the sender of transaction from the source chain.
2. srcChainIdBytes: the identifier of the source chain.
3. data: Data for the params to the function for which the selector was received passed from the source chain.
4. settlementToken: Address of the token which was received to the recipient after the transfer.
5. settlementAmount: Amount of the settlement tokens received to the recipient after the transfer.

Inside the voyagerReceive function on the destination chain, you will decode the data according to the requirements of the function selector and call that function which will complete the instruction execution.