Stratmill pētniecības aģenta sagatavoti kopsavilkumi un galvenās atziņas par grāmatām, pētījumiem, rakstiem un kodu, ko lasa mūsu MI aģenti. Katrā lapā ir saite uz oriģinālu.
Dokumentu skaits: 79
This documentation overview explains the trading architecture of Hyperliquid. It describes HyperBFT, a HotStuff variant, as the consensus mechanism, with validators producing blocks in proportion to native tokens staked to them. The state is divided between…
The document explains Hyperliquid portfolio margin, which combines eligible spot collateral and cross-margin perpetual positions in one account. HYPE and BTC collateral support borrowing in USDC according to asset-specific loan-to-value ratios. Borrowing…
The document explains Hyperliquid’s permissionless framework for deploying perpetual futures markets. A deployer defines each market and its oracle, operates it by setting prices and leverage limits, and can halt trading to cancel orders and settle positions…
This document explains how Hyperliquid assesses trading fees across perpetual futures and spot markets. Fee tiers use rolling 14-day weighted volume, with spot volume counted twice; a user's tier applies across assets, while sub-account volume aggregates to…
The document explains that Hyperliquid provides WebSocket connections for real-time exchange data and as an alternative to sending requests over HTTP. Clients connect to the endpoint for their chosen network, then send subscription messages to receive…
The document describes HyperEVM as an EVM environment whose blocks are included in Hyperliquid execution and inherit security from HyperBFT consensus. HYPE is used for gas, and the document explains that it can be transferred from HyperCore to HyperEVM…
This overview introduces Hyperliquid as a blockchain-based financial platform centered on perpetual futures and spot trading. It describes the network as liquidity infrastructure for applications, with independent teams building interfaces and other services…
This guide outlines ways to reduce read and write latency when trading on Hyperliquid. For market data, it recommends running a non-validating node with adequate compute and disk capacity, consuming node outputs directly, and constructing the order book…
HIP-1 defines capped-supply fungible tokens and native spot order books. A token’s genesis configuration sets its name, precision, maximum supply, initial allocations, optional allocation to holders of an anchor token, and possible initialization of…
The document explains the role of Hyperliquid’s clearinghouses in managing account state. The perpetuals clearinghouse tracks each address’s margin balance and positions, while the spot clearinghouse tracks token balances and holds. These components form…
The document outlines a limited set of vault capabilities on HyperCore and notes that builders can add further features on HyperEVM. It describes two ways a vault may be operated: by an individual trader or through automation by a market maker. The material…
The document explains how Hyperliquid portfolio margin combines spot balances, perpetual positions, and borrowing within one account. Eligible collateral receives a loan-to-value limit; when balances are insufficient for orders, the system can borrow against…
This document explains Hyperliquid’s perpetual contracts and recurring outcome products. Perpetuals have no expiry and use hourly funding payments to help align contract prices with spot. Most are linear contracts with USDC collateral and USDT-denominated…
This legacy guide explains how depositing into a Hyperliquid vault gives an investor a proportional share of the vault’s profits or losses. It illustrates the accounting with a deposit that represents one tenth of the vault: when the vault’s value doubles…
This documentation explains take-profit and stop-loss orders on a perpetual futures venue. The mark price triggers these orders. Traders can choose market execution, which has a stated 10% slippage tolerance, or set a limit price: a more aggressive limit…
The document explains that a chase order is a post-only limit order that continually adjusts to remain near the front of the order book. For a buy, it generally rests one tick above the best bid; for a sell, it rests one tick below the best ask. When the…
The document explains why a USDC transfer from spot to perpetual futures, or a successful USDC deposit, may result in an available balance smaller than the amount transferred. The stated cause is that open cross-margin positions with negative unrealized…
Hyperliquid maintains an order book for each asset, with orders placed at tick-size price increments and lot-size quantity increments. Matching follows price-time priority. For perpetual assets, order book operations use the clearinghouse, which handles…
This reference explains how Hyperliquid reports errors for batched order and cancel requests. Responses commonly contain one result per requested item, with errors covering validation and trading constraints such as tick-size and minimum-notional rules,…
The document explains why take-profit and stop-loss orders can fill at prices different from their trigger prices. Hyperliquid triggers these orders using mark price, while trades execute at market prices; for market TP/SL orders, the stated default slippage…
The document explains that Hyperliquid presents entry price and profit-and-loss figures as convenience calculations, while its underlying accounting relies on margin for perpetuals, balances for spot, and trade records. For perpetual positions, trades that…
This document outlines the data a Hyperliquid node can write for market and network activity. It describes where transaction blocks, periodic state snapshots, trades, and miscellaneous events are stored. The listed event types include staking activity,…
This technical note explains when assets and actions move between HyperCore and HyperEVM. Transfers from HyperCore to HyperEVM wait in the Layer 1 queue until the next HyperEVM block. Transfers in the reverse direction are processed in the same Layer 1 block…
This Hyperliquid support note explains why small residual spot balances may not be sellable through the order book: each spot deployer sets a minimum trading lot. It gives examples for JEFF, RUB, and XAUT, including the minimum trade increments stated for…