search

GAIA-X4PLC-AAD / gx-credentials-old

TP 1: Create portable verified credentials on Tezos with public accounts.
https://tzprofiles.com
Apache License 2.0
1 stars 0 forks source link

VC Storage #13

Open boz1 opened 2 years ago

boz1 commented 2 years ago

Where should ASCS (or any other issuer) store the verifiable credentials? The initial idea is that vcs shouldn't be publicly available but be only provided upon valid request.

jdsika commented 1 year ago

I think the ASCS should store them but then we need to define under which circumstances they are provided. First of all the ASCS needs the record for itself. As long as there is no "service" to offer them to others we can avoid the discussion and tools in the ecosystem might accept a simple "proof of existince" from the ASCS that a public key hash belongs to a certain identity? Is that technically feasable or even useful?

boz1 commented 1 year ago

I think for now we can skip the discussions about under which circumstances ASCS provides a VC to a third party. For now, let's assume that every company (i.e., VC holder) always provides their VC to any party in ENVITED which requires it.

The question here is, where should ASCS store the VCs it issues? A Mongo DB instance could be one option as VCs are in JSON format.