-
Notifications
You must be signed in to change notification settings - Fork 920
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Keymanageropts Pattern from Wallets and Remove Enable/Disable Feature for V1 CLI #7831
Conversation
e8f5915
to
47b55ad
Compare
@@ -387,30 +378,6 @@ func (w *Wallet) ReadKeymanagerConfigFromDisk(_ context.Context) (io.ReadCloser, | |||
|
|||
} | |||
|
|||
// LockWalletConfigFile lock read and write to wallet file in order to prevent |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now we don't have anything to lock. Slashing protection will take care of this. Additionally, we allow importing keys dynamically at runtime which would be invalidated by a lock
@@ -0,0 +1,65 @@ | |||
package imported |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please review carefully
@@ -0,0 +1,240 @@ | |||
package imported |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please review these tests
Thanks for cc me. This is much better indeed! |
No tracking issue. This PR removes the legacy
KeymanagerOpts
pattern we used in our wallets. We were basically storing a json file full of versioning and configuration options for a wallet that is underutilized and ultimately unnecessary in Prysm. This leads to more complex code in our wallet and makes it harder for people to programmatically manipulate their wallet accounts on disk in cloud deployments. This PR completely removes the pattern.This PR also adds comprehensive tests to accounts enable + disable, but opts to remove the features from our CLI entrypoints for Prysm v1 until we have confidence in prod. cc @fabdarice