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.
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
Generalize Sapling note encryption to allow reuse with Orchard notes. #358
Generalize Sapling note encryption to allow reuse with Orchard notes. #358
Changes from 11 commits
5baccdf
e778392
266285b
5b13bb3
be225da
213cd6c
dad8663
879eea8
a560101
24e62d3
cfdbafe
e654cc4
4f22f1d
324fc36
6fc1d1d
f34e878
fae1a15
389e6ca
12cb826
00d04de
b2b3efd
3434cc8
dc0f6e7
28a4502
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These not-quite-circular dependencies make publishing a pain. I dealt with it for
zcash_client_backend <-> zcash_client_sqlite
for the 0.5 release by specifying a version range per rust-lang/cargo#4242 but it would be good to formalize this in the repo. Non-blocking, we can sort this out later.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the zcash_client_backend issue, I'm planning to address that by making the tests just run against the in-memory backend once that's complete, and move the sqlite tests back to the sqlite crate. Here, I'm not sure what the best approach is; I guess we could move these tests to zcash_primitives and implement a set of tests here that just relies upon the note-encryption functionality without using Sapling.