Skip to content

Rename opcodes for clarity #1803

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nicksavers merged 7 commits into from
Apr 30, 2019
Merged

Rename opcodes for clarity #1803

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
86cca96
Add EIP for renaming opcodes for clarify
axic Jul 31, 2017
813558c
Use new header format
axic Mar 1, 2019
d650a60
Rename to eip-1803.md
axic Mar 1, 2019
0110e9a
Also rename invalid to abort
axic Mar 1, 2019
9c2a203
Mark as 1803 as Interface category
axic Apr 26, 2019
2b78070
Mention EIP-59 in 1803
axic Apr 26, 2019
4b4567d
Add opcodes to mnemonics in 1803
axic Apr 29, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions EIPS/eip-1803.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
---
eip: 1803
title: Rename opcodes for clarity
author: Alex Beregszaszi (@axic)
type: Standards Track
category: Interface
status: Draft
created: 2017-07-28
requires: 141
---

## Abstract

Rename the `BALANCE`, `SHA3`, `NUMBER`, `GASLIMIT`, `GAS` and `INVALID` opcodes to reflect their true meaning.

## Specification

Rename the opcodes as follows:
- `BALANCE` (`0x31`) to `EXTBALANCE` to be in line with `EXTCODESIZE`, `EXTCODECOPY` and `EXTCODEHASH`
- `SHA3` (`0x20`) to `KECCAK256`
- `NUMBER` (`0x43`) to `BLOCKNUMBER`
- `GASLIMIT` (`0x45`) to `BLOCKGASLIMIT` to avoid confusion with the gas limit of the transaction
- `GAS` (`0x5a`) to `GASLEFT` to be clear what it refers to
- `INVALID` (`0xfe`) to `ABORT` to clearly articulate when someone refers this opcode as opposed to "any invalid opcode"

## Backwards Compatibility

This has no effect on any code. It can influence what mnemonics assemblers will use.

## Implementation

Not applicable.

## References

Renaming `SHA3` was previously proposed by [EIP-59](https://github.com/ethereum/EIPs/issues/59).

## Copyright

Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).