Skip to content
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

ZSA sync test vectors #10

Closed
wants to merge 1 commit into from
Closed

ZSA sync test vectors #10

wants to merge 1 commit into from

Conversation

naure
Copy link

@naure naure commented Jul 19, 2022

No description provided.

@naure naure force-pushed the zsa-sync-test-vectors branch from ddf51a3 to 83dcc62 Compare July 20, 2022 08:49
@naure naure force-pushed the zsa-sync-test-vectors branch from 83dcc62 to e4b4d05 Compare July 20, 2022 08:53
@naure naure closed this Jul 20, 2022
dmidem added a commit that referenced this pull request Jul 31, 2024
… PR #2 issues resolve (#111)

Orchard has been synced with the changes from [PR
#10](QED-it/zcash_note_encryption#10) in the
`zcash_note_encryption` repository. This update includes the following
changes:

- Implements new `parse_note_plaintext_bytes`,
`parse_note_ciphertext_bytes`, and `parse_compact_note_plaintext_bytes`
methods of the `Domain` trait from `zcash_note_encryption`.
- Uses the `NoteBytes` trait and `NoteBytesData` structure from
`zcash_note_encryption` instead of having local definitions and
implementations.

### Note
This PR uses the `resolve_zcash_pr2_issues` branch of
`zcash_note_encryption` in `Cargo.toml`. Before merging this PR, [PR
#10](https://github.com/zcash/zcash_note_encryption/pull/10) needs to be
merged into the `zsa1` branch of `zcash_note_encryption`. Then, this
Orchard PR branch should be updated to use the `zsa1` branch of
`zcash_note_encryption` befor merging this PR.

---------

Co-authored-by: Dmitry Demin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant