Solana Migration Guide
Last updated
Last updated
Across is expanding support to Solana, enabling seamless USDC bridging between Ethereum Mainnet, other supported chains and Solana. The migration is scheduled to go live soon. All integrators and relayers are encouraged to complete the necessary updates before the migration happens to prevent disruptions.
For Solana routes, check out this utility script demonstrating how to call deposit()
with the integratorID for seamless transaction execution.
Developers are requested to build transactions by fetching details from the API, adding integratorID and calling the deposit()
function in the SVM SpokePool contract to execute deposit transactions. We will let you know as soon as Solana routes are available in the /suggested-fees
API.
There are no changes in the API's response body. However please note that you will be able to see Solana addresses (in Pubkey format) in fields like recipient
, inputToken
, outputToken
, spokePoolAddress
, exclusiveRelayer
and destinationSpokePoolAddress
.
We do not support Solana devnet or testnet at the moment. We urge developers and integrators to test their Solana integration using the Solana mainnet with small amount of tokens. We will let you know as soon as we are live and you can begin testing.
Solana is not currently supported in the Across App-SDK. We’re actively working on expanding support and improving the developer experience for Solana. Stay tuned — we’ll share updates as soon as it becomes available.
Relayers supporting Solana will need:
A valid Solana address to perform fill operations.
The following package dependencies:
@across-protocol/sdk
@across-protocol/contracts
@solana/kit
(previously @solana/web3.js@^2.0.0
)
While each relayer can decide how to manage their Solana addresses, the recommended approach is deriving the Solana address from the same private key used for EVM operations. This approach minimizes the need to store additional secrets.
When filling to or from Solana, relayers must always specify a valid address on the chain where they request repayment. Failing to do so may result in loss of funds.
For relayers, the most significant update for relayers is the transition from fillV3Relay
to fillRelay
for handling crosschain transactions:
For deposits from Solana to EVM chains:
Relayers monitor for deposit events on Solana
Use fillRelay
to complete the fill transaction on the EVM destination. You can learn more about it here.
For deposits from EVM chains to Solana:
Monitor for deposit events on EVM chains
Use Solana-specific fill functions to complete the transaction
We use emit_cpi!() method in Anchor to emit events through a Cross Program Invocation (CPI) by including the event data in the instruction data. Here, you need to fetch all transactions involving the SVM Spokepool program and inspect the internal event data. Please checkout the helper in the SDK to implement this.
The deposit function is used when users want to transfer funds from Solana to an EVM chain:
Relayers use this function to complete crosschain transactions:
Want to learn more or need personalized help? Check out developer support and reach out to us!