A verifiable data layer for IoT & edge devices.
Edge devices act on data and produce it, and both directions are usually unverifiable. Dynamic Feed is the layer they plug into: signed world-data in that a gateway can verify on-device before acting, and a keyless anchor endpoint to commit a hash of a device's own reading to Bitcoin for a tamper-evident record. One keyless API, with reference clients for the stacks fleets already run.
The call
One keyless call returns a signed datapoint an edge device verifies before acting:
curl -s -X POST https://dynamicfeed.ai/v1/batch \
-H 'Content-Type: application/json' \
-d '{"calls":[{"tool":"current_weather","args":{"city":"Sydney"}}]}'Sample response
{ "results": [ { "tool": "current_weather", "ok": true,
"data": { "temperature_c": 16.3, "conditions": "Light drizzle",
"provenance": { "source": "Open-Meteo", "measured_at": "2026-06-15T09:45:00Z" },
"freshness": { "state": "live", "age_seconds": 434 } } } ],
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-...", "sig": "..." } }
# verify the signature on-device against /.well-known/keys before actingWhy live data
Most IoT data is unsigned: a device trusts the pipe, and its own telemetry can't be proven later. Dynamic Feed closes both gaps over one keyless API. Inbound, every datapoint - weather, air quality, energy-grid, GPS-interference, space weather and more - is Ed25519-signed over its exact bytes and carries source, observed-at time and a freshness state, so a gateway verifies it on-device (an open-source verifier runs on a Pi or an ESP32) before acting. Outbound, a device hashes its own reading locally and anchors just the hash to Bitcoin (free, no wallet) for a tamper-evident proof it existed at a time. Reference clients exist for Raspberry Pi, ESP32, MicroPython, Home Assistant, Node-RED and MQTT. A signature proves the datapoint existed unchanged as we reported it at that time; it is not a claim the value is objectively true, and it is evidence, not a safety guarantee — your device's own stack owns every decision. Full integration guide: dynamicfeed.ai/iot.
Use it for
- Feed a gateway signed world-data it verifies on-device before acting
- Anchor a hash of a device's own reading for a tamper-evident audit/warranty record
- Drop one keyless feed into Home Assistant, Node-RED or an MQTT broker
- Run the open-source verifier on a Pi-class device with no network round-trip
FAQ
What can run the on-device verifier?
A Raspberry-Pi / Linux SBC does full float-exact verification today; ESP32 (Arduino C++) and MicroPython verify integer/string payloads and anchor receipts. An 8-bit Arduino Uno is too small - verify on a Pi-class gateway and fan out.
Does my sensor data leave the device when I anchor it?
No. You hash the reading locally and send only the 64-hex digest; the underlying data never leaves your side. We sign and Bitcoin-anchor the hash.
What exactly does a signature prove?
Proof-of-existence-at-a-time and tamper-evidence: the datapoint existed unchanged as we reported it. It is not a claim the value is true, and it is evidence, not a safety guarantee. See the full guide at dynamicfeed.ai/iot.