Struct ChainIdFiller

pub struct ChainIdFiller(/* private fields */);

A TxFiller that populates the chain ID of a transaction.

If a chain ID is provided, it will be used for filling. If a chain ID is not provided, the filler will attempt to fetch the chain ID from the provider the first time a transaction is prepared, and will cache it for future transactions.

Transactions that already have a chain_id set by the user will not be modified.

Example

let pk: PrivateKeySigner = "0x...".parse()?;
let provider =
    ProviderBuilder::<_, _, Ethereum>::default().with_chain_id(1).wallet(pk).on_http(url);

provider.send_transaction(TransactionRequest::default()).await;

Implementations

impl ChainIdFiller

pub fn new(chain_id: Option<ChainId>) -> Self

Create a new ChainIdFiller with an optional chain ID.

If a chain ID is provided, it will be used for filling. If a chain ID is not provided, the filler will attempt to fetch the chain ID from the provider the first time a transaction is prepared.

Trait Implementations

impl Clone for ChainIdFiller

fn clone(&self) -> ChainIdFiller

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ChainIdFiller

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for ChainIdFiller

fn default() -> ChainIdFiller

Returns the “default value” for a type.

impl PartialEq for ChainIdFiller

fn eq(&self, other: &ChainIdFiller) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl<N: Network> TxFiller<N> for ChainIdFiller

type Fillable = u64

The properties that this filler retrieves from the RPC. to fill in the TransactionRequest.

fn status(&self, tx: &N::TransactionRequest) -> FillerControlFlow

Return a control-flow enum indicating whether the filler is ready to fill in the transaction request, or if it is missing required properties.

fn fill_sync(&self, tx: &mut SendableTx<N>)

Performs any synchronous filling. This should be called before TxFiller::prepare and TxFiller::fill to fill in any properties that can be filled synchronously.

async fn prepare<P>( &self, provider: &P, _tx: &N::TransactionRequest, ) -> TransportResult<Self::Fillable>

where P: Provider<N>,

Prepares fillable properties, potentially by making an RPC request.

async fn fill( &self, _fillable: Self::Fillable, tx: SendableTx<N>, ) -> TransportResult<SendableTx<N>>

Fills in the transaction request with the fillable properties.

fn join_with<T>(self, other: T) -> JoinFill<Self, T>

where T: TxFiller<N>,

Joins this filler with another filler to compose multiple fillers.

fn continue_filling(&self, tx: &SendableTx<N>) -> bool

Returns true if the filler is should continue filling.

fn ready(&self, tx: &N::TransactionRequest) -> bool

Returns true if the filler is ready to fill in the transaction request.

fn finished(&self, tx: &N::TransactionRequest) -> bool

Returns true if the filler is finished filling in the transaction request.

fn prepare_and_fill<P>( &self, provider: &P, tx: SendableTx<N>, ) -> impl Send + Future<Output = TransportResult<SendableTx<N>>>

where P: Provider<N>,

Prepares and fills the transaction request with the fillable properties.

fn prepare_call( &self, tx: &mut N::TransactionRequest, ) -> impl Send + Future<Output = TransportResult<()>>

Prepares transaction request with necessary fillers required for eth_call operations asyncronously

fn prepare_call_sync( &self, tx: &mut N::TransactionRequest, ) -> TransportResult<()>

Prepares transaction request with necessary fillers required for eth_call operations syncronously

impl Eq for ChainIdFiller

impl StructuralPartialEq for ChainIdFiller

Layout

Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...) attributes. Please see the Rust Reference's “Type Layout” chapter for details on type layout guarantees.

Size: 8 bytes