-
Notifications
You must be signed in to change notification settings - Fork 986
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
Use eth.staging as a default fleet for development and nightlies #9216
Comments
cc @oskarth |
Is anyone handling this in @status-im/status-core (also cc @andremedeiros in case you aren't in that team yet)? |
This can be easily changed by using the |
Although do take into account that the |
It seems like the app might be ignoring this setting and using beta fleet anyway
|
closed via #9379 |
Feature Issue
After upgrade of geth and Whisper, the algorithm to calculate envelope's PoW in Whisper changed. It means that sending a message from a client before and after the change might calculate PoW totally different and messages won't be exchanged.
In order to fix it, all clients and forwarding Whisper nodes have to use the same Whisper PoW algorithm.
That's why in status-im/status-go#1641 we upgraded
eth.staging
fleet to the newest status-go version. It means thateth.staging
and the current status-react develop builds use the same Whisper PoW algorithm and messages can be properly exchanged.User Story
As a developer, I would like to use a fleet which runs Whisper nodes compatible with the status-react develop builds.
Acceptance Criteria
eth.staging
as a default fleetThe text was updated successfully, but these errors were encountered: