Edmond

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.

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.

Previously integrated Biomni into our intelligent workspace:

https://blog.codesolvent.com/2025/07/ai-assistant-with-biome...

Happy to chat if intrigued.

>We have public-key infrastructure for machines. We don’t have it for people.

We do, you just don't know about:)

SDK: https://github.com/CipherTrustee/certisfy-js

Web trust use: https://bsky.app/profile/bitlooter.bsky.social

Some examples of how you could leverage it: https://blog.certisfy.com/

Happy to answer questions.

it's called workflow automation: https://blog.codesolvent.com/2025/12/workflow-automation-let...

Everyone is just taking a round about way to get there. The workflow/program as "tools" approach is the right one. Agents skills are more or less in that same direction.

For example of how you could use this:

https://blog.certisfy.com/2026/04/trusted-urls-via-cryptogra...

Basically wrap urls in trustworthy cryptographic signatures that users (human, or even user agents, ie browsers) can verify.

More info: https://github.com/CipherTrustee/certisfy-claim-recipes

Just released:

https://github.com/CipherTrustee/certisfy-js

It's an SDK for Certisfy (https://certisfy.com)...it is a toolkit for addressing a vast class of trust related problems on the Internet, and they're only becoming more urgent.

Feel free to open discussions here: https://github.com/orgs/Cipheredtrust-Inc/discussions

For an example of what an "async" agent implementation should help you accomplish: https://youtu.be/hGhnB0LTBUk?si=q78QjgsN5Kml5F1E&t=5m15s

You can use the idea to spin-off background agent tasks that can then be seamlessly merged back into context when they complete.

The example above is a product specific approach but the idea should be applicable in other environments.... it's really an attempt to integrate long running background tasks while continuing with existing context in an interactive manner.

When you start working on the problem of working with automation programs (AKA agents) in an interactive human-in-the-loop fashion, you will naturally run into these kinds of problems.

We've all seen sci-fi movies with AI assistants that seamlessly work with humans in a back and forth manner, async spin-offs are essential for making that work in practice for long running background tasks.

Age verification could indeed be implemented in other ways. The approach outlined above is for information verification and trust projection in general, meaning you can put just about any verified information on a certificate and it can be used online.

Here is a concrete example of how trustworthy certificates can be used online, this is my personal profile on bluesky with verification that is independent of the Blue sky service: https://bsky.app/profile/bitlooter.bsky.social

If you click on the profile image you can enter that code into https://certisfy.com/app to verify the identity of the profile. That sticker could be on any online profile to prove high quality authenticity, it could for instance be on an e-commerce site to prove that the site isn't a scam.

If the hammer ever comes down on this issue, ie hardcore requirement for age verification, there are ways to do this while protecting privacy.

We are experimenting with bootstraping a PKI certificate trust chain for facilitating trust projection and information verification online. Think of it as the ability to do things like age verification at scale via a peer-2-peer ish mechanism instead of sending your government id to a service provider.

One experiment is with PGP key holders (for now Keybase key holders) as CAs:

https://news.ycombinator.com/item?id=46576590

And also .gov email holders:

https://blog.certisfy.com/2025/12/using-gov-email-addresses-...

It's all self-service and requires no sign-up or download of anything, the app (https://certisfy.com/app) is an in-browser app and all the cryptography happens in the browser.

Trying to bootstrap a PKI certificate trust chain for facilitating trust projection and information verification online. Think of it as the ability to do something such as age verification at scale via a peer-2-peer ish mechanism instead of sending your government id to a porno service.

We are experimenting with Keybase key holders as CAs:

https://news.ycombinator.com/item?id=46576590

And also .gov email holders:

https://blog.certisfy.com/2025/12/using-gov-email-addresses-...

It's all self-service and requires no sign-up or download of anything, the app (https://certisfy.com/app) is an in-browser app and all the cryptography happens in the browser.

Work related versions of this, expense report:

https://youtu.be/h0Bg-lqNlkU

In general Just-In-Time app generation is a bad idea. The right approach is to create human-in-loop tools that a bot would recognize and invoke as needed, of course the human-in-loop tool would itself be AI generated.

Example of human-in-loop tool in use:

https://youtu.be/srG5Ze7mS7s