G.

Sure. Not sure if we should change the merkle tree root validation section to account for partial tree misalignments through a windows of allowed roots. In such case probably better...

@fryorcraken seems to be a revision of https://github.com/kilic/rlnapp/blob/master/packages/contracts/contracts/RLN.sol but no PR/issue/review though.

Related issue: https://github.com/status-im/nwaku/issues/1238

When you talk about export/import you mean in encrypted form? Most likely we will use JSON to store credentials and all the crypto information (salt, hashes, etc.) and such JSON...

Note that in any proposed solution the RLN index should have a fixed size (e.g. in hex of either 4 or 8 bytes). The reason is that credentials will be...

Thanks for the issue. I think was fairly agreed that we want to generate credentials as described in semaphore so that we have compatibility. The only thing I'd like to...

This issue has been addressed by https://github.com/waku-org/nwaku/pull/1285 and its follow-up PR https://github.com/waku-org/nwaku/pull/1466. The solution implements https://github.com/waku-org/nwaku/issues/1238#issuecomment-1278114079, that is a structured JSON keystore supporting multiple membership credentials encrypted with an implementation...

Look good in general! My main concern is that Phase2 might require lots of new effort to adapt what already done in Phase1. That is, I would personally spend more...

> The other aspect is to coordinate the task distribution, please check the current task distribution and let me know your thoughts. Indeed the two phases seems a bit unbalanced...

> 3. The exchange of the service fee preferably should not require direct communication between the two parties. The benefits of this design choice are two-fold: 1) makes the design...