alexpeterson91
commented
1 year ago I was thinking we import the global envs for execution clients on mainnet, goerli, and gnosis.
Use basically the same logic used in the entrypoint script of SSV Shifu to set envs of the querying RPC API or each EL. Then use jq or yq to write the info to the mainnet_chain_template.json and reload the app which it should on chnsge of global envs used by the packsge anyway.
Would just need to prompt users that they may need to restake depending on the UI. Also since not many people can run all chains we currently have available on one machine we should probably add envs in the advanced editor to allow users to pass an arbitrary value for any given chain. Like Ethereum archival trace, maybe you can't run erigon on your main machine so you will enter your https endpoint from the other machine for erigon. Or LAN endpoint if multiple machines on one network.
What do you think @@mgarciate
There's several components of the config like max peers, seed nodes, persistent nodes (would be great if pokt validators share their node endpoints to add to each others seed or persistent nodes to help with peering which can be difficult sometimes.) These all currently must be put in the config file and then built and uploaded. Or manipulated over root SSH/terminal access.