Hey @Ravenith, thanks for putting the LLM to the task. That’s a lot to read though, but I made it. I think a succinct version is:
Internet Identity: ICP Skills
II derives a principal per origin, so
https://<canister-id>.icp.netandhttps://shop.example.comare two different users to the same person. To keep one account per person, pick one origin as the derivation origin and list the others as alternative origins.Pick the canister address as the derivation origin. Custom domains can be changed or dropped; the canister address cannot.
Canister control | ICP Developer Docs
Dapps are commonly reachable over their own custom domain name instead of icp.net. These domains are registered with a DNS registrar by one of the developers. The developer can choose to have this domain point at a completely different web application, even one not hosted on ICP. Users will trust this domain and the app it serves. This could allow such a developer to steal funds, leak data, etc.
users are doing this all over the IC without actually understanding the situation
Ultimately this isn’t answering my question and it isn’t a solution to the questions I’m asking.
Most users don’t understand that practically all dapps they ever log into on the IC are leaving them trusting some random bloke who has so far decided not to (we suppose) extract funds from their wallets on that dapp. Why don’t they know? This attack vector isn’t just a dev concern - first and foremost it’s a user’s concern. Why are we as a community standing for this gap between reality and belief? Instead disinformation is being disseminated to users even via official channels.
Further, the canonical ‘https://.icp.net’ URL isn’t a silver bullet, it’s just another domain that someone else manages. Who is that person? Does anybody know?
Even with the canonical URL as the origin that pins a user’s principal, use of any other custom domain still leaves the users highly vulnerable under that session. They’re also vulnerable in any case, which is not what they expect, because it’s not what the ‘collective consciousness’ claims that ICP delivers.
The solution
The solution has always been decentralised DNS, which is a big undertaking, but the NNS recognised the need almost 5 years ago. We’ve come a long way since then and there has been much work on the matter, but progress and comms went dead about a year ago and questions are going ignored.
This is not what we as a community deserve for having facilitated this R&D, and if it’s not obvious, I’m disatisfied with the current status quo (even angry) and I would like some proper communication on the matter from DFINITY.
I gather the initiative has been de-prioritised - but I suspect that if someone with an audience made this common knowledge it would become the priority again pretty quickly.
Can we get ahead of that please someone in DFINITY who can clarify the current situation with regards to the Chain Name System (CNS)?
In addition, I’d like to understand the current security setup better given that I use the NNS dapp for holding numerous assets: