Batch signing endpoint - Ethereum Remote Signing API #1097
Description
web3signer is the most widely used remote signer that implements the Ethereum Remote Signing API. I believe it would be of benefit if web3signer supported a proposed new API endpoint that could be used to sign data in batches, instead of sending hundreds to thousands of separate signing requests.
It would be great if your team could give some feedback on this, especially in terms of estimating how difficult it would be to add such an endpoint to web3signer. I'm happy to get involved myself in speccing out the endpoint if you agree this is a useful and feasible thing to implement.
Notable expected points of complexity from my basic understanding of the web3signer codebase:
- slashing protection measures - I believe the code related to slashing protection would need to be duplicated (or ideally refactored) to account for single-message and batch signing. This also involves the Postgres DB locking mechanism.
For more details and motivation, please refer to the related issue in the API spec repository - ethereum/remote-signing-api#19