guides/cointracking

CoinTracking + Hyperliquid: importing a complete record

updated october 2026 · ~5 min · not tax advice

CoinTracking's strength is your bottleneck

CoinTracking's model is built around imports: exchange APIs where available, CSV files everywhere else. That model is fine — the problem for Hyperliquid users is upstream. The venue has no export button, and the data you can pull yourself has hard retention limits.

So the real question isn't whether CoinTracking can ingest Hyperliquid activity — it can, via CSV — it's whether the file you feed it contains the whole record or a stub of it.

Why a DIY export under-reports

The venue's fill endpoint retains roughly the last 30 hours. Anything you export through it covers days, not your tax year — and nothing in the API warns you about the boundary. A 'full history' CSV built on it is silently ~1% of an active account's year.

Two more streams live outside fills entirely: funding settles hourly on its own endpoint (8,760 events a year on an open position), and the ledger — deposits, withdrawals, sub-account and spot transfers — is a third. A fills-only export misses both.

And builder-dex markets (HIP-3 venues like xyz:, flx:), which carried over half of perp volume at their mid-2026 peak, sit outside the main perp book an export might enumerate.

What a complete import file needs

Fills from a chain indexer, not the venue endpoint — the indexer keeps the full history the venue API drops. Funding and ledger from the venue's full-history endpoints. Then a basis method applied across the reconstructed history, so each disposal carries proceeds and cost instead of a raw trade list.

That's the file worth feeding CoinTracking: disposals with date, asset, proceeds, basis and gain — the columns its tax engine actually computes on. A raw fill dump makes the tool re-derive your PnL and guess your basis; an evidenced disposal file carries both.

The European wrinkle

CoinTracking's user base skews European — and European regimes are why record quality matters more here, not less. FIFO is the default or mandatory method in several EU jurisdictions; others tax perp gains under futures/derivatives rules rather than simple capital gains. Whatever your country requires, it computes on the same raw record — completeness is the precondition either way.

Our exports give you the reconstructed disposals with basis under FIFO or weighted average; how your jurisdiction classifies them stays with you and your adviser.

Common questions

?Does CoinTracking have a Hyperliquid integration?

Whatever sync exists is bounded by the venue's API — the fill endpoint only retains ~30 hours. The reliable path is a complete CSV built from indexer data, which CoinTracking's import system is designed to consume.

?What format should I import?

Disposal-level rows — date, asset, proceeds, basis, gain — not raw fills. Raw fills force the tool to re-derive PnL and guess basis; a proper export file carries both already computed and verified.

?I'm on FIFO — does that change the import?

The record doesn't change, the basis method does. FIFO must be applied across the full reconstructed history — including fills before the tax year — or earlier lots get assigned wrong or missing cost. Our report lets you pick the method before export.

?Why does my imported history stop in the middle of my trading?

Fill retention. The venue endpoint only serves the last ~30 hours, so anything built on it truncates at that boundary. An indexer-built export covers the whole period.

Get the complete record first — free

Paste your address and the check recomputes every fill from indexer data — complete history, full funding, verified against the account-value identity. Importable exports come with the report.

Run the free check