-
Notifications
You must be signed in to change notification settings - Fork 45
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: switch wakuv2 fleet to waku #1049
Conversation
Jenkins BuildsClick to see older builds (3)
|
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.
Looks good.
But we also need to update ReadMe files in examples where specific peerIDs or IP's are referred to of the fleets that we want to decomission.
e.g:
go-waku/examples/chat2/README.md
Line 31 in bdf10a4
./build/chat2 -staticnode=/ip4/134.209.139.210/tcp/30303/p2p/16Uiu2HAmPLe7Mzm8TsYUubgCAW1aJoeFScxrLj8ppHFivPo97bUZ |
Better to search for all PeerID's or IP addresses of the fleets that are about to be decomissioned and update them to new fleet as well.
@chaitanyaprem, not sure, what you mean. I've updated this file |
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
Missed it my bad. |
1448a0a
to
6900367
Compare
6900367
to
826c7fb
Compare
See status-im/infra-nim-waku#91 for details
Mostly done automatically. Some parts manually.