-
Notifications
You must be signed in to change notification settings - Fork 111
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
Upgrade zcash_script
after the zcashd
5.5.0 release
#6535
Upgrade zcash_script
after the zcashd
5.5.0 release
#6535
Comments
The zcash_script crate upgrades are in ZcashFoundation/zcash_script#84 |
Hey team! Please add your planning poker estimate with Zenhub @arya2 @conradoplg @dconnolly @oxarbitrage @teor2345 @upbqdn |
@teor2345 are you working on this one in ZcashFoundation/zcash_script#84 ? Is there anything else that needs to be done to close this issue? |
Yes, please see my updates on that PR and in Slack. I am waiting for the ECC developers to push the zcashd v5.5.0 tag, but we can proceed based on the second release candidate if we need to. Is there any reason we need to do this soon?
We need to:
|
You can see the detailed instructions here: |
No no :) I was just trying to figure out if this was in progress and who was working on it |
I think we still need to:
|
Motivation
After
zcashd
5.5.0 is released:https://github.com/zcash/zcash/tags
We want to update our script engine to match its implementation. There haven't been any significant changes to script behaviour, but the surrounding code has been refactored.
Scheduling
This doesn't need to be in the same release as #6232, but builds will be slower until we update our entire set of dependencies. There's also a small but acceptable risk of consensus divergence.
Specifications
Zcash transparent scripts are mostly unspecified, so we must match
zcashd
's behaviour.Complex Code or Requirements
This is consensus-critical code.
Testing
Our existing unit and integration tests have good coverage of this code.
Manually use
cargo tree
to check that we don't depend on any vulnerableorchard
versions: we must only depend on orchard 0.4 or later.Related Work
Follow up to:
The text was updated successfully, but these errors were encountered: