Solana Overview
Introduction
LI.FI offers seamless integration with the Solana blockchain through Mayan, Allbridge and Jupiter.
We only support single step transactions per ecosystem at this point. Currently expanding to support two step transactions across the two ecosystems.
The native SOL is represented using the System Program address 11111111111111111111111111111111
when making requests to the backend. Native Solana doesn’t really have an address, so this is a representation specific to our system.
Wrapped Solana should use the wSOL address So11111111111111111111111111111111111111112
Solana chainID in LI.FI BE is 1151111081099710
.
Mayan integration
Enables users to perform blue chip coins transfer between Solana and EVM chains supported by Mayan. This integration also supports the native USDC bridge CCTP.
Mayan is split into three different keys by provider:
mayan
- Swift
mayanMCTP
- CCTP
mayanWH
- Wormhole
AllBridge integration
Allbridge enables users to perform cost efficient stable coin transfers between Solana (USDC) and other supported Ethereum Virtual Machine (EVM) compatible chains, including ETH, POL, BSC (only USDT), OPT, AVA, ARB, and BAS.
Jupiter integration
Enables users to perform Solana swaps of wide range of tokens.
Only Jupiter verified tokens are supported by LI.FI.
Architectural differences with EVM
Solana works the same way in the LI.FI BE as any other chain so quote requests are the same except for token addresses and chainID.
Onchain tx submission is different from EVM because of fundamental differences between EVM and SVM. More detailed information and tx examples can be found on the solana example page.