The Status module that consumes go-ethereum
https://status.im
a609b468fe
This change implements connection manager that monitors 3 types of events: 1. update of the selected mail servers 2. disconnect from a mail server 3. errors for requesting mail history When selected mail servers provided we will try to connect with as many as possible, and later disconnect the surplus. For example if we want to connect with one mail server and 3 were selected, we try to connect with all (3), and later disconnect with 2. It will to establish connection with live mail server faster. If mail server disconnects we will choose any other mail server from the list of selected. Unless we have only one mail server. In such case we don't have any other choice and we will leave things as is. If request for history was expired we will disconnect such peer and try to find another one. We will follow same rules as described above. We will have two components that will rely on this logic: 1. requesting history If target peer is provided we will use that peer, otherwise we will request history from any selected mail server that is connected at the time of request. 2. confirmation from selected mail server Confirmation from any selected mail server will bee used to send a feedback that envelope was sent. I will add several extensions, but probably in separate PRs: 1. prioritize connection with mail server that was used before reboot 2. disconnect from mail servers if history request wasn't expired but failed. 3. wait some time in RequestsMessage RPC to establish connection with any mail server Currently this feature is hidden, as certain changes will be necessary in status-react. partially implements: https://github.com/status-im/status-go/issues/1285 |
||
|---|---|---|
| .github | ||
| .vscode | ||
| _assets | ||
| account | ||
| api | ||
| cmd | ||
| config | ||
| contracts | ||
| db | ||
| discovery | ||
| extkeys | ||
| lib | ||
| logutils | ||
| mailserver | ||
| metrics/node | ||
| node | ||
| notifications/push | ||
| notifier | ||
| params | ||
| peers | ||
| profiling | ||
| rpc | ||
| services | ||
| signal | ||
| static | ||
| t | ||
| timesource | ||
| transactions | ||
| vendor | ||
| .codeclimate.yml | ||
| .dockerignore | ||
| .gitignore | ||
| .golangci.yml | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| LICENSE.md | ||
| Makefile | ||
| README.md | ||
| VERSION | ||
README.md
Status bindings for go-ethereum
Docs
License
Releasing
To create a release, first increase the VERSION file according to semantic versioning.
You can then build the artifacts for the specific platform.
Once done, you can run:
make prepare-release
and
make release release_branch={{release_branch}}
Where release_branch is the branch you are targeting.
You will also need to specify some form of credentials, GITHUB_TOKEN environment variable for example.