discussions-to for EIP-7907: Meter Contract Code Size And Increase Limit
(original PR: Add EIP: Meter Contract Code Size And Increase Limit by charles-cooper · Pull Request #9483 · ethereum/EIPs · GitHub)
discussions-to for EIP-7907: Meter Contract Code Size And Increase Limit
(original PR: Add EIP: Meter Contract Code Size And Increase Limit by charles-cooper · Pull Request #9483 · ethereum/EIPs · GitHub)
I performed jumpdest analysis benchmarks for eip 7903, which are relevant here.
Twitter is cheering up.
But this incentivises tha lazy inclusion of libraries and goes against the principle of maximum reuse of what is already deployed on chain.
Ofc, the question is whether there is even a common agreement on such a principle of deployed code reusability.
If the account is warm, no change to the gas schedule occurs.
The account being warm doesn’t mean the code is loaded:
EXTCODEHASH
also warms the account but doesn’t load the codeOther actions loading the code are not included in the pricing:
EXTCODESIZE
loads the codeDo you need to add all these to pricing, or add as second “warm” list that records if code is loaded?