Commit Graph

8 Commits

Author SHA1 Message Date
Adam Babik 8b61d92d58
Remove protocol and eth-node submodules () 2020-02-10 12:22:37 +01:00
Adam Babik 549fe06339
fix linter gocyclo error for bootnode 2019-12-06 10:59:29 +01:00
Jakub Sokołowski 99a5a4d7b7 add -genkey flag to bootnode for making new keys
also add -writeaddress for getting the public node address

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2019-12-04 13:44:05 +01:00
Adam Babik b1f9030177
update to geth v1.8.20 () 2018-12-19 11:02:07 +01:00
Pedro Pombeiro 354e23aaf5 Fix issues reported by lint. Part of 2018-06-14 13:52:51 +02:00
Dmitry 68966af049 Allow to set key hex as a flag 2018-06-07 13:53:04 +03:00
Dmitry Shulyak 5323af7da2 Fill new bootnode dht using already running bootnodes 2018-05-30 10:45:19 +03:00
Dmitry Shulyak ed1cdf0418
Custom status bootnodes ()
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: 
Partially closes:  (960 requires futher investigations on devices)
2018-05-18 16:43:07 +03:00