Skip to content

[ZIP 230] Adding back the assetBase field to the IssueNote structure#1081

Closed
vivek-arte wants to merge 1 commit into
zcash:mainfrom
QED-it:zsa1
Closed

[ZIP 230] Adding back the assetBase field to the IssueNote structure#1081
vivek-arte wants to merge 1 commit into
zcash:mainfrom
QED-it:zsa1

Conversation

@vivek-arte
Copy link
Copy Markdown
Contributor

The merge of #987 happened to delete the table entry for the Asset Base in the Issue Note Description of ZIP 230. This PR adds it back.

The merge of zcash#987 happened to delete the table entry for the Asset Base
in the Issue Note. We are adding it back here.
Comment thread zips/zip-0230.rst
+-----------------------------+------------------------------+------------------------------------------------+---------------------------------------------------------------------+
| 8 |``value`` |``uint64`` |The amount being issued in this note. |
+-----------------------------+------------------------------+------------------------------------------------+---------------------------------------------------------------------+
| 32 |``assetBase`` |``byte[32]`` |The encoding of the Asset Base. |
Copy link
Copy Markdown
Collaborator

@str4d str4d Sep 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The removal was an intentional choice by the ZIP Editors: 80ac162 (see commit message for rationale).

If you have alternative rationale for having it in the format, please provide it. Otherwise, close this PR.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see - there is a benefit in terms of reduced transaction size, and the removal of that consensus check.

The way the issuance bundle is structured, however, it is not possible to completely specify the constituent Issue Notes as they are parsed -- the issuer identifier (issuer) field is only parsed after the entire vIssueActions vector, but it is needed to be able to construct the Issue Note.

We can avoid this if we reorder the issuance bundle to start first with issuer, then the vIssueActions vector, then the issueAuthSig; accompanied by the appropriate change in the digest algorithm. (Or we can include the asset base in the Issue Note, as in this PR)

I prepared this change in #1086 , along with some other necessary corrections (such as the note size being changed to 115 bytes from 147 bytes, and the removal of the now extra consensus checks).

I'd appreciate if you could review and let me know what you think works best, and we can close one of these PRs.

@vivek-arte
Copy link
Copy Markdown
Contributor Author

Closing in favour of #1086

@vivek-arte vivek-arte closed this Sep 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants