Hi, This is a very fascinating open source which is solving a real problem. I am bit lost in certificate verification flow.
- recipient sends his Public key through wallet to Issuer.
- Issuer uses that key to create the hash of the certificate and reciept
- Issuer put all these hashes into a merkle and only the merkle hash is getting recorded in the Bitcoin/Ethereum.
- Issuer saves the certificate at some URL and sends that url to recipient. Does the last part of url contain the public key or some random generated url?
- Recipient can send the URL to employer/some third party.
This is where I am lost too.
Whoever is verying can see only the Merkle root hash but how does he/she find the hash of the certificate?
Any clarification is much appreciated.