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.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.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 size limit. If you append custom instructions to the transaction (e.g., for tracking, fee collection, or other logic), the combined transaction can exceed this limit and fail. When a Solana-origin quote is routed through a third-party aggregator and the generated deposit transaction would exceed 1232 bytes,POST /quote/v2 returns
a 400 response instead of a successful quote with calldata that cannot be
executed. Use the mitigations below to keep transactions under the limit.
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: