12 Commits

Author	SHA1	Message	Date
kdeme	b80a5b90df	Adjustments to store bootnode enrs in discovery object + bump nim-eth	2020-03-24 22:14:40 +02:00
Zahary Karadjov	19847bbd20	Remove some warnings	2020-03-22 19:00:09 +02:00
Dustin Brody	0d3de00714	remove unused imports	2020-03-11 10:50:55 +00:00
kdeme	02717a6354	Use randomNodes from discv5 instead of lookup	2020-03-05 13:17:34 +02:00
Zahary Karadjov	fa0f3b4468	Use the specified extip address in the advertised ENR records	2020-02-22 20:54:15 +02:00
Zahary Karadjov	55886ff0ac	More proper fix replacing hotfix 052a6ac3bc ... nim-eth was bumped to take advantage of a fixed `==` for public eth keys	2020-02-19 11:59:38 +02:00
Zahary Karadjov	b2d5aba749	Advertise the TCP port of the bootstrap node properly	2020-02-18 12:53:49 +02:00
Zahary Karadjov	2a3e40e298	Fix test_discovery_helpers	2020-02-18 12:53:49 +02:00
Zahary Karadjov	2c814db750	Temporary switch to supporting only ENR bootstrap addresses ... Turns out the DiscV5 code relies heavily on the presence of ENR records at the moment, so we cannot drive it with ENodes. @kdeme is working on refactoring that will relax these requirements.	2020-02-18 12:53:49 +02:00
Zahary Karadjov	7f395e554a	WIP Working local network sim with discovery ... * The bootstrap_nodes.txt file in the node's data dir is now optional * Log more data on start-up * Use the latest ENR APIs * Fix simulation build errors	2020-02-18 12:53:49 +02:00
Zahary Karadjov	ee7c2c9dff	Unify the bootstrap nodes handling code ... We no longer discriminate between ENR, MultiAddress or ENode bootstrap records (all of them are remapped to ENodes). The discovery loop will stochastically try to reconnect to accidentally disconnected nodes.	2020-02-18 12:53:49 +02:00
Zahary Karadjov	52878405b7	Integrate Discovery V5 and support ENR bootstrap records	2020-01-21 01:26:57 +02:00