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
@markya0616@yutelin@alanchchen@bailantaotao@tailingchen
I am trying to set a private Istanbul network, however, every client I bring up has a coinbase/etherbase which I didn't create and eth.accounts[0] is not equal to eth.coinbase, because of which the coinbase/etherbase address is not in validator set and hence network just halts thus nothing proceeds. Even using --etherbase flag to set the ehterbase base doesn't change it. Can you please tell me how the etherbase is set differently to the account I have in my keystore and how do I make sure that the client is started with the correct coinbase/etherbase?How do I create a network with existing accounts where Istanbul automatically recognises the account in keystore, like in other consensus algorithms?
In the backtrace, the unauthorised addresses are which is set by the client and unlocked accounts are the desired addresses which should have been set by the client and are in the validator set.
Steps to reproduce the behaviour
Create multiple accounts with the same password since its a test network
Add the public addresses to a toml file
Use the toml file to generate extra data
Add this extra data to the genesis file
Use the genesis file to initialise nodes
Create a bootnode
Launch each node is a tmux window under the same session
I have a bash script which takes in 2 arguments: 'location of geth binary' and 'the number of nodes to bring up the network', the following creates a network for 2 nodes which are connected using a bootnode (both files need to be in the same directory):
Yes, I discovered the problem is here, the authors force set the node key as mining ether-base then this means the validators added in the genesis are not responsible for creating a block, therefore I get "unauthorized address".
Please refer here for my hack (this is not a solution) around this problem.
@markya0616 @yutelin @alanchchen @bailantaotao @tailingchen
I am trying to set a private Istanbul network, however, every client I bring up has a coinbase/etherbase which I didn't create and
eth.accounts[0]
is not equal toeth.coinbase
, because of which the coinbase/etherbase address is not in validator set and hence network just halts thus nothing proceeds. Even using--etherbase
flag to set the ehterbase base doesn't change it. Can you please tell me how the etherbase is set differently to the account I have in my keystore and how do I make sure that the client is started with the correct coinbase/etherbase?How do I create a network with existing accounts where Istanbul automatically recognises the account in keystore, like in other consensus algorithms?In the backtrace, the unauthorised addresses are which is set by the client and unlocked accounts are the desired addresses which should have been set by the client and are in the validator set.
Steps to reproduce the behaviour
I have a bash script which takes in 2 arguments: 'location of geth binary' and 'the number of nodes to bring up the network', the following creates a network for 2 nodes which are connected using a bootnode (both files need to be in the same directory):
The script creates a new network everytime as well as a new tmux session, so please kill the tmux session before the script is run again.
istprivatenetwork.sh:
updategenesis.js:
Backtrace
Node1:
Node2:
The text was updated successfully, but these errors were encountered: