token-2022: Update to use program build with zk-ops enabled #33747
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mergify bot
pushed a commit
that referenced
this pull request
Oct 18, 2023
token-2022: Update to use version with zk-ops enabled (cherry picked from commit d337581)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The 1.17 release will have all features for zk-ops, but program-test and test-validator default to a version of token-2022 that disables zk-ops.
Summary of Changes
Update the packaged shared object file to the verifiable build with zk-ops enabled. This will not be backported to 1.16 because the required features are slated to be enabled starting with 1.17.
The release page includes both builds, but defaults to the one with zk-ops enabled: https://github.com/solana-labs/solana-program-library/releases/tag/token-2022-v0.9.0
Fixes #