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:
- Does the liquidation eventโs
accountValuerepresent the exact economic value transferred during a backstop liquidation? - If not, what is the correct accounting formula for the transferred value, especially when unrealized PnL and the takeover price are involved?
- Can the exact transferred value be reconstructed from historical node data such as
misc_eventsor other official records?
| Field | Where the issue says it appears | What is confirmed by the supplied sources |
|---|---|---|
accountValue | WsLedgerLiquidation | The issue identifies the field, but the supplied docs do not define it or confirm that it equals transferred value. |
leverageType | WsLedgerLiquidation | Mentioned in the issue; no field definition is provided in the supplied docs. |
liquidatedPositions | WsLedgerLiquidation | Mentioned in the issue; no field definition is provided in the supplied docs. |
liquidated_account_value | WsLiquidation | Mentioned in the issue; no field definition is provided in the supplied docs. |
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:
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). โ- Liquidations are triggered when the entire portfolio margin account is below its portfolio maintenance margin requirement.
- Portfolio margin liquidations are taken over directly by the backstop liquidator at system address
0xbbb...b. - If user health is below the full liquidation threshold, supplied assets with positive LTV and borrowed assets are fully taken over.
- If user health is between the partial and full liquidation thresholds, supplied assets with positive LTV and borrowed assets are taken over in 20% intervals, stopping as soon as the user is no longer liquidatable.
- The backstop liquidator converts collateral assets to debt assets for repayment using a TWAP with a half life of 10 minutes.
- Unlike perps, there is no market liquidation phase for the described portfolio margin liquidation flow.
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:
- Whether
accountValueequals the exact value transferred to the backstop liquidator. - Whether the same interpretation applies to cross margin and isolated margin.
- How to treat unrealized PnL and the takeover price without double-counting.
- Which historical fields, if any, can reconstruct the exact transferred value.
- Whether
misc_eventsor another official record contains the needed accounting fields.
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:
- Store
accountValueand any liquidation value field separately. - Do not use
accountValueas the transferred value unless an official source confirms that equivalence. - Record the event timestamp, DEX, positions, and any available ledger identifiers.
- Reconcile against official ledger or historical data only after the field semantics are confirmed.
- Treat the result as unresolved if the only available source is an open community issue.
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.