You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Below is a list of action items, extracted from the reviews received from DINPS 22, to be taken for the extended version of the waku-rln-relay article for journal submission.
These items have not been addressed in the initial submission due to the page limit and the fact that the project was still in progress and not deployed on a large scale.
Maintaining Merkle tree in a storage efficient manner suited for resource-limited devices
Benchmarking and performance evaluation, especially the proof verification time.
The text was updated successfully, but these errors were encountered:
cc: @oskarth
We already have a rough solution for the first item, I suggest prioritizing it for this/next next quarter and publishing it as a short paper.
Another extension idea: How to break user anonymity by making proofs against an old version of the Merkle tree. Basically, what can go wrong if the index of one's identity public key gets (or the range of the index) exposed to/inferred by the network.
Below is a list of action items, extracted from the reviews received from DINPS 22, to be taken for the extended version of the waku-rln-relay article for journal submission.
These items have not been addressed in the initial submission due to the page limit and the fact that the project was still in progress and not deployed on a large scale.
The text was updated successfully, but these errors were encountered: