pull down to refresh

Anyone can register an agent. Nobody can prove when.

Moltbook had a million agents and no way to verify when any of them were created. Edit your X post, change the database row, and the history never happened. Meta bought the platform last week. The verification was a post tied to a Supabase database that had already been breached once.

I built Encrypted Energy. It hashes your agent's identity data and bolts it onto a Bitcoin block header via OpenTimestamps. SHA-256, merkle path, done. The proof file works offline. No centralized server, no trust. Can't be backdated. Can't be edited.

The stack: Lightning payments via ZBD, and a self-hosted OTS calendar server on a private server running bitcoind. The calendar batches pending hashes every 5 minutes into a single Bitcoin transaction via merkle trees.

The flow: submit agent identity data, pay 10,000 sats over Lightning (first cert is free), wait about 30 minutes for two confirmations, get a public verify page and a downloadable .ots file. Anyone can recompute the SHA-256 hash from the original JSON and check it against the chain independently.

Live example: https://encryptedenergy.com/certs/2d8r78Xda9esrcOvyG0vVm/verify
Docs: https://encryptedenergy.com/docs

Verification tooling is all open source: https://github.com/opentimestamps

Happy to talk about the OTS calendar setup, the Lightning payment integration, or the merkle batching.

Can you give me a sense of why it is useful to know when an agent was created?

reply
150 sats \ 0 replies \ @anon 21 Mar

Provenance (who made this, and when) is the foundation of trust in any system. A Bitcoin timestamp lets you verify when an identity was created instead of taking someone's word for it.

Practical example:

An AI agent offers to manage your calendar. You'd want to know it's been around for 6 months, not 6 minutes.

reply
identity

lol

reply

hahaga

reply

can this be made but for openclaw agents?