Bungee also supports swapping assets from any EVM chain to HyperCore and from HyperCore to any EVM chain. This guide walks you through swapping assets between EVM chains and HyperCore using Bungee. It covers transaction options, and current limitations.Documentation Index
Fetch the complete documentation index at: https://docs.bungee.exchange/llms.txt
Use this file to discover all available pages before exploring further.
Quick Start
Key differences
Follow the “Auto routing” guides when going from any EVM to HyperCore. The main difference when integrating HyperCore Bungee API compared to standard EVM chains: Transaction Flow from HyperCore to EVM- User sends funds to a Deposit contract with the quote ID
- Bungee indexes the transaction and delivers the funds on the destination chain
- Both
userAddressandreceiverAddressrequired for quotes - The only assets supported from/to HyperCore are USDC (Spot) and USDC (Perps).
- There is no Fee collection currently from HyperCore to EVM
- The quote responses already take into account that HyperCore charges a 1 USDC activation fee for new account activation and withdrawals
- Only USDC (Perps) is supported when bridging out of Hypercore
Integration Steps
HyperCore to EVM
The “Auto routing” guide from Bungee Docs outlines how to integrate the deposit flow as it is a quite similar process.- Select Chains: Users choose the source and destination chains, which determine the tokens available for bridging.
- Fetch Routes: After selecting the tokens, retrieve the deposit route if available using the
/quoteendpoint. The response will containdepositRoute.signTypedDataanddepositRoute.quoteId. - Sign and Submit: Sign the
signTypedDatafrom the quote response usingprimaryType: "HyperCoreTransaction:SendAsset", then submit the signed data to HyperLiquid’s API endpoint (https://api.hyperliquid.xyz/exchange). - Track Transaction Status: Monitor the transaction’s progress by polling the
/statusendpoint using thequoteIdfrom the quote response until the bridging process is complete.
For HyperCore quotes, please ensure both
Conversion formula:
userAddress and receiverAddress are defined.inputAmount Format for HyperCore:The inputAmount parameter must be provided as an integer string in 6-decimal base units (micro-units). This is the same format used for USDC on most EVM chains.| Human-readable | inputAmount value |
|---|---|
| 9.99 USDC | "9990000" |
| 2.00 USDC | "2000000" |
| 10.23 USDC | "10230000" |
inputAmount = humanAmount × 10^6 (rounded to integer)For example, to send 9.99 USDC, use inputAmount: "9990000" (9.99 × 1,000,000 = 9,990,000).The HyperCore signature generation uses this micro-unit value directly. Do not pass decimal strings like "9.99".Also, note that from HyperCore to EVM is a separate route from autoRoute since it is under depositRoute.Examples
Queries
Quote from Optimism USDC to HyperCore USDC (Spot)
Quote from Optimism USDC to HyperCore USDC (Spot)
Quote from HyperCore USDC (Perps) to Optimism USDC
Quote from HyperCore USDC (Perps) to Optimism USDC
For HyperCore quotes,
inputAmount must be provided as an integer string in 6-decimal base units (micro-units). For example, to send 10.23 USDC, use inputAmount: "10230000" (10.23 × 10^6).Scripts
Quote and swap from Optimism USDC to HyperCore USDC (Spot)
Quote and swap from Optimism USDC to HyperCore USDC (Spot)
Quote and swap from HyperCore USDC (Perps) to Optimism USDC
Quote and swap from HyperCore USDC (Perps) to Optimism USDC