---
title: "Attestation and proof verifier | Observatory Protocol"
description: "Appraises attestation evidence and proof challenges and issues results bound to a nonce, an expiry and a scope."
url: https://nexusobservatory.com/nodes/verifier/
publisher: GCRI Canada
updated: 2026-11-18
---

[Observatory Protocol](https://nexusobservatory.com/)[Node registry](https://nexusobservatory.com/nodes/)Attestation and proof verifier

# Attestation and proof verifier

Appraises attestation evidence and proof challenges and issues results bound to a nonce, an expiry and a scope.

**Version**: 0.1.0-draft
**Status**: Draft specification
**Specification**: CC BY 4.0
**Code**: Apache-2.0
**Steward**: GCRI Canada
**Source**: obsp-0.1-foundation

[Onboard a node](https://nexusobservatory.com/onboarding/)

[Explore the schemas](https://nexusobservatory.com/schemas/)

## Role

Verifier role. (OBSP 0.1 §3) A verifier MUST bind the result to a nonce and an expiry. (OBSP 0.1 §5.1) A receipt MUST be signed and bound to the challenge, the evidence digests and the scope. (OBSP 0.1 §5.11)

**Class**: [Assurance](https://nexusobservatory.com/nodes/#c=assurance) Verifiers that appraise evidence and proof challenges.
**Protocol role**: `VERIFIER` Verifier. (OBSP 0.1 §3)
**Conformance profile**: OBSP-SITE carries the local verifier role for proofs. OBSP 0.1 defines no stand-alone verifier profile.
**Technology domains**: [Security, identity and supply chain](https://nexusobservatory.com/technical/domains/security/)

## Interfaces

The planes and bindings this type uses. Bindings are normative for OBSP 0.1; radio and link layers follow their own standards. (OBSP 0.1 §6)

| Interface | Binding | Sources |
| --- | --- | --- |
| Attestation | RATS passport and background-check models | (IETF RFC 9334; OBSP 0.1 §5.1) |
| Evidence | SCITT transparency receipts | (OBSP 0.1 §6; IETF SCITT) |

## Schemas it emits and accepts

Each document is a JSON Schema 2020-12 contract. Open one in the schema explorer. (JSON Schema 2020-12) Every request, command and event also carries a request context. (OBSP 0.1 §4.3)

### Emits

- [`attestation-result`](https://nexusobservatory.com/schemas/#s=attestation-result) AttestationResult
- [`proof-receipt`](https://nexusobservatory.com/schemas/#s=proof-receipt) ProofReceipt

### Accepts

- [`attestation-evidence`](https://nexusobservatory.com/schemas/#s=attestation-evidence) AttestationEvidence
- [`proof-receipt`](https://nexusobservatory.com/schemas/#s=proof-receipt) ProofReceipt
- [`request-context`](https://nexusobservatory.com/schemas/#s=request-context) RequestContext

## Lifecycle and conformance

OBSP-SITE carries the local verifier role for proofs. OBSP 0.1 defines no stand-alone verifier profile.

5.1 Join 5.2 Admit 5.3 Describe 5.4 Time 5.5 Observe 5.6 Qualify 5.7 Federate 5.8 Orchestrate 5.9 Correct 5.10 Exchange 5.11 Prove 5.12 Exit and decommission

Figure 1The twelve stages of the lifecycle. The stages in the type's profile are marked.

## Identity, attestation and security

Requirements of the security model that apply to this role. (OBSP 0.1 §8)

**Architecture**: Zero trust (NIST SP 800-207): every request is authenticated, authorised and logged; network position grants nothing (OBSP 0.1 §8)
**Workload identity**: SPIFFE-style SVIDs, rotated; no shared secrets (OBSP 0.1 §8)
**Supply chain**: SBOM, SLSA provenance, signed artifacts, TUF update metadata, SUIT for firmware (OBSP 0.1 §8)
**Privacy**: Observation data that can identify a person is a declared data class with its own policy; default is not to collect it (OBSP 0.1 §8)

## Interoperability profile and standards

The primary standards this type draws on. Alignment with a standard is stated as alignment. It is not an approval by the standards body. (OBSP 0.1 §13)

- [IETF RFC 9334](https://www.rfc-editor.org/rfc/rfc9334.html) Remote ATtestation procedureS (RATS) Architecture ( IETF RFC 9334 )
- [TCG TPM 2.0](https://trustedcomputinggroup.org/resource/tpm-library-specification/) Trusted Platform Module Library Specification ( TCG TPM 2.0 )
- [TCG DICE](https://trustedcomputinggroup.org/work-groups/dice-architectures/) Device Identifier Composition Engine architectures ( TCG DICE )
- [IETF SCITT](https://datatracker.ietf.org/wg/scitt/about/) Supply Chain Integrity, Transparency and Trust working group ( IETF SCITT )

## Not yet defined

What the protocol does not define for this type in version 0.1, stated as the specification states it. Nothing here is filled in from elsewhere.

- The proof verifier is an open gap in OBSP 0.1 (G-PROVE-1). ( OBSP 0.1 §9 )

## Across the consortium

Related pages on the consortium's other networks, in their own words.

**Standards Nexus Standards**: Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry. [nexustandards.com](https://nexustandards.com/)
**Index The Global Risks Index**: Country risk indicators that observations with provenance and quality can inform. [risksindex.com](https://risksindex.com/)
**Academy Risk Academy**: Training for implementers and operators of observing systems. [risksacademy.com](https://risksacademy.com/)
**Reports Reports at Nexus Standards**: Published evidence with provenance, citation and corrections. [nexustandards.com/nexus-reports](https://nexustandards.com/nexus-reports/)

## References

Sources cited on this page, in order of first citation. Addresses were last checked on the date shown.

1. [OBSP 0.1 §3: Participant roles](https://nexusobservatory.com/development/text/#c-3) Observatory Protocol 0.1 (draft), CC BY 4.0.
2. [OBSP 0.1 §5.1: Join](https://nexusobservatory.com/development/text/#c-5-1) Observatory Protocol 0.1 (draft), CC BY 4.0.
3. [OBSP 0.1 §5.11: Prove](https://nexusobservatory.com/development/text/#c-5-11) Observatory Protocol 0.1 (draft), CC BY 4.0.
4. [OBSP 0.1 §6: Wire bindings](https://nexusobservatory.com/development/text/#c-6) Observatory Protocol 0.1 (draft), CC BY 4.0.
5. IETF RFC 9334 Remote ATtestation procedureS (RATS) Architecture [www.rfc-editor.org/rfc/rfc9334.html](https://www.rfc-editor.org/rfc/rfc9334.html) Checked 2026-11-12
6. IETF SCITT Supply Chain Integrity, Transparency and Trust working group [datatracker.ietf.org/wg/scitt/about/](https://datatracker.ietf.org/wg/scitt/about/) Checked 2026-11-12
7. JSON Schema 2020-12 JSON Schema draft 2020-12 [json-schema.org/draft/2020-12](https://json-schema.org/draft/2020-12) Checked 2026-11-12
8. [OBSP 0.1 §4.3: Request context](https://nexusobservatory.com/development/text/#c-4-3) Observatory Protocol 0.1 (draft), CC BY 4.0.
9. [OBSP 0.1 §8: Security model](https://nexusobservatory.com/development/text/#c-8) Observatory Protocol 0.1 (draft), CC BY 4.0.
10. [OBSP 0.1 §13: Sovereign deployment for every operator and environment](https://nexusobservatory.com/development/text/#c-13) Observatory Protocol 0.1 (draft), CC BY 4.0.
11. TCG TPM 2.0 Trusted Platform Module Library Specification [trustedcomputinggroup.org/resource/tpm-library-specification/](https://trustedcomputinggroup.org/resource/tpm-library-specification/) Checked 2026-11-12
12. TCG DICE Device Identifier Composition Engine architectures [trustedcomputinggroup.org/work-groups/dice-architectures/](https://trustedcomputinggroup.org/work-groups/dice-architectures/) Checked 2026-11-12
13. [OBSP 0.1 §9: Gaps register](https://nexusobservatory.com/development/text/#c-9) Observatory Protocol 0.1 (draft), CC BY 4.0.

On this page

1. Role
2. Interfaces
3. Schemas it emits and accepts
4. Lifecycle and conformance
5. Identity, attestation and security
6. Interoperability profile and standards
7. Not yet defined
8. Across the consortium
9. References

- [View the source](https://nexusobservatory.com/development/text/)
- [Report a defect](https://nexusobservatory.com/development/take-part/)
- [Propose a change](https://nexusobservatory.com/development/proposals/)
- [Changes](https://nexusobservatory.com/governance/changes/)
