==== EIP 695: Create `eth_chainId` method for JSON-RPC (DRAFT) ====
[[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip| Return to Ethereum ERCs ]]

  : **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>
<caption>Data sheet for Create `eth_chainId` method for JSON-RPC</caption>
| 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 |
</table>

=== Simple Summary === 
  : //Include ''eth_chainId'' method in ''eth_-namespaced'' JSON-RPC methods.//

=== Abstract === 
  : //The ''eth_chainId'' method 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 [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0155]] | EIP-155]].//

=== Motivation === 
  : //Currently although we can use net_version [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:1831]] 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 [[dido:public:ra:xapend:xapend.a_glossary:b:blockchain|blockchain]] using the RPC.//