QRVP-1 • QR Verification Protocol • Specification Layer

QRVP-1 Protocol

QRVP-1 defines how QR-based identifiers are resolved into verifiable records through a registry-backed verification network.
It establishes deterministic resolution, structured verification responses, and separation between identifiers, records, and results.

—

Purpose of the Protocol

QRVP-1 exists to replace non-deterministic QR redirects with a verifiable resolution process.

Traditional QR systems:

Resolve directly to URLs
Depend on endpoint trust
Do not validate issuer identity
Do not support record lifecycle states

QRVP-1 introduces:

Registry-anchored resolution
Verification-aware responses
Issuer-linked records
Deterministic lookup paths

Resolution Model

Scan → Identifier → Resolver → Registry → Validation → Result

The protocol ensures that verification results are derived from authoritative registry data rather than uncontrolled redirects.

—

Protocol Principles

Deterministic Resolution

Each identifier resolves through a defined verification path.

Registry Authority

Canonical records exist independently of presentation layers.

Issuer Binding

Records are associated with identifiable issuing entities.

Verification Output

Structured responses communicate status and metadata.

—

Core Components

Identifier

QR-V encoded reference

Resolver

Routes request

API Layer

Verification processing

Registry

Canonical record store

Result

Verification response

—

Identifier Format (Conceptual)

QRVP-1 identifiers represent references to registry-backed records.

qrv:///

namespace: issuer or system domain
record_id: unique identifier for the record

Identifiers do not contain verification data. They reference records that are resolved through the verification network.

—

Verification Response Model

Response Fields

Status
Issuer identity
Record type
Timestamp
Metadata
Verification path

The response is designed to be machine-readable and human-interpretable.

Example Response

{
  "status": "verified",
  "issuer": "Example Institution",
  "record_type": "certificate",
  "timestamp": "2026-03-19T14:00:00Z",
  "record_id": "QRV-XXXXXXXX",
  "verification_path": "registry"
}

—

Lifecycle States

Verified — Record exists and is valid
Revoked — Record invalidated by issuer
Expired — Record no longer valid due to time
Not Found — No registry match

—

Protocol Scope

QR-based identifier resolution
Registry-backed record verification
Issuer-linked credential systems
Product authenticity verification
Document validation workflows
API-based verification systems

—

Build on QRVP-1

Integrate verification into your applications, issuance workflows, and infrastructure.

Developer Docs

API Documentation

Enterprise Integration

—

QRVP-1 Protocol • QR-V™ Verification Network • Registry-Based Resolution Standard