From ef5f47ca08d49772cc243e4dde1bf86d98632cd4 Mon Sep 17 00:00:00 2001
From: teor <teor@riseup.net>
Date: Wed, 21 Apr 2021 08:08:12 +1000
Subject: [PATCH] ZIP-244: Clarify sapling shared anchor hashing (#490)

* ZIP-244: Clarify sapling shared anchor hashing

Unlike the orchard shared anchor, the sapling v5 transaction shared anchor
is hashed into *each* spend.

* Uppercase Sapling and Spend

Co-authored-by: Deirdre Connolly <durumcrustulum@gmail.com>
---
 zip-0244.rst | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/zip-0244.rst b/zip-0244.rst
index 23213bb1..c24425a1 100644
--- a/zip-0244.rst
+++ b/zip-0244.rst
@@ -267,6 +267,9 @@ signature(s). For each spend, the following elements are included in the hash::
    T.3a.ii.2: anchor (field encoding bytes)
    T.3a.ii.3: rk     (field encoding bytes)
 
+In Transaction version 5, Sapling Spends have a shared anchor, which is hashed
+into the sapling_spends_noncompact_digest for *each* Spend.
+
 The personalization field of this hash is set to::
 
   "ZTxIdSSpendNHash"