Using release/v2.4.x-a3f809dbee5915baa8b871782953d99efa160b1a
When requesting a single signing-info using a validator consensus public address, an error is systematically returned : Error: invalid character 'x' in literal false (expecting 'a')
e.g. fxcored q slashing signing-info fxvalconspub1zcjduepqqz6gjgknrmz0aepxmmfztlnlu9qy89ed3rkwj4aukxzfntgtzqdq8cpdyk
I checked to the tech team and they mentioned that the EVM transactions need to obtain transaction details through the eth-web3 interface. JSON RPC Server | Function X Docs