dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_1898
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_1898 [2020/11/13 02:21] nick ↷ Links adapted because of a move operation |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_1898 [2021/08/11 11:06] (current) murphy |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| === Abstract === | === 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 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 blockchain state that they are interested in, even in the presence of reorgs, without requiring that the node maintain a persistent connection with the client or store any client-specific state.// | + | ://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.// |
dido/public/ra/xapend/xapend.b_stds/defact/ethereum/eip/erc_1898.1605252092.txt.gz · Last modified: 2020/11/13 02:21 by nick
