-
-
Notifications
You must be signed in to change notification settings - Fork 300
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
feat: add electra support for remote signer #7100
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## unstable #7100 +/- ##
============================================
- Coverage 50.82% 50.82% -0.01%
============================================
Files 597 597
Lines 39789 39800 +11
Branches 2059 2063 +4
============================================
+ Hits 20224 20227 +3
- Misses 19565 19573 +8 |
Performance Report✔️ no performance regression detected Full benchmark results
|
spec PRs have been merged, I think we can merge this before web3signer has a release that supports electra |
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.
lgtm. Minor comment.
Not familiar with the deprecation schedule of remote signing api. When can we safely remove AGGREGATE_AND_PROOF
?
Since we only implement the client-side here, we can just stop using the v1 after electra fork on mainnet, all remote signers need to implement the v2 type until then, otherwise they won't be able to support post-electra aggregate signing. we can include that in our post-electra api cleanup |
🎉 This PR is included in v1.23.0 🎉 |
Motivation
Adds electra support for remote signer as per ethereum/remote-signing-api#15 and ethereum/remote-signing-api#17
Description
AGGREGATE_AND_PROOF_V2
message type which will be used post-electrasignAggregateAndProof
for different forksTODO
enable electra fork in e2e once web3signer release is outcan be done later