EIPs/EIPS/eip-608.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

772 B

eip title author type status created requires
608 Hardfork Meta: Tangerine Whistle Alex Beregszaszi (@axic) Meta Final 2017-04-23 150, 779

Abstract

This specifies the changes included in the hard fork named Tangerine Whistle (EIP 150).

Specification

  • Codename: Tangerine Whistle
  • Aliases: EIP 150, Anti-DoS
  • Activation:
    • Block >= 2,463,000 on Mainnet
  • Included EIPs:
    • EIP-150 (Gas cost changes for IO-heavy operations)

References

  1. https://blog.ethereum.org/2016/10/13/announcement-imminent-hard-fork-eip150-gas-cost-changes/
  2. https://blog.ethereum.org/2016/10/18/faq-upcoming-ethereum-hard-fork/

Copyright and related rights waived via CC0.