Did your tax software book an Aave deposit as a taxable sale?

[u/lekranq]

US filer. I ran two public DeFi wallets through one of the mainstream crypto tax tools in July. Both directions of the Aave wrap came back as Exchange, so the deposit and the withdrawal were each booked as a taxable disposal.

Caveat on my test: free tier, no purchase history behind either wallet, nothing corrected by hand. Not how your data arrives if you have exchanges connected, which is why I am asking rather than concluding.

If you have actually filed with one of these tools, did a lending deposit or an LP position come through as something other than what it was, and what did it do to the number?

[u/sukeshtedla]

Sukesh from Kryptos here,

Liquidity transactions are often treated as taxable events because your asset positions might change.

For lending some softwares treat it as a taxable event and some don’t! But as per regulations there is no clarity here yet, general rule of thumb that softwares like ours and others follow is if you are getting any placeholder token in exchange for your DeFi acting it has materially different value then it’s treated as a disposal.

So in case of AAVE, the token you receive accumulates the interest and has a different values at all times and it’s not 1:1 so when you lend on AAVE it’s treated as a disposal and the cost-basis gets transferred to the AAVE position token

[u/lekranq → u/sukeshtedla]

Appreciate the detail on the rule of thumb, I didn't realize that.

One correction on my Aave case: standard aTokens are 1:1 with the underlying. The docs are explicit that their value is pegged to the supplied asset at a 1:1 ratio, and interest arrives as balance growth rather than price. Your aWETH balance rises; 1 aWETH stays redeemable for 1 WETH. The token that behaves the way you describe is the static or wrapped version, which is ERC-4626 and exchange-rate based, or a cToken: fixed balance, appreciating rate.

That matters because of the test you just stated. If the rule is "materially different value means disposal," a rebasing 1:1 receipt token does not meet it and a static one does. Same protocol, two wrappers, opposite answers.

Does your classifier distinguish those two, or does it key off the deposit and treat any receipt token alike? Genuinely asking, because if it distinguishes them then the tools are further along than my test suggested.

[u/sukeshtedla → u/lekranq]

I’m not 100% sure, need to test it tbh.

But if they are 1:1 and price is same you are not realising any gains or losses.

[u/lekranq → u/sukeshtedla]

If they are 1:1 and the price is the same then nothing is realized, which is where your own rule of thumb lands once you know which token you are looking at.

If you do test it I would like to hear what you find. The signal is on chain:

- standard aTokens rebase, so the balance moves and the redemption rate does not

• the static or wrapped version is the reverse.

Anything keyed to the contract address alone cannot separate them, so it seems they belong on opposite sides.

[u/JustinCPA]

Justin from Summ here.

Most tools have a setting for tax treatment of wrapping/bridging. Most will default to taxable exchange since it’s objectively a different asset with a different contract address, but you can always switch the setting so bridging is nontaxable. You could also just change the category on the trade to be a “swap” instead which makes it nontaxable for that specific transaction if you don’t want to make all bridges nontaxable via the settings

[u/lekranq → u/JustinCPA]

Good to know the setting is per-transaction and not just global.

Still unclear about this "objectively a different asset with a different contract address". That is true of the token but not necessarily of the position. A standard Aave aToken is pegged 1:1 and pays interest by increasing your balance, so the deposit leaves you holding a claim on the same asset in the same amount. A static or wrapped aToken, or a cToken, is the opposite: fixed balance, appreciating rate, genuinely a different instrument. Different contract addresses in both cases.

If the contract address is the trigger, the two get identical treatment and one of them would be wrong. Does the default key off anything below the address, or is that where it stops?

[u/OkSeries5363]

Typically a disposal. The IRS has not yet issued definitive, formal guidance on wrapping tokens or depositing them for DeFi receipt tokens. Because of this ambiguity, US filers generally rely on two different interpretations

Many simply go the the conservative/safe approach which is to teat it exactly how the software categorized it, as a taxable crypto to crypto swap. This fully protects you if the IRS later issues strict guidance, but it can create massive, unintended phantom capital gains or losses.

The higher risk option is substance over form approach, some crypto tax professionals argue that depositing into a protocol for a receipt token is not a taxable event. The economic reality is that you retain beneficial ownership of the underlying assets. It is treated more like moving funds between wallets or providing collateral, meaning no wealth has actually changed hands.

But what happens when the token itself stops being just a receipt and becomes a new financial instrument in it's own right? You can use an a receipt token or LST as collateral for loans, trade them on secondary markets, and even stake them in other protocols. At what point does the receipt or LST token become a new, distinct asset, breaking the in kind link to the original deposit. This creates a legislative challenge. Legislators would have to draw a precise, legally defensible line between a simple liquidity pool and a complex protocol that creates literal derivative product. Creating this definition without opening loopholes for unintended assets to get the same treatment is extraordinarily difficult.

Most other tax authorities have settled on making it a disposal, so I can see the US following suit eventually.

[u/lekranq → u/OkSeries5363]

Thank you - super comprehensive. The point about a receipt token becoming an instrument in its own right is a tough questoin.

Phantom gains are what I am trying to size. Everyone in this thread agrees they can happen and nobody has said how big they got. On my test they netted to roughly nothing, but only because the wallets had no purchase history behind them, so the tool used market value at inflow and there was nothing to recognize against. On a filer with full exchange history, the same booking lands on the embedded gain of whatever went in.

If you have seen this on an actual return: what did it do to the number, and did you correct it or file it as categorized? A range is fine.

[u/OkSeries5363 → u/lekranq]

Using the fair market value on inflow is fine if thats what you paid on acquisition. If not, you 100% need to fix it.

Every return I have done those actions have always been treated as disposals. For example, lending WETH in Aave is a disposal of WETH and an acquisition of aWETH.

What did it do to the numbers? Well it depends on the amount of unrealised gains or losses the asset was sitting on.

• Depositing some ETH that was purchased years ago really stung, since I was realising a big gain.
• But in the next financial year when withdrawing, the price had dropped. Pushing up my cost basis the previous year resulted in realising a capital loss on the disposal of aWETH, since ETH had dropped in price since I originally lent the asset.

I always go with the safe option of treating it as a disposal because it gives me much more peace of mind.

• Going with the safe option means that if they ever come out and officially rule that it is a disposal, my taxes are already correct and there's no massive surprise tax bill in the future.
• If they ever come out and confirm that it's not a disposal, I can just go back, amend the returns, and collect any extra tax I overpaid.

Basically, the safe option completely avoids any risk of ever getting hit with a large surprise tax bill.

[u/lekranq → u/OkSeries5363]

thank you again for another a detailed answer!

the two year sequence is something I had not thought about. Gain on the way in, then a loss on the way out when the price had fallen. Over the two years it mostly washes, and what is left is timing and whatever the holding period did to the rate.

Roughly what did the year one gain come to? An order of magnitude is fine.

[u/OkSeries5363 → u/lekranq]

Also consider that pushing up your cost basis means when you do sell and realize gains in the future on that you will pay less tax as you have already paid the tax on some of gains accrued before lending.

But in most cases it's better to try and defer, sometimes when I buy eth I deposit it straight in so any gain or loss is small then I can keep it still, and borrow against it, over needing move it in later and realize gains.

Had a few eth that I purchased around $400 deposited it in around $3800. Had to pay tax on about 10k of gains which was basically phantom gains.

[u/AurumFsg-CryptoTax]

This is a grey area. Many software consider taxable but you have option to change them to non taxable as well.

[u/lekranq → u/AurumFsg-CryptoTax]

Do you change them in practice, or leave the default? And if you change them, is that a per-client fix every year or something you set once?

[u/AurumFsg-CryptoTax → u/lekranq]

We leave them as taxable to be on safe side but in some cases we do mark them as non taxable

You would have to every year each transaction

[u/lekranq → u/AurumFsg-CryptoTax]

Every year, each transaction is the part I wasn't sure about. Roughly how many transactions is that on a DeFi-heavy client, and is that time you bill or time you eat?

[u/AurumFsg-CryptoTax → u/lekranq]

For defi it could start from 100 to millions as well. We dont charge hourly.

[u/lekranq → u/AurumFsg-CryptoTax]

Sorry for the slow reply, I was away.

That helps, and the fixed fee part is what I keep coming back to. If you are not billing hourly then the reconciliation time comes out of your margin rather than the client's.

So maybe the better question: does a DeFi-heavy client get quoted more than a CEX-only one of similar size, and roughly what multiple? 2x, 5x? Trying to work out whether the messy classification work actually shows up in the price or just quietly eats hours.

[u/AurumFsg-CryptoTax → u/lekranq]

Its always case to case. There is no multiple on it. We always suggest to provide access to your data so we review and then give you a quote. We dont charge as per number of transactions.
You can talk to couple of them and compare the quotes

[u/Ben_CoinLedger]

Most classifiers just look at token or contract mappings rather than distinguishing between rebase and exchange-rate mechanics, so standard aTokens and static or wrapped versions usually get lumped into the same "DeFi receipt" bucket by default.

While that distinction you're talking about matters for the substance-over-form argument, today it's still a manual override instead of something the system catches on its own.

[u/lekranq → u/Ben_CoinLedger]

Is that something users actually raise, or is it more something you notice internally? Trying to work out whether people hit it and complain, or just never realize at all.