Skip to main content

Architecture and protocol mechanics

From public funds to private state​

Core does not expose a readable private balance per wallet. It registers Note/Credit commitments and verifies private conditions through ZK proofs. Wallets derive their views from authenticated deliveries, membership and consumption state.

Application: accounts, signing, authenticated decryption, persistence
│
├─ SDK ── local prover ── authorized proof and transaction
│ │
│ direct / Broadcaster submission
│ │
└─ Protocol RPC ←── Core contracts and chain events

IPP requests and receipts ←── Facilitator evaluates payment evidence
Scoped source claims ←── Provenance evidence and recognition

Chain RPC provides blocks, code, receipts and state calls. Protocol RPC adds protocol indexes, candidate discovery and membership data. They are different APIs with different trust roles.

Commitments, membership and nullifiers​

A private Note opening contains asset, amount and receiving identity material. Its commitment is inserted into the instance’s append-only tree. Spending proves valid membership and publishes a nullifier to prevent reuse. Acceptance of a historical root does not establish current spendability.

Credit holds debit authority with limits and expiry. A draw consumes old states and produces successors and a payment Note. Revocation independently sets the original grant slot; an old membership root cannot bypass effective revocation.

Public observations​

Funding sources, Shield amount information, commitments, nullifiers, public withdrawals, Credit payer/grouped debit facts, transaction timing and co-occurrence can remain observable. Keeping openings private does not hide every amount, timing or network correlation.

Relaying changes submission but does not erase application network metadata or voluntary disclosures. Source proofs do not establish unrestricted real-world identity or legal conclusions.

Three state layers​

LayerQuestionVerification
Chain executionDid the call succeed and remain canonical?Successful receipts, block identity and native confirmation
Wallet assetsAre credentials authentic, unconsumed and unreserved?Authenticated decryption, membership, nullifiers, revocation and journals
Payment requestWere the requested terms met before cutoff?IPP bindings, evidence validation and receipts

Do not substitute success at one layer for another. The quickstart follows all three.