A proposal landed on HMRC's desk this week. Stani Kulechov, founder of Aave, wants stablecoins — and the yield they generate when lent out — treated as eligible assets inside a UK Individual Savings Account.
That's it. No code. No protocol upgrade. No TVL milestone. Just a document and a signature.
And yet it's the most interesting thing I've read all month. Because it's the first time a top-three DeFi lending protocol has publicly asked a tax authority to reclassify on-chain lending as ordinary savings behavior. Not as a security. Not as a derivative. As savings.
I've been tracking DeFi's regulatory crawl since the 2020 summer, when I was writing yield-farming breakdowns at 3 a.m. and none of us imagined a founder would ever volunteer for tax paperwork. Speed is the only currency that matters — but this is a slow-moving trade, and the people pricing it are reading it wrong.
Let me slow down and explain the machinery.
An ISA is a tax wrapper. You put cash, stocks, funds, or certain bonds inside it. Whatever interest, dividends, or capital gains you generate stays untaxed. There's an annual contribution cap, and several million adults in the UK hold one. For most households it is the single most tax-efficient place to park money, and the reason is simple: the wrapper is boring, and the tax code treats it as sanctioned.
Stablecoins are not on the eligible list. Not because anyone banned them — because the list was written before they existed in meaningful form. That is the whole fight. Aave is asking HMRC to add a new category of qualifying asset.
HMRC is the tax authority. That detail matters more than most coverage admits. Tax authorities decide how something gets taxed. They generally do not decide what a regulated savings account may hold. That's a job for the Treasury, and often the FCA sits in the chain too. So a proposal addressed to HMRC is a proposal addressed to one node of a multi-node gate.
Aave's business case is clear enough. Crypto-backed loans and stablecoin lending are two of its oldest revenue lines. If British ISA capital could legally earn lending yield inside the wrapper, Aave would be bidding against cash ISAs, index funds, and gilts. That's a real retail pool. That's the prize Kulechov is pointing at when he says millions of ISA users could benefit.
Now the hard part. Five things have to go right, and they are sequenced, not parallel.
First: the eligible-asset list has to be expanded by someone who doesn't run HMRC. An ISA manager — a bank, a platform, a broker — decides what it will administer. HMRC decides whether the tax relief survives. The Treasury writes the list. So the proposal needs at least three desks to agree, and they do not share a calendar. Watching UK crypto policy from the exchange side during the 2024 ETF cycle taught me the gap between "a regulator says something positive" and "a rule is in force" is usually measured in years, not quarters. I watched SEC filings get translated into threads in under an hour. I watched the same clarity take eighteen months to arrive in rule text.
Second: yield has to be characterized. ISA relief covers interest, dividends, and capital gains. Stablecoin lending yield is none of these cleanly. It is closer to interest — but interest from whom? A smart contract? A pool? A DAO treasury? Each answer produces a different tax line, and the wrong line flips the whole thing from "tax-free" to "reportable income." The proposal's real payload isn't inclusion — it's the tax characterization that rides along with it. If HMRC rules that lending yield is taxable income regardless of the wrapper, the wrapper stops mattering and the pitch evaporates.
Third: custody has to map to an account shell. An ISA has an account holder, an account manager, and a nominee structure where assets sit legally detached from the user. Aave is a permissionless protocol. There is no nominee. There is no manager. There is a user, a wallet, and a smart contract. To fit stablecoins inside an ISA you need a compliant wrapper — a custodian or a managed structure — between the user and the pool. The moment you insert that wrapper, you have rebuilt the intermediary DeFi was designed to delete.
Fourth: the KYC paradox. ISA accounts are named, verified, and reported. That is non-negotiable. So any stablecoin held inside one is KYC'd by construction. Fine for a user chasing tax relief. But it means the retail flow entering through the ISA door is not the permissionless flow Aave's architecture assumes. It is a permissioned slice riding on permissionless rails. Hybrids are where most DeFi-compliance attempts quietly die — not because regulators say no, but because the product becomes a worse version of a bank deposit.
Fifth: cross-agency silence. The worst outcome for a proposal like this isn't rejection. It's no answer at all. A quiet HMRC means the narrative has nothing to anchor to and the market has nothing to price. In sideways conditions, that is the default outcome for policy pitches — filed, reviewed, shelved.
Here is where I want to plant a flag. Stablecoin lending inside an ISA is not a technical problem. I can sketch the account structure on a whiteboard: a custodian holds USDC, the user signs a delegation, the protocol earns yield, the custodian reports to HMRC, the wrapper handles the tax envelope. Every piece already exists. The bottleneck is purely legal characterization. That's worth saying out loud, because this sector keeps blaming engineering for problems that are actually about definitions.
And the definitional fight is not neutral. If the UK decides lending yield is ordinary interest, Aave gets a distribution channel no high-street bank can match on rate. If the UK decides it is something else, the entire DeFi-to-retail thesis has to route through fund wrappers, and the cost base eats the advantage before the first pound arrives.
Everyone is reading this as a UK story. I don't think it is.
Look at the sequencing. Hong Kong spent two years building a licensing regime that reads less like openness and more like a bid to take Singapore's chair at the Asia finance table. The EU locked MiCA into place. The US is still arguing with itself. Every major jurisdiction is now competing to define what "compliant digital asset" means, and the first mover on retail tax treatment sets the template everyone else copies.
So when Aave's founder files with HMRC, the audience isn't only HMRC. It's every finance ministry watching how a mainstream tax authority handles the question. A favourable UK treatment becomes the reference document for a dozen follow-on jurisdictions. A rejection becomes the excuse every other regulator uses to say, quietly, that even the UK said no.
That reframes the risk. This isn't a product launch. It's a precedent bid, and precedents are won on framing, not features. The proposal's strongest asset is that it asks for something boring: tax neutrality on savings yield. Not token listings. Not derivatives. Not leverage. Boring asks are the ones that survive contact with civil servants.
There's a second angle the coverage is missing. Aave doesn't need ISA money to grow. Aave needs a regulatory moat. Layer2 fragmentation has spread the same small user base across dozens of chains, and lending liquidity has been sliced along with it. Compliance, done early, is one of the few moats that doesn't get copied in a week. If Aave is the protocol sitting inside the UK's tax wrapper, that is a distribution position competitors cannot fork.
Watch three signals. Does HMRC respond publicly within a quarter — silence is the bear case. Does the Treasury or the FCA issue anything parallel, because a solo HMRC filing is a dead end. And does Aave's stablecoin lending volume on Ethereum show any UK-correlated bump, which would tell you whether retail actually cares.
Surviving the winter to plant for spring. This is a seed, not a harvest. Live from the edge of the unknown — where the paperwork is the alpha.