What is CORE-M?
CORE-M by Kronox Data is a multi-tenant IoT platform that does what every IoT platform does — connect devices, ingest telemetry, store it, and act on it — with one difference that changes everything downstream: every accepted data point is anchored to the BSV blockchain, so its existence and timestamp can be verified by anyone, without trusting Kronox Data or any platform operator.
The problem it solves
Section titled “The problem it solves”Conventional IoT platforms (AWS IoT Core, Azure IoT Hub, ThingsBoard) manage devices and data well, but they ask you to take the data’s integrity on faith. There is no way to prove that a sensor reading existed at a specific moment and has not been altered since, without trusting the operator who controls the database. For a sensor log that feeds a billing dispute, a regulatory filing, a warranty claim, or a safety audit, “trust us, the record is unchanged” is not good enough.
CORE-M closes that gap. As telemetry is ingested, each accepted point is hashed,
the hashes are batched into a Merkle tree, and the tree’s root is written to the
BSV blockchain in an OP_RETURN output. The blockchain is an append-only public
ledger no single party controls, so the anchor becomes an immutable,
independently verifiable timestamp for that data. Later, anyone holding the
original data point plus its proof can confirm it was anchored — even if CORE-M
itself is offline or untrusted.
Who it’s for
Section titled “Who it’s for”- Fleet operators running large device estates who need a single multi-tenant control plane for connectivity, telemetry, rules, and alarms.
- Device integrators who need to get hardware talking to the platform over whatever protocol the device speaks — HTTP, MQTT, CoAP/DTLS, LwM2M, or SNMP.
- Compliance auditors who need to verify that historical telemetry is authentic and untampered, using a portable proof rather than privileged access to the operator’s systems.
The five pillars
Section titled “The five pillars”Device connectivity
Section titled “Device connectivity”Devices reach CORE-M over the protocol that suits them — HTTP, MQTT, CoAP/DTLS, LwM2M, or SNMP — and authenticate with an API key, a pre-shared key (PSK), or an X.509 certificate. Gateway devices can relay telemetry on behalf of child devices behind a single uplink. See Connecting Devices.
Telemetry pipeline
Section titled “Telemetry pipeline”Ingested telemetry is validated and enriched, then made available for both sub-millisecond operational reads and historical analytics. See Sending Telemetry.
Rules and alarms
Section titled “Rules and alarms”User-defined CEL rules evaluate against live telemetry and can raise first-class alarms, fire notifications with escalation and quiet hours, or dispatch commands back to devices. See Rules & Alarms.
Blockchain anchoring
Section titled “Blockchain anchoring”Every accepted point is hashed and batched into a Merkle tree; the platform
publishes the Merkle root on the BSV blockchain via an OP_RETURN transaction on
your behalf. You set the anchoring policy — the platform handles the rest. See
Anchoring.
Trustless verification
Section titled “Trustless verification”Given a data point and its proof bundle, the verifier returns the Merkle path and a BEEF/SPV proof of block inclusion. Verification is independent: a third party can confirm the anchor on-chain without trusting CORE-M at all. See Verification.