The sudden discontinuation of Internet Identity support by a dApp project raises serious concerns for users who had created their accounts and stored assets using this feature. It raises serious concerns about user account access and asset recovery.
Users who created accounts using this feature and stored their asset inside it, may find themselves unable to access their assets if the developers don’t respond.
It highlights the importance of decentralized solutions that ensure user ownership and control of their assets, even in the face of changes or disruptions in the project’s development.
Is there already way or method to solve this issue ?
I think that is simply a matter of the dapp showing some basic respect to the user, same as in web2. If I offer login via email, Google, and Facebook accounts and simply delete one method overnight, a lot of users will not be able to login anymore. Most projects won’t do that because it’ll cost them a lot of trust and users, but there’s not much one can do.
Absolutely. In web3 you can have solutions where the user owns their data and can access it independently from the dapp/frontend/service, but it has to be explicitly set up this way
It probably depends the architecture of the dapp, that’s an advantage of the IC. If the project creates a canister per user - e.g. in which the user’s data are saved - and let users assign additional controllers to these smart contract, then the main project disappearing does not mean the users lost their assets.
e.g. in my project Juno, the main app is “just” a facilitator, each user gets a personal canister to which they can add additional controllers. Likewise for other canisters they create. So if the main app would ever disappear (not the plan, just an example ), they would still have everything because they control their smart contracts, they own their data (https://juno.build/docs/architecture).
Papyrs, OpenChat, Hot or Not (I think) use that architecture. In Papyrs it’s not yet possible to add extra controllets but, if the project would ever been discontinued, I would offer such a feature first.
Wallet extensions like Metamask offer significant advantage for users, the ability to access assets with the same PID using other supported extension wallet with the same 12 seed phrases.
In contrast, this convenience is not available with Internet Identity, although I understand that the Internet Identity main purpose is to offer more privacy.
I agree with the idea of user independent wallet canisters that would provide greater control and privacy for users on dApps.
Would it be a good idea if this is enforced at ICP base protocol layer ? So it will become the standard of best practice for dApps that support Internet Identity.
Not sure you can enforce such an architecture on the ICP protocol layer (my two cents, might be wrong) but, there are some initiative from the community to implement this wider, e.g. the wApps (“Wallet Apps” I think) topic.