op-proposer, op-batcher: Support private keys in addition to mnemonics#3155
op-proposer, op-batcher: Support private keys in addition to mnemonics#3155
Conversation
|
|
This PR changes implementation code, but doesn't include a changeset. Did you forget to add one? |
39a95c3 to
e1a3609
Compare
bc14ea2 to
4f832f3
Compare
4f832f3 to
e8647cb
Compare
e8647cb to
9f4a0c7
Compare
b4b587f to
f57eee5
Compare
f57eee5 to
b6e4ca7
Compare
b6e4ca7 to
0befcf2
Compare
|
I think @protolambda wanted to move to using encrypted keystores I think this is fine because it won't require any changes in tooling or the way we handle secrets |
|
Maybe ideally we define one go module that can support the loading of private keys, in various ways:
That way we don't duplicate security-critical code, make it easy to audit, and easy to use. Also ideally with discouraged use of mnemonic and private key. And warnings if you put the mnemonic, private key, or password in CLI instead of env var. (Since shell history / log streaming may log the CLI command and leak it) I've been thinking we should have an I'm fine with merging this PR as-is, but it would be nice if we can refactor it all into a common |
|
I agree with the I'll merge this as-is, but will ticket the |
No description provided.