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
If you only want to connect to peers manually (with admin.addPeer in the console), run with --nodiscover. That flag turns off peer discovery and prevents geth from trying to find peers for your network id on the internet.
If you want your private network to set itself up automatically, use --bootnodes. Start one node first with --bootnodes=none, note down the enode://... URL that it prints and start all other nodes with --bootnodes "<that url>". Please be aware that discovery is 'contagious', that is, if one of the nodes has a different bootnode (or had one before) it will discover the rest of the world pretty quickly and you're back to square one. Start with an empty datadir on all nodes to prevent this.
### Description
This enables mycelo and e2e tests to set the espresso block number.
This is was done to test celo typed transactions and espresso.
This commit also renames any reference of "E" hardfork or block
to "Espresso".
Also updates the mycelo load bot to use the latest signer instead of
the homestead signer.
### Tested
Unit test, CI. Tested that e2e tests can activate the Espresso fork.
### Backwards compatibility
Yes
Hi, I tried to run my private network for testing but it tries to connect to external. I took tutorial from here: https://github.com/ethereum/go-ethereum/wiki/Setting-up-private-network-or-local-cluster
geth version :1.1.0
logs:
The text was updated successfully, but these errors were encountered: