0a80a3bb25
This avoid restarting the node always with a full radius, which causes the node the be bombarded with offers which it later has to delete anyhow. In order to implement this functionality, several changes were made as the radius needed to move from the Portal wire protocol current location to the contentDB and beaconDB, which is conceptually more correct anyhow. So radius is now part of the database objects and a handler is used in the portal wire protocol to access its value. |
||
|---|---|---|
| .. | ||
| beacon_lc_bridge | ||
| docker | ||
| eth_data_exporter | ||
| portal_bridge | ||
| utp_testing | ||
| benchmark.nim | ||
| blockwalk.nim | ||
| content_verifier.nim | ||
| eth_data_exporter.nim | ||
| fcli_db.nim | ||
| portalcli.nim | ||