mirror of
https://gitlab.com/pulsechaincom/erigon-pulse.git
synced 2024-12-22 11:41:19 +00:00
f110102023
This is an update to the devnet code which introduces the concept of
configurable scenarios. This replaces the previous hard coded execution
function.
The intention is that now both the network and the operations to run on
the network can be described in a data structure which is configurable
and composable.
The operating model is to create a network and then ask it to run
scenarios:
```go
network.Run(
runCtx,
scenarios.Scenario{
Name: "all",
Steps: []*scenarios.Step{
&scenarios.Step{Text: "InitSubscriptions", Args: []any{[]requests.SubMethod{requests.Methods.ETHNewHeads}}},
&scenarios.Step{Text: "PingErigonRpc"},
&scenarios.Step{Text: "CheckTxPoolContent", Args: []any{0, 0, 0}},
&scenarios.Step{Text: "SendTxWithDynamicFee", Args: []any{recipientAddress, services.DevAddress, sendValue}},
&scenarios.Step{Text: "AwaitBlocks", Args: []any{2 * time.Second}},
},
})
```
The steps here refer to step handlers which can be defined as follows:
```go
func init() {
scenarios.MustRegisterStepHandlers(
scenarios.StepHandler(GetBalance),
)
}
func GetBalance(ctx context.Context, addr string, blockNum requests.BlockNumber, checkBal uint64) {
...
```
This commit is an initial implementation of the scenario running - which
is working, but will need to be enhanced to make it more usable &
developable.
The current version of the code is working and has been tested with the
dev network, and bor withoutheimdall. There is a multi miner bor
heimdall configuration but this is yet to be tested.
Note that by default the scenario runner picks nodes at random on the
network to send transactions to. this causes the dev network to run very
slowly as it seems to take a long time to include transactions where the
nonce is incremented across nodes. It seems to take a long time for the
nonce to catch up in the transaction pool processing. This is yet to be
investigated.
|
||
|---|---|---|
| .. | ||
| adapter | ||
| app | ||
| backup | ||
| 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