forked from zcash/librustzcash
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Diff from upstream, for ref only #37
Draft
PaulLaux
wants to merge
131
commits into
main
Choose a base branch
from
zsa1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
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
…to Domain implementation.
…ShieldedOutput trait
…textBytes, wrapping the AEADBytes in a struct
This PR updates the `zcash_primitives` crate to align with the recent changes in the `sapling-crypto` crate, which was updated to sync with the latest changes in `zcash_note_encryption`. ### Changes: - Updated the usage of `enc_ciphertext` to call `.as_ref()` to match the new return type. - Adjusted the import of the `ENC_CIPHERTEXT_SIZE` constant to use the definition from `sapling-crypto` instead of `zcash_note_encryption`, as the constant has been moved to `sapling-crypto`. Co-authored-by: Dmitry Demin <[email protected]>
This updates the test vectors to be of version 6 (as opposed to version 7). It also provides a new file for the V6 test vectors, an improvement to having them in the same file but behind feature flags. It provides a error for when the asset description string is not a UTF8 encoding.
ZSA has been implemented across the entire codebase, including: - **TransactionData** now contains two extra components: `OrchardZsaBundle` and `IssueBundle`. - Serialization and deserialization of the new components have been added. - Digests of the new components are considered in the calculation of `sighash`/`txid`. The **Nu7 network upgrade** has been introduced. However, the "nu6" `zcash_unstable` flag is currently used to separate ZSA from the regular build. All Nu7-related flags are annotated with `/* TODO nu7 */` comments. - Builder methods for ZSAs have been implemented. - Wallet-related functionality (in `zcash_client_backend`, `zcash_client_sqlite`) is currently disabled, as they do not yet support ZSAs.
This makes the changes that are required after the merging of QED-it/orchard#113
…update prost dependency version (#75) Updates the repository to ensure compatibility with the `zebra` project. ## Changes: 1. Uncommented the `zcash_client_backend` crate in the root `Cargo.toml`. Initially it was commented out under the assumption that it wasn't utilized by Zebra. However, it has been identified that Zebra relies on this crate. 2. Synchronized `zcash_client_backend` crate with `zcash_note_encryption` updates. 3. Updated the `prost` dependency version in the root `Cargo.toml` (the pinned version 0.12.3 caused compatibility issues with Zebra’s dependencies, preventing compilation).
Add Regtest network
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.
No description provided.