-
Notifications
You must be signed in to change notification settings - Fork 106
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
Implement Sapling note commitment tree #286
Labels
C-design
Category: Software design work
NU-1 Sapling
Network Upgrade: Sapling specific tasks
S-needs-design
Status: Needs a design decision
Milestone
Comments
relevant discord conversation: https://discordapp.com/channels/676527656170160146/716086297210650634/728052748238585917 |
dconnolly
added
S-needs-design
Status: Needs a design decision
C-design
Category: Software design work
labels
Jul 2, 2020
This was referenced Jul 6, 2020
dconnolly
changed the title
Design Sapling note commitment trees.
design: Tree State in Rust, including Note Commitment Tree and its Nullifier Set
Jul 30, 2020
hdevalence
changed the title
design: Tree State in Rust, including Note Commitment Tree and its Nullifier Set
Note commitment trees
Aug 11, 2020
Edited title to distinguish from #289 for the nullifier set. |
Edited title to distinguish from #36 |
dconnolly
changed the title
Sapling note commitment tree
Implement Sapling note commitment tree
Sep 10, 2020
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-design
Category: Software design work
NU-1 Sapling
Network Upgrade: Sapling specific tasks
S-needs-design
Status: Needs a design decision
We need a note commitment tree implementation for both Sprout and Sapling, even when checkpointing on Sapling activation, because we need to accumulate the correct tree state up to Sapling activation in order to validate V4 Sprout-on-Groth16 proofs.
We may want to adapt the implementation in librustzcash to fit our needs.
Depends on #273
Related to #36 (Sprout note commitment tree)
The text was updated successfully, but these errors were encountered: