Hyperliquid System Events

Overview

The Hyperliquid System Events data type provides exchange-level system events from Hyperliquid L4. Rows include event metadata and the original JSON payload emitted by the source stream.

[!NOTE]

This is an exchange-consolidated stream for HYPERLIQUIDL4. Files are not split by symbol.

File Organization

Hyperliquid System Events data is organized in the coinapi bucket using the structure below.

T-HLSYSTEMEVENTS/
└── D-{YYYYMMDD | YYYYMMDDHH}/
    └── E-HYPERLIQUIDL4/
        └── *.csv.gz

Where:

• T-HLSYSTEMEVENTS: Indicates the data type (Hyperliquid System Events)
• D-{YYYYMMDD | YYYYMMDDHH} defines the time partition:
  • YYYYMMDD in coinapi -> legacy daily partitions published before 2026-06-09
  • YYYYMMDDHH in coinapi -> hourly partitions for data published on or after 2026-06-09
• E-HYPERLIQUIDL4: Hyperliquid L4 exchange identifier

File Format

Files are in CSV format, compressed with gzip. Each row represents one system event.

Data Fields

Example Data

time_exchange;time_coinapi;exchange_id;block_number;event_type;json_payload
2026-06-09T00:17:41.4000000;2026-06-09T00:17:41.7249815;HYPERLIQUIDL4;47261520;validatorSetChange;{"height":47261520,"validators":[{"id":"v1"}]}

Data Collection Process

1. We subscribe to Hyperliquid L4 system-level raw event streams.
2. System event payloads are normalized and serialized into CSV rows.
3. Data is uploaded to the coinapi bucket as hourly partitions for data published on or after 2026-06-09. Legacy daily partitions published before that date remain in coinapi.

Corner Cases and Special Considerations

1. json_payload may include deeply nested JSON objects.
2. Event ordering should rely primarily on block_number, then timestamp fields.
3. System event taxonomies may expand over time with new event_type values.