zkCoins is best understood as a productized path toward Shielded CSV, not as a generic Bitcoin privacy wallet. The docs make the architecture explicit: sender-side proof generation, offchain proof handoff, receiver-side client verification, and minimal Bitcoin publication for double-spend prevention.
The strongest reusable mechanism is proof-carrying data for coin history. The protocol summary stresses that proof size remains constant rather than growing with transaction ancestry, which is the main analytical split from earlier client-side-validation families.
The 64-byte nullifier framing is important because it shows how aggressively the design tries to shrink Bitcoin’s role. The chain becomes an ordering and anti-double-spend surface, while balance logic and validity checking move to counterparties.
The most important caveat is implementation status. The project’s own PROTOCOL_STATUS.md says the current zk-coins stack still lacks several core paper features, including the full nullifier system, NISSHAC half-aggregation, conditional NAV, trustless publisher-fee flow, and scanner-side cryptographic verification.
That means the current product should be treated as a serious implementation lineage and deployment path, but not as a finished realization of the full Shielded CSV paper.
Specific source signals worth retaining
docs.zkcoins.app/: clearest high-level articulation of the wallet’s purpose and the onchain-footprint contrast with normal Bitcoin transactions.
docs.zkcoins.app/protocol/: best short-form description of Shielded CSV’s core ideas, predecessor lineage, constant-size proofs, and 64-byte-nullifier framing.
zk-coins/research: useful because it packages the upstream paper, related articles, historical code lineages, and the current project’s source hierarchy in one place.
PROTOCOL_STATUS.md: the most analytically important source because it separates what the paper specifies, what the current implementation fully supports, what is partial, and what remains unimplemented.
ePrint 2025/068 / shieldedcsv.org: canonical protocol references for the underlying Shielded CSV mechanism beyond the wallet UX layer.
Why this entry belongs in the corpus
It adds a sharp Bitcoin-native comparison point where privacy and scalability come from moving validity proofs and state interpretation offchain rather than from launching a new chain, sidechain, or opt-in mixer.
It strengthens the corpus around client-side validation, proof-carrying transaction history, and minimal-onchain anti-double-spend layers.
The durable insight is that zkCoins should be analyzed as a control-plane split between sender proofs, receiver validation, publisher batching/nullifier publication, and Bitcoin ordering — with a still-important gap between paper design and current deployment.