Closed nflaig closed 5 days ago
Attention: Patch coverage is 22.22222%
with 14 lines
in your changes missing coverage. Please review.
Project coverage is 50.82%. Comparing base (
ad4ec77
) to head (4e9ddf4
). Report is 3 commits behind head on unstable.
✔️ no performance regression detected
by benchmarkbot/action
spec PRs have been merged, I think we can merge this before web3signer has a release that supports electra
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
Motivation
Adds electra support for remote signer as per https://github.com/ethereum/remote-signing-api/pull/15 and https://github.com/ethereum/remote-signing-api/pull/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