Most data for AI is 'trust me.' This is 'prove it' — every snapshot is Ed25519-signed and its hash timestamped on the Bitcoin blockchain, so anyone can verify what was true the moment an AI acted.
Signed by us, anchored on a public chain — so you don't have to take our word for it.
# Every awareness snapshot is signed. Fetch the public key:
curl https://dynamicfeed.ai/.well-known/keys
# Anchor any snapshot's hash to Bitcoin (free, no wallet):
curl -X POST https://dynamicfeed.ai/v1/anchor -H "Content-Type: application/json" -d '{"snapshot": { ... }}' "signature": { "alg": "Ed25519", "key_id": "df-ed25519-3a52a473cde2", "sig": "base64url(...)" }
# POST /v1/anchor ->
{ "chain": "bitcoin", "status": "pending", "digest_sha256": "...", "proof_ots_b64": "..." }When an AI acts on the world, 'trust me' isn't enough. Signing proves a datapoint came from Dynamic Feed and wasn't altered; anchoring its hash to the Bitcoin blockchain proves it existed at that exact moment — independently verifiable by anyone, even against us. That's the audit trail an agent or robot needs to defend a decision after the fact.
Ed25519 over the canonical JSON of each snapshot. The public key is published at /.well-known/keys (JWKS-style), so anyone can verify independently.
A signature proves who and what. Anchoring the hash to Bitcoin (via OpenTimestamps) proves when — an un-backdateable, third-party-verifiable timestamp, even against us.
No. Anchoring is free and wallet-less — OpenTimestamps folds your hash into a Bitcoin block. Only the hash goes on-chain, never your data.
Yes — that's the point. Verify the Ed25519 signature against the public key, and verify the .ots proof against Bitcoin with the standard OpenTimestamps client.