You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can parametrize the number of consensus instances we launch using malachite's spawn script but we cannot vary the number of reth nodes beyond 4.
Currently, for every node we have hardcoded the setup in a compose.yml file.
Ideally, we want to also be able to pass reth config params rather than hardcoding them in the compose file.
What needs to be done:
have a reth.conf file with:
all the reth cli flags we want to pass on to container on boot up.
prefix for reth URLs - the ports will be appended afterwards
path to reth.toml as we will need to send a custom reth.toml file to configure node pruning (it is passed to reth via --config path_to_file . This file can be stored in .assets alongside the jwt secret so we do not need to mount another folder.
We can parametrize the number of consensus instances we launch using malachite's spawn script but we cannot vary the number of reth nodes beyond 4.
Currently, for every node we have hardcoded the setup in a
compose.ymlfile.Ideally, we want to also be able to pass reth config params rather than hardcoding them in the compose file.
What needs to be done:
--config path_to_file. This file can be stored in.assetsalongside the jwt secret so we do not need to mount another folder.reth.confwe fill up thecompose.yamlfile for docker.