RLN-Relay testnet1 preparation

[staheri14]

In the current PoC implementation of rln-relay, we support spam protection against a static group of members whose private and public keys are hardcoded in the nim-waku clients. We would like to extend the work by deploying it on a testnet and supporting dynamic groups via on-chain interactions. This issue aims to present the critical path and the remaining major steps to get Rln-relay live on testnet. The following steps are identified so far:

• The contract should be deployed on the testnet
• Add support for dynamic group management as explained in RLN-Relay: Support for dynamic group #712. This basically means enabling peers to collect emitted events from the contract and to amend their locally stored membership Merkle tree.
• Integrate dynamic mode into chat2
• A tutorial on how to run rln-chat2 in dynamic mode

cc: @oskarth @jm-clius

Next

• Integrating a wallet application into nim-waku so that peers can securely initiate registration and deletion transactions needless to disclose their accounts' private keys. This is the tracking issue Wallet integration into waku-rln-relay #819

[oskarth]

This sems fine, but shouldn't we start first testing it with static keys? We are all waiting for instructions on how to run it!

[staheri14]

@oskarth
Right, dogfooding with static keys is still in the plan and in progress. That is the prerequisite for starting rln-relay live on the Ethereum testnet. This issue contains tasks that are related to dynamic group management with the assumption that the static group scenario will work out.