9 points | by Edmond 2 hours ago ago
8 comments
SDK: https://github.com/CipherTrustee/certisfy-js
Web of trust use case example: https://bsky.app/profile/bitlooter.bsky.social
Experimenting with Keybase key holders as CAs:
https://www.reddit.com/r/Keybase/comments/1q5ys71/using_keyb...
Cryptographic Implementation of Exclusivity Agreements: https://github.com/CipherTrustee/certisfy-claim-recipes/tree...
Build Your Own Trust Chain: https://blog.certisfy.com/2026/04/build-your-own-trust-chain...
Some other examples of how you could leverage it: https://blog.certisfy.com/
Happy to answer questions.
Just emailed you, I'm working on something similar https://github.com/MinistryofMany
it's basically an OIDC provider as an identity wallet using verifiable credentials, but I've got a "share link" system built in where you can share specific credentials/proofs with others.
How do you foresee this being implemented or made popularly available?
what was the hardest part about this project?
Everything :)
But I wouldn't characterize it in terms of being hard.
It's been a work in progress for many years,... so more of a problem solving and exploratory endeavor.
What happens if the destination/contents of the URL changes after I sign it?
How does this differ from e.g. S3 pre-signed URLs?
How to implement signed URLs with W3C DID keys and W3C Verifiable Credentials?
SDK: https://github.com/CipherTrustee/certisfy-js
Web of trust use case example: https://bsky.app/profile/bitlooter.bsky.social
Experimenting with Keybase key holders as CAs:
https://www.reddit.com/r/Keybase/comments/1q5ys71/using_keyb...
Cryptographic Implementation of Exclusivity Agreements: https://github.com/CipherTrustee/certisfy-claim-recipes/tree...
Build Your Own Trust Chain: https://blog.certisfy.com/2026/04/build-your-own-trust-chain...
Some other examples of how you could leverage it: https://blog.certisfy.com/
Happy to answer questions.
Just emailed you, I'm working on something similar https://github.com/MinistryofMany
it's basically an OIDC provider as an identity wallet using verifiable credentials, but I've got a "share link" system built in where you can share specific credentials/proofs with others.
How do you foresee this being implemented or made popularly available?
what was the hardest part about this project?
Everything :)
But I wouldn't characterize it in terms of being hard.
It's been a work in progress for many years,... so more of a problem solving and exploratory endeavor.
What happens if the destination/contents of the URL changes after I sign it?
How does this differ from e.g. S3 pre-signed URLs?
How to implement signed URLs with W3C DID keys and W3C Verifiable Credentials?