mirror of https://gitlab.com/pulsechaincom/erigon-pulse.git synced 2025-01-09 12:31:21 +00:00

History

battlmonstr 32ca0e5ab1 sync: revert flawed dropUselessPeers logic and alleviate its issues (#8062 ) The current logic is flawed, because it drops all peers that are less synced. It is valid to return empty responses by the eth spec. A proper logic should penalize from the context of the sync process, where enough "reputation" data is collected about a peer. In order to be able to connect to erigon 2.48 peers that have --sentry.drop-useless-peers enabled, this adds a check to not reply with an empty headers list. If we reply with an empty list, we're going to be considered useless and kicked. Once enough of erigon nodes are updated in the network past this commit, this check should be removed, because it is totally acceptable to return an empty list by the eth spec.		2023-08-25 11:42:54 +02:00
..
sentry	sync: revert flawed dropUselessPeers logic and alleviate its issues (#8062 )	2023-08-25 11:42:54 +02:00
main.go	mdbx_to_mdbx: to use logger (#7860 )	2023-07-09 08:04:20 +01:00
README.md	Sentry doc (#5040 )	2022-08-13 21:37:51 +07:00

README.md

Sentry - component to

In the root of Erigon project, use this command to build the sentry:

make sentry

There are two modes in which the program can be run - with external p2p sentry, or with internal p2p sentry (also called combined). Ethereum mainnet configuration is currently hard-coded.

Running with an external p2p sentry

./buid/bin/sentry

./buid/bin/sentry --datadir=<sentry_datadir>

The command above specifies --datadir option - directory where the database files will be written (it doesn't need access to Erion's datadir). These two options will need to be specified regardless of the mode the program is run. This specific command above assumes and external p2p sentry running on the same computer listening to the port 9091. In order to use a p2p sentry on a different computer, or a different port (or both), the option --sentry.api.addr can be used. For example:

./buid/bin/sentry --datadir=<sentry1_datadir> --sentry.api.addr=localhost:9091
./buid/bin/sentry --datadir=<sentry2_datadir> --sentry.api.addr=localhost:9191
./build/bin/erigon --sentry.api.addr="localhost:9091,localhost:9191"

The command above will expect the p2p sentry running on the same computer, but on the port 9091

Options --nat, --port, --staticpeers, --netrestrict, --discovery are also available.

We are currently testing against two implementations of the p2p sentry - one internal to Erigon, and another - written in Rust as a part of rust-ethereum: https://github.com/rust-ethereum/sentry In order to run the internal sentry, use the following command: