==== EIP 1898: ERC-NN Add `blockHash` to JSON-RPC methods which accept a default block parameter (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 Add `blockHash` to JSON-RPC methods which accept a default block parameter</caption>
| Title                      | Add `blockHash` to JSON-RPC methods which accept a default block parameter |
| Author                     | Charles Cooper |
| Status                     | Draft |
| Created                    | 2019-04-01  |
| Description                | [[http://eips.ethereum.org/EIPS/eip-1898]] |
| Specification              | [[http://eips.ethereum.org/EIPS/eip-1898#Specification]] |
| Category                   | Interface |
</table>

=== Simple Summary === 
  : //For JSON-RPC methods which currently accept a default block parameter, additionally allow the parameter to be a block hash.//

=== Abstract === 
  ://This EIP can be considered a generalization of [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0234| EIP234]]. It would enable [[dido:public:ra:xapend:xapend.a_glossary:c:client|clients]] to unambiguously specify the block they want to query for certain JSON-RPC methods, even if the block is not in the canonical chain. This allows clients to maintain a coherent picture of [[dido:public:ra:xapend:xapend.a_glossary:b:blockchain|blockchain]] state that they are interested in, even in the presence of reorgs, without requiring that the [[dido:public:ra:xapend:xapend.a_glossary:n:node|node]] maintain a persistent connection with the client or store any client-specific state.//