Sidebar
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0695
Table of Contents
EIP 695: Create `eth_chainId` method for JSON-RPC (DRAFT)
- Note: The following is an excerpt from the official Ethereum site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference.
Table 1: Data sheet for Create `eth_chainId` method for JSON-RPC
| Title | Create `eth_chainId` method for JSON-RPC |
| Author | Isaac Ardis, Wei Tang, Fan Torchz |
| Status | Draft |
| Created | 2017-08-21 |
| Description | http://eips.ethereum.org/EIPS/eip-695 |
| Specification | http://eips.ethereum.org/EIPS/eip-695#Specification |
| Category | Interface |
Simple Summary
-
Include
eth_chainIdmethod ineth_-namespacedJSON-RPC methods.
Abstract
-
The
eth_chainIdmethod should return a single STRING result for an integer value in hexadecimal format, describing the currently configured “Chain Id” value used for signing replay-protected transactions, introduced via EIP 155: Simple replay attack protection | EIP-155]].
Motivation
- Currently although we can use net_version RFC1831 - Remote Procedure Call Protocol Specification Version 2 (RPC) call to get the current network ID, there’s no RPC for querying the chain ID. This makes it impossible to determine the current actual blockchain using the RPC.
dido/public/ra/xapend/xapend.b_stds/defact/ethereum/eip/erc_0695.txt · Last modified: 2021/07/27 13:34 by murphy
Translations of this page:
