Overview
The Writer Actions stream records actions sent from HyperEVM to HyperCore through CoreWriter, along with system bridge transfers. Each event includes the action payload, a user address, a nonce, and the associated HyperEVM transaction hash. Contracts can initiate orders, cancellations, transfers, staking operations, and other actions in this stream.
Stream Type: WRITER_ACTIONS
API Availability: gRPC Streaming API + JSON-RPC/WebSocket APIs
Activity: Depends on CoreWriter calls and system bridge transfers; blocks can contain an empty events array.
CoreWriter Action Types
Use the exact action.type names below in subscription filters. The numeric action ID belongs to the encoded CoreWriter call on HyperEVM; it is not a field in the writer-action event.
| CoreWriter action ID | Action | Writer stream action.type |
|---|---|---|
| 1 | Limit order | order |
| 2 | Vault transfer | vaultTransfer |
| 3 | Token delegate | tokenDelegate |
| 4 | Staking deposit | cDeposit |
| 5 | Staking withdraw | cWithdraw |
| 6 | Spot send | SystemSpotSendAction |
| 7 | USD class transfer | SystemUsdClassTransferAction |
| 8 | Finalize EVM contract | finalizeEvmContract |
| 9 | Add API wallet | approveAgent |
| 10 | Cancel order by oid | cancel |
| 11 | Cancel order by cloid | cancelByCloid |
| 12 | Approve builder fee | SystemApproveBuilderFeeAction |
| 13 | Send asset | SystemSendAssetAction |
| 14 | Aligned quote supply change (mint or burn) | SystemAlignedQuoteSupplyDeltaAction |
| 15 | Borrow / lend | SystemBoleAction |
| 16 | Set user abstraction | userSetAbstraction |
| 17 | User outcome | userOutcome |
This mapping covers 17 action types observed on mainnet since December 19, 2025. New action types can appear as Hyperliquid adds actions; consumers should handle unknown action.type values. ID 14 is a historical observation, not a guarantee of current availability.
For the binary action encoding and supported call parameters, see Hyperliquid's CoreWriter reference. The encoded call parameters are distinct from the JSON field layout returned by this stream.
Many names, such as order and cancel, also appear as signed user actions in the Blocks dataset. In this stream, they represent actions submitted through CoreWriter.
Data Structure
Each block contains timestamps, a HyperCore block number, and an events array. The example below shows one system bridge transfer from a captured block (other events omitted):
{
"local_time": "2026-11-06T12:20:12.170340794",
"block_time": "2026-11-06T12:20:12.002074848",
"block_number": 1211260626,
"events": [
{
"user": "0x2000000000000000000000000000000000000000",
"nonce": 5623020,
"evm_tx_hash": "0xde5522a0afada28e25061a26e1d8cbfc54609510a86ce97d9afbe717b4be7fad",
"action": {
"type": "SystemSpotSendAction",
"destination": "0x6b9e773128f453f5c2c60935ee2de2cbc5390a24",
"token": 0,
"wei": 49967894300
}
}
]
}
Field Definitions
Event Structure
| Field | Type | Description |
|---|---|---|
| user | string | Address that called CoreWriter, or the system address for a bridge transfer |
| nonce | integer | Nonce associated with the writer action |
| evm_tx_hash | string | HyperEVM transaction hash; use it to retrieve the EVM receipt and correlate CoreWriter logs |
| action | object | Action details (see Action Structure below) |
Action Structure
The fields inside action depend on action.type. Do not expect transfer fields on orders, cancellations, staking actions, or other variants. The two transfer types (SystemSpotSendAction and SystemSendAssetAction) share the following fields:
| Field | Type | Description |
|---|---|---|
| type | string | Action type name from the CoreWriter Action Types table above |
| destination | string | Destination address for the token transfer |
| token | integer | Token ID (numeric identifier for the specific token) |
| wei | integer | Transfer amount in the token's smallest unit (weiDecimals from spotMeta) |
SystemSendAssetAction Additional Fields
SystemSendAssetAction events include three additional nullable fields not present on SystemSpotSendAction:
| Field | Type | Description |
|---|---|---|
| destinationDexOrSpot | integer|null | Destination DEX index; null when the CoreWriter call used uint32::MAX (spot). |
| fromSubAccount | string|null | Source sub-account address (null when not applicable) |
| sourceDexOrSpot | integer|null | Source DEX index; null when the CoreWriter call used uint32::MAX (spot). |
Ledger delta types such as internalTransfer, vaultCreate, vaultLeaderCommission, cStakingTransfer, accountActivationGas, and activateDexAbstraction belong to the Events dataset. They are not part of the observed writer-action type mapping above.
API Usage
Filter by the string type name, not the numeric CoreWriter action ID. The gRPC and WebSocket examples select orders, cancellations, and spot sends; the HTTP example retrieves unfiltered blocks. Add a user filter to match an address, or omit filters from a subscription to receive all writer actions. Filters also search nested fields, so check the event's top-level user when you need to identify the CoreWriter caller. See Filtering for filter semantics.
gRPC Streaming
// Subscribe to writer actions
const request = {
subscribe: {
stream_type: 'WRITER_ACTIONS',
filters: {
type: { values: ['order', 'cancel', 'SystemSpotSendAction'] }
}
}
};
JSON-RPC
# Get latest writer action blocks
curl -X POST https://your-endpoint.hype-mainnet.quiknode.pro/your-token/hypercore \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "hl_getLatestBlocks",
"params": {
"stream": "writer_actions",
"count": 10
},
"id": 1
}'
WebSocket
// Subscribe to writer actions with filters
ws.send(JSON.stringify({
jsonrpc: '2.0',
method: 'hl_subscribe',
params: {
streamType: 'writer_actions',
filters: {
type: ['order', 'cancel', 'SystemSpotSendAction']
}
},
id: 1
}));
Example Writer Action Records
These records were checked against writer-actions data. The order example shows how a non-transfer payload differs from the transfer variants.
order
{
"user": "0xa4826a978f5ba73a062d7da7771088970d21de3b",
"nonce": 5623013,
"evm_tx_hash": "0x93ab35f8a6384ae8dedab06fee2f22442356df0a8b81427398aa54f7d012e676",
"action": {
"type": "order",
"orders": [
{
"a": 110015,
"b": true,
"p": "715.13",
"s": "0.008",
"r": false,
"t": {
"limit": {
"tif": "Ioc"
}
}
}
],
"grouping": "na"
}
}
SystemSendAssetAction
{
"user": "0x6af3bccd77314d35d47317e1d1bc17df248c991f",
"nonce": 1184125,
"evm_tx_hash": "0x299c90b15e410587841ab057f84faafa4d076a26db53c34a35231fe7dc4361bf",
"action": {
"type": "SystemSendAssetAction",
"destination": "0x6043daf4fbd6bd60601d277312a0664551302e70",
"fromSubAccount": null,
"sourceDexOrSpot": 0,
"destinationDexOrSpot": 0,
"token": 0,
"wei": 1882600
}
}
SystemSpotSendAction - Token ID 299
{
"user": "0x200000000000000000000000000000000000012b",
"nonce": 1184153,
"evm_tx_hash": "0x172a41083c44c9568494fbec81d11292e192938674b861e410e4a7e965235c67",
"action": {
"type": "SystemSpotSendAction",
"destination": "0x46bbfef00cde256f834340c50286dd7b495ca418",
"token": 299,
"wei": 56697105031
}
}
SystemSpotSendAction - Token ID 268
{
"user": "0x200000000000000000000000000000000000010c",
"nonce": 1184131,
"evm_tx_hash": "0x350349ac511ce5c8b02964999538653a508b1ad770bc10e1921b563f0f67177c",
"action": {
"type": "SystemSpotSendAction",
"destination": "0x796bc4eb6cc934d3432d5d08c74f2d957f60e7bc",
"token": 268,
"wei": 427229100
}
}
SystemSpotSendAction - Token ID 0
{
"user": "0x2000000000000000000000000000000000000000",
"nonce": 1184132,
"evm_tx_hash": "0xba6756dc9cbd35cfe2deb90686271df9981c6442c7f85226ce0738d5494a4649",
"action": {
"type": "SystemSpotSendAction",
"destination": "0x6b9e773128f453f5c2c60935ee2de2cbc5390a24",
"token": 0,
"wei": 1738000000
}
}
Important Notes
- Contract-initiated actions: For CoreWriter calls,
useridentifies the caller. These actions can originate from user interactions with contracts. - System bridge transfers: Many
SystemSpotSendActionevents originate from token system addresses beginning with0x2000…or the HYPE system address0x2222222222222222222222222222222222222222. These bridge events are not CoreWriter calls. - Transaction correlation: Multiple CoreWriter actions can share an
evm_tx_hash. Correlate all events for that hash with the CoreWriter logs in its HyperEVM receipt rather than assuming one action per transaction. - Execution status: A writer-action event shows that HyperCore recorded the action. Its presence alone does not prove successful execution on HyperCore.
- Amounts: The
weifields in the two transfer types are integer amounts in the token's smallest unit. Other action variants have their own field layouts and units.
Token ID Reference
For transfer payloads, token is a numeric token index. Use the spotMeta Info API to resolve it against tokens[].index, read the token's name, and obtain weiDecimals for amount conversion. Do not assume a token's identity from its numeric ID or use HYPE's decimals for every asset.