-
Notifications
You must be signed in to change notification settings - Fork 975
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
Integrate Accounts v2 Keymanager Into Validator Client #6489
Conversation
… it easy to include at runtime
Codecov Report
@@ Coverage Diff @@
## master #6489 +/- ##
==========================================
+ Coverage 60.07% 61.52% +1.44%
==========================================
Files 323 363 +40
Lines 27422 28330 +908
==========================================
+ Hits 16473 17429 +956
+ Misses 8733 8525 -208
- Partials 2216 2376 +160 |
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.
Should we test this run time before merging?
Or at least add EnableAccountsV2
to e2e
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.
Confirmed with @rauljordan, we have tested this run time
What type of PR is this?
What does this PR do? Why is it needed?
This PR begins integrating
--enable-accounts-v2
into the validator client's runtime, allowing for full-featured functionality by using an EIP-2335 direct keystore manager implemented by #6466. This functionality will be gated by a feature flag until all keymanager implementations are complete and the code is deemed production ready.This PR additionally abstracts functionality of loading an existing keymanager configuration file into the
accountsv2.OpenWallet
function, cleaning up some old code paths to ensure v2 functionality is simple to access.Which issues(s) does this PR fix?
Part of #6220