EIPs/eip-2488.md at ec9a79d8fe46ee73c0cc338cb2b670eb6fa1a699

mirror of https://github.com/status-im/EIPs.git synced 2025-02-22 11:48:19 +00:00

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.6 KiB

Raw Blame History

eip	title	author	discussions-to	status	type	category	created	requires
2488	Deprecate the CALLCODE opcode	Alex Beregszaszi (@axic)	https://ethereum-magicians.org/t/eip-2488-deprecate-the-callcode-opcode/3957	Draft	Standards Track	Core	2019-12-20	7

Abstract

Deprecate CALLCODE in a somewhat backwards compatible way, by making it always return failure.

Motivation

CALLCODE was part of the Frontier release of Ethereum. In the first few weeks/months it became clear that it cannot accomplish its intended design goal. This was rectified with introducing DELEGATECALL (EIP-7) in the Homestead update (early 2016).

CALLCODE became never utilized, but it still puts a burden on EVM implementations.

Disabling it will not improve the situation for any client whose goal is to sync from genesis, but would help light clients or clients planning to sync from a later point in time.

Specification

If block.number >= FORK_BLOCK, the CALLCODE (0xf2) instruction always returns 0, which signals failure.

Rationale

It would be possible just to remove the opcode and exceptionally abort if it is encountered. However, by returning failure, the contract has a chance to act on it and potentially recover.

Backwards Compatibility

This is a breaking change and has a potential to break contracts. The author expects no contracts of any value should be affected.

TODO: validate this claim.

Security Considerations

TBA

Test Cases

TBA

Implementation

TBA

1.6 KiB Raw Blame History