How HyperCore and HyperEVM Communicate
How HyperEVM smart contracts read HyperCore state through precompiles, and why that matters for DeFi composability.
032CoreWriter Explained
How HyperEVM contracts can send supported actions to HyperCore and what this enables for onchain applications.
034HYPE Staking and Validators Explained
How HYPE delegation connects token holders to HyperBFT validators, rewards, lockups, and network security.
038Building With the Hyperliquid API
A practical map of the Info API, Exchange actions, signing, and the minimum architecture for a Hyperliquid application.
039WebSockets and Real-Time Hyperliquid Data
How to stream books, trades, candles, fills, and account updates without polling the API for every change.
080Hyperliquid L1 Read Precompiles: Complete Guide
Hyperliquid L1 read precompiles let HyperEVM contracts query selected HyperCore state directly at protocol-defined addresses, avoiding a separate offchain oracle for supported data.
081CoreWriter Actions: Complete Reference
CoreWriter is Hyperliquid's system contract for sending supported HyperEVM-originated actions into HyperCore, using versioned action IDs and ABI-encoded payloads.
082Placing HyperCore Orders From HyperEVM Smart Contracts
HyperEVM contracts can submit supported HyperCore order actions through CoreWriter, but the path is deliberately slower than the native order route and should be used for composable application logic rather than latency-sensitive trading.
083Vault Transfers Through CoreWriter
CoreWriter can initiate supported vault transfers from HyperEVM, allowing contracts to move value into or out of HyperCore vault relationships under protocol-defined rules.
084Staking Through CoreWriter
CoreWriter exposes supported staking actions so HyperEVM contracts can coordinate native HYPE staking operations with smart-contract logic.
085Borrow and Lend Actions Through CoreWriter
CoreWriter can submit Portfolio Margin supply and withdraw operations from HyperEVM contracts, making native lending state programmable from the EVM while preserving HyperCore's own risk engine.
086HyperCore to HyperEVM Asset Transfers
HyperCore and HyperEVM share one L1 but maintain different asset accounting, so supported transfers use protocol-defined system paths rather than an external crosschain bridge.
087How Hyperliquid API Signing Works
Hyperliquid API actions are cryptographically signed, but different action families use different signing schemes and serialization details must match the protocol exactly.
088Hyperliquid Nonces and Replay Protection
Hyperliquid uses nonces to make signed actions single-use and time-bounded, preventing a valid signed request from being replayed indefinitely.
089Designing API Wallets for Hyperliquid Trading Systems
API wallets isolate automated signing from the master account, letting a trading system operate without storing the account's highest-authority private key.
090Hyperliquid API Rate Limits Explained
Hyperliquid applies both IP-based request weights and address-based action limits, so production clients need batching, caching, WebSockets, and deliberate retry logic rather than brute-force polling.
091REST vs WebSocket on Hyperliquid
Use REST for snapshots, metadata, and action submission where appropriate; use WebSockets for continuously changing market and account state that would be wasteful or slow to poll.
092Hyperliquid Info Endpoint Guide
The Info endpoint is Hyperliquid's read API for market, account, staking, portfolio, and historical state; correct integrations query the economic account, use the right asset identifiers, and respect endpoint-specific weights.
093Hyperliquid Exchange Endpoint Guide
The Exchange endpoint submits signed HyperCore actions such as orders, cancels, transfers, staking, vault operations, API-wallet approvals, and account configuration.
094How to Build a Production-Grade Hyperliquid Trading Bot
A production Hyperliquid bot is a state-reconciliation and risk system first and an order-generation strategy second.