6 comments

[ 1.9 ms ] story [ 26.0 ms ] thread
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.

How does this differ from e.g. S3 pre-signed URLs?
How to implement signed URLs with W3C DID keys and W3C Verifiable Credentials?
What happens if the destination/contents of the URL changes after I sign it?
Google AMP had the concept of Signed Exchanges so that you can host content on a third party server while proving its integrity https://developer.chrome.com/blog/signed-exchanges

Unfortunately, AMP itself was controversial and the system was not really adopted elsewhere, but it is something.

What does this add over message signing?