After removing the fallback for engines in the execution_layer crate, we don't need the secret_files and execution_endpoint to be able to hold more than one in each field. Those could be changed to be options or even mandatory fields.
high performance lightweight solution for efcore sharding table and sharding database support read-write-separation .一款ef-core下高性能、轻量级针对分表分库读写分离的解决方案，具有零依赖、零学习成本、零业务代码入侵
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:
✖ YError: item.split is not a function at Object.runValidation [as _runValidation]
The reason is that yargs parses the hex literal string to numeric value, which causes the logic in the coe
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered
Description
After removing the fallback for engines in the execution_layer crate, we don't need the
secret_filesandexecution_endpointto be able to hold more than one in each field. Those could be changed to be options or even mandatory fields.The relevant code is [here](https://github.com/sigp/lighthouse/blob/748475be1ded2c9a29cbd8b985f6ae2980720a36/beacon_node/execution_layer/src