bug(rln-relay): light push does not check proofs before forwarding to relay

[richard-ramos]

When a messge is published via lightpush, the message is broadcasted via relay without performing the rln proof verification. Ideally the proof should be verified before the message is published.

To see this scenario in action, use the following setup

A: js-waku
B: wakunode2 (with lightpush + filter, compiled with `RLNZEROKIT=true`)
C: chat2 (with rln-relay=true, rln-relay-dynamic=true, fleet=none and dns-discovery=false, compiled with `RLNZEROKIT=true`)

A --> B <-- C

https://examples.waku.org/rln-js/ can be used for the js-waku node.

A message generated in js-waku node should not arrive to chat2

cc: @staheri14 @fryorcraken

[Ivansete-status]

@jm-clius - I've assigned this issue to @shash256 just to make it more explicit that this is part of #2595

[fryorcraken]

Considering "Provision RLN for light push clients PoC" milestone, this does not seem needed at this point in time.

[jm-clius]

Considering "Provision RLN for light push clients PoC" milestone, this does not seem needed at this point in time.

This will be implemented as a side effect of the first step for a RLN proofs service (validating the message before publishing, whether the proof was added by the lightpush client or the RLN service node). In fact, I think this issue can be closed with the merging of #2695. @shash256 please confirm and close if addressed.