mirror of
https://github.com/status-im/EIPs.git
synced 2025-02-23 12:18:16 +00:00
15f61ed0fd
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).
40 lines
1.7 KiB
Markdown
40 lines
1.7 KiB
Markdown
---
|
|
eip: 1716
|
|
title: "Hardfork Meta: Petersburg"
|
|
author: Afri Schoedon (@5chdn), Marius van der Wijden (@MariusVanDerWijden)
|
|
type: Meta
|
|
status: Final
|
|
created: 2019-01-21
|
|
requires: 1013, 1283
|
|
---
|
|
|
|
## Abstract
|
|
|
|
This meta-EIP specifies the changes included in the Ethereum hardfork that removes [EIP-1283](./eip-1283.md) from [Constantinople](./eip-1013.md).
|
|
|
|
## 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](./eip-1283.md): 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](https://medium.com/chainsecurity/constantinople-enables-new-reentrancy-attack-ace4088297d9). Removing this was agreed upon at the [All-Core-Devs call #53 in January 2019](https://github.com/ethereum/pm/issues/70).
|
|
2. https://blog.ethereum.org/2019/02/22/ethereum-constantinople-st-petersburg-upgrade-announcement/
|
|
|
|
## Copyright
|
|
|
|
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
|