Technology · The Reality Engine

The architecture behind the signed data.

The Reality Engine takes a physical environmental signal and carries it, unbroken, from a secure element in the field to a registry-grade proof on chain. Hardware signs at the source. The edge verifies. An independent validator network reaches consensus. Cardano anchors the record. Every link is cryptographic, and every link is inspectable.

01 · Proof of origin

Signed inside the silicon, before it leaves the device.

Every field node carries a tamper-resistant secure element. Its signing key is generated and burned in at manufacture and is never exportable from the chip. Signing happens inside the secure element, so the signature exists before a reading ever touches a network. There is no software path to forge it.

Secure element · ATECC608B

The key never leaves silicon

  • Private key provisioned at manufacture and non-exportable from the chip
  • Signing operations run inside the secure element, not in application firmware
  • On-device identity is bound to the hardware, not a config file
  • Tamper-evidence subsystem in the enclosure guards the physical boundary
Chain of custody

The signature is the source of truth

  • Legacy MRV signs a PDF months after the fact; Mālama signs the reading at the instant of measurement
  • Change one digit of the payload and the signature breaks
  • Custody starts at the sensor, not the spreadsheet
  • Buyers, registries, lenders, and regulators verify the record directly

What gets signed

Each device packet binds identity, policy, time, geography, payload, sequence, firmware, and calibration into a single SHA-256 digest, then signs that digest with device-bound key material. The result is a record the protocol can defend on origin, integrity, continuity, and replay grounds.

H = SHA256(d || p || t || g || v || n || f || c)
d · device id
p · policy id
t · timestamp
g · geospatial context
v · sensor payload
n · monotonic nonce
f · firmware version
c · calibration state
02 · Edge verification

Six checks before a reading is ever trusted.

Raw signed data is processed at the edge before transmission. The verification stack runs cryptographic, protocol, physical, spatial, temporal, and methodology checks in sequence, and statistical anomaly detection flags readings that are spoofed or physically implausible.

Cryptographic

Is the signature real?

The device signature is validated against the on-chain device registry. An unknown or mismatched key fails immediately.

Protocol

Does the packet conform?

Schema, policy id, and firmware version are checked against protocol standards for the methodology in force.

Physical

Is the reading possible?

Values are bounded against sensor physics and calibration state. A soil probe cannot report an atmospheric impossibility.

Spatial

Is it where it claims?

Geospatial context is checked against the node's registered H3 cell and neighbors. Location drift is caught at the edge.

Temporal

Is the sequence intact?

The monotonic nonce and timestamp enforce ordering and replay resistance. Gaps and rewinds are flagged.

Anomaly detection

Is it statistically plausible?

Outlier detection scores each reading against its own history and its neighbors, surfacing spoofed or drifting signals.

Edge verification is where context is captured at the moment of measurement. For AI compute nodes, the same stack pairs power draw with real-time grid carbon intensity: the same kilowatt-hour at 4 AM in Quebec and 4 PM in Texas carries a different emissions weight, and the edge records that difference before the data moves.
03 · Validator network

Independent validators, one Proof-of-Truth consensus.

Verified data is broadcast to the Mālama Hex Node network. Each node operates within an H3 geographic cell under a non-exclusive license and validates that the packet matches protocol standards and that the device signature is valid against the on-chain registry. Consensus is geographic, so a single validator cannot falsify unnoticed.

PONO credential

Skin in the ground

Validators operate under a PONO credential earned through KYB and operational milestones. It is a stake, not a login.

H3 k-ring BFT

Neighbors keep neighbors honest

The geographic consensus layer makes single-validator falsification detectable by neighboring nodes, giving the network Byzantine fault tolerance by construction.

Fraud economics

Cheating forfeits rewards

Fraudulent attestations trigger PONO revocation and forfeiture of unvested operator rewards, which route to the Genesis Performing Operator Bonus Pool.

Each Hex Node validates both carbon SaveCards and AI compute attestations through the same Proof-of-Truth consensus. The verification path is identical whether the underlying signal is a soil measurement or a rack-level power draw.

04 · On-chain anchoring

Constant on-chain footprint, complete off-chain proof.

Validated readings are batched by region and methodology and bundled into Merkle trees. Full payloads persist in immutable raw storage on Arweave, and only the Merkle root is anchored on Cardano. The on-chain footprint stays constant no matter how much telemetry flows, while auditors can still retrieve a full inclusion proof for any individual record.

Anchor chain
Cardano, deterministic eUTXO model with Plutus contracts for registry-grade auditability
SaveCard issuance
CIP-25 and CIP-68 native assets; CIP-68 datum-metadata carries richer, updatable asset state
Raw storage
Full signed payloads on Arweave, immutable and permanently retrievable off chain
On-chain object
Merkle root anchored via a CIP-68 reference NFT; on-chain size is independent of telemetry volume
Geospatial index
Uber H3 hex grid; Resolution 5 cells span roughly 252.9 km² and index the planet uniformly
Audit path
Any record's inclusion proof is retrievable from storage and checkable against the on-chain root

SaveCards live on Cardano as the archival, long-horizon custody layer. Execution, staking, and governance run on Base. The two chains do separate jobs and are not bridged at token generation; the protocol does not require them to be.

05 · Hardware vs software MRV

Why hardware signing beats software-only MRV.

Software-only measurement asks you to trust a report. Hardware signing lets you verify the measurement. The difference is where the chain of custody begins.

Property Software-only MRV Mālama Reality Engine
Point of trustThe report, signed after the factThe reading, signed at the instrument
Tamper-evidenceProcedural and reviewableCryptographic, breaks on any edit
Key custodySoftware keys that can be copiedNon-exportable key inside the secure element
Verification time12 to 24 monthsContinuous, real-time
Data reliabilitySubjective and periodicObjective and continuous
Coverage logicConvenience-drivenH3 zone-weighted by climate value
AuditabilityTrust the intermediaryTrust the cryptography, verify on chain
Estimation is the start. Sensors are the truth. Published, cited assumptions get the field talking and the methodology improving; hardware-signed measurement is what moves the field beyond debate. Both tiers are necessary, and the Reality Engine is built for the second.
06 · Get started

Build on verifiable data.

Register interest to operate validator infrastructure, integrate the SaveCard data primitive, or license hardware-signed environmental data for your application.