-
Notifications
You must be signed in to change notification settings - Fork 78
account password? #14
Comments
my workaround was to not even try to unlock, but that meant to switch off the unlocking in my own code. but would be better if |
perhaps this is the reason?
might mean that not all rpc apis are accessible, right? please by default open all those apis; this setup is not for production but for development only anyways, right? |
You do not need to unlock the account, as it is already unlocked by default in the Images. Geth is started with the |
As I understand that it is not ideal to have all nodes automatically unlocked, would it help if the first node was unlocked by default and the other nodes needed to be unlocked via RPC? |
Yes, looks like case by case this differs. And in this case not. What if my standard chainhammer code always does that, at the beginning? Looks like I really have to include all kind of situation specific exceptions, have a look = that is prone to future problems, though. |
IMHO account unlocking should be done by the client, i.e. my chainhammer. Simply for not to seduce a coder into assuming any account is wide open. There is a BUT I think for this great dev tool that you are supplying us with .... I think all RPC APIs could be made accessible, not only |
I think you are right. Being auto unlocked is almost never a use case which is useful. I will change this. I am happy that the tool is helpful! I will create another task to enable all RPC API, and try to update it asap. |
#14 - remove permanent unlocking for all nodes
Changes merged in; accounts are no longer unlocked permanently. |
Unfortunately, for the clique consensus protocol the nodes need to be unlocked in order to start mining. I enabled the unlocking again for the miner-1 and miner-2, the node behind miner-3 is not mining anyways and can be used for all applications which need to unlock manually. |
Oh, oops ;-)
All good as long as the |
one more "oops": https://github.com/javahippie/geth-dev/blob/master/miner/Dockerfile#L27 your 32c5455 is not part of master yet? because I get this:
and
|
You are right. I am not sure what happened there, I committed the changes and merged to master |
perhaps forgot to git push ? |
s.th.'s wrong with the password?
The text was updated successfully, but these errors were encountered: