TokenTax + Hyperliquid: what the sync can and can't see
updated november 2026 · ~5 min · basisproof research · not tax advice
Complex-case marketing, same upstream API
TokenTax positions itself for the hard cases — DeFi, derivatives, margin. Hyperliquid traders land there expecting completeness. But every sync, in every tool, is bounded by what the venue's API serves — and Hyperliquid's fill endpoint only retains roughly the last 30 hours of history. A premium subscription buys more features, not deeper access to a truncated endpoint.
Worth stating fairly: integrations change constantly, and TokenTax may source Hyperliquid data through more than one path. This page is a checklist for verifying whatever your sync produced today — not a verdict on any vendor.
Where a perps account breaks a generic import
Fill truncation. If the import path reads userFillsByTime, it physically cannot see fills older than ~30 hours — no error, no warning, just a shorter record. On an active account that's the difference between a real year and a long weekend.
A $0 funding line. Perp funding settles hourly through its own endpoint, separate from fills. An account that held positions overnight and shows zero funding isn't clean — it's missing an entire taxable stream.
Missing markets and phantom transfers. Builder-dex markets (HIP-3 venues — xyz:, flx: and friends) carried over half of perp volume at their mid-2026 peak but aren't part of the main perp universe an importer enumerates. And sub-account or spot↔perp transfers that never left your own wallets can surface as deposits and withdrawals — inflating both sides of the ledger.
Three numbers to compare
Transaction count vs reality. Does the imported count look plausible for how much you actually traded? Truncated imports are usually obvious against memory — thousands of fills become hundreds.
The funding line. Exactly $0 on a perps account that carried positions is a red flag, not a clean slate.
Market coverage. Search the imported symbols for xyz:, flx: or any builder-dex market you traded. Absence means the importer only enumerated the main book.
What a complete record looks like
Complete fills only exist on a chain indexer — the venue endpoint structurally can't serve them. Funding and ledger flows come from separate full-history endpoints. And the result should be checked against an independent account-value identity before it goes anywhere near a filing.
Run the free check on your address: we rebuild the record fill by fill and print the totals. If they match your sync, that's evidence you're complete. If they don't, the delta tells you exactly which stream was dropped — and the paid report delivers the corrected artifacts (fills, funding, ledger, 8949-format rows) your preparer or manual CSV import can consume.
Common questions
?Does TokenTax support Hyperliquid?
TokenTax supports a wide range of venues and DeFi protocols — but support and completeness are different questions. Verify the three numbers above on your synced record rather than trusting the integration's label.
?Is this a TokenTax problem specifically?
No — these are upstream API constraints. Any tool reading the retention-limited fill endpoint hits the same wall. The failure is silent in every importer that doesn't measure its own coverage.
?Can corrected data go back into TokenTax?
TokenTax accepts manual CSV imports, so a complete recomputed export can replace or supplement the sync — the fix lives upstream, in where the data comes from.
Sources & method
See what the venue API isn't showing you — free
The fill endpoint forgets everything older than ~30 hours. The free gap check measures what fraction of your record it actually serves — seconds, not minutes.
Measure my gap