Sign & timestamp your IoT sensor data.
A device can hash a reading locally and request an RFC 3161 artifact for the digest. The underlying reading stays on-device; independent time evidence depends on validating the token/CMS, digest binding, certificate chain, EKU, revocation status and configured trust anchor.
The call
Keyless. Hash a reading on the device, submit only the 64-hex digest and store the returned artifact. Your underlying data stays entirely on your side.
# 1) hash the sensor reading locally — your data never leaves the device
DIGEST=$(printf '{"device":"sensor-7","temp_c":17.1,"t":"2026-06-14T04:00:00Z"}' \
| shasum -a 256 | cut -d' ' -f1)
# 2) request an RFC 3161 artifact for JUST the digest — keyless, hashes only
curl -s https://dynamicfeed.ai/v1/anchor -H "Content-Type: application/json" \
-d "{\"digest_hex\":\"$DIGEST\"}"
# → store the returned RFC 3161 artifact with the reading.Sample response
{ "digest_sha256": "09207fd234c0ab808f2d8861a5d55f7cc8497229cb4353f997d2ee1e75604880",
"backend": "rfc3161",
"artifact_b64": "...",
"note": "Validate the token, digest binding and certificate path before relying on time evidence." }Why live data
When a warranty claim, audit or dispute asks what a sensor read and when, an internally controlled log may not be enough. The device can send only the reading's SHA-256 digest and request an RFC 3161 artifact. The underlying reading never leaves the device. The artifact is not self-validating: independent time evidence requires validation of the token/CMS, digest binding, certificate chain, EKU, revocation status and configured trust anchor. It does not prove that the reading is accurate.
Use it for
- Fleet & asset telematics — an independent, signed record per asset for a dispute
- Agritech — anchor a hash of yield or soil readings for a buyer, insurer or subsidy claim
- Industrial IoT — a tamper-evident record of a process reading for an audit or incident review
- Smart-city sensors — make a published environmental record independently verifiable
FAQ
Does my sensor data leave the device?
No. You compute a SHA-256 locally and send only the 64-hex digest. The underlying reading, file or payload stays entirely on your side — privacy by construction.
What does the timestamp artifact prove?
Only a fully validated RFC 3161 artifact can support independent time evidence for the submitted digest. It does not prove the underlying reading is accurate or true.
Is it keyless?
Yes. POST /v1/anchor accepts a digest without signup. Preserve the artifact and validate its token/CMS, digest binding and certificate path before relying on it.