Skip to main content
classifies how trustworthy the data in a submitted is. Higher trust levels indicate stronger guarantees about the event’s authenticity.

The three levels

Self-reported

The machine or operator attests to the event. No external verification: the submitter’s word is the source of truth.

On-chain verifiable

The event is backed by an reference (, receipt, or cross-chain proof) that anyone can independently verify.

Hardware-signed

The event is signed by (a secure element on the device) that binds the event to a specific physical device.
Choose the highest level you can honestly attest to. Trust levels are a field on each EventRegistry event and are self-declared today. Third-party attestation of the machine itself arrives with Verify, which in its first release accepts one certified chip family (Infineon OPTIGA Trust M) rather than any TPM or enclave.

Trust weight in the MCR

Higher trust levels contribute more to the MCR score. Hardware-signed events carry the strongest weight, on-chain verifiable events sit in the middle, and self-reported events the lowest. Self-reported machines with a sustained track record (a year or more of event history) earn a small graduation bonus on their trust contribution, though they remain below the on-chain tier. A machine flagged with a negative event incurs a temporary penalty on its trust contribution for a fixed window from the flag timestamp, after which the penalty expires automatically.

Admin overrides

peaq operates two on-chain admin functions (AdminFlags contract) that adjust how the treats a machine. Both are owner-only and emit events. Submitting an event with trustLevel > 2 on EventRegistry.submitEvent with InvalidTrustLevel().