ZecPad Protocol Infrastructure

Open infrastructure for shielded assets on Zcash. ZecPad is building the verification, indexing and private wallet layers required to make ZSA usable without turning an application database into the source of truth.

ZSA DEVELOPMENT NETWORKINDEXER LIVERE-INDEXABLEPULL-PROOFPRIVATE CLIENT SCANNING

Overview

ZSA defines how assets can be issued and transferred under the Zcash protocol. ZecPad starts where the consensus specification stops: discovery, reconstruction, metadata resolution, wallet synchronization, witnesses, private ownership detection and independent verification.

Design goal

Public claims should be independently reconstructible. Private ownership should remain private to the wallet.

Core separation

Public protocol data

blocks
transactions
issuance actions
issuer
assetDescHash
issued amount
finalization
commitments
nullifiers

Private wallet data

spending keys
viewing capability
owned notes
note plaintexts
private balances
recipient relationships
transfer authorization

ZecPad infrastructure indexes public protocol data. It does not need a user's spending keys to determine the public history of an asset.

Re-index

The ZecPad database is not the ZSA ledger. The public index is a derived view and can be reconstructed from network data.

ZSA Network
     │
     ▼
Block Scanner
     │
     ▼
Issuance Parser
     │
     ▼
Public Asset State
     │
     ▼
ZMD-1 Resolution
     │
     ▼
Searchable Index

If an index is lost or replaced, a clean scanner can replay public chain history and reconstruct the observable asset state.

Pull-proof verification

An API response is a convenience, not proof. ZecPad links indexed claims back to independently retrievable protocol evidence.

ZecPad Asset
     │
     ▼
Transaction Reference
     │
     ▼
Public ZSA RPC
     │
     ▼
Issuance Action
     │
     ├── issuer
     ├── assetDescHash
     ├── amount
     └── finalize
     │
     ▼
Independent Verification

Reproducible asset identity

Asset identity is derived from protocol inputs rather than invented by the ZecPad database.

assetDescHash = BLAKE2b-256(
  personalization = "ZSA-AssetDescCRH",
  message = asset_desc
)

AssetId = (issuer, assetDescHash)

A verifier can reproduce the descriptor hash and compare it with the issuance data returned by the network.

Metadata resolution

ZMD-1 connects the protocol commitment to the information required to present an asset. The chain remains the cryptographic anchor while manifests and media remain independently retrievable and verifiable.

ZSA assetDescHash
       │
       ▼
   descriptor
       │
       ▼
     ZMD-1
       │
       ├── collection
       ├── item
       ├── manifest
       ├── media
       └── traits

Private wallet scanning

The public indexer can observe candidate shielded data without publishing an ownership graph. The wallet privately determines which notes belong to it.

Public Network
      │
      ▼
Candidate Shielded Data
      │
      ▼
Private Client Scanner
      │
      ├── trial decrypt
      ├── identify owned notes
      └── derive wallet state

Witness infrastructure

Public infrastructure supplies synchronization material. Proof construction and spending authority stay with the client.

Public Chain State
       │
       ▼
Indexer / Witness Service
       │
       ▼
Browser Wallet
       │
       ├── private note
       ├── witness
       ├── proof
       └── authorization

Nullifiers and spent state

The wallet can derive the nullifier relevant to an owned note and query public spent state without asking the server to determine wallet ownership.

Owned Note (private)
       │
       ▼
Expected Nullifier
       │
       ▼
Public Nullifier State
       │
       ▼
Spent / Unspent (local)

Client-side transaction authority

Private notes, keys, proof construction and authorization stay with the wallet. Public infrastructure receives only the completed transaction required for broadcast and indexing.

Broadcast is not custody

A broadcaster does not need a seed phrase, spending key, wallet backup or private note plaintext.

Rebuildability

A correct independent indexer consuming the same finalized public chain data should converge on the same public asset facts.

             ZSA Network
            /           \\
           ▼             ▼
  ZecPad Indexer   Independent Indexer
           │             │
           └──────┬──────┘
                  ▼
          Protocol Evidence

Testnet protocol loop

The development network is the protocol laboratory. ZecPad uses it to exercise the complete lifecycle repeatedly, not only to demonstrate that an issuance transaction can parse.

ISSUE → INDEX → RE-INDEX → PULL PROOF → VERIFY
  ↑                                      ↓
VERIFY ← NULLIFIER ← NEW BLOCK ← BROADCAST ← TRANSFER
                                         ↑
                         WITNESS ← OWNED NOTE ← PRIVATE SCAN

Protocol principles

The database is not the ledger.
Public state must be reconstructible.
Indexed claims must lead to protocol evidence.
Asset identity must be independently reproducible.
Private ownership is resolved client-side.
Spending authority stays with the wallet.
Witness infrastructure does not imply custody.
Broadcasting does not require private keys.
Metadata resolves back to cryptographic commitments.
Testnet proves the complete lifecycle.