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. |
||
|---|---|---|
| .. | ||
| common | ||
| database | ||
| docs/the_fluffy_book | ||
| eth_data | ||
| grafana | ||
| network | ||
| rpc | ||
| scripts | ||
| tests | ||
| tools | ||
| README.md | ||
| conf.nim | ||
| fluffy.nim | ||
| fluffy.nim.cfg | ||
| logging.nim | ||
| network_metadata.nim | ||
| nim.cfg | ||
| portal_node.nim | ||
| version.nim | ||
README.md
Fluffy: The Nimbus Portal Network Client
Introduction
Fluffy is the Nimbus client implementation of the Portal network specifications.
You can find all the information you need to run a Fluffy node in The Fluffy Book.
The quickstart page in particular will help you to get quickly connected to the Portal network.
Development Updates
Monthly development updates are shared here.
To keep up to date with changes and development progress, follow the Nimbus blog.
License
Licensed and distributed under either of
- MIT license: LICENSE-MIT or http://opensource.org/licenses/MIT
or
- Apache License, Version 2.0, (LICENSE-APACHEv2 or http://www.apache.org/licenses/LICENSE-2.0)
at your option. These files may not be copied, modified, or distributed except according to those terms.