Hyperliquid vs dYdX

Hyperliquid docs describe HyperCore as including fully on-chain perpetual futures and spot order books.عرض المصدر ↗

HIP-3 documentation says the protocol supports permissionless builder-deployed perpetuals.عرض المصدر ↗

Hyperliquid fees documentation says fees are based on rolling 14 day volume, assessed at the end of each UTC day, with separate schedules for perps and spot; sub-account volume counts toward the master account fee tier while vault volume is treated separately.عرض المصدر ↗

A Hyperliquid fees search should split cost evidence into four official lanes: the fee schedule for maker/taker tiers, funding docs for hourly peer-to-peer funding, contract specifications for market mechanics, and liquidation docs for maintenance-margin failure paths.عرض المصدر ↗

Hyperliquid funding docs say funding is peer-to-peer, collected by neither side of the venue, paid every hour, and based on the difference between the perpetual contract price and the spot oracle price.عرض المصدر ↗

A Hyperliquid fees query should be read as a bundle: maker/taker schedule, hourly funding, margin mode and liquidation threshold can all change the position cost before PnL is known.عرض المصدر ↗

Before placing a Hyperliquid perp order, compare the quoted maker/taker tier, expected hourly funding direction, margin mode, maintenance margin, liquidation path, bridge or USDC movement cost, and whether the order belongs to main account, sub-account or API wallet flow.عرض المصدر ↗

Hyperliquid combines perp and spot volume into one fee tier, with spot volume counting double in the published 14-day weighted-volume formula; the applicable maker or taker rate still depends on the current official tier and asset context.عرض المصدر ↗

HIP-3 perpetuals share the user's fee tier, but growth mode and deployer-configured fee shares can change all-in fees, rebates and volume contribution. Users should verify the specific HIP-3 market instead of applying one protocol-wide perp rate.عرض المصدر ↗

Hyperliquid USDC docs describe native Hyperliquid L1 USDC and point users to Circle's Arbitrum-to-HyperCore CCTP transfer documentation.عرض المصدر ↗

Hyperliquid exchange-endpoint docs separate signed trading actions from user-signed Core USDC transfers, so wallet movement cost and transfer signing should be checked separately from maker/taker fees and funding.عرض المصدر ↗

Hyperliquid account-abstraction docs separate unified, portfolio margin and manual/standard modes, which determine how spot and perps balances interact and whether assets are used as perps collateral.عرض المصدر ↗

Hyperliquid testnet faucet docs say users need a mainnet deposit with the same address before receiving mock USDC for testnet use.عرض المصدر ↗

A Hyperliquid funded-account search should be split into wallet funding, USDC collateral, account modes, sub-accounts and API-wallet delegation; the official docs do not turn that phrase into a guaranteed prop-account allocation.عرض المصدر ↗

For a Hyperliquid funded-account query, use USDC docs for funding the wallet, account-abstraction docs for collateral mode, sub-account docs for account separation, API-wallet docs for delegated signing, and vault docs for vault participation; none of those sources proves a third-party prop account allocation.عرض المصدر ↗

When the query is 'Hyperliquid funded account', NexuAlpha should not collapse wallet collateral, sub-accounts, vault deposits and outside prop-firm language into one CTA; each meaning requires a different official source check.عرض المصدر ↗

Hyperliquid sub-account docs say up to 10 sub-accounts can be created only after reaching $100,000 in volume, and referral discounts do not apply to sub-accounts.عرض المصدر ↗

Hyperliquid API wallet docs say API wallets sign on behalf of a master account or sub-account, but account data queries must use the actual account address, not the agent wallet.عرض المصدر ↗

Hyperliquid liquidation docs say liquidation begins when account equity falls below maintenance margin, which varies by asset and maximum leverage.عرض المصدر ↗

dYdX docs say each v4 full node maintains an in-memory order book and validators propose matched trades into blocks.عرض المصدر ↗

dYdX funding docs state funding rates are used to keep perpetual market prices close to oracle prices.عرض المصدر ↗