Expand description
Reth RPC implementation
Provides the implementation of all RPC interfaces.
§Note on blocking behaviour
All async RPC handlers must non-blocking, see also What is blocking.
A lot of the RPC are using a mix of async and direct calls to the database, which are blocking and can reduce overall performance of all concurrent requests handled via the jsonrpsee server.
To avoid this, all blocking or CPU intensive handlers must be spawned to a separate task. See
the EthApi handler implementations for examples. The rpc-api traits make no use of the
available jsonrpsee blocking
attribute to give implementers more freedom because the
blocking
attribute and async handlers are mutually exclusive. However, as mentioned above, a
lot of handlers make use of async functions, caching for example, but are also using blocking
disk-io, hence these calls are spawned as futures to a blocking task manually.
Re-exports§
pub use eth::EthApi;
pub use eth::EthApiSpec;
pub use eth::EthFilter;
pub use eth::EthPubSub;
pub use eth::EthSubscriptionIdProvider;
Modules§
eth
namespace handler implementation.- Additional helpers for converting errors.
Macros§
- A macro that implements the
ToRpcResult
for a specific error type
Structs§
admin
API implementation.debug
API implementation.- Re-export for convenience The Engine API implementation that grants the Consensus layer access to data and functions in the Execution layer that are crucial for the consensus process.
- A wrapper type for the
EthApi
andEthFilter
implementations that only expose the required subset for theeth_
namespace used in auth server alongside theengine_
namespace. Net
API implementation.- Otterscan API.
rpc
API implementation.reth
API implementation.trace
API implementation.txpool
API implementation.web3
API implementation.