Open brewmaster012 opened 1 year ago
cc @aldapp7
@brewmaster012 I will take a look.
@brewmaster012 can you pls provide examples of txs when that happens?
There are no signatures arguments being passed in TransactionArgs structure and signing is being done inside sign_tx method and fails deep inside signing ethermint and go-ethereum methods. The theory is that it might be due to incorrect chainId parsing and that signer/sender is failed to be derived from transaction message.
We can add additional checks (I've already did locally) to verify chainId for tx and check that signer and sender could be correctly derived from transaction msg before signing to avoid panics due to such reason.
Some RPC calls might cause panic of the Ethermint RPC server. Here's a log.
Is there anything that we could do about it? The correct behavior should be to check the signature length and return error in JSON-RPC response, not panic.