Awaken + Hyperliquid: what to check after the sync
updated october 2026 · ~5 min · not tax advice
The address looks EVM — the chain isn't
Hyperliquid addresses are 0x-prefixed and 20 bytes, identical in shape to Ethereum and Solana-adjacent tooling expects. But Hyperliquid is its own L1: it isn't an EVM chain, doesn't emit standard token transfers, and its activity lives on custom venue endpoints — not on any chain a generic multi-chain sync already walks.
That's the first thing that trips a tool like Awaken up: the wallet address validates, the sync accepts it, and then the question becomes which of the venue's data endpoints the importer actually reads.
What a generic sync does with a Hyperliquid wallet
If the tool reads the venue's fill endpoint directly, it gets roughly the last 30 hours — the endpoint retains nothing older. Your tax-year view can silently contain a few days of trading.
Funding, settling hourly on its own endpoint, is invisible to a fills-only import — $0 funding on an account that held positions means the stream was dropped. Builder-dex markets (xyz:, flx: and other HIP-3 venues) sit outside the main perp book; they carried over half of perp volume at their mid-2026 peak.
And spot activity, sub-account moves and deposits all live on the ledger — a third endpoint — so single-endpoint syncs can't even see where account value actually moved.
The cross-chain user's specific trap
If you came to Hyperliquid from Solana or an EVM chain, your year probably spans wallets on both — and the bridge hop is where basis gets lost. USDC bridged in isn't a purchase event the venue records; the lot's real cost sits on the origin chain.
A sync that covers your Solana wallet and your Hyperliquid wallet separately can produce two halves that never reconcile: proceeds on one side, unexplained balance on the other. The record has to be continuous across the bridge to carry basis through.
What actually fixes it
A complete Hyperliquid record starts from a chain indexer — fills the venue API has already forgotten — plus the funding and ledger endpoints, verified against an independent account-value identity. Basis carried in from an exchange or another chain can be seeded from that side's own export.
Run our free check on the address and compare its totals to whatever your sync produced: fill count, funding sum, realized PnL. The delta tells you which stream the sync couldn't reach — and the paid report emits the corrected, basis-tracked record in the formats your filing flow consumes.
Common questions
?Does Awaken support Hyperliquid?
Hyperliquid uses EVM-shaped addresses, so adding the wallet is easy — support for the chain's actual data is the variable. Check fill count, funding, and builder-dex markets to see what your sync really covered.
?My Hyperliquid address is a 0x address — isn't that an EVM chain?
No — it's a coincidence of address format. Hyperliquid is its own L1 with custom endpoints; nothing on it behaves like Ethereum. Tools that treat it as EVM miss every stream.
?I bridged USDC from Solana — how does basis carry over?
The bridge deposit isn't a purchase — the lot's cost lives in the Solana-side buy. Our CEX/chain-basis seeding replays the origin record and attaches real cost to the arriving lot; without it, the Hyperliquid side reports unknown basis.
?The sync shows my recent trades but nothing older — why?
The venue's fill endpoint only retains ~30 hours of history. Anything older must come from a chain indexer; re-syncing reads the same endpoint and returns the same window.
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