Milestone: RLN-Relay testnet1 - dynamic group and on-chain

[oskarth]

Problem

This is the second testnet for RLN-Relay. It is about being able to join the RLN group dynamically from your nwaku node, and registering on chain.

Scope

NOTE The following is not necessarily a complete list, and we should prioritize making this scope as minimal but complete as possible

List of issues:

• (Many other issues were complete since testnet0 and aren't necessarily listed here)
• On chain setup: Waku-Rln-Relay Onchain Setup waku-org/nwaku#1015
• testnet preparation RLN-Relay testnet1 preparation waku-org/nwaku#827
• Tutorial chore(Rln-relay): Tutorial on how to run rln-chat2 in on-chain mode waku-org/nwaku#1044
• Persisting rln credentials waku-org/nwaku#1037
• Announce to relevant parties (e.g. #vac-pm? or more open group) to start dogfooding with clear actions
• At least ~5 people participating and providing feedback
• Feedbacks are addressed or captured as GH issues

Risks and uncertainty

• New components bring additional risks and complications. The on-chain model and dynamic group management model is new and there are likely several kinks to work out.
• Exact scope is currently variable and needs to be cut/minimized (however this seems doable)
• Some unknowns regarding contract and spec thereof (though probably good enough for testnet)

In terms of timelines expect this testnet to conclude by mid August (TODO: to be confirmed).

Acceptance criteria

Issues defined in scope addressed. Testnet has been run by multiple participants and feedback has been gathered and captured.

Out of scope

• Performance work
• Zerokit integration
• ERC20 usage
• Multi client testnet

Notes and links

Future steps

• Make testnet2 scope clear (mutli-client, including dependency on e.g. js-waku integration; ERC20 integration etc)
• Understand performance work needed and scope this
• Ensure testnets are integrated with operator-outreach and invite multiple participants, write-up etc
• Have an understanding of when an audit and trusted setup would be needed

[oskarth]

@staheri14 I wrote this up as a stub, please edit it to make it more complete and make any corrections necessary here.

cc @s1fr0 @kgrgpg

[oskarth]

The owner/assignee is the main person responsible for the milestone outcome

(Unclear if we want to have multiple people here as "working on it", but in general good to have one main person to make sure things that haven't been thought about are dealt with by default. Otherwise that person becomes me, which is unsustainable for this many tracks and milestones.)

[oskarth]

@staheri14 please edit the above issue so you are happy with this. There are some mentions of TODOs that should either be filled out and remove.

I see you highlighted a few individuals in the dogfooding channel, is there a specific timeline for when you expect this to run and feedback to be collected? Say, this week? And then collect the feedback somewhere to conclude this milestone.

[oskarth]

@staheri14 what's left for this milestone to be considered done?

[staheri14]

@oskarth The feedbacks of the first testnet are yet to be incorporated (see the tracking issue waku-org/nwaku#1069). However, since all the items in this issue are covered, I think we can consider the first testnet concluded.