status-im/EIPs
2
0
Fork 0
mirror of https://github.com/status-im/EIPs.git synced 2025-02-22 11:48:19 +00:00
Code Issues Projects Releases Wiki Activity
EIPs/EIPS/eip-1716.md
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

1.7 KiB
Raw Blame History

eip title author type status created requires
1716 Hardfork Meta: Petersburg Afri Schoedon (@5chdn), Marius van der Wijden (@MariusVanDerWijden) Meta Final 2019-01-21 1013, 1283

Abstract

This meta-EIP specifies the changes included in the Ethereum hardfork that removes EIP-1283 from Constantinople.

Specification

  • Codename: Petersburg
  • Aliases: St. Petersfork, Peter's Fork, Constantinople Fix
  • Activation:
    • Block >= 7_280_000 on the Ethereum mainnet
    • Block >= 4_939_394 on the Ropsten testnet
    • Block >= 10_255_201 on the Kovan testnet
    • Block >= 4_321_234 on the Rinkeby testnet
    • Block >= 0 on the Görli testnet
  • Removed EIPs:
    • EIP-1283: Net gas metering for SSTORE without dirty maps

If Petersburg and Constantinople are applied at the same block, Petersburg takes precedence: with the net effect of EIP-1283 being disabled.

If Petersburg is defined with an earlier block number than Constantinople, then there is no immediate effect from the Petersburg fork. However, when Constantinople is later activated, EIP-1283 should be disabled.

References

  1. The list above includes the EIPs that had to be removed from Constantinople due to a potential reentrancy attack vector. Removing this was agreed upon at the All-Core-Devs call #53 in January 2019.
  2. https://blog.ethereum.org/2019/02/22/ethereum-constantinople-st-petersburg-upgrade-announcement/

Copyright

Copyright and related rights waived via CC0.