BCH Confidential Direct Spend

Bounded direct-spend milestone

Privatize BCH with a verifiable direct-spend path

Build Private Send flows where Private Balance is tracked internally, proof artifacts are transaction-bound, and public surfaces are classified truthfully.

Try the Verifier Read Docs and Specs

Private Balance is tracked internally as confidential notes. Wallet BCH and Fee Support remain explicit when used.

Current published scope

  • Live first-hop and follow-on direct spend
  • Bounded two-input proof-enforced accounting lane
  • Runtime-proof-authoritative transaction path
  • Truthful public vs hidden artifact boundary

What this proves today

Private Send semantics

Recipient amount, sender private change, and continuation reserve are proof-bound in the published bounded lane.

Transaction-bound proof carrier

Runtime proof artifacts are assembled and checked against the same transaction path used for broadcast.

Truthful public boundary

Shell carrier sats, miner fee sats, and Fee Support remain explicit public observables on BCH L1.

Try the verifier

Paste a bounded direct-spend package JSON and run browser-side boundary checks.

Validation result

Waiting for input

    This demo validates bounded package shape and claim boundary signals in browser JavaScript. It does not run a full cryptographic prover.

    Why it matters

    This path demonstrates practical confidential transfer semantics on BCH while keeping claim boundaries explicit. It is a protocol-first base path: wallets can integrate now, and later optional aggregation can target observability reduction without changing the trust base.

    Hidden today

    • Private Balance transfer semantics in the bounded lane
    • Sender private change semantics in the bounded lane
    • Continuation reserve semantics in the bounded lane

    Public today

    • BCH graph and settlement topology
    • Shell carrier sats and miner fee sats
    • Fee Support inputs and change when used

    Bounded now

    • Bounded two-input proof-enforced milestone lane
    • Live-validated first-hop and follow-on direct spend
    • No broad full-system zero-knowledge claim

    Future work

    • Repeated no-top-up sustainability improvements
    • Private reserve replenishment path
    • Later optional aggregation for observability reduction

    Get started

    Technical docs and specs

    Read the protocol publication and full detailed spec corpus.

    Open MkDocs site

    Reference Protocol Runtime

    Integrate proving and verification through official runtime APIs.

    Open runtime docs

    Reference Wallet Integration

    Build Private Send orchestration and receiver recovery flows.

    Open wallet docs