Skip to content
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

Jump to bottom

EIP-1344: Add chain id opcode #1344

Merged
merged 7 commits into from
Apr 1, 2019
Merged

EIP-1344: Add chain id opcode #1344

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
3a407dd
Add chain id opcode
rmeissner Aug 22, 2018
1407b4f
Update EIP number
rmeissner Aug 23, 2018
f1ecf1f
Merge branch 'master' into patch-1
rmeissner Aug 23, 2018
c386cd3
Update file name
rmeissner Aug 23, 2018
6630b3d
Merge branch 'master' into patch-1
rmeissner Aug 28, 2018
f5885e2
Add discussion-to
rmeissner Aug 28, 2018
6e343c1
Merge branch 'master' into patch-1
rmeissner Oct 10, 2018
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
16 changes: 16 additions & 0 deletions EIPS/eip-1344.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
eip: 1344
title: ChainID opcode
author: Richard Meissner (@rmeissner)
discussions-to: https://ethereum-magicians.org/t/add-chain-id-opcode-for-replay-protection-when-handling-signed-messages-in-contracts/1131
category: Core
type: Standards Track
status: Draft
created: 2018-08-22
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a discussions-to URL.

### Specification
Adds a new opcode at 0x46, which takes 0 stack arguments. It will return the chain id of the chain where the block was mined. It should cost 2 gas (G_base) to execute this opcode.
### Motivation
[EIP-155](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-155.md) proposes to use the chain id to prevent replay attacks between different chains. It would be a great benefit to have the same possibility inside smart contracts when handling signatures.
The current approach proposed by [EIP-712](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-712.md) is to specify the chain id on compile time. Using this approach will result in problems after a hardfork.
By adding the opcode it would be possible to access the current chain id and validate signatures based on that.