Commit Graph

5 Commits

Author SHA1 Message Date
Igor Sirotin 7ee45bab1c
chore_: cleanup unused cmd (#6045)
* chore!: remove cmd/node-canary

* chore!: remove unused root files

* chore!: remove cmd/bootnode and cmd/statusd-prune

* chore!: remove waku _examples

* chore!: remove cmd/spiff-workflow and cmd/topics
2024-11-11 17:17:41 +07:00
Jakub Sokołowski 0f06b4ca6a fix entrypoint for bootnode Docker image
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2019-12-17 22:04:34 +01:00
Adam Babik e164cbe421
Upgrade Go to 1.13 in our Docker images (#1629) 2019-10-05 16:27:48 +02:00
Adam Babik 16c7b94eb5
Add labels to docker images and add Jenkinsfile to build docker images (#1160)
* fixed generating `params.Version`
* added labels to all Docker images including git_commit and the author of the build (using `$USER` env variable)
2018-08-24 12:25:07 +02:00
Dmitry Shulyak ed1cdf0418
Custom status bootnodes (#968)
This change makes invalidation mechanism more aggressive. With a primary goal to invalidate short living nodes faster. In current setup any node that became known in terms of discovery will stay in this state until it will fail to respond to 5 queries. Removing them earlier from a table allows to reduce latency for finding required nodes.

The second change, one adds a version for discovery, separates status dht from ethereum dht.
After we rolled out discovery it became obvious that our boot nodes became spammed with irrelevant nodes. And this made discovery process very long, for example with separate dht discovery takes ~2s, with mutual dht - it can take 1m-10m and there is still no guarantee to find a max amount of peers, cause status nodes is a very small part of whole ethereum infra.

In my understanding, we don't need to be a part of ethereum dht, and lower latency is way more important for us.

Closes: #941
Partially closes: #960 (960 requires futher investigations on devices)
2018-05-18 16:43:07 +03:00