franjoespejo
franjoespejo
Please see below the set of available operations for BLS at the moment: BLS12-381 signature (sign, verify, aggregate) The BLS scheme also supports threshold signatures. This is where a secret...
### Problem description Lodestar already implements the w3signer standard https://chainsafe.github.io/lodestar/run/validator-management/external-signer The standard assumes the w3s trusts the validator client, since there is no way for the w3s to verify the...
### 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...
Teku implements the w3signer standard https://docs.teku.consensys.io/how-to/use-external-signer/use-web3signer, but it is unknown when the validator client requests the pubkeys to the w3s. For some w3s implementations, as diva (https://docs.divastaking.net/) the pubkeys array...
Teku already implements the w3signer standard https://docs.teku.consensys.io/how-to/use-external-signer/use-web3signer. The standard assumes the w3s trusts the validator client, since there is no way for the w3s to verify the payload to be...
# 🚀 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...
# 🚀 Feature Request ### Description Prysm implements the w3signer standard https://docs.prylabs.network/docs/wallet/web3signer, but it is unknown when the validator client requests the pubkeys to the w3s. For some w3s implementations,...