Skip to main content
Relay now fully supports depositing & withdrawing to Solana from any EVM chain we support. This is a great way to get users funds on Solana to complete transactions. You can onboard users funds from Blast ETH to Solana USDC to make transactions on a game. You could also swap funds from Solana SOL to Zora ETH for users to mint. The possibilities are limitless when you use Relay embedded in your app.

Required Information

There are few things that make transacting on Solana different than another EVM chain. The provided information below should review all the exceptions where your input is Solana specific.
Solana wallet addresses are case sensitive.

SDK Properties

When withdrawing from Solana using the SDK, you will not need to specify the depositing wallet address.

Solana Tokens

In the table, we have provided the most frequently used Solana tokens & their contract addresses. We do support all tradeable tokens on Jupiter.
Solana token addresses are case sensitive.
Relay supports any Solana token available on Jupiter. You can visit Jupiter to explore all the tokens available.

API

Params

Execution

Once you have the necessary information, you can start utilizing our API for full Solana withdrawal and deposit support. To get started, check out the execution steps of our API. Then when you’re ready to swap, head over to the Get Quote API endpoint. Please note that instead of the usual calldata returned with EVM transactions, there’s different calldata that needs to be handled accordingly.

Example: Deposit to Solana from Base

Transaction Size Optimization

Solana transactions have a hard 1232-byte wire limit. Relay gates every Solana-origin quote — same-chain and cross-chain — against this raw limit at quote time, so a quote that returns successfully is guaranteed to be signable and broadcastable as-is. When the compiled deposit transaction would exceed 1232 bytes, POST /quote, POST /quote/v2, and POST /price return a 400 response with errorCode: "SOLANA_TX_TOO_LARGE" and a message that reports the measured size and the number of bytes over the limit:
Re-quoting the same route with the same input typically returns another oversized route. To recover, restrict routing (see the mitigations below) or retry with a different input amount.
Wallets and SDKs that prepend compute-budget instructions at send time (roughly 60 bytes) are responsible for checking that their additions still fit under 1232 bytes. A quote that fits the wire limit exactly leaves no room for client-added instructions — clients that add them should measure the returned steps and skip the injection if there is not enough room.
Pass includedOriginSwapSources in your quote request to restrict routing to a single, size-conservative source:
Pass maxRouteLength in your quote request to limit the number of hops in the Solana swap routing. Fewer hops means a smaller transaction. Recommended values: For the full list of quote parameters, see the Get Quote API reference.

SDK

To use the SDK with Solana, install and configure the SVM wallet adapter. The adapter handles transaction signing and broadcasting.
For implementation details and code samples, see the Adapters documentation.