status-im/EIPs
2
0
Fork 0
mirror of https://github.com/status-im/EIPs.git synced 2025-02-23 20:28:21 +00:00
Code Issues Projects Releases Wiki Activity

Automatically merged updates to draft EIP(s) 695 (#2643)

Browse Source 
Hi, I'm a bot! This change was automatically merged because:

 - It only modifies existing Draft or Last Call EIP(s)
 - The PR was approved or written by at least one author of each modified EIP
 - The build is passing
This commit is contained in:
Erik Marks 2020-05-14 01:18:27 -07:00 committed by GitHub
parent 14c3b08887
commit 3f639902b9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
EIPS/eip-695.md
View File

@ -1,7 +1,7 @@
--- ---
eip: 695 eip: 695
title: Create `eth_chainId` method for JSON-RPC title: Create `eth_chainId` method for JSON-RPC
author: Isaac Ardis <isaac.ardis@gmail.com>, Wei Tang (@sorpaas), Fan Torchz (@tcz001), Erik Marks <rekmarks@protonmail.com> author: Isaac Ardis <isaac.ardis@gmail.com>, Wei Tang (@sorpaas), Fan Torchz (@tcz001), Erik Marks (@rekmarks)
discussions-to: https://ethereum-magicians.org/t/eip-695-create-eth-chainid-method-for-json-rpc/1845 discussions-to: https://ethereum-magicians.org/t/eip-695-create-eth-chainid-method-for-json-rpc/1845
type: Standards Track type: Standards Track
category: Interface category: Interface
@ -20,7 +20,7 @@ Include `eth_chainId` method in `eth_`-namespaced JSON-RPC methods.
The `eth_chainId` method should return a single STRING result The `eth_chainId` method should return a single STRING result
for an integer value in hexadecimal format, describing the for an integer value in hexadecimal format, describing the
currently configured `CHAIN_ID` value used for signing replay-protected transactions, currently configured `CHAIN_ID` value used for signing replay-protected transactions,
introduced by [EIP 155](https://eips.ethereum.org/EIPS/eip-155). introduced by [EIP-155](https://eips.ethereum.org/EIPS/eip-155).
## Motivation ## Motivation
@ -34,7 +34,7 @@ the RPC.
### `eth_chainId` ### `eth_chainId`
Returns the currently configured chain ID, a value used in replay-protected transaction Returns the currently configured chain ID, a value used in replay-protected transaction
signing as introduced by [EIP 155](https://eips.ethereum.org/EIPS/eip-155). signing as introduced by [EIP-155](https://eips.ethereum.org/EIPS/eip-155).
The chain ID returned should always correspond to the information in the current known The chain ID returned should always correspond to the information in the current known
head block. This ensures that caller of this RPC method can always use the retrieved head block. This ensures that caller of this RPC method can always use the retrieved
@ -81,7 +81,7 @@ Not relevant.
Consumers should prefer `eth_chainId` over `net_version`, so that they can reliably identify chain they are communicating with. Consumers should prefer `eth_chainId` over `net_version`, so that they can reliably identify chain they are communicating with.
Implementers should take care to implement `eth_chainId` correctly and promote its use, since the chain ID is critical in replay attack prevention as described in [EIP 155](https://eips.ethereum.org/EIPS/eip-155), and consumers will rely on it to identify the chain they are communicating with. Implementers should take care to implement `eth_chainId` correctly and promote its use, since the chain ID is critical in replay attack prevention as described in [EIP-155](https://eips.ethereum.org/EIPS/eip-155), and consumers will rely on it to identify the chain they are communicating with.
## Implementation ## Implementation
@ -91,7 +91,7 @@ Implementers should take care to implement `eth_chainId` correctly and promote i
## Reference ## Reference
Return value `QUANTITY` adheres to standard JSON RPC hex value encoding, as documented here: https://github.com/ethereum/wiki/wiki/JSON-RPC#hex-value-encoding. Return value `QUANTITY` adheres to standard JSON RPC hex value encoding, as documented in the [Ethereum Wiki](https://github.com/ethereum/wiki/wiki/JSON-RPC#hex-value-encoding).
## Copyright ## Copyright