-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First round of modifications on ZIP227 #20
Conversation
…d circular dependency between ZIPs
✅ Deploy Preview for zcash-zips-qedit ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
zip-0227.rst
Outdated
Varies nNotes compactSize The number of notes in the issuance action | ||
TBD noteSize byte The size, in bytes, of a Note |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per: #20 (comment) it'd be nice to document the noteSize
@@ -263,6 +275,7 @@ For each `IssueAction` in `IssueBundle`: | |||
|
|||
- check that :math:`0 < \mathsf{assetDescSize} <= 512`. | |||
- check that :math:`\mathsf{asset\_desc}` is a string of length :math:`\mathsf{assetDescSize}` bytes. | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
asset_desc
is defined as "UTF-8 encoded string, of size assetDescSize bytes" in the table. Yet, it's Byte size is set to Varies
and its type is set as byte
.
It seems like it's Byte size shouldn't be Varies
but assetDescSize
instead and it's type should be a byte array byte[assetDescSize]
zip-0227.rst
Outdated
Varies nNotes compactSize The number of notes in the issuance action | ||
TBD noteSize byte The size, in bytes, of a Note |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per: #20 (comment) it'd be nice to document the noteSize
9a10f3f
to
f81e13b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved with comments, see above.
Thanks @vivek-arte, but then, why is notes used with single backticks? (same for IssueBundle, IssueAuthSig etc) |
You're right, the use of single backticks was confusing and unnecessary. I've tried to improve on those parts in PR#28, moving to double backticks for the table items. The I'm also wondering how strict we need to be about using double backticks only for table entries -- for example, in the above PR, I changed I'm not sure there is a single consistent choice throughout all the prior ZIPs, but if we pick a strict format and stick to it that would be good too. We should document it somewhere, probably in the issue #25 discussion. I'm not sure we should include it in the Rationale section of either ZIP, but we can bring it to the attention of the ZIP editors, and they could choose if they want to make these conventions uniform going ahead and so on. |
As an update, also see this comment made by Daira on the |
Improved style and content of ZIP 227. --------- Co-authored-by: Vivek Arte <vivek@qed-it.com>
Improved style and content of ZIP 227. Co-authored-by: Vivek Arte <vivek@qed-it.com>
As per the title, this PR does a first round of changes on ZIP 227.
Each commit does one change, so we can easily cherry pick/rebase to keep the relevant ones.