dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_1474
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_1474 [2020/11/13 02:21] nick ↷ Links adapted because of a move operation |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_1474 [2021/08/11 10:57] (current) murphy |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| === Simple Summary === | === Simple Summary === | ||
| - | : //This proposal defines a standard set of remote procedure call methods that an Ethereum node should implement.// | + | : //This proposal defines a standard set of remote procedure call methods that an [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum_node|Ethereum node]] should implement.// |
| === Abstract === | === Abstract === | ||
| - | : //Nodes created by the current generation of Ethereum clients expose inconsistent and incompatible [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:1831]] methods because no formal Ethereum RPC specification exists. This proposal standardizes such a specification to provide developers with a predictable Ethereum RPC interface regardless of underlying node implementation.// | + | : //[[dido:public:ra:xapend:xapend.a_glossary:n:node|Nodes]] created by the current generation of Ethereum clients expose inconsistent and incompatible [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:1831]] methods because no formal Ethereum RPC specification exists. This proposal standardizes such a specification to provide developers with a predictable Ethereum RPC interface regardless of underlying node implementation.// |
dido/public/ra/xapend/xapend.b_stds/defact/ethereum/eip/erc_1474.1605252098.txt.gz · Last modified: 2020/11/13 02:21 by nick
