Wrapped Crypto Tax UK: WETH, wstETH, rETH & cbETH

Wrapping tokens is one of those operations that sounds like it should be straightforward from a tax perspective. You had ETH, now you have WETH. Same thing, different wrapper. Not taxable, right?

Sometimes. But not always. And the distinction matters more than most people realise, because getting it wrong doesn't just affect one transaction. It can distort the Section 104 pool for that asset and affect later disposal working.

The wrapping question is one of the genuinely unsettled areas of crypto tax, and automation needs an explicit stance. A blanket rule may treat every wrap as a swap, generating phantom gains on large ETH positions. Others treat everything as a transfer, missing genuine disposals when you acquire yield-bearing tokens like rETH or cbETH. Both approaches can be wrong.

The actual answer depends on what the wrapped token does.

ChainTax's direct ETH and WETH basis-carry treatment

ETH and WETH are economically identical. WETH is simply ETH inside an ERC-20 wrapper, redeemable 1:1, at any time, with no fee beyond gas. The wrapper exists because many DeFi protocols and smart contracts require ERC-20 tokens and can't handle native ETH directly.

You probably wrap ETH more often than you think. Many DEX routers do it automatically inside swaps. If you trade native ETH for USDC on Uniswap, the router wraps your ETH to WETH as the first step, then routes the swap. You never see the WETH. It happens inside the transaction.

HMRC CRYPTO22100 says a disposal does not occur where beneficial ownership is retained. HMRC does not publish a WETH-specific rule, so ChainTax applies that general principle to a direct decoded wrap where the same person retains ownership and economic exposure.

We classify both verified directions as Transfer with cost basis preserved. This is a disclosed product treatment, and the evidence still matters.

The common mistake here is tools that see "ETH out, WETH in" and record a swap. If you wrapped 50 ETH when the price was £2,500, that's a £125,000 "disposal" creating a phantom gain against your original cost basis. At 24% CGT, the consequences are severe.

wstETH: basis carry needs both legs and the actual rate

Lido's wstETH (wrapped staked ETH) is more interesting. When you wrap stETH into wstETH, the exchange rate is not 1:1. One wstETH is worth more than one stETH, and the ratio increases over time as staking rewards accrue. This is by design: wstETH is a non-rebasing wrapper around stETH that captures yield through price appreciation rather than balance changes.

The non-1:1 ratio does not decide the tax treatment by itself. ChainTax applies basis carry only where the decoded stETH and wstETH legs support preserved economic rights, and records the actual conversion rate. Missing legs remain a review risk.

For that supported pattern, ChainTax uses Transfertreatment and carries cost basis.

But here's where people get confused: the step before the wrap has completely different tax treatment.

ETH → stETH and stETH → wstETH need different evidence

When a Lido deposit returns stETH, the receipt token has rights and mechanics that differ from native ETH: it rebases, reflects staking returns, and trades separately. ChainTax currently applies disclosed disposal treatment to that supported exchange. HMRC CRYPTO61620 still requires the beneficial ownership and arrangement to be examined.

A later fully decoded stETH to wstETH wrap uses the separate basis-carry treatment described above when the economic rights are preserved.

Two steps, two disclosed product treatments. ChainTax classifies the supported ETH → stETH exchange as Disposal and a verified stETH → wstETH wrap as Transfer, while incomplete evidence remains reviewable.

rETH and cbETH: ChainTax applies disposal treatment

Rocket Pool's rETH and Coinbase's cbETH look similar to wstETH on the surface, since they're all liquid staking tokens that appreciate against ETH. Their protocol and market evidence supports a different product treatment from a direct technical wrap.

rETH is its own token with its own market price and protocol claim. ChainTax currently treats a supported ETH to rETH exchange as a disposal and acquisition. The underlying tax result still depends on the rights and beneficial ownership transferred.

ChainTax applies the same disclosed disposal treatment to a supported ETH to cbETH exchange because cbETH has separate rights, pricing, and market evidence.

We classify ETH → rETH and ETH → cbETH as Disposal. A reverse sale or swap is analysed separately.

The evidence: representation change vs token exchange

The on-chain mechanics help establish those facts. A direct WETH wrap is redeemable 1:1, while receipt-token exchanges can create different contractual rights and market exposure. The labels alone are not conclusive.

Appreciation in rETH/cbETH isn't taxed until you sell

One more thing that trips people up. If you bought rETH at 1.05 ETH/rETH and it's now worth 1.12 ETH/rETH, that appreciation is not a taxable event in itself. There's no disposal, no crystallisation of gain. It's unrealised.

The gain is only realised when you sell or swap the rETH. At that point, the difference between your disposal proceeds and your original cost basis (what you paid in ETH terms, converted to GBP at acquisition date) is your chargeable gain. This is different from stETH, where the daily rebase could be argued as income received on each rebase event. See our guide on reporting staking rewards to HMRC for how that works.

Quick reference: wrapped token tax treatment

Redemption ratio is useful evidence, not a complete rule. Check asset rights, beneficial ownership, the actual contract call, and both economic legs before applying either treatment.

Why wrapped-token classification can go wrong

The fundamental problem is the same one that causes bridge misclassification: a flow-only classifier looks at token movements, not transaction intent. It sees tokens leave your wallet and different tokens arrive. That pattern looks identical whether ChainTax's direct-wrap basis-carry treatment or receipt-token disposal treatment is appropriate.

Without understanding which contracts are involved and what the method signatures mean, a tool cannot distinguish between these operations. So it guesses. And for someone with a large ETH position who wraps and unwraps regularly as part of DeFi activity, those guesses compound into significant errors across a tax year. A UK crypto tax calculator that reads contract addresses and method signatures (rather than just token flow) has better evidence for making that distinction.

Check how your wrapping transactions are classified

If you've been wrapping and unwrapping ETH, staking with Lido, or holding rETH or cbETH, it's worth checking how your current tax tool handles these. Look for phantom disposals on WETH wraps and missing disposals on rETH/cbETH acquisitions. Both create errors that propagate through your Section 104 pool.

You can paste any transaction hash into the free transaction explainer to see exactly how ChainTax classifies it: the protocol, the classification, and the reasoning behind it.

For related edge cases, compare this with our guides to bridge transfers and Aave lending and borrowing, where the same beneficial-ownership question often drives the tax answer.