Arbitrum uses EVM account addresses and ETH for source gas. Solana uses Solana accounts, transaction signatures, and SOL for destination activity. A 0x address is not a valid substitute for the Solana receiving address shown by the route. SOL uses SOL contract token on the source; DAI uses DAI contract token on Solana.
Base58-encoded Solana account address A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path. A compatible wallet may create or use an associated token account, and SOL—not DAI unless it is SOL—pays later Solana fees.
ETH is the native gas asset for Arbitrum. SOL is contract-tracked and can require an allowance before transfer. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval.
DAI is a crypto-backed dollar-oriented stablecoin whose canonical and bridged contracts vary by network. Its peg design does not make two network representations interchangeable. The destination wallet must support the exact Solana representation. The route converts a native-asset source into a stablecoin balance; the destination ticker alone is not a contract check.
Route-specific mistakes include sending on a network other than Arbitrum; using a destination that is not valid for Solana; running out of ETH before the source transaction is submitted; assuming evm and solana addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.
Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Arbitrum. The recorded Arbitrum representation uses 9 decimal places. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead.
Dai is classified as a stablecoin for this route. DAI uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.
Arbitrum wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this SOL on Arbitrum to DAI on Solana path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Base58-encoded Solana account address; it does not hide either chain's public records.
No. The destination must be a Solana-compatible address. Base58-encoded Solana account address
An SPL-token receipt uses the relevant mint and token account; the wallet or route may create an associated token account when needed. SOL is used for later Solana activity.
SOL is a contract representation on Arbitrum with 9 decimals at 0x2bcC6D6CdBbDC0a4071e48bb3B969b06B3330c07. ETH, not SOL, pays gas unless both symbols are the same. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead.
DAI is a contract representation on Solana with 8 decimals at EjmyN6qEC1Tf1JxiG1ae7UTJhUxSwk1TCWNWqxWV4J6o. SOL, not DAI, pays gas unless both symbols are the same. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.
Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. On receipt, The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.
SOL is the deposited native-asset input; DAI is the quoted stablecoin output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The receiving wallet must recognize the exact destination DAI contract. Peg intent does not guarantee that a bridged representation has the same liquidity or issuer path.
Requirements are checked for the live SOL Arbitrum to DAI Solana quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.
