Skip to main content
Socket 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 Socket, including transaction options and current limitations.

Quick Start

Key differences

Follow the “Auto routing” guides when going from any EVM to HyperCore. The main differences when integrating HyperCore compared to standard EVM chains: Transaction Flow from HyperCore to EVM
  • User sends funds to a Deposit contract with the quote ID
  • Socket indexes the transaction and delivers the funds on the destination chain
API Behavior
  • Both userAddress and receiverAddress required 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
  • Quote responses already account for HyperCore’s 1 USDC activation fee for new account activations and withdrawals
  • Only USDC (Perps) is supported when bridging out of Hypercore

inputAmount format for HyperCore

The inputAmount parameter must be provided as an integer string in 6-decimal base units (micro-units): Conversion formula: inputAmount = humanAmount × 10^6 (rounded to integer)

Integration Steps

HyperCore to EVM

  1. Select Chains: Choose source and destination chains.
  2. Fetch Routes: Retrieve the deposit route using the /quote endpoint. The response contains depositRoute.signTypedData and depositRoute.quoteId.
  3. Sign and Submit: Sign the signTypedData with primaryType: "HyperCoreTransaction:SendAsset", then submit the signed data to HyperLiquid’s API endpoint (https://api.hyperliquid.xyz/exchange).
  4. Track Transaction Status: Poll the /status endpoint using the quoteId until the bridging process is complete.
For HyperCore quotes, ensure both userAddress and receiverAddress are defined.HyperCore to EVM is under depositRoute (not autoRoute).

Examples

Queries

Scripts