EIP-1344: Add chain id opcode #1344
Conversation
| type: Standards Track | ||
| status: Draft | ||
| created: 2018-08-22 | ||
| --- |
There was a problem hiding this comment.
Please add a discussions-to URL.
|
@Arachnid Hey, what do I need to do to get this merged? :D |
|
Wanted to ping this EIP. I think inclusion of this opcode for Istanbul may be very valuable for EIP-712 (#712) applications (being able to programmatically query chain ID for constructing the domain separator) |
|
Would love that too, still not sure what the best way is to push this forward :/ |
|
Have to go through the process, and place it on the Istanbul roadmap before May 17th. Would love to help you out in making this happen, if another similar EIP hasn't already been planned. |
|
@rmeissner picking up the conversation on EthMagicians, probably needs some additional detail as it's missing the "Rationale" and "Backwards Compatibility" sections. Not sure if we should write Test Cases, but the Implementation is easier enough it is probably okay leaving that empty. |
* Add chain id opcode * Update EIP number * Update file name * Add discussion-to
PR based on the issue #901
Discussions at https://ethereum-magicians.org/t/add-chain-id-opcode-for-replay-protection-when-handling-signed-messages-in-contracts/1131