Trading on HyperCore from Elysium

Contracts on Elysium can drive orders on HyperCore's books in ≈100–200 ms from intent to resting order. Trading happens on the user's own HyperCore account, so custody never moves to Elysium or Kinetiq.

The keeper lane and the ElysiumCoreWriter predeploy ship in an ArbOS network upgrade about four weeks after mainnet.

How it works

1. Bind once. The dapp's contract binds its HyperCore trading account on the ElysiumCoreWriter predeploy and designates a registrar: Kinetiq's managed signing service, or your own agent.
2. Authorize a trade-only agent. The HyperCore account approves an API agent. HyperCore itself enforces that agents can place and cancel orders but can never withdraw or transfer funds.
3. Emit intents. The contract emits order intents on Elysium through the predeploy.
4. Execute on HyperCore. The keeper signs each intent as the agent and submits it to HyperCore, typically within about one HyperCore block.

Fills belong to the user's account, at the user's own fee tier.

Custody and exit

• The agent is trade-only by HyperCore's own enforcement. It cannot move funds.
• The user can revoke the agent at any time with one native HyperCore action, or trade directly with the account's master key. Neither involves Elysium.
• The service is substitutable. The intent event stream is the open interface, so you can run your own key and listener instead of Kinetiq's signer, and switching providers is a rebind.

The HyperCore account must exist (be funded) before its first action.

Result callbacks

HyperCore actions are asynchronous. A dapp can opt in to an on-chain callback by prefunding a small HYPE gas escrow on the predeploy. Each action's HyperCore outcome is then delivered back to the originating contract, with the callback gas refunded from the escrow, so escrowed intents never fail silently. Callbacks should be idempotent and deduplicate by intent nonce, since there is no atomicity between Elysium and HyperCore.

Compared with HyperEVM's CoreWriter

HyperEVM's CoreWriter interface is asynchronous and gated to HyperEVM's 1-second block cadence, gives no execution guarantee, and reports no failures. The keeper lane runs at Elysium's block cadence, acts on the user's own account rather than the calling contract's, and can report outcomes back on-chain.