Send a transaction

Sending a transaction is a three-step flow: prepareTransaction fetches a quote, signTransaction signs it, submitTransaction sends it to the orchestrator. Splitting the steps lets you show the user a quote before they approve, fetch on a backend and sign on a mobile frontend, or pick a non-default route.

Send a single-chain transaction

Pass a chain and a list of calls. The example below transfers USDC on Base Sepolia:

import { encodeFunctionData, erc20Abi } from 'viem'
import { baseSepolia } from 'viem/chains'

const receiver = '0xd8da6bf26964af9d7eed9e03e53415d37aa96045'
const usdcAmount = 1n

const prepared = await rhinestoneAccount.prepareTransaction({
  chain: baseSepolia,
  calls: [
    {
      to: 'USDC',
      value: 0n,
      data: encodeFunctionData({
        abi: erc20Abi,
        functionName: 'transfer',
        args: [receiver, usdcAmount],
      }),
    },
  ],
})
const signed = await rhinestoneAccount.signTransaction(prepared)
const transaction = await rhinestoneAccount.submitTransaction(signed)

const result = await rhinestoneAccount.waitForExecution(transaction)
console.log('Result', result)

Send a cross-chain transaction

Swap chain for sourceChains + targetChain. The SDK handles bridging and routing with no separate bridge interaction required:

import { baseSepolia, arbitrumSepolia } from 'viem/chains'

const prepared = await rhinestoneAccount.prepareTransaction({
  sourceChains: [baseSepolia],
  targetChain: arbitrumSepolia,
  calls: [
    {
      to: 'USDC',
      value: 0n,
      data: encodeFunctionData({
        abi: erc20Abi,
        functionName: 'transfer',
        args: [receiver, usdcAmount],
      }),
    },
  ],
  tokenRequests: [
    {
      address: 'USDC',
      amount: usdcAmount,
    },
  ],
})
const signed = await rhinestoneAccount.signTransaction(prepared)
const transaction = await rhinestoneAccount.submitTransaction(signed)

const result = await rhinestoneAccount.waitForExecution(transaction)

To deploy the account on a specific chain before transacting, call await rhinestoneAccount.deploy(chain) first. Otherwise, any transaction triggers deployment as part of the intent — token transfers, contract calls, approvals, anything.

Custom fill deadline

A transaction’s on-chain fill deadline defaults to 2 minutes. For a same-chain transaction that settles without bridging, extend it with customDeadline — an absolute unix timestamp in seconds. Useful when a user needs longer to approve, or you prepare a quote now and submit it later.

const prepared = await rhinestoneAccount.prepareTransaction({
  chain: baseSepolia,
  calls: [
    /* … */
  ],
  customDeadline: Math.floor(Date.now() / 1000) + 3600, // 1 hour from now
})

The value must be between now + 120s and now + 86400s (24 hours); outside that range the request is rejected.

customDeadline is honored only on same-chain transactions that settle without bridging. On cross-chain transactions it is ignored and the default 2-minute deadline applies.

Next steps

Crosschain

Send funds across chains with a single signature. No bridging required.

Unified balance

Aggregate user balances across chains to fund any intent.

Sponsor fees

Cover gas, bridging, and swap fees for your users.

Tutorials

Smart account setup

Gas & fee sponsorship

Smart Sessions

More features

Configuration

Module development

SDK Reference

Send a single-chain transaction

Send a cross-chain transaction

Custom fill deadline

Next steps

Crosschain

Unified balance

Sponsor fees

​Send a single-chain transaction

​Send a cross-chain transaction

​Custom fill deadline

​Next steps

Crosschain

Unified balance

Sponsor fees

Send a single-chain transaction

Send a cross-chain transaction

Custom fill deadline

Next steps