Skip to content

System Flow

What This Page Explains

This page shows how the major protocol components interact from sender construction to receiver recovery.

Why It Matters

New readers often understand the protocol faster from component interactions before reading byte-level or relation-level details.

Plain-Language Concept

A wallet prepares a confidential transition, a prover/runtime produces verifier-facing artifacts, BCH carries and settles the transaction, and the receiver wallet recovers the resulting note/state.

Technical Detail

High-Level Interaction Map

flowchart LR
    A[Sender wallet] --> B[Build confidential transition request]
    B --> C[Reference prover/runtime]
    C --> D[PIv1 and PBv1 artifacts]
    D --> E[BCH transaction carrier assembly]
    E --> F[Verifier acceptance path and host checks]
    F --> G[Broadcast and chain confirmation]
    G --> H[Receiver scan and recovery]

Component Responsibilities

  • Sender wallet: selects continuation source, prepares transition inputs, assembles transaction carrier.
  • Prover/runtime: consumes witness and public inputs, emits proof artifacts for the bounded lane.
  • Verifier path: validates accepted boundary formats and bounded statement checks.
  • BCH chain: provides settlement, ordering, and public observability anchor.
  • Receiver wallet: discovers candidate transactions and recovers confidential receiver-side state.

Boundary Clarification

  • The protocol contract defines semantics and boundaries.
  • Runtime and wallet are implementation layers under that contract.
  • Optional aggregation may be added later for observability reduction, but it is not required for base-path correctness.

Code Mapping