mirror of
https://gitlab.com/pulsechaincom/erigon-pulse.git
synced 2025-01-08 20:11:21 +00:00
94f4ea805d
the root cause is that when `inMemoryExecution` lambda gets created in the `eth/backend.go`, it captures the reference of `backend.notifications`, and so the execution of side-forks actually adds notifications to there, and it all gets sent out to tx pool (and RPC daemon) at the end of the stage loop (regardless of whether there was forkchoice update or not) so we can create a separate notification, but then somehow flush it to the "main" nofitications when the in-memory exec state is flushed Co-authored-by: Alexey Sharp <alexeysharp@Alexeys-iMac.local> Co-authored-by: Alex Sharp <alexsharp@Alexs-MacBook-Pro.local> |
||
---|---|---|
.. | ||
adapter | ||
app | ||
builder | ||
cli | ||
engineapi | ||
mock | ||
node | ||
rlphacks | ||
rpchelper | ||
services | ||
shards | ||
snapshotsync | ||
stages | ||
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