VaultGREXIE VAULT / DOCUMENTATION
Hyperliquid
Use an Ethereum identity's public address to inspect its account without an approval:
vault --identity pixi-timoshisa hyperliquid balance
vault --identity pixi-timoshisa hyperliquid positions
vault --identity pixi-timoshisa hyperliquid orders
# A public address works without a paired Vault catalogue:
vault hyperliquid positions --address 0xPUBLIC_ADDRESS --network mainnetReads default to mainnet and include all perpetual DEXes. Use --dex native or --dex NAME to select one. Orders include the standard venue's spot orders. Unified-account balances must not be summed as independent spot and perpetual cash: the output includes the account mode and raw venue figures so callers can interpret them correctly.
Sign an exact action envelope from stdin:
vault --identity trading --reason 'Sign the exact order the user requested' \
hyperliquid sign --network mainnet < action.json
vault hyperliquid review --network mainnet --address 0xPUBLIC_ADDRESS < action.jsonThe envelope contains action, nonce, and supported optional vaultAddress / expiresAfter fields. Vault inserts the protocol's fixed signing fields for user actions. sign requires an explicit network, one fresh Vault approval and the pinned signing device. It returns the signed exchange envelope to stdout and never submits it. The requesting process receives only the signature, not the key. review and public reads require no private-key approval.
L1 actions include orders, cancellation, modification, leverage and isolated-margin changes, scheduled cancellation, TWAP orders/cancellation and no-op. User actions include USD/spot transfers, withdrawals, class transfers, sendAsset, approveAgent, approveBuilderFee, token delegation and DEX abstraction settings. Unknown action types and ambiguous or overlarge JSON are rejected. All signed fields, numeric asset IDs, network, nonce, expiry and optional vault address are displayed. A builder fee or API-wallet delegation can grant authority beyond this one signature; its review makes that effect explicit.
The implementation is checked against 164 fixtures generated by the official Python SDK, with the exact upstream revision and generation instructions in internal/hyperliquid/testdata/README.md.
For ordinary browser login, install the Chrome wallet, choose Grexie Vault on Hyperliquid and connect the identity. Terms signatures use the same exact EIP-712 approval flow. Connecting or accepting terms does not authorize enabling a trading API wallet, placing orders, transferring assets or approving a builder fee.