Trait TxPoolApiClient
pub trait TxPoolApiClient<T>: ClientT{
// Provided methods
fn txpool_status(
&self,
) -> impl Future<Output = Result<TxpoolStatus, Error>> + Send { ... }
fn txpool_inspect(
&self,
) -> impl Future<Output = Result<TxpoolInspect, Error>> + Send { ... }
fn txpool_content_from(
&self,
from: Address,
) -> impl Future<Output = Result<TxpoolContentFrom<T>, Error>> + Send { ... }
fn txpool_content(
&self,
) -> impl Future<Output = Result<TxpoolContent<T>, Error>> + Send { ... }
}
Expand description
Client implementation for the TxPoolApi
RPC API.
Provided Methods§
fn txpool_status(
&self,
) -> impl Future<Output = Result<TxpoolStatus, Error>> + Send
fn txpool_status( &self, ) -> impl Future<Output = Result<TxpoolStatus, Error>> + Send
Returns the number of transactions currently pending for inclusion in the next block(s), as well as the ones that are being scheduled for future execution only.
See here for more details
fn txpool_inspect(
&self,
) -> impl Future<Output = Result<TxpoolInspect, Error>> + Send
fn txpool_inspect( &self, ) -> impl Future<Output = Result<TxpoolInspect, Error>> + Send
Returns a summary of all the transactions currently pending for inclusion in the next block(s), as well as the ones that are being scheduled for future execution only.
See here for more details
fn txpool_content_from(
&self,
from: Address,
) -> impl Future<Output = Result<TxpoolContentFrom<T>, Error>> + Send
fn txpool_content_from( &self, from: Address, ) -> impl Future<Output = Result<TxpoolContentFrom<T>, Error>> + Send
Retrieves the transactions contained within the txpool, returning pending as well as queued transactions of this address, grouped by nonce.
See here for more details
fn txpool_content(
&self,
) -> impl Future<Output = Result<TxpoolContent<T>, Error>> + Send
fn txpool_content( &self, ) -> impl Future<Output = Result<TxpoolContent<T>, Error>> + Send
Returns the details of all transactions currently pending for inclusion in the next block(s), as well as the ones that are being scheduled for future execution only.
See here for more details
Dyn Compatibility§
This trait is not dyn compatible.
In older versions of Rust, dyn compatibility was called "object safety", so this trait is not object safe.