Validator fails to start when hex literal value is passed to externalSignerPublicKeys #3817
Labels
good first issue
Issues that are suitable for first-time contributors.
prio-low
This is nice to have.
scope-ux
Issues for CLI UX or general consumer UX.
Describe the bug
When an hex literal value (prefixed with 0x) is supplied as the value of
externalSignerPublicKeys
, then the application fails to start. It throws the following error:The reason is that yargs parses the hex literal string to numeric value, which causes the logic in the coerce function here to throw an exception
Expected behavior
Validator should start, even if literal hex value (with the 0x prefix) is supplied as value to the
externalSignerPublicKeys
flagSteps to Reproduce
externalSignerPublicKeys: "0x97b1b00d3c1888b5715c2c88bf1df7b0ad715388079de211bdc153697b69b868c671af3b2d86c5cdfbade48d03888ab4"
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: