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

Add server for consuming events, storing in DB, and recreating the tree. #10

Open
drewstone opened this issue Dec 10, 2020 · 0 comments
Assignees
Labels
v2 Version 2 tasks

Comments

@drewstone
Copy link
Collaborator

drewstone commented Dec 10, 2020

We will need a server implementation for rebuilding the merkle tree that functions as the relayer system similar to https://github.com/tornadocash/tornado-relayer.

This can be done by consuming the historical events of tree insertions and rebuilding the tree locally, likely in conjunction with a database of sorts. As the trees grows large, checkpointing will also be worthwhile.

On the topic of testing/rebuilding the tree, it might make sense to also support for the time being a flag that stores all leaves on-chain. Having the flag would reduce complexity on the client front, as users can just query the chain for the time being.

@lazovicff lazovicff self-assigned this Dec 18, 2020
@drewstone drewstone added the v1 Version 1 tasks label Jan 27, 2021
@drewstone drewstone added v2 Version 2 tasks and removed v1 Version 1 tasks labels Feb 8, 2021
@drewstone drewstone changed the title Add client for consuming events, storing in DB, and recreating the tree. Add server for consuming events, storing in DB, and recreating the tree. Feb 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v2 Version 2 tasks
Projects
None yet
Development

No branches or pull requests

3 participants