Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
EIP-1712: Disallow Deployment of Unused Opcodes #4
Most importantly, because if there are provisions to skip any data, then stuffing the data with a payload becomes a workaround.
As-is, there's no way to guard against, say,
A much weaker point is that if, as in this proposal, there's no provision to stop on encountering a
Deploying code with "unused opcodes" can be immensely useful for a generalised fork oracle.
(I'm not claiming sanity; I'm pointing out a valid use case for the pattern.)
That's not true. In the case you provided,
The Solidity argument is valid. However, a trivial fix to Solidity can be deployed, where we just prefix a
This EIP does not prevent implementation of a generalised fork oracle. Once this is in force, a fork oracle can test by using
I assume same checks as for