๐Ÿ”Œ API & Developers

Hyperliquid accountValue vs Transferred Value in Backstop Liquidation Events (2026)

โš ๏ธ Disclosure: Some links on this page are affiliate links. If you sign up through them, I may earn a commission โ€” at no extra cost to you.
There is no confirmed equivalence between accountValue and the value transferred in a Hyperliquid backstop liquidation event, based on the public sources available as of November 17, 2026.

The community-reported Hyperliquid Python SDK issue #336 asks whether the liquidation eventโ€™s accountValue represents the exact economic value transferred to the HLP liquidator vault during a backstop liquidation, for both cross and isolated margin. The issue is open and does not include a maintainer answer in the retrieved excerpt.

The Hyperliquid portfolio margin documentation confirms that portfolio margin liquidations are taken over directly by the backstop liquidator at system address 0xbbb...b. It also describes full and partial takeover behavior, but it does not define accountValue, liquidated_account_value, or a formula for converting an event field into the transferred value.

What the issue is asking

Issue #336 frames the question around reconstructing HLP PnL from backstop liquidations. The reporterโ€™s working approach is:

HLP PnL = value transferred at takeover
        + PnL from subsequently holding and closing the acquired positions

The issue then asks three unresolved questions:

  1. Does the liquidation eventโ€™s accountValue represent the exact economic value transferred during a backstop liquidation?
  2. If not, what is the correct accounting formula for the transferred value, especially when unrealized PnL and the takeover price are involved?
  3. Can the exact transferred value be reconstructed from historical node data such as misc_events or other official records?
The issue lists the fields it is trying to reconcile:
FieldWhere the issue says it appearsWhat is confirmed by the supplied sources
accountValueWsLedgerLiquidationThe issue identifies the field, but the supplied docs do not define it or confirm that it equals transferred value.
leverageTypeWsLedgerLiquidationMentioned in the issue; no field definition is provided in the supplied docs.
liquidatedPositionsWsLedgerLiquidationMentioned in the issue; no field definition is provided in the supplied docs.
liquidated_account_valueWsLiquidationMentioned in the issue; no field definition is provided in the supplied docs.
Because the issue is a community question rather than an official specification, these field names should be treated as reported event fields pending official confirmation.

What the portfolio margin docs confirm

The portfolio margin documentation confirms the mechanics of backstop takeover, but not the WebSocket field mapping.

For portfolio margin accounts:

๐Ÿ’ก Hyperliquid

Like what you're reading? Try it yourself โ€” this link supports ChartedTrader at no cost to you.

Create a Hyperliquid account (referral link; we may earn a commission; referred accounts get a 4% fee discount on the first $25M of volume; Vaults and sub-accounts are excluded). โ†’
๐ŸŽ You receive: 4% fee discount on first $25M volume ยท per account, lifetime

This matters for programmatic reconciliation because the takeover is described as an asset takeover and conversion process, not as a single documented cash-transfer field. That does not prove that accountValue is wrong, but it means the event field cannot be assumed to be the final transferred or realized value without an official formula.

What remains unanswered

The following questions remain open in the public issue:

Until Hyperliquid publishes a field definition or accounting formula, the safest interpretation is that accountValue and transferred value are related but unconfirmed quantities.

Practical rule for processing liquidation deltas

If you are building a program that processes Hyperliquid liquidation events, a conservative reference approach is:

  1. Store accountValue and any liquidation value field separately.
  2. Do not use accountValue as the transferred value unless an official source confirms that equivalence.
  3. Record the event timestamp, DEX, positions, and any available ledger identifiers.
  4. Reconcile against official ledger or historical data only after the field semantics are confirmed.
  5. Treat the result as unresolved if the only available source is an open community issue.
A minimal pseudocode guard looks like this:

def classify_liquidation_value(event):
    account_value = event.get("accountValue")
    liquidated_account_value = event.get("liquidated_account_value")

    return {
        "account_value": account_value,
        "liquidated_account_value": liquidated_account_value,
        "transferred_value": None,  # not confirmed by available official docs
        "reconciliation_status": "unresolved",
    }

This is a reference pattern, not an official Hyperliquid API response or a tested production implementation.

Bottom line

accountValue should not be treated as the transferred value in backstop liquidation events without further official confirmation. The open issue identifies the ambiguity, and the portfolio margin docs confirm the backstop takeover process but do not define the event fields or provide a reconciliation formula. For programmatic use, keep the fields separate and mark the transferred value as unresolved until Hyperliquid documentation or a maintainer answer clarifies the accounting.

For broader background, see Hyperliquid Liquidations Explained and Hyperliquid Account Value & Unrealized PnL Explained.

Create a Hyperliquid account using this referral link. We may earn a commission if you sign up. Referred accounts receive a 4% fee discount on the first $25M of volume; Vaults and sub-accounts are excluded.

Continue with Hyperliquid

Browse the Hyperliquid guide hub for the complete user journey.

๐Ÿงฎ Free Hyperliquid calculators

Fee Calculator โ†’
Hyperliquid vs centralized exchange fee comparison
PnL & Liquidation โ†’
Perp PnL + liquidation price
Position Size โ†’
Risk-aware position sizing for HL perps
Hyperliquid

Ready to get started? Use the link below โ€” it helps support ChartedTrader at no cost to you.

Create a Hyperliquid account (referral link; we may earn a commission; referred accounts get a 4% fee discount on the first $25M of volume; Vaults and sub-accounts are excluded). โ†’
๐ŸŽ You receive: 4% fee discount on first $25M volume ยท per account, lifetime
๐Ÿ“ˆ

About the author

I'm a systematic trader running live strategies on IB (USDJPY momentum) and Hyperliquid (crypto perps). Questions? Reach out.

๐Ÿ“š Related Articles

โš–๏ธ
Comparisons

Hyperliquid Cross vs Isolated Margin: Which Mode for (2026)

Cross margin shares collateral across positions while isolated margin confines risk. Learn which mode fits your Hyperliquid trading strategy and risk tolerance.

March 22, 2026 โฑ 3 min read
๐Ÿ”Œ
API & Developers

Hyperliquid subAccounts Info Endpoint: List Subaccount Addresses (Python Example)

POST type subAccounts to Hyperliquid's info endpoint with a user address to get subaccount names, addresses, master address, clearinghouse, and spot state.

November 13, 2026 โฑ 3 min read
๐Ÿ“–
Guides

Hyperliquid Liquidation Price & Maintenance Margin (2026)

Calculate your exact liquidation price on Hyperliquid. Understand maintenance margin, leverage limits, and how to avoid getting liquidated in 2026.

July 8, 2026 โฑ 3 min read