Cleanup Ethereum RPC client
See original GitHub issueRight now, the EthereumConnection uses two different connections
- HTTP for all basic RPCs,
- Websocket for subscriptions.
It would be nice to have a generic EthereumRpcClient that uses a different implementation depending on the base URL (very similar to the Tendermint-RPC Client). This EthereumRpcClient does not have subscription functionality when used with a http implementation.
This can be split into two steps:
- Update implementation respecting
baseUrl
andEthereumConnectionOptions.wsUrl
in an intelligent way - Remove field
EthereumConnectionOptions.wsUrl
(API breaking)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
cubedro/ethrpc: Fast, ultra-simple C++ RPC retrieval ... - GitHub
Fast, ultra-simple C++ RPC retrieval of Ethereum blocks and transactions. Easily extended to include transaction receipts and traces. Usage. Download the code ...
Read more >Ethereum JSON-RPC Client - metacpan.org
contract. Creates a new contract instance. Parameters: contract_address ( Optional - only if the contract already exists ), contract_abi ( Required ...
Read more >Guide to Staking on Ethereum (Ubuntu/Teku) | by Somer Esat
This is a step-by-step guide to staking on the Ethereum mainnet via an Execution Client and the Teku Consensus Client.
Read more >Blockchain Blunders: Exposing Digital Pickpockets in ... - Rapid7
Unfortunately, Ethereum clients that activate JSON-RPC and connect their wallets to the internet, essentially exposed their miner information ...
Read more >Let's build a simple asynchronous Web3 client for Ethereum ...
We can see the list of methods provided by Ethereum blockchain via JSON-RPC protocol here. Here is a sample JSON-RPC payload to get...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@willclarktech I was never facing a case where a WS connection was possible but HTTP was preferred. In some cases the stateless HTTP is better/easier, but as soon as a WS URL is provided and WS is used, it is safe to assume everything should go via WS.
Closed in #1050