Also removed empty optional sections while here. They can be added back if/when tests/implementations are added, but they are otherwise optional.
I also moved this to review, since that is a much more appropriate state for an EIP that is going into a soon-to-be-scheduled hard fork, and there are no major changes planned to this EIP by the authors that I know of.
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing Draft, Review, or Last Call EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing Draft or Last Call EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing Draft or Last Call EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* EIP-2930: Updates transaction format to match EIP-2718
2718 has the first byte of every transaction be the transaction type, and the remaining bytes are interpreted however this EIP wants. This is the minimal change required to get it in line with 2718 so I think we should merge this ASAP and then continue discussion on whether we think this is the optimal format or not.
* Update EIPS/eip-2930.md
Co-authored-by: lightclient <14004106+lightclient@users.noreply.github.com>
* Changes same thing in more places.
Co-authored-by: lightclient <14004106+lightclient@users.noreply.github.com>
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing Draft or Last Call EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Adds a transaction type which contains an access list, a list of addresses and storage keys that the transaction plans to access. Accesses outside the list are possible, but become more expensive. Intended as a mitigation to contract breakage risks introduced by EIP 2929 and simultaneously a stepping stone toward broader use of access lists in other contexts.
