Skip to content

Security Posture Overview

This section documents the current direct-spend boundary and claim limits.

Current Status

  • identity safe/default path is commitment-authoritative
  • runtime-proof-authoritative tx assembly is landed
  • verifier/export boundary hardening against conservation-opening leakage is landed
  • bounded two-input proof-alignment milestone is materially complete for current lane
  • first-hop and follow-on live validations are present

Explicit Limits

  • repeated no-top-up continuation is reserve-limited
  • private reserve replenishment is not yet deployed in direct spend
  • public graph/shell/settlement observables remain visible
  • broad system-level "fully zero-knowledge deployed system" claim is out of scope

BCH-Fit And Conservation Caveat

  • BCH L1 fee and topology observables remain public constraints on direct-spend deployment.
  • Bounded proof alignment does not remove public fee burn and shell economics disclosure.
  • Conservation semantics are published for the bounded lane; broader generalized claims are out of scope for current milestone.

Reading Order

  1. Claim Boundary
  2. Direct-Spend Hardening Journey