You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't see a way to estimate in advance the size limit or have a size limit in users' transactions. Could a collator try to execute Ethereum transactions with a size hint as the remaining size available in the block, and with a modified gasometer the EVM could panic of the storage size goes above the limit to prevent the transaction being included in the block?
The text was updated successfully, but these errors were encountered:
@sorpaas, @nanocryk is coming with some ideas to support it. For now it seems it doesn't require much logic as it is kind of disabled, but we will need to come up with a strategy for it. Probably updating the gasometer to include some computation for it.
We also discussed some improvements that need to be done for GETCODESIZE and GETCODEHASH which are currently reading the code from storage (big PoV) and need to be moved to their own storage.
Question
What is the plan to support storage size introduced in paritytech/substrate#12277 ?
I don't see a way to estimate in advance the size limit or have a size limit in users' transactions. Could a collator try to execute Ethereum transactions with a size hint as the remaining size available in the block, and with a modified gasometer the EVM could panic of the storage size goes above the limit to prevent the transaction being included in the block?
The text was updated successfully, but these errors were encountered: