mirror of
https://gitlab.com/pulsechaincom/erigon-pulse.git
synced 2025-01-08 20:11:21 +00:00
7f31b047f1
According to EIP-1186 the `proof` parts of the response to eth_getProof should be returned "starting with the stateRoot-Node, following the path of the SHA3 (address) as key." Currently, the proof is returned in traversal order, rather than from the root. Although all of the proof elements are there and correct, this is contrary to the EIP and will cause problems for some clients. The existing rpc test uses a map to lookup proof elements by hash, rather than by index, so this bug was not initially caught. This commit fixes the behavior, updates the existing test, and adds additional checks to the rpc test. Co-authored-by: Jason Yellick <jason@enya.ai> |
||
---|---|---|
.. | ||
adapter | ||
app | ||
builder | ||
cli | ||
cmdtest | ||
debug | ||
engineapi | ||
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