guides/united kingdom · lighter

Lighter taxes in the UK

updated november 2026 · ~5 min · basisproof research · not tax advice

The UK frame is the same — the record isn't

Everything HMRC asks of a perp trader on Hyperliquid applies on Lighter: disposals default to Capital Gains Tax (with 'financial trading' as the income-tax boundary your volume may cross), every position close needs its date, proceeds and matched acquisition, and every figure needs a GBP value at transaction time. The April 6 → April 5 tax year still matches no calendar export.

What's different is the account structure underneath. Lighter accounts are identified by an account index — and a single L1 address can own several of them (master account plus sub-accounts). That changes what 'your record' even means.

Pooling is per person, not per account index

HMRC's share pooling — same-day rule, 30-day 'bed and breakfast' rule, then the s.104 pool — attaches to you, the taxpayer, not to a venue account. If you accumulate a token position on index 764924 and dispose of the same token on index 812233, those events pool together. The s.104 average cost is computed across your whole identity, not within each index.

This is the trap in treating each sub-account as its own book: the 30-day rule in particular re-anchors a disposal to an acquisition that happened on a different index entirely. A report built index-by-index will silently misstate pooled costs — the indexes have to be merged into one identity first, then pooled.

Aggregation has a second edge: account indexes are only discoverable through the owning L1 address. A complete identity starts from the address, resolves every index under it, and rebuilds each one's fills — including indexes you forgot existed.

Zero-fee doesn't mean zero basis effect

Lighter's retail taker fills carry no fee — there's no maker-rebate stream to net off either. But 'no fee' isn't universal: integrator and collector-role fees exist, and wherever a fee is actually paid it adjusts the disposal's proceeds or the acquisition's cost like any other dealing expense. The sign convention matters: on venues with rebates the fee column can be income; here it is pure cost when present.

Funding is the other UK-relevant stream. Lighter accrues funding hourly and the venue's own record exposes it through the funding index sampled at each fill — a reconstructed hourly series, labelled as such. Whether funding receipts are income or adjustments to dealing costs is a classification question for your adviser; what isn't optional is having the per-market totals in front of them.

Positions can appear without a trade

Lighter positions don't always originate in the public trades dataset. Accounts can hold positions established through non-trade flows — internal claims and transfers between accounts — and the venue's own fill records then carry a position_size_before and entry_quote for a position no trade created. On a real account we've verified: eight markets whose first recorded fill showed an existing position with a venue-attested entry price, and zero earlier trades anywhere in the dataset.

For HMRC that kind of position still needs an acquisition story. A transferred-in position carries the basis it had at its source — document where it came from (which account transferred it, at what cost), because the venue's entry_quote is an attestation, not independently verifiable evidence. Basisproof marks those lots as venue-attested rather than pretending the cost was independently recomputed.

L1 deposits and withdrawals aren't disposals

Collateral moves on and off Lighter through the zkLighter contract on Ethereum mainnet — deposits credit your account index, withdrawals pay USDC back to your L1 address. Neither is a disposal: you're moving your own asset to your own control. But each is exactly the kind of record HMRC asks for when an exchange flow appears in their data — keep the tx hashes matched to the credit/debit events.

Transfers between account indexes you own are the same: not disposals, but they need to be on record or a balance sheet won't reconcile. The harder case is a position transfer between accounts — see the section above.

The April 5 problem, unchanged

The UK tax year runs 6 April to 5 April and every figure needs a GBP value at transaction time. Lighter's trading API serves a rolling recent window — the deep history lives in the venue's own published parquet dataset and L1 events, which is what a correct record has to be built from. Where the venue's data runs out, the honest answer is 'unknown', not an interpolation.

What works: a complete fill-level record merged across your account indexes, filtered to your April window, pooling applied per token across the merged identity — same-day, 30-day and s.104 legs, each disposal row naming the rule that covered it.

Common questions

?Does HMRC know about my Lighter trading?

Lighter itself reports nothing — it's a zk-rollup venue with no KYC. But HMRC receives exchange data under CARF, and every L1 deposit or withdrawal to the zkLighter contract is permanent public on-chain record. The self-reporting duty is yours regardless.

?Do my Lighter sub-accounts pool separately?

No — HMRC pooling is per taxpayer. Fills across every account index under your L1 address merge into one identity before same-day, 30-day and s.104 rules apply. Per-index pooling understates or overstates the 30-day matches.

?Are Lighter point airdrops taxable?

HMRC treats airdrops as income when you have dominion and control — typically at claim, not at points accrual. Points themselves aren't property. The judgement call is yours and your adviser's; what you need on file is the claim date, amount and GBP value.

?Is a deposit to zkLighter a taxable event?

Moving your own USDC to your own collateral account isn't a disposal. Keep the L1 tx hash matched to the account-index credit anyway — it's the cleanest evidence if HMRC later asks what the flow was.

Sources & method

Verify your own record first — free

Paste your account index or L1 address and the check replays every fill through the position chain, reconciles the terminal account value, and scans L1 for the flows the trading API never reports.

Run the free Lighter check