Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
mds1 opened this issue Feb 3, 2024 · 2 comments
Open

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

mds1 opened this issue Feb 3, 2024 · 2 comments

Comments

@mds1
Copy link

mds1 commented Feb 3, 2024

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

image

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
Copy link
Member

0xngmi commented Feb 6, 2024

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
Copy link
Author

mds1 commented Feb 6, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants