Sign & anchor your IoT sensor data.
A device records a reading — but that telemetry isn't independently provable later. Hash it locally and anchor just the hash to Bitcoin: a permanent, tamper-evident proof the reading existed unchanged at a time, that anyone can check — even against us.
The call
Keyless. Hash a reading on the device, anchor only the 64-hex digest, store the proof. 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) anchor JUST the digest — keyless, hashes only
curl -s https://dynamicfeed.ai/v1/anchor -H "Content-Type: application/json" \
-d "{\"digest_hex\":\"$DIGEST\"}"
# → status:"pending" + a proof_ots_b64 you store on the device.
# ~1 block later: POST /v1/anchor/upgrade for the Bitcoin attestation.Sample response
{ "digest_sha256": "09207fd234c0ab808f2d8861a5d55f7cc8497229cb4353f997d2ee1e75604880",
"status": "pending",
"proof_ots_b64": "...",
"note": "Submitted to OpenTimestamps calendars; upgrade ~1 block later for the Bitcoin attestation." }Why live data
When a warranty claim, a compliance audit, or a dispute asks 'what did this sensor read, and when?', a value in a log you control proves nothing — it could have been written after the fact. Anchoring commits a reading's SHA-256 to Bitcoin via OpenTimestamps (free, no wallet): a permanent, independent timestamp that the record existed no later than that block. Only the hash is sent — the underlying reading never leaves the device, so there is nothing for us to read, store or leak. It is proof-of-existence-at-a-time and tamper-evidence — not a claim the reading is accurate, and evidence, not a safety guarantee.
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 anchor actually prove?
Proof-of-existence-at-a-time and tamper-evidence: that the exact reading existed no later than a Bitcoin block, and that any later change is detectable. It is not a claim the reading is accurate or true.
Is it keyless?
Yes. POST /v1/anchor works right now with no key, signup or wallet. About a block later, POST /v1/anchor/upgrade fetches the Bitcoin attestation.