Skip to main content
Hypermid supports 90+ blockchains across EVM and non-EVM networks. Every chain has a slug (human-readable string) and a numeric ID. Both are accepted in all API params, widget config, and SDK methods. You can also fetch the full list programmatically via GET /v1/chains.

EVM Chains

EVM chains support wallet mode — the execute endpoint returns a transactionRequest that you sign and broadcast directly from your app. No manual steps needed.

EVM Example (Wallet Mode)

All EVM swaps return a transactionRequest — sign it and broadcast:
PulseChain swaps use the same wallet mode but may require an extra confirmation step for inbound multi-step routes. See the SuperSwap guide for details.

Non-EVM Chains

Non-EVM chains support two deposit modes depending on the chain:
  • Wallet — Returns a transactionRequest you can sign programmatically (same as EVM). Works for Solana, Bitcoin, TON, and Tron.
  • Manual — Returns a depositAddress (and optional memo). The user sends tokens from their native wallet app.
Wallet chains can also use manual mode. Pass depositMode: "manual" in your execute request to force a deposit address for any chain. Useful if your app doesn’t have a native wallet integration for that chain.

Wallet Mode Example (Solana)

Wallet-mode non-EVM chains work the same as EVM — you get a transactionRequest:

Manual Deposit Example (XRP)

Manual-mode chains return a depositAddress and optional memo. Show these to the user so they can send from their native wallet:
Memo is required for XRP and Stellar deposits. If the user omits the memo, the funds may be lost. Always display the memo prominently in your UI.

Forcing Manual Mode

Any wallet-mode chain can be switched to manual deposit by passing depositMode: "manual":

Using Chain Identifiers

Both slugs and numeric IDs work in all API endpoints:
Use slugs for non-EVM chains"solana" is much easier to read than 1151111081099710.