Module tx

Create and submit extrinsics.

An extrinsic is submitted with an “signed extra” and “additional” parameters, which can be different for each chain. The trait crate::config::ExtrinsicParams determines exactly which additional and signed extra parameters are used when constructing an extrinsic, and is a part of the chain configuration (see crate::config::Config).

Modules

signer

A library to submit extrinsics to a substrate node via RPC.

Structs

DefaultPayload

A transaction payload containing some generic CallData.

PairSignersubstrate-compat

A Signer implementation that can be constructed from an [sp_core::Pair].

PartialExtrinsic

This payload contains the information needed to produce an extrinsic.

SubmittableExtrinsic

This represents an extrinsic that has been signed and is ready to submit.

TxClient

A client for working with transactions.

TxInBlock

This struct represents a transaction that has made it into a block.

TxProgress

This struct represents a subscription to the progress of some transaction.

Enums

TransactionInvalid

The transaction is invalid.

TransactionUnknown

The runtime was unable to validate the transaction.

TxStatus

Possible transaction statuses returned from our TxProgress::next() call.

ValidationResult

The result of performing SubmittableExtrinsic::validate().

Traits

Payload

This represents a transaction payload that can be submitted to a node.

Signer

Signing transactions requires a Signer. This is responsible for providing the “from” account that the transaction is being signed by, as well as actually signing a SCALE encoded payload.

Functions

dynamic

Construct a transaction at runtime; essentially an alias to DefaultPayload::new() which provides a Composite value for the call data.

Type Aliases

DynamicPayload

The type of a payload typically used for dynamic transaction payloads.