Send Omnichain Transactions
To make your first cross-chain transaction, make sure that:
- The account is deployed on any chain.
- The account has at least one of the supported assets on the chain with the deployed account.
Assuming you had USDC on Base Sepolia, this will bridge some of that USDC to Arbitrum Sepolia and execute the transfer transaction.
If the smart account is not deployed on the target chain (i.e., Arbitrum Sepolia), it will also deploy the account code on that chain.
calls
and tokenRequests
corresponds to the target chain.Token Requests
tokenRequests
is a list of token assets and their amounts that are required on the target chain to make the transaction. It tells the solvers to ensure those assets are present before executing the transaction calls
. If you don’t need any assets on the target chain, you can omit this.
tokenRequests
. If the user already has the required assets, don’t add them into tokenRequests
.Gas Limit
You can override the default gas limit for the target chain execution with gasLimit
. Doing this will make the intent better priced, because we can more accurately calculate the fee that a solver needs to be reimbursed with for paying the gas. If this is not provided, we calculate using a gas limit of 1_000_000.
Source Chain
Providing the source chain deploys the account on that chain, as well as uses the funds on that chain to fulfill the intent.
If you already have an account deployed on one or more source chains, you can omit the sourceChain
. In that case, the orchestrator will use the best chain(s) to source funds.
sourceChain
is required when working with session keys.