Skip to content

1.13.0: mempool channel for pending Hyperliquid transactions - #22

Merged
0xFantomMenace merged 2 commits into
masterfrom
feat/mempool-channel
Oct 8, 2026
Merged

0xFantomMenace merged 2 commits into
masterfrom
feat/mempool-channel

Conversation

@0xFantomMenace

Copy link
Copy Markdown
Member

Adds the mempool WebSocket channel: signed Hyperliquid transactions as our Hyperliquid node receives them, before they are included in a block, for every Hyperliquid product.

  • STREAM_WS_URL, subscribe_mempool(symbol=None), unsubscribe_mempool and on_mempool, with typed MempoolItem and WsMempoolData.
  • WsChannelSpec and Capability gain optional ws_endpoint and plans, set only on mempool.
  • Live only: replay() refuses it. Included with the Pro, Scale and Enterprise plans; other plans receive forbidden.

…(1.13.0)

- subscribe_mempool(symbol=None), unsubscribe_mempool() and on_mempool():
  signed transactions before they are in a block, unfiltered or by symbol.
- MempoolItem, MempoolSignature and WsMempoolData typed messages.
- STREAM_WS_URL, the only endpoint that serves the channel; ws_endpoint and
  plans on WsChannelSpec and Capability.
- Version 1.13.0.
- A channel or capability row without ws_endpoint is served at the default
  endpoint, wss://api.0xarchive.io/ws; without plans, on every plan.
- The unfiltered stream carries the pending transactions our node receives,
  and pending transactions are never stored.
@0xFantomMenace
0xFantomMenace merged commit c14d5a5 into master Oct 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant