That merkle tree selective disclosure is interesting, but in that case where the data would be stored? In some issuer’s (e.g. IOG) server or on the chain (very unlikely and highly not recommended)?
Whether selective disclosure or not, the data can’t be stored on-chain due to privacy reasons, it is generally driven from a peer to another peer by sending end to end encrypted messages through a middle server.
Institutions have a specific web app where they store the data from people, as well as the credentials they issue/receive, such web app should run on the institution’s infrastructure, and they are in charge of protecting such information.
When a credential is shared to the mobile apps, the app keeps it locally, so that it can share it later with other peers/institutions.
Sorry for being to pushy, but how did doc from a DID resolution would work ? Similar to Bitcoin?
For the first stage, we’d have a separate service that allows resolving our DIDs, the goal is to eventually get our DID Method registered so that it can be resolved from the universal-resolved from DIF.
It is not really related to Bitcoin, while it was supported initially, we haven’t actively worked on that for months, and are fully focused on Cardano.
Because, you mentioned that it was initially built on top of the Bitcoin, that means, afaik, that the
method specific id of the DID contains a bitcoin transaction details, and that tx’s input (UtxO is the public key) of the DID doc, and it’s resolved by some URL embedded in one of the some tx’s output as metadata.
While this is a possibility, all the data related to the Prism protocol doesn’t depend on the underlying ledger, hence, it doesn’t matter which address posted the Prism data, we just take data and process the keys that came there.
And that metadata contains some URL or similar to a service for resolving the DID doc.
There are no URLs (or service endpoints) involved, yet, those will likely be required when registering our DID method.