mirror of
https://gitlab.com/pulsechaincom/erigon-pulse.git
synced 2025-01-08 03:51:20 +00:00
32ca0e5ab1
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. |
||
|---|---|---|
| .. | ||
| adapter | ||
| app | ||
| backup | ||
| builder | ||
| cli | ||
| cmdtest | ||
| debug | ||
| engineapi | ||
| execution/eth1 | ||
| jsonrpc | ||
| logging | ||
| mock | ||
| node | ||
| rlphacks | ||
| rpchelper | ||
| services | ||
| shards | ||
| snapshotsync | ||
| stages | ||
| testlog | ||
| transactions | ||
| trie | ||
| README.md | ||
Erigon-API
Erigon-API is a set of tools for building applications containing Erigon node.
Our own binary erigon is built using it.
Modules
-
cli- erigon-cli, methods & helpers to run a CLI app with Erigon node. -
node- represents an Ethereum node, running devp2p and sync and writing state to the database. -
stagedsync- staged sync algorithm.
Examples
-
erigon- our binary is using erigon-api with all defaults -
erigoncustom- a very simple example of adding a custom stage, a custom bucket and a custom command-line parameter -
erigon-examples - a series of examples for Erigon api