Both Ethereum client developers and downstream dapp developers lack a formal Ethereum RPC specification. This proposal attempts to standardize such a specification in a way that's versionable, human-readable and machine-readable. It will improve the accuracy of documentation, API, and clients.
Ethereum clients can expose RPC endpoints with differing method signatures; this forces applications to work around method inconsistencies to maintain compatibility with various Ethereum RPC implementations.
Much of Ethereums effectiveness as an enterprise-grade application platform depends on its ability to provide a reliable and predictable developer experience.
The clients are generated from the OpenRPC Document
openrpc.json in this repository, and can be used as an alternative to web3.js or ethers.js but for various languages:
npm install @etclabscore/ethereum-json-rpc --save
Add this to your Cargo.toml:
[dependencies] ethereum-json-rpc = "0.0.0-development"
Proposals to make method changes should be made as an issue.
- Ethereum JSON-RPC Specification walkthrough
- @bitpshr - https://github.com/ethereum/EIPs/pull/1474