-
Notifications
You must be signed in to change notification settings - Fork 251
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
zcash_address: Add support for ZIP 316, Revision 1 #1135
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1135 +/- ##
==========================================
- Coverage 53.23% 53.10% -0.14%
==========================================
Files 168 168
Lines 20945 21276 +331
==========================================
+ Hits 11150 11298 +148
- Misses 9795 9978 +183 ☔ View full report in Codecov by Sentry. |
87bcae5
to
3314d2a
Compare
3314d2a
to
e78a5ec
Compare
e78a5ec
to
776ec12
Compare
Returning to draft status to update the parsing of the HRP for ZIP 316, Revision 1 |
93225df
to
2833744
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.
Some changes needed — see the "(blocking)" comments.
3c90d56
to
7852a31
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.
Reviewed 7852a31.
assert_eq!( | ||
Address::parse_internal(Address::MAINNET, &encoded[..]), | ||
Address::parse_internal(Address::MAINNET_R0, &encoded[..]), |
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.
(Just picking this test as an example)
I'm a little unhappy about the lack of Revision 1 tests. I think we'll be fine for now (particularly if my earlier suggestion to generate arbitrary revisions for proptests is accepted), but please open an issue for expanding testing to cover revision 1.
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.
Opened #1647
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.
I actually think it's essential to have tests covering the differences between R0 and R1 (for example, tests that a single transparent Receiver is allowed for R1 but not for R0).
1251f95
to
f1455af
Compare
force-pushed to address comments from code review. |
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.
utACK with comments. (Note that I was tired by the end of the review so it might not be as thorough as usual.)
3a04ed2
to
c7b0e01
Compare
force-pushed to rebase on Then force-pushed to take into account review suggestions. |
154b002
to
16b78e1
Compare
Co-authored-by: Daira-Emma Hopwood <[email protected]>
16b78e1
to
022685a
Compare
Closes #1153.