Solana

Solana is fully supported for onramps, offramps, and swaps. Of the supported networks it has the lightest per-transaction setup — there are no trustlines, and the network fees are negligible. The end-to-end flows live in the Onramps, Offramps, and Swaps guides.

​

Supported operations

​

Asset identifiers

Solana assets use the Base58 mint address — e.g. AvvetPGuuB5FD5m86fpw3LtDKyQoUFT1mG9WarNQLW4q.

​

Stablebond addresses

Live mint accounts for every stablebond on Solana, each linked to Solscan:

​

Wallet & gas

There’s no trustline or account-reserve step on Solana, and associated token accounts are created as part of the transaction Etherfuse builds. Network fees are a tiny fraction of a cent, so there’s no per-wallet funding requirement to plan for.

​

Swaps: read the webhook payload, not the status sequence

Swap progress is delivered over the swap_updated webhook. Which intermediate statuses fire varies by chain — for example, Solana may not emit a distinct funds_received update the way some other chains do. Drive your logic off the fields in the payload, not off assuming a specific status will arrive:

• sendTransaction is present while you still need to send funds; once the funds are received it’s dropped from the payload.
• On completion you get sendTransactionHash (your send) and receiveTransactionHash (Etherfuse’s delivery to you).

See Swaps and Webhooks for the full payload semantics.

​

Related