sigp
verifying remote signing / web3signer
Problem description
Lighthouse already implements the w3signer standard https://lighthouse-book.sigmaprime.io/validator-web3signer.html.
The standard assumes the w3s trusts the validator client, since there is no way for the w3s to verify the payload to be signed.
Solution description
The implementation of the following specs would solve the issue:
https://github.com/ethereum/remote-signing-api/pull/10 By sending the merkle proofs, it provides verification capabilities of the block proposal content to remote signers before signing the block, thereby facilitating a trustless operational setup between the validator client and the remote signer.
Nimbus has implemented this: https://nimbus.guide/web3signer.html#verifying-web3signer, it is specially useful for diva which distributes the w3s signatures.
