Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add sapling nullifier set #3191
@Eirik0 In a meeting @str4d @daira @bitcartel agreed that it would be a good design to prepare for future nullifier sets, beyond sapling. So use of
One area to investigate then would be how to avoid a collision / avoid exhausting the single char written to the database, which is used to distinguish records on reading. In this case, distinguishing between many nullifier sets including
We can cross the single-char-exhaustion bridge when we come to it, or when we change the database format (which we plan to do anyway). In the meantime we just need a treestate enum, that is mapped to a char manually chosen for each treestate when writing to the db.