Tax Reporting on Hyperliquid: Accounting for Perpetuals, Liquidations, and Funding Payments

A trader on Hyperliquid closes a 5x leveraged perpetual futures position after three weeks of holding, capturing a modest profit. The same day, they receive a funding payment credited directly to their account. Two months later, they open and close an identical trade, then immediately reverse it at a slight loss—a wash trade that their tax accountant flags as problematic. The practical question is not whether these events trigger tax liability. In most jurisdictions, they do. The unresolved challenge is how to track, categorize, and report them accurately when the platform’s transaction history spans perpetuals, spot trades, liquidations, funding rate income, and margin adjustments—all denominated in multiple assets and settled on-chain at sub-second intervals.

Hyperliquid’s structure as a fully on-chain central limit order book (CLOB) creates both transparency and complexity. Every trade execution, liquidation event, and funding payment is recorded on the blockchain, theoretically auditable and verifiable. Yet that on-chain record often differs from the wallet perspective, the account statement view, and the tax authority’s expectation of what constitutes income or loss. A trader who uses hyperliquid for frequent perpetuals trading must understand how each transaction type affects their taxable position, where common mistakes occur, and what documentation accountants require to defend those calculations during an audit.

How perpetual futures trades generate taxable events on Hyperliquid

A perpetual futures position on Hyperliquid differs from spot trading in one crucial tax respect: it does not result in token custody. When a trader opens a long position on ETH/USD perpetuals, they are not acquiring Ethereum. They are entering a derivative contract whose value fluctuates with the underlying price but whose economic effect is leverage-adjusted profit or loss. That difference has direct implications for tax treatment. Most tax jurisdictions classify perpetual futures as either capital gains from derivatives trading or, in some cases, section 1256 contracts eligible for 60/40 favorable treatment under US tax code.

The entry point for tax calculation is the opening trade. Hyperliquid records the entry price, notional size, and leverage ratio when the position opens. If a trader enters 10 ETH worth of perpetuals at $3,500 with 5x leverage, they have committed $7,000 notional value. Their initial cost basis, for tax purposes, is the amount they actually risked or paid in margin—not the notional exposure. This is where spot purchases and derivatives diverge sharply. A spot purchase of 2 ETH at $3,500 has a cost basis of $7,000 in most scenarios; a derivative trade’s basis is the margin posted or the collateral amount, reduced by any partial winnings during the hold.

When the position closes, the realized profit or loss is the difference between the entry price and exit price, multiplied by the position size, then adjusted for fees and funding payments received or paid during the hold. If that same 10 ETH notional perpetual closes at $3,600, the trader realizes a $1,000 gross profit before accounting for trading fees (typically 2.5 basis points on Hyperliquid for maker orders, 5 basis points for takers) and any funding costs. The realized loss or gain is therefore $1,000 minus approximately $25 in fees (2.5 bps on entry and exit), yielding a net realized gain of approximately $975. That gain is taxable in the year the position closes, regardless of when the margin was posted.

A common mistake is treating funding payments as offsetting the gain retroactively. They do not. Funding payments are separate income items, addressed in their own tax treatment. The perpetual trade itself is closed at a realized gain or loss determined solely by entry and exit prices and direct trading fees. Maintaining separate records—one for the perpetual P&L and another for funding income—is essential for accurate reporting and audit defense.

Understanding liquidations and their tax consequences

Liquidation on Hyperliquid occurs when a position’s mark price moves against the trader sufficiently that remaining collateral cannot cover the loss. The protocol automatically closes the position at the bankruptcy price, triggering an involuntary sale at often a worse price than the current market level due to liquidation penalty and slippage in the on-chain order book. From a tax perspective, a liquidation is still a realized gain or loss—the position is closed, and the economic outcome is finalized.

The calculation follows the same logic as a voluntary close: entry price minus exit price (in this case, the liquidation price) times the position size, adjusted for fees. A trader who enters a 10 ETH short perpetual at $3,800 with 3x leverage, sees the price rise to $3,850, and gets liquidated has realized a loss of ($3,850 − $3,800) × 10 = $500. If Hyperliquid’s liquidation mechanism imposed an additional liquidation fee of $15 or more, the total realized loss is $515 or higher. That loss is deductible in the current tax year, subject to wash-sale rules (which we address separately) and the trader’s overall tax situation.

What makes liquidations tax-tricky is documentation. Many traders receive a liquidation notification but fail to export the precise liquidation price, fee structure, and exact timestamp from Hyperliquid’s transaction history. If an accountant or tax authority requests verification, the trader who relied on screenshots or memory is at a disadvantage. The platform records liquidations on-chain with full granularity; exporting or querying that data is the necessary defensive step. Without clear records showing the liquidation price and the exact margin-to-loss ratio at liquidation, a tax authority might question whether the loss was legitimate or whether it resulted from reckless leverage misuse (which could affect deductibility treatment in some jurisdictions).

Another complication is partial liquidations. If a trader’s collateral drops close to the liquidation threshold but the protocol’s automated systems reduce position size rather than fully closing, the trader should record that event separately. Each reduction in notional size is a realized close, even if it occurred at an unfavorable price. Documentation should include the reason (margin pressure, partial liquidation protection, or other automated triggers), the price, and the timestamp to distinguish it from a voluntary close at a different price.

Funding payments as ordinary income

On Hyperliquid, funding rates are the periodic payments transferred between long and short positions to maintain the perpetuals contract’s price aligned with the spot market. When longs are more numerous or larger than shorts, longs pay shorts. The amount is typically a small percentage (0.01 to 0.05 percent per hour in normal market conditions) applied to the notional size of the position. For tax purposes, funding payments are treated as ordinary income in nearly every jurisdiction that has issued guidance on crypto derivatives.

A trader holding a long 10 ETH notional perpetual position for a full eight-hour funding interval at a 0.02 percent rate receives 0.0002 × $35,000 = $7 in funding income. That $7 is ordinary income, taxable as received, in the year it is credited to the account. If a trader receives 52 funding payments over the course of a year, each is a separate taxable event, though they are typically aggregated into a single line item on a tax return: “Cryptocurrency Derivatives Funding Income.” The key is that the income is realized when credited to the account balance, not when the position closes. A trader who receives $500 in funding payments over six months, closes all positions at a $300 loss, cannot net those items directly. Both are reported: $500 in funding income (ordinary income) and $300 in capital loss (from the perpetuals trade).

Tracking funding payments requires regular exports from Hyperliquid. The platform’s API and UI provide transaction history that should itemize funding credits separately from trade executions. A trader using spreadsheet accounting or an external crypto-tax service should ensure that funding payments are categorized as income, not as reductions to realized loss or adjustments to cost basis. This is a frequent accounting error: treating funding as a cost offset rather than income, which understates tax liability and invites audit risk.

The tax implication of funding payments also depends on the trader’s tax residency and the tax authority’s classification of derivatives income. In the United States, ordinary income from funding rates is typically subject to ordinary income tax rates (not capital gains treatment). In other jurisdictions, derivatives income may be classified as business income if the trader is engaged in frequent trading, which could expose them to self-employment tax or different ordinary income thresholds. Consulting a tax professional familiar with crypto derivatives is advisable if funding income is substantial.

Wash sales and matching trades

A wash sale occurs when a trader realizes a loss on an investment and, within 30 days before or after the loss sale, purchases substantially identical property. The realized loss is disallowed for the current tax year; instead, it adjusts the cost basis of the replacement position. US tax code section 1091 originally applied only to stocks and securities, but the IRS has extended wash-sale logic to crypto spot transactions in regulatory guidance (see 2019 guidance clarifying that like-kind exchanges no longer applied to crypto after the Tax Cuts and Jobs Act of 2017).

Whether wash sales apply to perpetual futures derivatives is less definitively settled than it is for spot purchases. The strongest interpretation is that perpetual futures are derivatives contracts, not investments in property, and therefore wash-sale rules do not apply. However, some conservative tax advisors and a few tax authorities have suggested that if a trader opens a long perpetual after realizing a loss on a short perpetual of the same underlying (e.g., long ETH perpetual after closing a short ETH perpetual at a loss), the pattern could be challenged as a wash sale or similar substance-over-form violation.

The practical defense is: (1) maintain clear records of each perpetual as a separate position with its own entry, exit, and duration; (2) if opening a new position within 30 days of closing a loss-generating position, document the economic difference (such as different leverage ratios, different funding rate environments, or different price expectations); and (3) do not describe the second trade as a hedge of the first in correspondence with accountants or advisors—hedge language can invite wash-sale assertions even if the positions are technically derivatives. For traders routinely executing identical perpetual trades (opening long, closing, then opening long again), documenting the business intent and the distinct timing of each decision strengthens the position against scrutiny.

Exporting transaction data and structuring records for audit defense

Hyperliquid’s on-chain settlement provides an audit trail, but extracting clean transaction data for tax purposes requires deliberate effort. The platform offers account history export features (typically in CSV or JSON format) that include trade executions, funding payments, liquidations, and transfers. A trader preparing tax returns should export the complete history for each tax year and cross-reference it with wallet activity, margin adjustments, and any transfers of collateral between accounts or wallets.

The essential columns in a clean export are: trade timestamp (in UTC), position type (long or short), entry price, exit price (or liquidation price), notional size, leverage used, fees paid, realized P&L before fees, realized P&L after fees, funding payments received or paid (as a separate line item), and any liquidation fees. Many tax-software platforms designed for crypto trading (CoinTracker, Koinly, or professional-grade tools like Bloomberg Tax) can ingest Hyperliquid API data or imported CSVs and automatically categorize perpetuals trades, funding, and liquidations. However, even automated tools require manual review. A position mislabeled as a spot trade instead of a perpetual, or a funding payment incorrectly netted against realized loss, will persist through final tax return preparation unless caught during review.

For traders using Hyperliquid with high transaction frequency (more than 50 trades per year), storing both the raw export and a cleaned summary spreadsheet is prudent. The summary should aggregate trades by month or quarter, showing total perpetual P&L, total funding income, and total trading fees. That summary, paired with the raw export, gives an accountant or tax authority confidence that the reported figures are grounded in detailed transaction-level records rather than estimates or approximations.

One additional export consideration: Hyperliquid’s email-based account model means that a single email address can theoretically maintain multiple trading accounts. If a trader operates separate accounts for different strategies or position sizes, each account’s transaction history must be exported and consolidated for tax purposes. Tax authorities typically expect a single consolidated tax return for all trading activity by a filer, regardless of how the accounts are segregated internally. Failing to consolidate would understate total income or loss and invite penalty assessment during audit.

Choosing the right cost-basis method for frequent perpetuals trading

Tax code allows traders to use specific identification, FIFO (first-in, first-out), LIFO (last-in, first-out), or average cost basis for investments. For perpetual futures trading, the distinction matters less than for spot holdings because each perpetuals trade is a discrete event with its own entry and exit. However, if a trader holds multiple perpetual positions on the same underlying simultaneously (e.g., two long ETH perpetuals at different leverage ratios, opened on different dates), specifying which position is closed when can optimize tax outcome.

Under specific identification, a trader can elect to close the position with the highest unrealized loss first, deferring the close of the more profitable position. That approach minimizes current-year taxable gains. Under FIFO, the oldest position closes first, which may force the realization of a larger gain if older positions happened to be more profitable. For a trader executing dozens of perpetuals trades per year, maintaining accurate records to support specific identification decisions is essential.

The critical point is consistency: choose a cost-basis method, document it, and apply it uniformly across all trades in a given tax year. Switching methods between years or between perpetuals and spot trading can trigger IRS scrutiny. A trader who used specific identification for perpetuals in 2024 but switches to FIFO in 2025 must obtain IRS Form 3115 approval or risk adjustment. When in doubt, average cost or FIFO is the safer default because it requires less documentation, though it may not be optimal for tax minimization.

Collateral, margin calls, and no-tax-event transfers

Depositing collateral into a Hyperliquid account to initiate margin trading is not itself a taxable event. Moving $50,000 from a wallet to the Hyperliquid platform is a transfer, not a sale or disposition. However, if that $50,000 was previously held in a spot wallet and the trader paid a fee to move it, that fee is not deductible; it adjusts the cost basis of the funds if they will later be used to purchase spot assets, or it is a sunk expense if the collateral is used solely for derivatives trading.

Margin calls and forced collateral liquidations are similarly non-taxable transfers. If Hyperliquid forces liquidation of collateral held in a spot position to cover a derivatives margin shortfall, that liquidation is a taxable event for the spot asset but not an additional tax event beyond the underlying perpetuals loss that triggered the margin pressure. A trader should carefully separate these: the perpetuals trade generates its own realized loss, and if collateral was posted using a separate spot asset, the liquidation of that spot asset is a separate realized gain or loss.

Withdrawing collateral at the end of trading is also a non-taxable transfer. Receiving $45,000 back from Hyperliquid after a trading session has generated realized gains is not additional income; the gains were already recognized when the perpetuals positions closed. The withdrawal is merely the return of collateral, less any net loss realized during the session.

Common mistakes and how to avoid them

First mistake: aggregating funding payments into realized perpetuals P&L. Funding is separate income and should be reported separately. Second mistake: failing to document liquidation prices and liquidation fees. Liquidation is a valid realized loss, but without clear documentation, a tax authority may deny it. Third mistake: not maintaining consistent records across multiple account transfers or wallet changes. If a trader moves funds or positions between wallets or accounts mid-year, the old and new account records must be consolidated and cross-referenced for tax purposes.

Fourth mistake: treating a wash sale defense as optional. Even if wash sales may not technically apply to perpetuals, the IRS could challenge a pattern of offsetting trades. A trader who systematically closes losing perpetuals and immediately reopens identical positions should be prepared to explain the business justification. Fifth mistake: confusing notional exposure with cost basis. A $35,000 notional ETH perpetual with 5x leverage has a cost basis equal to the margin posted (perhaps $7,000 or less, depending on collateral requirements), not $35,000. Reporting the notional amount as the taxable gain or loss basis inflates the apparent return and invites computational audit.

Sixth mistake: not reconciling API data with the UI transaction history. Hyperliquid’s API and web interface should display the same data, but timing mismatches or display bugs can cause discrepancies. A trader relying solely on API exports without spot-checking key trades against the UI may miss discrepancies. Seventh mistake: assuming funding payments are taxed at capital gains rates. They are ordinary income in most jurisdictions, triggering higher tax rates than long-term capital gains. This mistake typically results in significant underpayment of estimated tax and potential penalties.