Cryptographic Architecture · Terminology & Taxonomy · v1.0

Terminology & Taxonomy

Cryptography is the science of constructing protocols that resist adversarial behavior. This document maps REF's operations to the six primary subfields of modern cryptography and establishes the shared vocabulary for evaluating the protocol's architecture.

Classification
Public Reference
Methodology
Domain Engineering (Shared Vocabulary)
Companion
Cryptographic Stack Architecture
Primitives
6 subfields · 5 active in REF
Architectural Position
REF is a signing, commitment, and proving system that uses cryptographic primitives for authentication and integrity — not confidentiality. This document formally defines the taxonomy of operations utilized within the protocol.
01 — Cryptographic Taxonomy

Six Subfields, Five Active in REF

Modern cryptography encompasses six primary subfields, each addressing a distinct security property. REF's architecture draws on five of these subfields. The sixth — encryption, which provides confidentiality — is not a core protocol mechanism.

Cryptography

The science of constructing and analyzing protocols that resist adversarial behavior

Katz & Lindell · Goldreich — standard definition
Digital Signatures
Authentication · Non-repudiation
Active
Binding purchase attestations to merchant identity. Providing authentication, integrity, and non-repudiation for every review token.
Ed25519 (production) · BLS12-381 (Phase 2)
Hash Functions
Integrity · Binding
Active
Creating deterministic, one-way commitments that bridge the attestation layer to the ZK proof layer with domain separation.
SHA-256 (attestation) · Poseidon (circuits)
Zero-Knowledge Proofs
Verification without disclosure
Active
Proving purchase-to-review binding without revealing PII, purchase details, or the underlying witness.
Groth16 / BN254 · 1,155 constraints · 742-byte proofs
Commitment Schemes
Binding · Hiding
Active
Allowing consumers to commit to a token value while keeping it hidden until review submission — preventing front-running.
Poseidon commitments · Pedersen (optional)
Consensus Protocols
Byzantine agreement
Active
Reaching BFT agreement on token inclusion using cryptographic quorum certificates with rotating committees.
PBFT · BLS-aggregated QCs · Ed25519 sigs
Encryption
Confidentiality
Not Primary
Transforming plaintext to ciphertext. Present for data-at-rest and data-in-transit protection, but not a core protocol mechanism.
AES-256-GCM (infrastructure only)
Precision Note

AES-256-GCM is deployed for standard data-at-rest and TLS transit protection, as in any production system. However, encryption does not appear in the REF protocol's core operations — token generation, proof construction, consensus, or verification. The distinction is between infrastructure encryption (universal) and protocol-level cryptographic operations (REF-specific).

02 — Core Protocol Operations

Five Cryptographic Verbs

REF's protocol-level operations are signing, committing, proving, verifying, and reaching consensus. Each is a cryptographic operation. None is encryption.

Sign
Ed25519
attestations
Commit
Poseidon
token binding
Prove
Groth16
ZK verification
Agree
PBFT
consensus
Encrypt
Not a core
protocol operation

The operations that make it impossible to review without purchasing are signing, committing, proving, and reaching consensus. These four verbs define the protocol boundary. Encryption operates below this boundary, at the infrastructure layer, where it serves the same function it serves in any secure system.

03 — Industry Precedent

Protocols Called "Cryptographic" Without Encryption as Primary Mechanism

REF's taxonomic position is standard. Several foundational protocols in wide deployment are universally described as "cryptographic" despite relying primarily on signatures, hashing, and consensus rather than encryption.

Protocol
Described as "Cryptographic"
Primary Mechanism
Bitcoin
"Cryptocurrency"
Hashing + signatures + consensus
Certificate Transparency
"Cryptographic log"
Merkle trees + signatures
TLS 1.3
"Cryptographic protocol"
Key exchange + signatures + then encryption
Git (signed commits)
"Cryptographic integrity"
SHA hashing + GPG signatures
REF Protocol
"Cryptographic authentication"
Signatures + ZK proofs + commitments + consensus

In each case, the term "cryptographic" refers to the broader field — the use of mathematically grounded primitives to resist adversarial behavior — not specifically to encryption. REF follows this established convention.

04 — Formal Summary

Position Statement

Protocol Classification
Cryptographic Review Authentication
Uses cryptographic primitives (signatures, proofs, commitments, consensus) to bind reviews to verified purchases.
Primary Security Properties
Authentication · Integrity · Non-repudiation
Provided by Ed25519 signatures, Poseidon commitments, Groth16 proofs, and BFT consensus with quorum certificates.
Confidentiality Role
Infrastructure only — not protocol-level
AES-256-GCM protects data at rest and in transit. Zero-knowledge proofs provide selective disclosure without encryption.
Taxonomic Basis
Katz & Lindell · Goldreich
Cryptography = protocols resisting adversarial behavior. Encryption is one subfield. REF utilizes five of six.
"The question is not 'what encryption does REF use?' The question is 'what mathematical operations make it impossible to review without purchasing?' Those operations are signing, committing, proving, and reaching consensus — not encrypting."
— Core Architectural Principle