From 0191fa0a471fd8ec3103198d68e4df4f6af6f7e9 Mon Sep 17 00:00:00 2001 From: Daira Hopwood Date: Sat, 27 Mar 2021 16:56:21 +0000 Subject: [PATCH] Orchard book: minimal description of unified addresses. Signed-off-by: Daira Hopwood --- book/src/design/keys.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/book/src/design/keys.md b/book/src/design/keys.md index 00b338d4..a2b42d68 100644 --- a/book/src/design/keys.md +++ b/book/src/design/keys.md @@ -35,12 +35,14 @@ We make several structural changes, building on the lessons learned from Sapling for diversified addresses. Other than the above, Orchard retains the same design rationale for its keys and addresses -as Sapling, and the same bech32 encoding. For example, diversifiers remain at 11 bytes, so -that Orchard addresses are the same length as Sapling addresses. +as Sapling. For example, diversifiers remain at 11 bytes, so that a raw Orchard address is +the same length as a raw Sapling address. -The "human-readable part" for Orchard payment addresses is "zo", i.e. all addresses -have the prefix "zo1". Other prefixes and key formats will be described in section 5.6 -of the protocol specification. +Orchard payment addresses do not have a stand-alone string encoding. Instead, we define +"unified addresses" that can bundle together addresses of different types, including +Orchard. Unified addresses have a Human-Readable Part of "u" on Mainnet, i.e. they will +have the prefix "u1". For specifications of this and other formats (e.g. for Orchard viewing +and spending keys), see section 5.6.4 of the NU5 protocol specification [#NU5-orchardencodings]. ## Hierarchical deterministic wallets @@ -95,3 +97,4 @@ and more complicated "extended" ones defined by ZIP 32.) [BIP 32]: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki [BIP 44]: https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki [ZIP 32]: https://zips.z.cash/zip-0032 +[NU5-orchardencodings]: https://zips.z.cash/protocol/nu5.pdf#orchardencodings