erigon-pulse/cmd/observer
ledgerwatch b0117a7c30
[devnet] separate logging - p2p (#7547)
Co-authored-by: Alex Sharp <alexsharp@Alexs-MacBook-Pro-2.local>
2023-05-19 18:41:53 +01:00
..
database cli: use SplitAndTrim instead of strgings.Split(",") (#7369) 2023-04-23 10:54:55 +07:00
observer [devnet] separate logging - p2p (#7547) 2023-05-19 18:41:53 +01:00
reports Grow string builders (#6192) 2022-12-04 10:51:20 +07:00
utils go1.19 gofmt (#4988) 2022-08-10 19:04:13 +07:00
main.go [devnet] separate logging - p2p (#7547) 2023-05-19 18:41:53 +01:00
README.md Observer - P2P network crawler (#3928) 2022-04-22 12:02:12 +01:00

Observer - P2P network crawler

Observer crawls the Ethereum network and collects information about the nodes.

Build

make observer

Run

observer --datadir ... --nat extip:<IP> --port <PORT>

Where IP is your public IP, and PORT has to be open for incoming UDP traffic.

See observer --help for available options.

Report

To get the report about the currently known network state run:

observer report --datadir ...

Description

Observer uses discv4 protocol to discover new nodes. Starting from a list of preconfigured "bootnodes" it uses FindNode to obtain their "neighbor" nodes, and then recursively crawls neighbors of neighbors and so on. Each found node is re-crawled again a few times. If the node fails to be pinged after maximum attempts, it is considered "dead", but still re-crawled less often.

A separate "diplomacy" process is doing "handshakes" to obtain information about the discovered nodes. It tries to get RLPx Hello and Eth Status from each node. The handshake repeats a few times according to the configured delays.