Their response is utterly unhelpful. It seems they haven’t even read the issue or made any effort to identify the problem.
Jan 5, 2024, 14:22 EST
Thanks for contacting the DFINITY Support Team.
In order to best help troubleshoot your issue, Internet Identity ensures privacy by generating a unique pseudonym for each dapp whenever an anchor is used.
This prevents the dapp from tracking users across the various dapps they use.
This means that each dapp which you connect to has a unique wallet address. Assets are not transferred across dapps because dapps don’t share a common wallet.
Internet Identity ensures privacy by generating a unique pseudonym address for each dapp whenever an anchor is used. You would need to send the funds to the wallet address connected in the dapp.
"Internet Identity ensures privacy by generating a unique pseudonym address for each dapp whenever an anchor is used. You would need to send the funds to the wallet address connected in the dapp.
So, how do you explain the fact that in this situation, despite using a single Internet Identity, it has led us to a new address on ICPSwap?
Hi, to help more, I actually think following should be the right order of resolution steps:
1. user re-tries logins on original device as per my previous comment
it will be convenient to take some screenshots to collect evidence of which II is used and what are the resultant addresses for all login options
2. investigation with @ICPSwap - that is the DApp with which the user interacted
a lot was done already but possibly more can be conducted
like videocall with the user where the user is sharing and showing what all happened etc.
NOTE: if anyone has an issue with some app (e.g. Netflix), then seeks support from that app directly
this step is generic and not related to differences between Web2 and Web3
3. if @ICPSwap suspects that there is some glitch with Internet Identity generating a unique address they should reach out to DFINITY support with summary, logs and other evidence for further investigation
in this case, DFINITY is the last level of support, not starting from zero but building up on already collected findings
NOTE: if support team of some app (e.g. Netflix) suspects that there is a problem with underlying infrastructure, then this team seeks support from provider of the underlying infrastructure (e.g. AWS in case of Netflix)
this step is generic and not related to differences between Web2 and Web3
DISCLAIMER: I don’t have any knowledge of involved parties support options and SLAs, there can be also privacy concerns and other complications.
[quote=“plsak, post:69, topic:25876”]
glitch
[/quote
Thank you, at the start, we already sent video clip of logging in ICPSwap with original phone and sent to their technician. No help! It still goes to the new address!
I must share this until they can resolve this issue and my friend can regain access to her account. This situation is highly detrimental to their reputation. It also affects me negatively as I have invested heavily in ICP and tokens in IC ecosystem.
We have all the transaction records from Binance to the ICPSwap address. Besides that, what else do we need? All you have to do is set up an internet identity and connect to @ICPSwap, right? It’s quite simple. Even if you intentionally try to do something wrong, you won’t be able to. You try to put in the wrong seed phrase, it refuses anyway.
“Internet Identity ensures privacy by generating a unique pseudonym address for each dapp whenever an anchor is used.” So, the problem may be that there is a slippage of the anchor that links an internet identity to an address in ICPSwap. That is the only explanation I can think of.
I believe that if they genuinely want to fix the situation, they have the ability to do so. Currently, it seems they are placing the blame on me. Do you have any suggestions on how I can take legal action in this case?
A few days before this happened, ICPSwap was displaying incorrect token balances, particularly with SNS1. We had a sense that something was amiss, but we never anticipated it would escalate to such a severe extent.
I sincerely hope that the community takes notice of these incidents and that no one else loses money. In the case of my friend, it amounts to 650 ICP. If such an event were to happen to me with a significantly larger account, the consequences would be devastating.
They’re deliberately brushing me off, foolishly expecting the problem to vanish. But let’s be clear: the money we’ve lost is still ours, and that fact cannot be ignored.
This is really strange. They talk about so many great things but completely overlook this obvious and serious problem. Investors shouldn’t have to deal with such a stupid issue.
@peterparker, can a dApp receive different anchor associated with the same Internet Identity?
I assume that it can’t, and if that’s the case, then it’s not likely that the mistake is on the ICPSwap side and more likely that it’s on the user’s side.
I rushed through the topic and might have missed if it was already answered. If so, I apologize.