prestonvanloon
commented
2 days ago Added the "help wanted" label. This seems to be a pretty specific use case for Diva/untrusted setups and we are quite limited on eng bandwidth. If Diva developers or anyone that wants this feature could implement it, then we would be able to allocate limited resources to review of the implementation.
🚀 Feature Request
Description
Prysm already implements the w3signer/remote-signer standard https://docs.prylabs.network/docs/wallet/web3signer.
The standard assumes the w3s trusts the validator client, since there is no way for the w3s to verify the payload to be signed.
Describe the solution you'd like
The proposal to fix that is: https://github.com/ethereum/remote-signing-api/pull/10,
It is specially useful for diva which distributes the w3s signatures.
Describe alternatives you've considered
Nimbus has implemented this: https://nimbus.guide/web3signer.html#verifying-web3signer,