13 Commits

Author SHA1 Message Date
vbuterin
83dea4789f
EIP 2929 -> final (#3501) 2021-04-16 14:15:14 +08:00
Nicolás Venturo
b3382c03fe
Automatically merged updates to draft EIP(s) 2929 (#3484)
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
2021-04-09 23:21:53 +12:00
Martin Holst Swende
ae79580643
eip2929 and eip2930: move to last call (#3457) 2021-04-01 22:30:20 +02:00
Vie
676abd5e10
EIP-2929: fix typo (#3363) 2021-03-11 14:10:31 +08:00
Pooja Ranjan
197f0c8881
Change EIP-2929 status from "Draft" to "Review" (#3233) 2021-02-01 10:40:57 -07:00
Martin Holst Swende
62f5f2105e
Automatically merged updates to draft EIP(s) 2929 (#3063)
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
2020-10-22 19:06:45 +13:00
Martin Holst Swende
134f68d8b8
Automatically merged updates to draft EIP(s) 2929 (#3060)
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
2020-10-20 00:05:21 +13:00
Micah Zoltu
15f61ed0fd
Adds rule to EIP-1 that references to other EIPs must use relative path format and the first reference must be linked. (#2947)
I have gone through and updated all existing EIPs to match this rule, including EIP-1.

In some cases, people were using markdown citations, I suspect because the long-form was a bit verbose to inline.  Since the relative path is quite short, I moved these to inline but I wouldn't be opposed to putting them back to citation format if that is desired by the authors.

In doing the migration/cleanup, I found some EIP references to EIPs that don't actually exist.  In these cases I tried to excise the reference from the EIP as best I could.

It is worth noting that the Readme actually already had this rule, it just wasn't expressed properly in EIP-1 and the "Citation Format" section of the readme I think caused people a bit of confusion (when citing externally, you should use the citation format).
2020-09-30 12:22:43 +08:00
Martin Holst Swende
2adc96a603
EIP-2929: clarifications (#2998) 2020-09-26 11:43:07 +02:00
Martin Holst Swende
b032f384a2
EIP-2929: clarifications about scope revertals (#2984) 2020-09-18 08:53:41 +02:00
vbuterin
c506f8ee11
Optional access lists (#2930)
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.
2020-09-02 10:02:59 +08:00
vbuterin
12e25bb307
Fixes to EIP 2929 formatting
Thanks to @lightclient and @MicahZoltu for all the suggestions/fixes!
2020-09-02 09:32:55 +08:00
vbuterin
e7ffa279c4
Gas cost increases for state access opcodes (#2929)
Increase the gas cost of SLOAD to 2100, and the CALL opcode family, BALANCE and the EXT* opcode family to 2600. Exempts (i) precompiles, and (ii) addresses and storage slots that have already been accessed in the same transaction. Additionally reforms SSTORE metering and SELFDESTRUCT to ensure "de-facto storage loads" inherent in those opcodes are priced correctly.
2020-09-02 00:11:28 +08:00