Configuration
If this is your first time installing an es-node, you'll need to configure it by creating a data file for each shard using the es-node init
command. After that, you can start the es-node with various options.
During devnet tests, the run.sh
file already includes the proper options for your convenience, but you should be prepared to specify configurations as needed.
Configuration to create data files
With es-node init
command, you can init your es-node by creating a data file for each shard.
You can specify shard_len
(the number of shards) or shard_index
(the index of specified shards, and you can specify more than one) to create shards that you would like to mine. If both appear, shard_index
takes precedence.
Here are the options that you can use with init
command:
Name | Description | Default | Required |
---|---|---|---|
| Data directory for the storage files, databases and keystore | ✓ | |
| Encoding type of the shards. 0: no encoding, 1: keccak256, 2: ethash, 3: blob poseidon. Default: 3 | ||
| Number of shards to mine. Will create one data file per shard. | ||
| Indexes of shards to mine. Will create one data file per shard. | ||
| Address of L1 User JSON-RPC endpoint to use (eth namespace required) | ✓ | |
| Storage contract address on l1 | ✓ | |
| Miner's address to encode data and receive mining rewards | ✓ |
Configuration to run es-node
The full list of options that you can use to configure an es-node are as follows:
Name | Description | Default | Required |
---|---|---|---|
| Data directory for the storage files, databases and keystore | ✓ | |
| Where to dump the downloaded blobs | ||
| Block number which the downloader download blobs from |
| |
| Address of L1 beacon chain endpoint to use | ✓ | |
| A slot number in the past time specified by l1.beacon-based-time |
| ✓ |
| Timestamp of a slot specified by l1.beacon-based-slot |
| ✓ |
| Slot time of the L1 beacon chain |
| |
| Chain id of L1 chain endpoint to use |
| |
| Poll interval for retrieving new L1 epoch updates such as safe and finalized block changes. Disabled if 0 or negative. |
| |
| Min duration for blobs sidecars request |
| |
| Address of L1 User JSON-RPC endpoint to use (eth namespace required) | ✓ | |
| Chain id of L2 chain endpoint to use |
| |
| Color the log output if in terminal mode | ||
| Format the log output. Supported formats: 'text', 'terminal', 'logfmt', 'json' |
| |
| The lowest log level that will be output |
| |
| Enable metrics | ||
| Storage mining enabled | ||
| Gas price for mining transactions | ||
| Minimum profit for mining transactions |
| |
| Priority gas price for mining transactions | ||
| Number of threads per shard |
| |
| ZK prover mode, 1: one proof per sample, 2: one proof for multiple samples |
| |
| ZK prover implementation, 1: snarkjs, 2: go-rapidsnark |
| |
| zkey file name with path |
| |
| Predefined L1 network selection. Available networks: devnet | ||
| The IP address to advertise in Discv5, put into the ENR of the node. This may also be a hostname / domain name to resolve to an IP. | ||
| The TCP port to advertise in Discv5, put into the ENR of the node. Set to p2p.listen.tcp value if 0. |
| |
| The UDP port to advertise in Discv5 as fallback if not determined by Discv5, put into the ENR of the node. Set to p2p.listen.udp value if 0. |
| |
| Enables peer banning. This should ONLY be enabled once certain peer scoring is working correctly. | ||
| Comma-separated base64-format ENR list. Bootnodes to start discovering other node records from. | ||
| Completely disable the P2P stack, if P2P is disabled, mining will not start automatically. | ||
| Discovered ENRs are persisted in a database to recover from a restart without having to bootstrap the discovery process again. Set to 'memory' to never persist the peerstore. |
| |
| IP to bind LibP2P and Discv5 to |
| |
| TCP port to bind LibP2P to. Any available system port if set to 0. |
| |
| UDP port to bind Discv5 to. Same as TCP port if left 0. |
| |
| Enable NAT traversal with PMP/UPNP devices to learn external IP. | ||
| p2p request size is the initial number of bytes to request from a remote peer. It is value should not larger than 8 * 1024 * 1024. The request size will be changed according to network condition between the remote peer and the localnode. | 1048576 | |
| sync concurrency is the number of chunks to split a shard into to allow concurrent retrievals. | 16 | |
| fill empty concurrency is the number of threads to concurrently fill encoded empty blobs. | NumCPU - 2 | |
| Disable Discv5 (node discovery) | ||
| Grace period to keep a newly connected peer around, if it is not misbehaving. |
| |
| High-tide peer count. The node starts pruning peer connections slowly after reaching this number. |
| |
| Low-tide peer count. The node actively searches for new peer connections if below this amount. |
| |
| Peerstore database location. Persisted peerstores help recover peers after restarts. Set to 'memory' to never persist the peerstore. Peerstore records will be pruned / expire as necessary. Warning: a copy of the priv network key of the local peer will be persisted here. |
| |
| Read the hex-encoded 32-byte private key for the peer ID from this txt file. Created if not already exists.Important to persist to keep the same network identity after restarting, maintaining the previous advertised identity. |
| |
| Sets the peer score bands used primarily for peer score metrics. Should be provided in following format: <threshold>:<label>;<threshold>:<label>;...For example: -40:graylist;-20:restricted;0:nopx;20:friend; |
| |
| Sets the peer scoring strategy for the P2P stack. Can be one of: none or light.Custom scoring strategies can be defined in the config file. |
| |
| Sets the topic scoring strategy. Can be one of: none or light.Custom scoring strategies can be defined in the config file. |
| |
| Hex-encoded private key for signing off on p2p application messages as sequencer. | ||
| Comma-separated multiaddr-format peer list. Static connections to make and maintain, these peers will be regarded as trusted. | ||
| End of simple sync |
| |
| Start of simple sync |
| |
| Rollup chain parameters | ||
| RPC listening address |
| |
| RPC EsCall URL |
| |
| RPC listening port |
| |
| Address the signer is signing transactions for | ||
| Signer endpoint the client will connect to | ||
| HDPath is the derivation path used to obtain the private key for mining transactions | ||
| The HD seed used to derive the wallet's private keys for mining. Must be used in conjunction with HDPath. | ||
| The private key to sign a mining transaction | ||
| API that update es-node state to, the node will upload state to API for statistic if it has been set correctly. | ||
| File paths where the data are stored | ✓ | |
| Storage contract address on l1 | ✓ | |
| Miner's address to encode data and receive mining rewards | ✓ |
Check here for the detailed operation to change the default configurations.
Last updated