bug: RLN flags issues

[AlejandroCabeza]

Background

According to the "RLN Relay Configuration and Parameters" block in RLN's Test Plan, which are based on the RLN specs, there are some flags that can't be tested.

Details

Here goes a snippet of the aforementioned block that includes a brief description of the issue:

2. **RLN Relay Configuration and Parameters:**
    3. **RLN Relay Membership Index (`rln-relay-membership-index`)**: Confirm the correct usage of the on-chain commitment index.
        - Setting `rlnRelayCredIndex` in `WakuRlnConfig` doesn't fetch the keys in the keystore. Although this might be a symptom, and not the actual issue.
    5. **RLN Relay Identity Key Configuration (`rln-relay-id-key`)**: Validate the correct application of the RLN relay identity secret key from the provided Hex string.
        - `rlnRelayIdKey` flag is not used
    6. **RLN Relay Identity Commitment Key Configuration (`rln-relay-id-commitment-key`)**: Ensure the correct usage of the RLN relay identity commitment key from the Hex string.
        - `rlnRelayIdCommitmentKey` flag is not used
    9. **RLN Relay Ethereum Private Key (`rln-relay-eth-private-key`)**: Validate the use of the private key for broadcasting transactions on the Ethereum network.
        - `rlnRelayIdCommitmentKey` is not passed to `WakuRlnConf`
    10. **RLN Relay Credential Password (`rln-relay-cred-password`)**: Check the encryption of RLN credentials using the specified password.
        - `WakuRlnRelay.init` fails if used. Might be a similar situation to 3: not cause, but "symptom".
    11. **RLN Relay Merkle Tree Path (`rln-relay-tree-path`)**: Verify the correct configuration and usage of the path to the RLN Merkle tree database.
        - `WakuRlnRelay.init` fails if used. Might be a similar situation to 3: not cause, but "symptom".

Acceptance criteria

What's expected out of each of those flags?

[rymnc]

2,5,6 are deprecated. as i remember, they were to be removed after 2 releases after deprecation

[rymnc]

9 is used in the keystore generator subcommand for wakunode2

[rymnc]

10 and 11 work as intended, can you share a trace of the error you get if you use it?

[rymnc]

3 is interesting, investigating

[rymnc]

rlnRelayCredIndex

nwaku/waku/waku_rln_relay/group_manager/on_chain/group_manager.nim

Lines 572 to 573 in 6298267

	if g.membershipIndex.isSome():
	keystoreQuery.treeIndex = MembershipIndex(g.membershipIndex.get())

called from

nwaku/waku/waku_rln_relay/rln_relay.nim

Lines 423 to 432 in 66eba02

	groupManager = OnchainGroupManager(
	ethClientUrl: string(conf.rlnRelayethClientAddress),
	ethContractAddress: $conf.rlnRelayEthContractAddress,
	rlnInstance: rlnInstance,
	registrationHandler: registrationHandler,
	keystorePath: rlnRelayCredPath,
	keystorePassword: rlnRelayCredPassword,
	membershipIndex: conf.rlnRelayCredIndex,
	onFatalErrorAction: conf.onFatalErrorAction,
	)

called from

nwaku/waku/factory/node_factory.nim

Lines 198 to 209 in 66eba02

	let rlnConf = WakuRlnConfig(
	rlnRelayDynamic: conf.rlnRelayDynamic,
	rlnRelayCredIndex: conf.rlnRelayCredIndex,
	rlnRelayEthContractAddress: conf.rlnRelayEthContractAddress,
	rlnRelayEthClientAddress: string(conf.rlnRelayethClientAddress),
	rlnRelayCredPath: conf.rlnRelayCredPath,
	rlnRelayCredPassword: conf.rlnRelayCredPassword,
	rlnRelayTreePath: conf.rlnRelayTreePath,
	rlnRelayUserMessageLimit: conf.rlnRelayUserMessageLimit,
	rlnEpochSizeSec: conf.rlnEpochSizeSec,
	onFatalErrorAction: onFatalErrorAction,
	)

[AlejandroCabeza]

9 is used in the keystore generator subcommand for wakunode2

Well, now I found it. The day of posting I wasn't able to.

10 and 11 work as intended, can you share a trace of the error you get if you use it?

Error: failed to mount WakuRlnRelay: could not initialize the group manager: the commitment does not have a membership
You can reproduce it in branch tests/rln, file tests/node/test_wakunode_relay_rln.nim. Uncomment the last two lines of proc getWakuRlnConfigOnChain, lines 94 and 95, so the WakuRlnConfig contains rlnRelayCredPath and rlnRelayCredPassword.

#2763 (comment)

What do you mean to point out with this?