-
Notifications
You must be signed in to change notification settings - Fork 53
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
test(rln-relay): rln-relay testnet 3 #1624
Comments
in terms of needed work to get this ready, is it just about new contract address and new ABI or is there function code changes to do to? |
@fryorcraken, there are minor changes in the event returned. s/pubkey/idCommitment/g. everything else, should have the same functionality. |
tracking here: waku-org/js-rln#53 for js-waku |
go-waku: waku-org/go-waku#505 |
waku-org/nwaku#1624 status-im/infra-nim-waku#69 Signed-off-by: Jakub Sokołowski <jakub@status.im>
Testnet 3 wrapped up and retrospective completed - vacp2p/research#179 (comment) |
Problem
rln-relay has changed quite a bit since testnet 2, including -
Support for rln-relay in the
wakuv2.test
fleet was dropped some time back, hence, we cannot see live metrics for it.Proposal
We re-enable rln-relay on the
wakuv2.test
fleet for a period of 2-3 weeks, while we iron out any integration bugs, and measure performance.CC's make use of chat2/js-rln to send a few messages everyday.
Pre-requisites
Details
0x9C09146844C1326c2dBC41c451766C7138F88155
Sepolia
11155111
3193048
cc: @waku-org/waku-product
The text was updated successfully, but these errors were encountered: