Identity processes and architecture

[linear]

https://docs.google.com/document/d/1YSiYc02fgrI0HsoDl01jv1jzQIGxDgP0XodV79gvR2k/edit?tab=t.yuevlygt48r6#heading=h.33geuns5ja7b

https://concordium.slack.com/archives/C014NBY1QSD/p1743081664716619

So to be clear:  There's two layers to the ID layer stack.

1. ConcordiumID (or the base/core ID): this is the protocol-level system that is a prerequisite for any user to have an active account on Concordium. This makes it possible to do zk-proofs on attributes like age or citizenship
2. The "Web3ID" suite (sometimes called portable ID): this is a system for issuing and managing Verifiable Credentials. It can use ConcordiumID, but doesn't have to.

The MVP version of  standalone ID wallet only focuses on ConcordiumID
we will most likely NOT use Web3ID/Verifiable Credentials to connect to Safle or other 3rd party wallets. We would most likely use WalletConnect, as discussed in the call. (edited)