CoinTracker + Hyperliquid: what's missing from the sync
updated october 2026 · ~5 min · not tax advice
The sync works — the coverage is the question
CoinTracker can pull a Hyperliquid wallet by address — transactions appear, totals get computed. What a sync like that inherits is the venue's API shape, and that shape has hard limits no importer can negotiate past. Whether your copy of it is complete is a different question from whether the sync ran.
A fair caveat: integrations ship updates constantly. Treat this page as a five-minute checklist for what you're seeing today, not a permanent verdict on any tool.
What the venue's API quietly drops
Fill history. The venue's fill endpoint retains roughly the last 30 hours. A sync built on it shows recent activity and nothing else — an account's 'full year' can contain a few percent of its real trades with no error anywhere in the UI.
The funding stream. Funding settles hourly on a separate endpoint, outside trade fills. A fills-only import shows $0 funding — on an account that held positions, that's a dropped-data flag, not reality. Funding also dominates transaction counts on active accounts: 8,760 settlement events per year per open position.
Builder-dex markets. HIP-3 venues (xyz:, flx: and others) carried over half of perp volume at their mid-2026 peak but sit outside the main perp book. If your sync only enumerates main-dex markets, every builder-dex fill is invisible.
The billing wrinkle
CoinTracker prices by transaction count — and on a perps venue, fills are transactions. An active Hyperliquid account generates tens of thousands per year; a heavy one, hundreds of thousands. You can end up paying for a tier sized by the full stream while the import itself delivered a truncated one.
Check the count your wallet reports against what you actually did. If it looks implausibly low, the problem is coverage. If it looks right and the bill is what bothers you — the underlying stream is just that large, which is exactly why the record needs to be verified rather than sampled.
What actually fixes it
Get a verified complete record first; then it can go anywhere — a preparer's spreadsheet, or a CSV import your tool accepts. Fills have to come from a chain indexer (the venue endpoint physically can't serve older history), funding and ledger from the venue's full-history endpoints.
Run our free check on the same address and compare totals: fill count, funding sum, realized PnL. If they agree, your sync got the data. If they don't, the delta tells you exactly which stream was dropped — and the paid report emits the corrected, basis-tracked record in importable formats.
Common questions
?Does CoinTracker support Hyperliquid?
It offers wallet syncs for Hyperliquid addresses. The question is coverage, not connectivity — check fill count, the funding line, and whether builder-dex markets appear before trusting the totals.
?Why does my CoinTracker Hyperliquid wallet show so few transactions?
The likeliest cause is fill truncation: the venue's fill endpoint only retains ~30 hours. A sync reading it gets a few days of activity. Re-syncing reads the same endpoint and returns the same window.
?My funding line shows $0 — is that right?
Almost certainly not, if you held positions. Funding settles hourly on its own endpoint; a fills-only import never sees it. On any leveraged account, $0 funding means the stream was dropped.
?Why is my transaction count so high — do I really owe that many rows?
Probably yes. Perp trading generates a row per fill plus hourly funding settlements — 20,000+ a year is ordinary for an active account. What's worth checking isn't the count, it's whether all of them made it into the report.
Check what your sync actually got — free
Paste your address and compare the recomputed totals against your import: complete fills, the full funding stream, and a verified account-value identity — the three numbers that tell you what was dropped.
Run the free check