W3C home > Mailing lists > Public > public-credentials@w3.org > December 2021

Re: [EXTERNAL] RE: Blockcerts v3 release, a Verifiable Credentials implementation

From: Julien Fraichot <Julien.Fraichot@hyland.com>
Date: Tue, 14 Dec 2021 12:49:51 +0000
To: Nikos Fotiou <fotiou@aueb.gr>, "'W3C Credentials CG (Public List)'" <public-credentials@w3.org>
Message-ID: <SA1PR13MB56360EDD64B18ECA75A3318090759@SA1PR13MB5636.namprd13.prod.outlook.com>
Hi Nikos,

Thanks for your email and interest.


  *   We use the display property for the wallet, but also for the standalone web component (blockcerts-verifier) that issuers may host to facilitate access to the visual layer and verification of the credential. If you are talking at Blockcerts level, we have a schema that defines the expected format of the data. If you are talking at VC level, to my knowledge there is none. I know Open Badges are also working towards aligning with VC and there is some work done to meet at common ground with EDCI. I think though you are right, in the greater scheme of things it’d be interesting if that property were to be standardized across VC implementations.
  *   You are correct, MerkleProof2019 (and the Merkle Root) allows issuers of Blockcerts to issue a batch of credentials and optimize the cost of the transaction. We don’t do selective disclosure nor zkp at this moment but it’s something I would personally like to explore for Blockcerts as part of the recipient experience improvement.

Best,

From: Nikos Fotiou <fotiou@aueb.gr>
Date: Monday, 13 December 2021 at 21:09
To: Julien Fraichot <Julien.Fraichot@hyland.com>, 'W3C Credentials CG (Public List)' <public-credentials@w3.org>
Subject: [EXTERNAL] RE: Blockcerts v3 release, a Verifiable Credentials implementation
CAUTION: This email originated from outside of Hyland. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Julien,
Super interesting work. I have two questions.
- I see that in your context you are defining a “display” property. I guess this property is used for displaying some visual information about the VC in the wallet. I am wondering if there is any standard way for providing such information, or may be any ongoing draft.
- AFAIU you are using MerkleProof2019 to cover with a single Merkle tree root multiple VCs and not for implementing selective disclosure. Is that correct?

Best,
Nikos

From: Julien Fraichot <Julien.Fraichot@hyland.com>
Sent: Monday, December 13, 2021 1:53 PM
To: W3C Credentials CG (Public List) <public-credentials@w3.org>
Subject: Blockcerts v3 release, a Verifiable Credentials implementation

Hi CCG community,

I am excited to share with you today the release of Blockcerts [blockcerts.org]<https://urldefense.com/v3/__https:/www.blockcerts.org/__;!!C8mu0vCj!Jn4eX9uVLgxusyjB_OCTqeSsp1nAdlVjlgxTDiLUrLTRWIYJBy52X97Gt8XmjC1DyDfJ$> V3. As you may already know the earlier versions of Blockcerts were architected by Kim H. Duffy through Learning Machine and leveraged the Open Badge standard.
We have followed through with the initial ideas established at RWOT 9 [github.com]<https://urldefense.com/v3/__https:/github.com/WebOfTrustInfo/rwot9-prague/blob/master/final-documents/BlockcertsV3.md__;!!C8mu0vCj!Jn4eX9uVLgxusyjB_OCTqeSsp1nAdlVjlgxTDiLUrLTRWIYJBy52X97Gt8XmjITcC2Tz$> in Prague in December 2019, to align Blockcerts with the Verifiable Credential specification.

Furthermore this initial version includes support for Issuer’s DIDs. In practice we leverage the Verification Method to cryptographically prove that the issuing address matches the public key of the issuer.
As in earlier versions, we offer a display layer to the credentials, which beyond the original HTML capabilities now support images and pdf documents. The signature suite still relies on the blockchain anchoring of the hash of the document and merkle root of the issuance, now with MerkleProof2019 [w3c-ccg.github.io]<https://urldefense.com/v3/__https:/w3c-ccg.github.io/lds-merkle-proof-2019/__;!!C8mu0vCj!Jn4eX9uVLgxusyjB_OCTqeSsp1nAdlVjlgxTDiLUrLTRWIYJBy52X97Gt8XmjGF1xV0U$>.

In the future, we want to explore solutions to reinforce the trust layer with the DID ownership, improve the recipient experience in handling and sharing their certificates as well as allow for the recipient DID to be included in the process.

We would like to thank everyone in the community who directly and indirectly supported the release of this milestone in Blockcerts life, but as well we hope in the whole SSI ecosystem.

You may issue certificates through cert-issuer [github.com]<https://urldefense.com/v3/__https:/github.com/blockchain-certificates/cert-issuer__;!!C8mu0vCj!Jn4eX9uVLgxusyjB_OCTqeSsp1nAdlVjlgxTDiLUrLTRWIYJBy52X97Gt8XmjAYSv9uK$> and verify them with cert-verifier-js [github.com]<https://urldefense.com/v3/__https:/github.com/blockchain-certificates/cert-verifier-js__;!!C8mu0vCj!Jn4eX9uVLgxusyjB_OCTqeSsp1nAdlVjlgxTDiLUrLTRWIYJBy52X97Gt8XmjJVBftpB$> (both in the browser or the server) or use the visual web component blockcerts-verifier [github.com]<https://urldefense.com/v3/__https:/github.com/blockchain-certificates/blockcerts-verifier__;!!C8mu0vCj!Jn4eX9uVLgxusyjB_OCTqeSsp1nAdlVjlgxTDiLUrLTRWIYJBy52X97Gt8XmjAThUAnD$>.
As always, we do our best to tend to questions on the Blockcerts forum [community.blockcerts.org]<https://urldefense.com/v3/__https:/community.blockcerts.org/__;!!C8mu0vCj!Jn4eX9uVLgxusyjB_OCTqeSsp1nAdlVjlgxTDiLUrLTRWIYJBy52X97Gt8XmjKkJfpTb$> and welcome everyone in participating.

Best,

--

Julien Fraichot
Developer 4 – Hyland Trusted Documents

----------------------------------------- Please consider the environment before printing this e-mail -----------------------------------------

CONFIDENTIALITY NOTICE: This message and any attached documents may contain confidential information from Hyland Software, Inc. The information is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or an employee or agent responsible for the delivery of this message to the intended recipient, the reader is hereby notified that any dissemination, distribution or copying of this message or of any attached documents, or the taking of any action or omission to take any action in reliance on the contents of this message or of any attached documents, is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail or telephone, at +1 (440) 788-5000, and delete the original message immediately. Thank you.

-----------------------------------------  Please consider the environment before printing this e-mail -----------------------------------------  

CONFIDENTIALITY NOTICE: This message and any attached documents may contain confidential information from Hyland Software, Inc. The information is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or an employee or agent responsible for the delivery of this message to the intended recipient, the reader is hereby notified that any dissemination, distribution or copying of this message or of any attached documents, or the taking of any action or omission to take any action in reliance on the contents of this message or of any attached documents, is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail or telephone, at +1 (440) 788-5000, and delete the original message immediately. Thank you.
Received on Tuesday, 14 December 2021 12:50:24 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:25:25 UTC