Glossary

A quick reference for the terms that recur across the CORE-M docs. For the concepts behind them and how they connect, see Core Concepts.

BEEF — Background Evaluation Extended Format; a compact BSV transaction package that bundles a transaction with the SPV data needed to verify it offline.

BSV — BSV Blockchain; the public, append-only ledger CORE-M anchors telemetry to via OP_RETURN commitments.

CBOR — Concise Binary Object Representation (RFC 8949); a compact binary serialization format for structured data.

CDT — Complex Data Type; Aerospike’s nested list and map types, used for bins such as device groups, tags, and telemetry series.

CEL — Common Expression Language; the expression syntax users write rules in, evaluated against live telemetry by the rules engine.

DTLS-PSK — Datagram TLS with a pre-shared key; the secured transport used by CoAP devices that authenticate with a shared secret rather than a certificate.

Ed25519 — the elliptic-curve signature scheme the auth service uses to sign dashboard-user JWTs. It is not used for any blockchain operation.

finality — the point at which a confirmed anchoring transaction is treated as irreversible; the default threshold is 6 block confirmations.

hardware_id — a device’s physical identity (serial number, MAC, or IMEI), stored as metadata and kept distinct from its platform device_id.

JCS (RFC 8785) — JSON Canonicalization Scheme; a deterministic JSON serialization that produces identical bytes for identical data, so hashes are reproducible across implementations.

LwM2M — Lightweight M2M; an OMA device-management protocol over CoAP for constrained devices, supported as a connectivity option.

Merkle tree — a hash tree whose single root summarizes a whole batch of data points; only the root is anchored on-chain.

OP_RETURN — a BSV script opcode that embeds arbitrary data in a transaction output; CORE-M writes each batch’s Merkle root in an OP_RETURN output.

P2PKH — Pay-to-Public-Key-Hash; the standard BSV locking script used to pay to an address.

PSK — pre-shared key; a symmetric secret a device uses to authenticate, commonly with DTLS on CoAP.

Redpanda — the Kafka-compatible streaming event bus that carries telemetry, device, rule, and anchor events between services.

SPV — Simplified Payment Verification; the technique for proving a transaction’s inclusion in a block using block headers and a Merkle path, without running a full node.

TelemetryPoint — one reading from one device at one timestamp, carrying its device_id, tenant_id, timestamp, and a set of named numeric or string metric values.

tenant — an isolated customer account; every record in CORE-M is scoped to a tenant_id.

TimescaleDB — the PostgreSQL-based time-series database used as CORE-M’s cold store for historical telemetry.

UTXO — Unspent Transaction Output; a spendable chunk of BSV value, the unit consumed and produced by BSV transactions.