feature request: add a "EIP-155 enforced" field to RPC data

[mds1]

When looking at the list of RPC URLs for a chain, there are various properties given for each RPC:

I'd propose adding a new column named "EIP-155 Enforced" (or similar name) that is true if that RPC requires EIP-155 transactions (transaction must be signed over chain ID), or false if they allow pre-EIP-155 transactions (transaction may not be signed over chain ID and can be replayed across chains).

This is useful for users and developers that want to broadcast presigned transactions to deploy popular utility contracts, which usually provide a presigned transaction that is not signed over chain ID, so it can be replayed across chains.

Enforcing EIP-155 is the default in geth, so for most RPCs this field will be "true". But this setting can be changed by RPC providers via config file and is not a consensus requirement, so this feature would help users find RPC providers that allow pre-EIP-155 transactions to be broadcast

[0xngmi]

I can definitely see the usecase and its something that I've had trouble with before, however collecting that information for all RPCs and keeping it up to date seems a disproportionate amount of work compared to how niche this usecase is

[mds1]

Hmm, presumably you already make RPC calls to these servers to check the block heights, so perhaps EIP-155 support can be determined automatically by checking the response of an RPC call? I don't know offhand if there's an RPC method that could be used to simulate the effects of sending a raw, signed transaction though