Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Which library to "play" with? #9

Open
lemoustachiste opened this issue Jan 4, 2023 · 2 comments
Open

Which library to "play" with? #9

lemoustachiste opened this issue Jan 4, 2023 · 2 comments

Comments

@lemoustachiste
Copy link

Hi @OR13,

I am interested in exploring how this selective disclosure approach works.

In my research I have come across different projects that seem related/similar, but with different degrees of activity, so I was wondering which should I use to explore as proof of concept between this current repo, this one: https://github.com/w3c-ccg/Merkle-Disclosure-2021 and this one: https://github.com/transmute-industries/verifiable-data/tree/main/packages/merkle-proof?

Are you also open to contributions/collaborations or should those happen through the proper W3C charter?

Thanks

@OR13
Copy link
Sponsor Member

OR13 commented Jan 4, 2023

I built this over the holidays, https://github.com/transmute-industries/merkle-proof

It's maybe a bit easier to understand and provides visualizations of merkle proofs.

W3C is not the right place to attempt to standardize Merkle Proof Encodings for JSON or CBOR.

IETF COSE and JOSE working groups are the right place.

There is already some work underway to support COSE

ietf-scitt/draft-birkholz-scitt-receipts#15

https://certificate.transparency.dev/

https://www.rfc-editor.org/rfc/rfc9162

The problem is that folks keep overfitting the merkle proof standards to use cases, and then we don't end up with generic compact representations for merkle proofs that work for any use case that rely on JSON or CBOR encodings.

@lemoustachiste
Copy link
Author

Thanks, I'll take a look at all that today

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants