Orange Anchor  ·  Document Suite

Canonical Document Suite

The full corpus for Bitcoin-Anchored Collateral Commitments and the Orange Anchor instantiation

← back to economic argument
These are the load-bearing documents. Read in any order; the suite is internally consistent. Architecture and protocol surfaces are stable for review and integrator implementation. Forthcoming items are listed at the bottom.

Foundational

Introduction
A concise non-technical entry point. Useful for orientation before reading the white paper or construction document.
White Paper
The full architectural argument. Establishes per-commitment cost-linearity as a structural — not parametric — consequence of composing time-binding, memory-hardness, and physical-state witnessing against a stated threat model. Defines the in-scope adversary and the explicitly bounded acknowledged limits.
v2.4 · markdown · PDF version
Construction
The construction paper. Specifies the bracketed interval (lightweight 6-block and heavyweight 144-block tiers), the memory-hard work profile, sensor-coherence acceptance thresholds, anchor-transaction confirmation depth, and reorg handling. The mechanical basis for the cost-positivity property.
v1.9 · markdown · /docs/BACC_1_9.md
Lexicon
Canonical terminology. Defines envelope, burn, anchor, commitment, attribution, check-in, cosign. Reconciles the two-phase architectural framing with the construction-level burn / establishment / verification phasing. Authoritative for any term in the suite.

Attribution & Operators

BAVAI Reference
Design specification for the public attribution layer. Sparse-Merkle structure in the lineage of Certificate Transparency and CONIKS; Bitcoin-anchored epoch roots; authenticated range-query semantics sufficient to detect omission. Operator-neutral by construction.
v1.0 · markdown · /docs/BAVAI_Reference_v1.0.md
Operator Specification
Normative operator behaviour. Specifies proof formats, the inclusion-vs-construction verification boundary (§7), and the proof_internals slot layout. Operators are untrusted for correctness; the Bitcoin chain is the trust anchor.

Integration & Use

Interaction Patterns
The two practical patterns: check-in (presenting a commitment as a credential) and cosign (binding a commitment to a DID, verifiable credential, or Nostr npub). Demonstrates that the primitive composes with — rather than replaces — existing identity frameworks.
Integration Brief
Architectural framing for systems that wish to recognise commitments as credentials. Lays out the verifier-policy surface: weighting, attribution interpretation, and composition with existing account identifiers.
Widget Specification
Embeddable verifier widget. Technical specification for systems that wish to consume commitments at point of use without bespoke integration work.

Calibration & Audit

Calibration Model
Defines the in-scope adversary (substantial capital, virtualisation tooling, operational sophistication) and the methodology by which the per-commitment cost floor is composed from a finite set of structural levers. Calibration is parametric; cost positivity is structural.
Audit Methodology
Methodology for auditing verifier policies and accepting-system behaviour. For any party evaluating an Orange Anchor deployment against its stated security claims.

Forthcoming

Calibration Annex · Adversarial Scenario Analysis · Integrator Quick Start · Orange Anchor Technical Paper · Reference Implementation. Architecture and protocol surfaces in the current suite remain stable across these additions.