Non-EVM destinations

​

What changes vs. EVM destinations

​

Example: USDC from Base to Solana

import { solanaMainnet } from '@rhinestone/sdk'
import { base } from 'viem/chains'

const SOLANA_USDC = 'EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v'
const recipient = 'mvines9iiHiQTysrwkJjGf2gb9Ex9jXJX8ns3qwf2kN'

const prepared = await rhinestoneAccount.prepareTransaction({
  sourceChains: [base],
  targetChain: solanaMainnet,
  recipient,
  tokenRequests: [
    {
      address: SOLANA_USDC,
      amount: 5_000_000n, // 5 USDC, 6 decimals
    },
  ],
})

const signed = await rhinestoneAccount.signTransaction(prepared)
const result = await rhinestoneAccount.submitTransaction(signed)
const status = await rhinestoneAccount.waitForExecution(result)

​

Constraints

• No destination calls. Solana and Tron destinations are claim-only — you can’t pass a calls array on a non-EVM intent. If your flow needs onchain logic on the destination, route to an EVM chain.
• No UserOp path. sendUserOperation and the UserOp transaction shape remain EVM-only.
• No destination-side signing. Smart-session destination signatures are skipped on non-EVM chains — there’s no validator there to verify them. Origin signing is unchanged.
• EIP-7702 authorization is a no-op on non-EVM destinations.
• fillTransactionHash is a plain string. Was Hex on EVM destinations; widened so base58 and Tron hex round-trip cleanly.

​

Tracking the intent