From 5afefd55bfbe823a2e77cb189a77f55eaf0838b9 Mon Sep 17 00:00:00 2001
From: Deirdre Connolly <deirdre@zfnd.org>
Date: Mon, 30 Aug 2021 18:40:07 -0400
Subject: [PATCH] Specify Zebra Client will only support Unifed Addresses
 (#2706)

---
 book/src/dev/rfcs/0009-zebra-client.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/book/src/dev/rfcs/0009-zebra-client.md b/book/src/dev/rfcs/0009-zebra-client.md
index 427c05ae6..db31d469f 100644
--- a/book/src/dev/rfcs/0009-zebra-client.md
+++ b/book/src/dev/rfcs/0009-zebra-client.md
@@ -308,7 +308,7 @@ Supporting a wallet assumes risk.  Effort required to implement wallet functiona
     - generate unified address from a new seed phrase (or one provided by the user)
     - user can just backup seed phrase rather than a set of private keys
     - handles arbitrary keys from `zcashd` and other wallets, even if they weren't generated from a seed phrase
-    - handles Sprout funds without `zebra-client` having to support Sprout balances
+    - ~handles Sprout funds without `zebra-client` having to support Sprout balances~
     - startup is incredibly fast
         - sweep takes a few minutes to be confirmed
         - scanning the entire chain could take hours
@@ -335,6 +335,8 @@ Protocol, or something similar?
 viewing key (requires crypto). this could allow public access to the client
 endpoint
 
+- Use Unified Addresses only, no legacy addrs.
+
 <!-- Think about what the natural extension and evolution of your proposal would -->
 <!-- be and how it would affect Zebra and Zcash as a whole. Try to use this -->
 <!-- section as a tool to more fully consider all possible -->