Verify

Verify is coming soon. Details on this page are preliminary and may change. Track progress on the roadmap.

Verify is the attestation layer for peaqOS. It lets manufacturers, labs, and the peaq Foundation co-sign a machine’s identity, producing a portable signal that the machine exists and is who it claims to be. Today, trust levels are self-attested when an is submitted. Hardware-signed = 2 is a valid value but there’s no third-party attestation infrastructure behind it yet. Verify attests the machine (not individual events) and is what closes that gap.

What Verify v1 will be

The first release is specified and its contract is written; nothing is deployed and no SDK or API surface exists yet.

Piece	What it does
Attestation registry	An on-chain registry of M-of-N attester quorums. For each subject and topic it answers one of four states: `unverified`, `verified`, `expired`, `revoked`. Revocation dominates expiry. There is no aggregate “verified” boolean across topics.
Two topics	KYB on the machine’s current operator address, and chip on the machine ID. Each is reported independently.
Chip proof	Hardware attestation against one certified chip family in v1: an Infineon OPTIGA Trust M v3 secure element whose leaf certificate chains to the Infineon CA. No TPM, software key, or other secure element is accepted in v1.
Authority split	The SDK validates chip evidence locally and reads attestation state through the peaqOS API; it never touches the chip, submits evidence, or writes the registry. A verifier backend issues challenges, checks evidence, and anchors the result.

Contract addresses, endpoint paths, and SDK methods will appear here when they ship.

⌘I

Welcome

Get Started

Concepts

Functions

Guides

What Verify v1 will be

​What Verify v1 will be

What Verify v1 will be