reserveRequestWeight payload - Request Weight Reservations
Decode Hyperliquid `reserveRequestWeight` payloads for request weight reservations, returned through Dwellir's read-only L1 gRPC API.
Read-only action reference
Dwellir's Hyperliquid gRPC API returns this decoded action payload through
StreamBlocks and
GetBlock. It does not submit or execute this action.
Submit supported user write actions through Hyperliquid's native
POST /exchange
endpoint.
The decoded reserveRequestWeight payload records a request-capacity reservation in Hyperliquid's control plane.
How to Read It
Unlike trading or transfer actions, the payload here is intentionally compact: the action body only carries the requested weight. Signature, nonce, and execution status come from the surrounding signed-action envelope and the paired response entry.
Sample Data
{
"signature": {
"r": "0x3eab58f491988095343c3391ac498fcc8803a3692c0c3047c8f56088ab8589ea",
"s": "0xd59535932e8490a63d90d70071f033bd0b59fb4025aa5a57a65b8af57ea71ff",
"v": 27
},
"action": {
"type": "reserveRequestWeight",
"weight": 5000
},
"nonce": 1767951014393
}Field Reference
Envelope Fields
| Field | Type | Description |
|---|---|---|
signature | object | ECDSA signature for the signed action |
nonce | number | Replay-protection nonce used for ordering and uniqueness |
Action Fields
| Field | Type | Description |
|---|---|---|
type | string | Always "reserveRequestWeight" |
weight | number | Request weight to reserve |
Processing Guidance
- Treat this as a system or workflow signal rather than a user-visible balance change.
- Preserve the nonce and bundle ordering when indexing it. These actions are often most useful when analyzed in sequence with the actions that follow.
- Confirm execution with the paired response status before assuming the reservation succeeded.
- If your analytics focus on economic activity, classify this separately from trade, transfer, and collateral actions so it does not distort volume metrics.
Common Use Cases
Automation Observability
Track these actions to understand when bots, agents, or infrastructure workflows reserve capacity before a burst of subsequent activity.
Control-Plane Filtering
Separate request-weight reservations from user-facing actions when building dashboards or compliance summaries.
Related Action Payloads
- StreamBlocks for block and response pairing