Client-Side Validation
This lens is for systems that stop asking the base chain to replay full history and instead make counterparties carry proofs, state objects, or transfer lineage themselves.
Questions worth asking:
- Who carries the state object or proof after each transfer?
- What minimal artifact still hits chain: commitment, nullifier, seal, anchor, or dispute hook?
- How does a recipient check ancestry, spendability, and double-spend risk without full global replay?
- Which wallet, publisher, coordinator, or validator quietly becomes the real trust bottleneck once history moves offchain?
Curated comparison set
- Canonical Bitcoin client-side-validation systems: rgb and shielded-csv
- State-handoff cousins where the wallet and recipient inherit more of the validation burden: ark and mercury-layer
- Keep CoinJoin nearby but separate. It rhymes on coordination and wallet handoff, but it is not the same object model: bitcoin-coinjoin-coordination