This details the changes to the transaction digest algorithm for the
ZSA protocol.
- A new branch is added for hashing the information in a transaction
related to issuance.
- Some branches are added and modified in the orchard_digest subtree to
account for the additional Asset Base value that needs to be hashed.
This adds in the reference links to the test vectors and reference implementations corresponding to the ZSA Protocol. Some corrections to the notation for better consistency and some updates to the formulae for syncing with the implementation are also included here.
This rearranges and rewrites various sections of the ZIP to make it more in line with the suggestions in ZIP 0.
It also updates the Split Notes, Circuit Statement and Burn Mechanism sections with more information.
This covers the changes made to derive the issuance key independently of the Orchard key structure, using the techniques from [ZIP 32](https://zips.z.cash/zip-0032).
This reverts commit 7064e8229a, reversing
changes made to 82f98ec91b.
Revision 1 will be amended to include a change to the Human-Readable
Part of UA/UVK encodings in order to ensure that MUST-understand
metadata cannot be ignored by existing wallets.
This change adds metadata that allows a user to specify either an expiry
height or an expiry time (or both) for their addresses, and specifies
how wallets should interpret expiry metadata.
Co-authored-by: Daira Emma Hopwood <daira@jacaranda.org>
Reserve a range of metadata typecodes that unified container parsers
must understand; if a parser does not understand a typecode in the
specified range, then it must treat the entire unified address as
unsupported.
Co-authored-by: Daira Emma Hopwood <daira@jacaranda.org>
* ZIP 320: use normal block quote for modified sections of ZIP 316 rather
than a literal block.
* ZIP 320: add References heading.
* ZIP 320: fix incorrect markup in two references.
* CSS: adjust padding of block quotes and give them a grey background
(light grey for light theme, dark grey for dark theme).
* Regenerate README and index.
Signed-off-by: Daira Emma Hopwood <daira@jacaranda.org>
This provides two alternatives for how to implement
transparent-source-only addresses:
* A new, separate `bech32m` encoding with the `tex` human-readable part
* A modification to Unified Addresses to support the transparent-source
requirement.
The git push at the end didn't have permission to push back to the source repo, even if the PR author granted permission for contributors to push to the source branch.
This gets the Dockerfile behind the render workflow to build again.
I also renamed the workflow because it described only building the PDF, but it also builds all the .html files.