Hardcoding - seth blinding using network id as chain id, getting invalid sender error

[thapakazi]

Just thinking out loud, how safe is it to simply assume networkID and chainID same.
Stumbled upon here because I was using different chainID and netwworkID, and seth was just throwing out invalid sender error.

Turns out we have been setting chain-id.

seth/libexec/seth/seth-mktx

Line 18 in aae347d

--chain-id $(seth rpc net_version)

It would be better if we have a option to send the chain-id param explicitly and set rpc net_version as default like:

--chain-id ${chain_id_from_option:-(seth rpc net_version)} 

Thoughts ?