Hyperliquid Tax Reporting: OneKey Wallet Transaction Export

Why Hyperliquid tax reporting suddenly matters more (especially in 2026)

If you actively trade perpetuals or spot on Hyperliquid, your activity often spans multiple “data surfaces”: in-app trading fills, funding payments, and on-chain deposits/withdrawals (typically via Arbitrum). When tax season arrives, the hard part isn’t calculating gains—it’s reconstructing a complete, timestamped ledger that your accountant (or tax software) can reconcile.

This has become a top user concern as U.S. reporting rules phase in Form 1099-DA requirements: brokers must report gross proceeds for transactions effected on or after January 1, 2025, with basis reporting ramping up for certain transactions on or after January 1, 2026. See the IRS overview on Digital assets and the Instructions for Form 1099-DA (2025).

For self-custodial traders, that typically means one thing: your own exports are the source of truth.

Hyperliquid in one page: what you’re actually exporting

Hyperliquid’s trading layer + bridge flows

Hyperliquid operates a high-performance trading system where trading itself is designed to feel “exchange-like,” while deposits/withdrawals often involve an on-chain bridge flow. For example, Hyperliquid’s native bridge is between Hyperliquid and Arbitrum, and the developer documentation spells out the deposit/withdraw mechanics and signature flow in Bridge2.

For tax reporting, that split is important:

• Trades / fills / funding live in Hyperliquid’s trading records (exportable via UI CSV or queryable via API).
• Deposits / withdrawals leave an on-chain trail (commonly on Arbitrum), which you can export from explorers for reconciliation.

HyperEVM: the “new” source of wallet activity many users forget

As the ecosystem expands, more users also interact with HyperEVM (EVM-compatible activity can create additional taxable or reportable events such as swaps, LP actions, airdrop claims, and contract interactions). Hyperliquid maintains a curated list of ecosystem tooling (including explorers) under HyperEVM Tools.

What counts as “tax-relevant” on Hyperliquid (practical checklist)

Before exporting anything, decide what you must capture. A solid baseline is:

• Perp fills (opens/closes, partial fills, realized PnL, fees)
• Spot trades (buys/sells, fees)
• Funding payments (often treated as income/expense depending on jurisdiction and accounting method)
• Deposits and withdrawals (USDC movements in/out, bridge fees)
• Any HyperEVM activity tied to the same identity/address set

In practice, most reconciliation issues come from missing one of these categories—especially deposits/withdrawals that happened on-chain but aren’t obvious inside a trading CSV.

Exporting Hyperliquid data (CSV + API options)

Option A: Export CSV from the Hyperliquid UI (fastest)

Many users start with the built-in CSV exports:

• Trade History → Export as CSV
• Funding History → Export as CSV

A clear walkthrough is described in Cryptact’s guide: How to get trade history from Hyperliquid. CoinTracker also references the same workflow in its integration notes: How to do your HyperLiquid taxes with CoinTracker.

Tip: If you trade frequently, export regularly (monthly or quarterly). Some platforms and integrations note practical limits (for example, very large histories may require pagination or segmented exports), and staying ahead prevents year-end gaps.

Option B: Query fills via API (best for automation and completeness)

For power users (or anyone who wants reproducible tax pipelines), Hyperliquid exposes fills endpoints through its info API. The official documentation covers formats, limits, and time-range queries in Info endpoint.

A minimal example (illustrative) looks like:

curl -X POST "https://api.hyperliquid.xyz/info" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "userFillsByTime",
    "user": "0xYourAddressHere",
    "startTime": 1735689600000,
    "endTime": 1767225599000
  }'

This approach is especially helpful if you want to:

• Pull data in consistent time windows (monthly buckets)
• Re-run reports after corrections
• Merge fills with on-chain transfers using a single timestamp standard

Option C: Historical archives (advanced users)

If you’re doing research-grade analytics or reconstructing very large datasets, Hyperliquid also documents historical archives and formats, including S3 buckets, in Historical data.

OneKey wallet transaction export: how to build an audit trail that matches your Hyperliquid CSV

Hyperliquid activity is wallet-linked. That means your OneKey wallet address (or addresses) effectively becomes the “account ID” that ties together:

• Hyperliquid trading exports (fills, funding)
• On-chain deposits/withdrawals (bridge transfers)
• Any HyperEVM contracts you touched

Even if your wallet app doesn’t offer a one-click “tax CSV” today, you can still produce a tax-ready transaction export by using chain explorers as the neutral source of record.

Step 1: Identify which chains you used with Hyperliquid

Common patterns:

• Arbitrum for USDC deposits/withdrawals via the native bridge (see Bridge2)
• HyperEVM for ecosystem dApps (explorers listed in HyperEVM Tools)

Step 2: Export deposits/withdrawals from Arbitrum (bridge visibility)

The Hyperliquid documentation provides the Arbitrum bridge reference, and you can verify flows on a block explorer. For example, you can inspect the bridge address on Arbitrum via Arbiscan (address referenced in the official docs).

What you’re looking for in your wallet history:

• USDC transfers from your address to the bridge (deposits)
• USDC transfers from the bridge back to your address (withdrawals)
• Any approval transactions or related calls (depending on how you deposited)

This is the simplest way to reconcile “money in/out” against your Hyperliquid trading activity.

Step 3: Export HyperEVM activity (if you used it)

If you interacted with HyperEVM, use one of the explorers listed in Hyperliquid’s own tooling directory—e.g., those linked under HyperEVM Tools—to pull your address history and token transfers.

What to capture:

• Native gas token movements (fees)
• Token transfers
• Contract interactions that imply swaps, staking, LP deposits, claims, etc.

Step 4: Normalize and reconcile (the part that prevents tax-time pain)

Once you have:

• Hyperliquid fills (CSV or API)
• Hyperliquid funding (CSV)
• On-chain deposits/withdrawals (Arbitrum explorer export)
• HyperEVM transactions (if applicable)

Do a quick reconciliation pass:

• Time alignment: convert all timestamps to a single timezone (UTC is standard).
• Asset naming: unify symbols (USDC, bridged USDC variants if applicable, etc.).
• Fees: ensure fees from fills and fees from on-chain transactions are not double-counted.
• Transfers vs trades: deposits/withdrawals are usually non-taxable transfers by themselves, but they must be present to explain balance changes.

A simple integration model: how Hyperliquid + OneKey fit together

Here’s a clean mental model for the integration:

• Hyperliquid uses your wallet address as identity and requires signatures for key actions (for example, bridge withdrawals involve a signature flow described in Bridge2).
• OneKey provides hardware-based key isolation for those signatures, which is particularly valuable for active traders who frequently connect to dApps and sign messages.
• For tax reporting, Hyperliquid provides trade/funding exports, while your wallet-side exports (via explorers) provide the independent audit trail.

This division of responsibilities is exactly what you want: trading records from the venue, and settlement records from the chain.

Closing: why OneKey makes sense for serious Hyperliquid users

If you trade on Hyperliquid regularly, your main tax reporting risk is rarely “wrong math”—it’s missing or inconsistent source data across trading exports and wallet transfers.

Using OneKey as your signing environment helps keep the same on-chain identity stable over time (which makes exports and reconciliation easier), while keeping private keys off networked devices—an important operational advantage when you’re routinely connecting to trading and DeFi interfaces.

When you treat exports as part of your trading routine (not an annual scramble), Hyperliquid tax reporting becomes a straightforward data workflow instead of a year-end emergency.