Petur: Hi, I have just tried to reimport all transactions. Some were correctly handed as Uniswap LP transactions, but some look like they were imported as normal withdrawals. Is there any way to tag them as Uniswap liquidity in?

Tremendous Mole: Would it be possible for you to share a link to this transaction on the explorer, or a transaction hash?

The only case we know of where this could happen, is if the token you are dealing with has no pricing data.

Petur: These for example:

{}

There are many more. This one seems one that was correctly imported:

{}

But maybe something went wrong with my wallets? Because the wallet page is saying that the "API does not allow access to: Uniswap v3 liquidity." Even though I deleted the old wallet, some transactions (like permanently deleted ones) look like they were there from the previous wallet. Some of those that have the new LP Uniswap are tagged as csv.

Petur: Hi Peter.. where do we post bug reports? It detects Liquidity In and Liquidity Out for some of the entries, but others don't work and are detected as normal "Send" transactions. I deleted my wallet, and did a full import. Some detect, some don't. I think maybe because when you do liquidity with Uniswap V3 the transactions don't always follow the same pattern - so maybe there is an edge case that has not been handled yet.

Familiar Dove:

Hi JMP,

This thread is the best place to report any issues but you can also create a new Canny ticket if you prefer.

Would you be able to share a transaction hash (or explorer link) to one of the transactions that is not working? We should be able to address all issues quite quickly

Tremendous Mole:

Thank you for the details!

I've had a look and created a ticket for the developer. It should be fixed quite soon but I'll let you know :)

Tremendous Mole Familiar Dove

The issues discovered earlier have been fixed!

You can try clicking on 'Restart gains' in your settings to see if the transactions now get processed correctly. Please let me know if they don't

Petur: most of them autodetect now, but there are still others with issues (2 that i've found). 1. I've attached an image of a scenario that does not detect. It properly detects liquidity in of the two tokens, but because one of the tokens went to 0 during the interval, when you pull the liquidity it does not detect it as liquidity out. only one token comes out in the transaction because the other token has gone to 0 in the pool. koinly detects incorrectly as an exchange. 2. the opposite scenario also does not detect correctly, when you place the liquidity and you provide 0 of one of the coins, koinly detects it as an exchange instead of liquidity in.

Familiar Dove:

Hi JMP,

Yes, this is a known thing actually. Koinly's 'Liquidity' labels will only be applied when there are two assets coming or leaving the pool. When there is only one asset, it will just show as an exchange.

We're looking at improving this now but it doesn't have much of an effect, since these transactions are taxed the same way (ie. it's just useful for filtering really)

Petur: thanks a lot to all of you! I have tested it on arb and am very happy with the result.

100% regonition and the Single value exchange for lp token is actually how I manually dealt with this as well eg when zapping for v2 in the past. The nft no value deposit is a bit annoying but I guess we need it as uniswap is indeed spamming all of us with this nfts... Lol

Do you have plans to bring it to pancakeswap v3 on bcs chain? (it's using uniswap v3 code as well). Unfortunately that's where my main focus lies.

Cheers

Petur: I want to delete the individual transactions manually and re-sync (deleting the wallet would be painful given the amount of work done already on corrections), however I wonder if there is a way to search by contract?

I.e. 0xc36442b4a4522e871399cd717abdd847ab11fe88 is the Uniswap V3 contract given as Interacted With (To) in Koinly.

Ideally I want to surface just all the interactions with UniV3 to Perm Delete and then re-sync those wallets. This would be quicker than scanning for all Send / Deposits and opening the Tx in Etherscan to check it's related to a UniV3 position.

Magenta Horse: There is an advanced filter called "TxSrc" and another one called "TxDest". You can create a filter for all transactions where TxDest or TxSrc is equal to this contract address, and that should show all of these transactions.

However, we did find that there are some transactions where the main UNIv3 contract is not the TxDest, so this may not catch all transactions.

You should also look for all UNIv3 NFTs that you have received and delete those

Zinc white Chameleon:

Yes, we are planning to add support for Pancake as well, but I don't have an ETA for that atm

Petur: Thanks for pointing out the NFTs as well.

That means that for every LP position you have to delete the Send Tx and also check Etherscan for the corresponding ERC-721 token ID to find and delete that too, before re-syncing.

Petur: Hello Petur, I found a bug if stable coins are involved (at least on arbitrum chain for example usdc/eth). He fails to see the reward of the stable coin, so he trades the portion of the LP back into the correct stable amount + its rewards. However posting screenshots without doxxing myself is something i would fuck up for sure. If you are interested please tell me how to send you a txhash. Probably you can reproduce it easily tho yourself, dunno.

regards

Zinc white Chameleon:

Hi Nope,

In order to check this, I would need a transaction hash or explorer link.

You can post it here in the comment (and I'll remove it as soon as I've seen it) or you can send it to support@koinly.io and say that it's for Petur :)