Web3Signer is an open-source signing service capable of signing on multiple platforms (Ethereum1 and 2, Filecoin) using private keys stored in an external vault, or encrypted on a disk.
I think ultimately this should be less important at some point but if it's present it allows me to actually test some changes now, rather than waiting for future builds that build in some changes to teku that remove the need to define trustedSetup, so ideally it's ok to have this defined as a dev flag for testing for now...
The problem I was having was acceptance-tests use custom configuration and there was no way to specify this argument, so I wasn't able to check deneb for external-signer changes in teku...
I've got another change for teku that should make this less important again (default trusted-setup basically) but it'll be hard to coordinate that change plus external-signer changes without some blocking, unless this flag exists, and then i can just start testing things now.
Given this is hidden i didn't add it to changelog but happy to if needed... The only place calling it will be a teku acceptance test once i merge that...
Documentation
[X] I thought about documentation and added the doc-change-required label to this PR if updates are required.
Changelog
[X] I thought about adding a changelog entry, and added one if I deemed necessary.
Testing
[X] I thought about testing these changes in a realistic/non-local environment.
I think ultimately this should be less important at some point but if it's present it allows me to actually test some changes now, rather than waiting for future builds that build in some changes to teku that remove the need to define trustedSetup, so ideally it's ok to have this defined as a dev flag for testing for now...
The problem I was having was acceptance-tests use custom configuration and there was no way to specify this argument, so I wasn't able to check deneb for external-signer changes in teku...
I've got another change for teku that should make this less important again (default trusted-setup basically) but it'll be hard to coordinate that change plus external-signer changes without some blocking, unless this flag exists, and then i can just start testing things now.
Given this is hidden i didn't add it to changelog but happy to if needed... The only place calling it will be a teku acceptance test once i merge that...
Documentation
doc-change-required
label to this PR if updates are required.Changelog
Testing