-
Notifications
You must be signed in to change notification settings - Fork 4
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
The current state and future plan of the waku-rln-relay project #143
Conversation
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.
LGTM!
minor nits. IMO this should be a research post 😄
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.
Looks good! Left some nitpick comments
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.
Looked over it briefly and seems OK. I'd post as a research post.
published: true | ||
permalink: /waku-rln-relay-journey | ||
categories: research | ||
summary: The current state of the research and development of the WAKU-RLN-RELAY project. |
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.
This summary could be better:
-
Doesn't help someone who doesn't already know what RLN or RLN RELAY is.
-
It also doesn't hint at what the main delta is from last post (e.g. cross client on-chain testnet, etc) - can use a few keywords in a list to give people a better view of what the post about.
The first XX words of the summary shows up in e.g. Twitter view
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.
Doesn't help someone who doesn't already know what RLN or RLN RELAY is.
Fair point.
It also doesn't hint at what the main delta is from last post (e.g. cross client on-chain testnet, etc) - can use a few keywords in a list to give people a better view of what the post about.
Sure.
The first XX words of the summary shows up in e.g. Twitter view
Noted.
Please check the following commit 5e3ab81
|
||
|
||
**Academic publications**: The results of this project are published as 2 academic research articles in prestigious conferences of ICDCS and DINPS 2022. | ||
They are accessible at https://arxiv.org/pdf/2207.00117.pdf and https://ieeexplore.ieee.org/abstract/document/9912176/. |
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.
I think what s1fr0 is getting at is that this should be mentioned in the text. A question in a PR review of a text is usually feedback on the text itself, and just answering the PR comment doesn't actually improve the text...
|
||
# WAKU-RLN-RELAY: Why and How | ||
|
||
**Why**: The WAKU-RLN-RELAY project was started more than two years ago to protect the open p2p messaging protocol of [WAKU-RELAY](https://rfc.vac.dev/spec/11/) against spam and DDoS attacks. |
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.
Link back to previous post on RLN
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.
sure, done 33d5b37
Given that:
Perhaps we should save this write-up until we've done some work on RLNP2P? |
I agree and that is what I do, but this question didn't seem to require an update on the text as the separation of the two articles is pretty evident as the publication venues and links are not the same. Will stress on this more by putting the title of the articles. Please check 5528be6. |
353dab8
to
5e3ab81
Compare
Fine for me, then going to close this PR and keep the write-up locally until the due time comes. |
This is to address the last part of the second testnet tasks list i.e.,
The relation to operator outreach will be clarified separately in the operator outreach document.
This post can be published as a forum post or a research post. Open to suggestions.
I opened it as a PR here to ease the review process, once the decision reached about where to publish this doc, I'll move it to the relevant repo accordingly.