-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(rln-relay): add chain-id flag to wakunode and restrict usage if mismatches rpc provider #2858
Conversation
… mismatches rpc provider
You can find the image built from this PR at
Built from d4fc2d6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure i follow. Shouldn't this fail? rln-relay-chain-id
is wrong
docker run quay.io/wakuorg/nwaku-pr:2858 \
--cluster-id=1 \
--rln-relay-eth-client-address=https://rpc.cardona.zkevm-rpc.com \
--log-level=DEBUG \
--rln-relay-chain-id=111111
since you pass in the cluster-id as 1, we override the rln-relay-chain-id, shouldn't that be the intended behaviour? |
indeed, my bad. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
* CHANGELOG.md add info for v0.30.0 * fix(rln-relay): clear nullifier log only if length is over max epoch gap (#2836) * chore: add TWN parameters for RLNv2 (#2843) * fix(rln): nullifierlog vulnerability (#2855) * chore(rln-relay): add chain-id flag to wakunode and restrict usage if mismatches rpc provider (#2858) --------- Co-authored-by: Aaryamann Challani <[email protected]> Co-authored-by: Alvaro Revuelta <[email protected]>
chore: Update master from release v0.30 (#2866) * CHANGELOG.md add info for v0.30.0 * fix(rln-relay): clear nullifier log only if length is over max epoch gap (#2836) * chore: add TWN parameters for RLNv2 (#2843) * fix(rln): nullifierlog vulnerability (#2855) * chore(rln-relay): add chain-id flag to wakunode and restrict usage if mismatches rpc provider (#2858) --------- Co-authored-by: Aaryamann Challani <[email protected]> Co-authored-by: Alvaro Revuelta <[email protected]>
Description
As requested by @alrevuelta to restrict chainId usage and waku node initialization should fail if user erroneously passes in an rpc url for another chain.
Changes