Vadim Nicolai

Introduction​

TL;DR​

TL;DR​

TL;DR​

TL;DR Hyperliquid runs its own Layer-1 with two execution domains:

• HyperCore — native on-chain central limit order book (CLOB), margin, funding, liquidations.
• HyperEVM — standard EVM runtime (gas metered, paid in HYPE).

Trading on HyperCore is gasless: orders, cancels, TP/SL, TWAP, Scale ladders, etc. are signed actions included in consensus, not EVM transactions.

• You don’t need HYPE to place/cancel orders.
• You pay maker/taker fees and funding, not gas.
• Spam is mitigated with address budgets, rate limits, open-order caps.
• If you need more throughput: buy request weight at $0.0005 per action.

The design enables CEX-style strategies (dense ladders, queue dancing, rebates, hourly hedging) without the friction of gas.

Official GitHub repos:

• Python SDK → https://github.com/hyperliquid-dex/hyperliquid-python-sdk
• Rust SDK → https://github.com/hyperliquid-dex/hyperliquid-rust-sdk
• Node → https://github.com/hyperliquid-dex/node
• Order Book Server (example) → https://github.com/hyperliquid-dex/order_book_server

“The markets are never wrong; opinions often are.”
—Jesse Livermore (quoted by Bruce Kovner in Market Wizards)

TL;DR – PR #2577 introduces a fallible constructor, complete domain-level checks, and four focussed tests for MarketIfTouchedOrder, thereby closing long-standing Issue #2529 on order-validation consistency.