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

[Epic] 3.1: DoS requirements and design #69

Closed
1 task
chair28980 opened this issue Sep 1, 2023 · 4 comments
Closed
1 task

[Epic] 3.1: DoS requirements and design #69

chair28980 opened this issue Sep 1, 2023 · 4 comments
Labels
E:3.1: DoS requirements and design See https://github.com/waku-org/pm/issues/69 for details Epic Tracks a sub-team Epic.

Comments

@chair28980
Copy link
Contributor

chair28980 commented Sep 1, 2023

Epic label: 3.1: DoS requirements and design

Summary

This builds off the general specification phase to answer questions specific to DoS/spam protection in the public Waku Network. The deliverable is answer to questions such as:

  1. What is a reasonable epoch size and rate design for the network? Should this be managed per shard or for the entire autosharded network?
  2. What is a good initial, test membership mechanism and what is the roadmap to onboard more members?
  3. Should we allow a certain amount of "free" traffic (without membership/proofs) on the network? How is this fairly managed and limited?

Acceptance Criteria

Tasks

RAID (Risks, Assumptions, Issues and Dependencies)

@chair28980 chair28980 added the Epic Tracks a sub-team Epic. label Sep 1, 2023
@fryorcraken fryorcraken added this to Waku Sep 1, 2023
@fryorcraken fryorcraken added this to the Waku Network Gen 0 milestone Sep 5, 2023
@fryorcraken
Copy link
Contributor

@jm-clius @alrevuelta I believe this is not yet fully done. What is a realistic revised date? Cc @chair28980

@alrevuelta
Copy link
Collaborator

alrevuelta commented Sep 12, 2023

release v0.20.0 will "bump" rln to "non experimental" aka "ready" waku-org/nwaku#2001 which is a prerequisite for this to be completed. once done we would need:

  • deploy a stable rln contract in testnet (proxy imho)
  • deploy fleets with rln enabled by default

but we still have to decide:

  • epoch size. currently 10 seconds. unsure if there is quorum on this.
  • if we allow "free traffic".

both points can be discussed at the next research call.

@jm-clius
Copy link

This epic only tracks decisions around the design parameters. The RLN-in-production work (deploying to fleets, etc.) is tracked in: #70

Initial requirements would be set once we have merged vacp2p/rfc#616

Realistically, this should be done by 22 Sept, given the upcoming Research Call discussions.

@fryorcraken fryorcraken added the E:3.1: DoS requirements and design See https://github.com/waku-org/pm/issues/69 for details label Sep 13, 2023
@fryorcraken fryorcraken moved this to In Progress in Waku Sep 13, 2023
@jm-clius
Copy link

This issue is closed by the merging of vacp2p/rfc#616

@github-project-automation github-project-automation bot moved this from In Progress to Done in Waku Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E:3.1: DoS requirements and design See https://github.com/waku-org/pm/issues/69 for details Epic Tracks a sub-team Epic.
Projects
Status: Done
Development

No branches or pull requests

4 participants