Skip to content

Hyperliquid on Edith

Edith is the backend for onboarding new users to HyperEVM — and for everything they do once they're on. Both layers are first-class: HyperEVM (the EVM inside Hyperliquid) and HyperCore (the gasless order-book L1). One API relays your transactions, forwards and signs your Core actions, gives your users gasless smart accounts that compose EVM and Core in a single signature, quotes Core-spot swaps, and routes deposits into Core-native yield — all behind the same API keys, accounting, and status surface as every other chain.

Edith also runs on any EVM chain and Solana; this page is the map for the Hyperliquid surface specifically. New here? Skim the networks and the capability map, then jump into the feature pages below.

Build on HyperEVM

HyperEVM (chain 998 testnet / 999 mainnet) is a standard EVM, so Photon relays to it like any other chain — gas paid in HYPE, billed to your prepaid USD balance.

  • Relay ordinary transactions — see Supported networks for the HyperEVM caveats (small-block gas cap, no EIP-7702).
  • Gasless smart accounts — give a user an ERC-4337 account whose sponsored operations run gas-free and can drive HyperCore through CoreWriter. See Gasless smart accounts.

Act on HyperCore

HyperCore (chain 10200000 mainnet / 10200001 testnet) is not an EVM: actions are EIP-712-signed JSON, there is no gas, and acceptance is synchronous. Edith forwards them with the same retries, webhooks, and WebSocket as everything else.

  • Relay signed Core actions (orders, transfers, vault deposits, staking) — HyperCore actions.
  • Agent wallets — approve Edith's agent once, then place Core orders with no per-order signature — HyperCore agent wallets.
  • Orders + builder codes — agent-signed orders carry the operator's builder code — HyperCore orders.
  • Core-spot swaps — quote against the Core order book and execute gaslessly — HyperCore spot swap.

Earn Core-native yield

Meadow routes a deposit into the winning Core venue with one signature.

  • Core vault + staking venues — HLP-style vault deposits and HYPE staking delegation, gasless — Supported venues.
  • CoreWriter venue (flagship) — the same HLP yield, supplied through a gasless smart-account operation on HyperEVM via CoreWriter — one signature, composable with EVM steps — CoreWriter venue.

The flagship: compose EVM + Core in one signature

The primitive that ties the two layers together is a gasless ERC-4337 smart account on HyperEVM whose operations act on HyperCore via CoreWriter (0x3333333333333333333333333333333333333333). A single signed operation can run an EVM call and a Core action atomically — for example approve a token on the EVM side and supply into a Core vault — sponsored by an Edith paymaster and metered against the owner's prepaid balance. This is what the Meadow CoreWriter venue packages; build the calls yourself with Gasless smart accounts for anything else.

Try it: relay a signed Core action

A Core action is a complete signed exchange request {action, nonce, signature}, base64-encoded in callData, submitted to the HyperCore chain id — no gas, no to:

REQUEST='{"action":{"type":"spotSend","hyperliquidChain":"Testnet","signatureChainId":"0x66eee","destination":"0x…","token":"USDC","amount":"5","time":1753900000000},"nonce":1753900000000,"signature":{"r":"0x…","s":"0x…","v":27}}'

curl -X POST https://photon.example.com/api/submit-tx \
  -H "api-key: $EDITH_API_KEY" -H "Content-Type: application/json" \
  -d '{
    "chainId": 10200001,
    "to": "",
    "callData": "'"$(printf '%s' "$REQUEST" | base64)"'",
    "label": "core-spot-send"
  }'

From there, agent wallets remove the per-action signature, and smart accounts add gasless EVM↔Core composition.

Reference

  • Hyperliquid networks — the four chains, defaults, and caveats.
  • Capability map — every Hyperliquid capability, by service.
  • Hyperliquid runbook — operator setup: HYPE funding, big blocks, agent/builder config, the ERC-4337 deploy, and Meadow venue wiring.