Closed oxarbitrage closed 1 month ago
Note that by upgrading to those dependencies without setting the mainnet activation height, you are creating a mixed-consensus node state. I don't know how you manage that in Zebra; in zcashd
we upgraded to these in the 6.0.0 release PR itself (not the RC), in the same commit as the mainnet activation height. To split up the upgrade, we upgraded first (using a [patch.crates-io]
directive) to the librustzcash commit right before setting the mainnet activation height.
Ok, thanks for the head-up @str4d !
However, when i tried to do it as that, it seems to be an inconsistency problem with the revisions for zcash_client_backend
that zcashd does not has to build. Can you take a look?
@pili FYI: We decided with @str4d and other ECC folks in a meeting today that we want to do the Zebra v2.0.0-rc.0
with the patches pointing to commits just before the mainnet activation heights, this is the same zcashd did and should be the less risky process to follow.
To go over https://github.com/ZcashFoundation/zebra/pull/8918#issuecomment-2402213780some other patches were also needed. I am updating the PR with all that but i think we are back in track again.
I tried to remove elastic in https://github.com/ZcashFoundation/zebra/pull/8918/commits/6c21ecbf5557b8eb758f4bd10aae073e2b337e13 but had to revert in https://github.com/ZcashFoundation/zebra/pull/8918/commits/a568cb8d759249a789d80f5820f22bbcde70101b
Motivation
We need to upgrade the ECC dependencies for the next release.
This PR will also close https://github.com/ZcashFoundation/zebra/issues/8809
Solution
secp256k1
now that we can and do some deny.toml cleanup.Tests
All CI tests should pass.
PR Author's Checklist
PR Reviewer's Checklist