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
Describe the bug
We are comparing BlockScout and Beaconchain explorers and want to use one of them in our project.
We have a private local network with one/four besu clients and we want to use explorers to show blocks/txs in the network. I modified the config file and the shell script because I don't need to connect to testnet/mainnet. However, it was very hard to get it working with Beacon. If so, we have to choose BlockScout then.
To Reproduce
Steps to reproduce the behavior:
comment out code below "Spin up a local ethereum testnet" in main.star
modify provision-explorer-config.sh to set CL_PORT and EL_PORT to my besu rpc port "8545"
(hacky) modify provision-explorer-config.sh to set clConfigPath to empty and name to mainnet because running the script failed due to the failure to call eth/v1/config/spec for besu client
Describe the bug
We are comparing BlockScout and Beaconchain explorers and want to use one of them in our project.
We have a private local network with one/four besu clients and we want to use explorers to show blocks/txs in the network. I modified the config file and the shell script because I don't need to connect to testnet/mainnet. However, it was very hard to get it working with Beacon. If so, we have to choose BlockScout then.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
All containers running properly.
Screenshots
All containers exited and the logs are as follows.
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: