-
-
Notifications
You must be signed in to change notification settings - Fork 677
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
Add support for Zcash unified addresses - memory optimized #2398
Conversation
cc876ce
to
61dd5d2
Compare
This PR is ready for review @andrewkozlik . I don't understand why CI |
At the end of the log you can see
This is the output of If you run the following commands you will get the same result.
I think what you need to do is look at |
Thank you for clarification Andrew. I'm removing |
may I squash and merge , or waiting for another review ? @andrewkozlik |
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.
did a brief review, two small nitpicks.
@andrewkozlik do we want to add this to the upcoming release?
return hrp.encode() + bytes(16 - len(hrp)) | ||
|
||
|
||
def encode(receivers: Dict[Typecode, bytes], coin: CoinInfo) -> str: |
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.
please use py3.10-style annotations, i.e., in this case dict[Typecode, bytes]
without importing Dict
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.
|
||
def receiver_length(typecode: int): | ||
"""Byte length of a receiver.""" | ||
if typecode in [Typecode.P2PKH, Typecode.P2SH]: |
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.
nit: these should be tuples (Typecode.P2PKH, Typecode.P2SH)
not lists
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 will try to review today.
Is there any reason not to? |
the freeze is today; my question is, are you as the main reviewer confident enough in this code to include it? |
I don't think we need to force this into the release, since Suite integration of unified addresses is not on the roadmap yet. So I am not sure this could be used in production by anyone in the nearest future. On the other hand if we happen to merge this today somehow, then it's fine to include this in the freeze. (My apologies for not getting this reviewed earlier. I had a lot on my plate.) |
Let's merge after the freeze if there is no strong reason to merge it before. |
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
looks like this has all the approval it needs |
d872ac0
to
f17d25a
Compare
core fw regular debug build:
😢 |
Also, the address in
Strange, I still have 4 kB left when I build with
|
e738f24
to
d1373e2
Compare
d1373e2
to
a84ceab
Compare
I rebased over the current |
specification: https://zips.z.cash/zip-0316
optimization: f4jumble now uses C blake2b module