The Status module that consumes go-ethereum
https://status.im
1f6cccd0fc
This commit adds a list new table, installations, which is used to keep track of which installation are active for a given identity key. In general, we limit the number of installation that we keep synchronized to 5, to avoid excessive usage of resources. Any installation coming from our own identity, will have to be manually enabled, otherwise we trust the other peer has correctly paired their devices. We use a timestamp to decide which installations to keep synchronized as a logical clock would have make the creation of the bundle more complicated, but this can always be converted to a logical clock at later stages without breaking compatibility. |
||
---|---|---|
.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.