Skip to main content
Published July 28, 2026 The GoldRush Hyperliquid WebSocket API now exposes a GoldRush-exclusive builderLiquidations channel at wss://hypercore.goldrushdata.com/ws. Subscribe with your builder address to receive, in real time, every liquidation fill whose closing order was routed through your builder code - the builder-attributed slice of the global liquidationFills feed, with no equivalent on the public Hyperliquid WebSocket.

​
Why it’s different from liquidationFills

  • Builder-scoped - builder is required, and only liquidations attributable to your builder code are streamed. It is effectively the intersection of liquidationFills and builderFills.
  • Attribution on every entry - each fill carries both the liquidation object (liquidatedUser, markPx, method) and the builder, builderFee, and deployerFee attribution fields.
  • aggregateByTime defaults to false - partial fills of the same liquidation in a block are streamed separately unless you opt in to merging by (user, time, order_id).

​
What to know

  • TWAP-preceded liquidations are omitted - TWAP fills do not carry builder codes, so if a user’s last fill before liquidation was a TWAP slice, the liquidation cannot be attributed to a builder and is not emitted. Use the global liquidationFills stream when you need every liquidation regardless of attribution.
  • Optional dex filter - pass "xyz" or "main" to narrow to first-DEX fills.