Skip to content

docs: add comprehensive Address Types reference - #1906

Open
qwenbona wants to merge 1 commit into
ZecHub:mainfrom
qwenbona:add/address-types-guide
Open

docs: add comprehensive Address Types reference#1906
qwenbona wants to merge 1 commit into
ZecHub:mainfrom
qwenbona:add/address-types-guide

Conversation

@qwenbona

Copy link
Copy Markdown

Summary

Adds a new ~1700-word technical reference on Zcash address types to site/Zcash_Tech/.

Content:

  • t-addresses: Base58Check, t1/t3 prefixes, UTXO model, no privacy
  • z-addresses (Sapling): Bech32, zs1 prefix, trusted-setup SNARK
  • Orchard: Halo 2 proofs, no trusted setup, lives inside UAs
  • Unified Addresses (ZIP 316): u1 prefix, Bech32m, multi-receiver container, automatic receiver preference
  • Comparison table: prefix, encoding, value pool, on-chain visibility, trusted setup, recommended usage
  • Practical guidance: which format to use and when
  • Further Reading: links to ZIP 316, ZIP 32, ZIP 224, protocol spec

Why:

The existing guides/Visualizing_Zcash_Addresses.md (78 lines) focuses on visual screenshots. This article provides the technical depth — encoding schemes, protocol differences, and privacy guarantees — that developers and power users need.

Complements rather than duplicates the existing guide.

New ~1700-word article covering:
- t-addresses (transparent): prefixes, encoding, UTXO model
- z-addresses (Sapling): Bech32, trusted setup, privacy guarantees
- Orchard protocol: Halo 2, no trusted setup, UA integration
- Unified Addresses (ZIP 316): multi-receiver, Bech32m, receiver preference
- Comparison table across all dimensions
- Practical guidance on which format to use
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant