Add EIP: Block-Level Access Lists#9580
Conversation
|
✅ All reviewers have approved. |
|
The commit ecad749 (as a parent of 4c8e46e) contains errors. |
|
For parallelization would be better if read and write are distinguished (if in write list doesn't need to be in read list as SSTORE both reads and writes) This is as multiple txs that only read can happen at same time; is only ones that write that enforce a specific ordering of tx order |
This is already done by having an optional second value for the tuple of values. If there is only one, it's a read. This is early design though and not something I've spent much time further optimizing for practical and worst case use. |
Ah ok, I didn't pick that up |
jochem-brouwer
left a comment
There was a problem hiding this comment.
I love the work on this! Left some lengthy thoughts. In general, I think that besides storage slots we also need to track accesses to balances of accounts, and we also need to know if new contracts are created. Such that if Tx A creates contract Z, then if Tx B calls Z it thus has to "wait" before Tx A has executed. The nice property of https://eips.ethereum.org/EIPS/eip-6780 is that we know that if a contract is creatd, it will now stay there, and can't be deleted anymore 😄 👍
General other question: is there also a discussion chat about this topic?
Co-authored-by: g11tech <develop@g11tech.io>
bomanaps
left a comment
There was a problem hiding this comment.
Implementation of parallelization is mentioned in your motivation but not detailed in specification.
Co-authored-by: Ignacio Hagopian <jsign.uy@gmail.com>
Co-authored-by: Ignacio Hagopian <jsign.uy@gmail.com>
Co-authored-by: Ignacio Hagopian <jsign.uy@gmail.com>
Co-authored-by: Ignacio Hagopian <jsign.uy@gmail.com>
jochem-brouwer
left a comment
There was a problem hiding this comment.
Some more comments! 😄 👍
jochem-brouwer
left a comment
There was a problem hiding this comment.
Two comments on the latest changes 😄 👍
|
Great, incorporated all the feedback - thanks everyone! Would be great to have it merged now. It's ready for a first draft. |
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
No description provided.