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
It honestly might be a good idea to write the accounts explicitly, but to check the private keys against the supplied accounts, to avoid errors. Also the private keys should probably be providable separately from the config file (probably via environment variables? a secrets.toml file?) so that they do not get mingled to the config file, which should be commitable.
I'm changing the title of this issue to reflect this.
norswap
changed the title
Derive accounts from keys
Separate private keys from the rest of the config
Dec 12, 2023
Currently, we have a bunch of configuration options for accounts and private key.
This is super redundant: the accounts can be derived from the private keys, and by default we should do this derivation.
We can still allow accounts to be specified as a safety option, in which case, we will verify that the account & key match.
To do this we should install & use the eth_account python package.
The text was updated successfully, but these errors were encountered: