Work Attestation for IoT & Industrial Equipment

A machine that can prove what it did is worth more than one that can't. Work attestation is the layer that turns a machine's activity — parts cut, hours run, energy delivered, actions fired — into a tamper-evident record that an insurer, a lender, or an autonomous agent can verify. This is an honest map of the projects building it, the settlement protocols underneath, and where it all leads: machine credit. Curation, not a leaderboard.

Why attestation, and why now

Most machine activity lives in a log file anyone with write access can edit. That's fine until money or autonomy enters the picture. Equipment finance without verified work history is underwriting blind. Equipment-as-a-service billing without verifiable usage is a trust exercise. And when an autonomous agent throttles a line or dispatches a tech at 3am, "who authorized that, and what actually happened?" needs an answer that survives a regulator. Attestation provides it: a record whose integrity can be checked independently, usually by anchoring cryptographic hashes to an immutable ledger so the data itself never has to leave the site.

The pattern: hash locally, anchor the proof

Nearly every credible approach shares a shape. The machine (or an edge runtime) hashes each event and anchors only the digest — a Merkle root plus per-event hashes — to a public ledger. Raw telemetry, part geometry, and process data stay on-premises; the chain holds proofs, not secrets. That's what makes attestation palatable to industrial security reviews: a network trace shows hashes, not your production data. The projects below differ mainly in what they attest and for whom.

Implementations letting machines prove their work

FoundryNet / MINT — attested work for industrial machines

FoundryNet hashes every billable event — a trigger fire, a normalize result, a settlement candidate — into a durable on-edge buffer, then Merkle-roots it and anchors SHA-256 hashes only to a public ledger (Solana) through its MINT layer. It's industrial-first: the work being attested is normalized, cross-OEM machine activity, and attestation is opt-in and off by default so a Siemens Industrial Edge review sees zero outbound chain traffic until a customer enables it. The explicit goal is the path to machine credit — a verifiable work history a lender can price.

IoTeX — W3bstream verifiable device proofs

IoTeX's W3bstream generates verifiable proofs from real-world device data, turning raw machine and sensor output into attestations that smart contracts can act on. Paired with ioID (its device-identity primitive), it forms an identity-plus-proof stack aimed mostly at DePIN hardware — useful anywhere you need to prove a device did or measured something without trusting the operator.

peaq — attestation as part of the machine-economy stack

peaq approaches attestation as one layer of a broader machine-economy stack — identity (peaq ID), access, payment, and the data verification that lets a machine's actions be trusted and settled. If you've adopted peaq for identity and machine payments, its data/verification primitives keep the work record in the same network rather than bolting on a separate attestation system.

The path to machine credit

Attestation isn't the destination — it's the foundation. The sequence is: verifiable identity → tamper-evident work history → usage-based billing → machine credit scoring → equipment finance priced on real output. Each step depends on the one before it, and all of them collapse if the underlying record can be faked. That's why "boring" audit infrastructure — hash, anchor, verify — is the unlock for the more exciting outcomes everyone wants from the machine economy.

Building attestation or settlement for physical assets and want it listed here? Tell us about it. See also: Machine Identity in the Agent Economy →