Skip to content

Model C Architecture

What This Page Explains

This page explains Model C in plain technical language: why direct self-sovereign spend is the base path, what optional aggregation means, and what is implemented now versus later.

Why It Matters

Model C is the publication frame for this repo. Readers need to understand what the base path guarantees without assuming optional services.

Plain-Language Concept

Model C means a wallet can perform the confidential spend directly. The base path does not require a shared operator. Aggregation is a later optional service layer, not a requirement for basic use.

Technical Detail

Trust Model

  • Protocol contract: defines transition semantics and public boundary.
  • Reference prover/runtime: implements the published bounded proving/verifying profile.
  • Reference wallet: implements transaction assembly, host checks, and recovery workflows.
  • Optional aggregation: may later reduce observability, but is not in today’s trust base.

Why Direct Spend Is The Base Path

  • keeps authority anchored to user-controlled wallet flows
  • avoids making basic operation depend on a shared coordinator
  • supports truthful publication of what is already live versus still planned

BCH Constraints That Shape The Design

The current design is bounded by BCH script and transport constraints (including carrier size and script-path practicality), so the active verifier lane is intentionally bounded and profile-specific.

Bounded Lane And Current Status

  • active lane: Trustless Relation Query 1 (TRQ1), backend id 2
  • currently bounded to two source notes
  • first-hop and follow-on direct-spend flows are live-validated
  • verifier path is structural/kernel-facing for the published profile, not a final arbitrary-profile verifier completeness claim

Implemented Now vs Planned Later

  • Current truth: bounded direct-spend path is operational and published.
  • Proof-enforced semantics: bounded transition semantics are enforced in the active lane.
  • Artifact-described behavior: additional artifact fields remain descriptive.
  • Public observables: graph/economics/topology remain visible on BCH Layer 1.
  • Future optional aggregation: deferred, optional service layer for observability reduction.

Code Mapping