possible bug: [RLN] Mebership Index don't need to match #2742
Labels
bug
Something isn't working
effort/hours
Estimated to be completed in a few hours
track:rln
RLN Track (Secure Messaging/Applied ZK), e.g. relay and applications
Problem
When mounting
OnChainGroupManager
, theMembershipIndex
specified inWakuRlnConfig
doesn't need to match theMembershipIndex
used on theaddMembershipToKeystore
.Also, as for the
WakuRlnConfig
indices, for some reason they must begin at 0 in incremental order. Otherwise it timeouts.To reproduce
It's easier to understand by having a look at the test case
tests/node/test_wakunode_relay_rln:482
, namedValid contract
. This test represents the happy path for sending an OnChain RLN message.In the line 516 two
WakuRlnConfig
instances are defined, one withMembershipIndex
0, and the other withMembershipIndex
1. In line 536, the indices are retrieved usingonChainGroupManager.membershipIndex.get()
; but this is irrelevant, as any pair of numbers will do.Expected behavior
For a node to use a specific set of RLN credentials, their config should specify the same
MembershipIndex
as the one used to add those credentials to the keystore.nwaku version/commit hash
The text was updated successfully, but these errors were encountered: