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>
This commit is contained in:
teor 2021-04-21 08:08:12 +10:00 committed by GitHub
parent 2e6cdb3945
commit ef5f47ca08
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions

View File

@ -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"