2 comments
SDK:
<a href="https://github.com/CipherTrustee/certisfy-js" rel="nofollow">https://github.com/CipherTrustee/certisfy-js</a><p>Web of trust use case example:
<a href="https://bsky.app/profile/bitlooter.bsky.social" rel="nofollow">https://bsky.app/profile/bitlooter.bsky.social</a><p>Experimenting with Keybase key holders as CAs:<p><a href="https://www.reddit.com/r/Keybase/comments/1q5ys71/using_keybase_key_to_build_certificate_trust/" rel="nofollow">https://www.reddit.com/r/Keybase/comments/1q5ys71/using_keyb...</a><p>Cryptographic Implementation of Exclusivity Agreements:
<a href="https://github.com/CipherTrustee/certisfy-claim-recipes/tree/master/ppbv" rel="nofollow">https://github.com/CipherTrustee/certisfy-claim-recipes/tree...</a><p>Build Your Own Trust Chain:
<a href="https://blog.certisfy.com/2026/04/build-your-own-trust-chain.html" rel="nofollow">https://blog.certisfy.com/2026/04/build-your-own-trust-chain...</a><p>Some other examples of how you could leverage it:
<a href="https://blog.certisfy.com/" rel="nofollow">https://blog.certisfy.com/</a><p>Happy to answer questions.
How do you foresee this being implemented or made popularly available?
Just emailed you, I'm working on something similar <a href="https://github.com/MinistryofMany" rel="nofollow">https://github.com/MinistryofMany</a><p>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.
what was the hardest part about this project?
How does this differ from e.g. S3 pre-signed URLs?