LIVE STATUS: /uptime·PUBLIC CATALOGUE · SOURCE-ATTRIBUTED
DATA WITH RECEIPTS · ED25519 · RFC 3161·--:--:-- UTC
Home  /  Notarize
NOTARIZE · SIGNED · RFC 3161 TIMESTAMPED

Notarize anything. Prove it later.

Drop in any claim or datum. Dynamic Feed witnesses it and hands back an Ed25519-signed receipt anyone can verify, then time-stamp it with an independent RFC 3161 authority in one click for proof-of-when independent of us. Let's Encrypt for data, get your feed signed without building a signing stack.

dynamicfeed.ai · /v1/receipt · keyless
1 Witness any claim or data
keyless · nothing is stored unless you timestamp it
2 Verify it, in your browser, then RFC 3161 timestamp it
notarize something above, then verify + timestamp it here.
FOR YOUR OWN DATA FEED

Your feed, signed, without a signing stack.

Run a data feed others rely on? Notarize each datapoint so consumers can verify it came from you, unaltered, at a known time. Send the data, or keep it private and send only its hash, Dynamic Feed witnesses the bytes either way. One call (free key):

SHELL · POST /v1/notarize · private hash-only modeCOPY
curl -s https://dynamicfeed.ai/v1/notarize \
  -H "X-API-Key: $DF_KEY" -H "content-type: application/json" \
  -d '{"payload_sha256":"<64-hex sha256 of your bytes>","subject":"acme-prices-feed"}'
what a notarization proves

That Dynamic Feed witnessed these exact bytes (or this hash) at witnessed_at, proof-of-existence and tamper-evidence, independently time-stamped by an independent RFC 3161 authority so it holds even against us. It does not assert the content is true. Verify any receipt's Ed25519 signature yourself at /playground; read the format at the standard.

BE VERIFIABLE

Make your data provable.

Sign it, timestamp it, hand anyone a receipt they can check without trusting you, or us.

Takedown-clock receipts  ·  Chain-of-custody receipts