Module bp_runtime::extensions
source · Expand description
Primitives that may be used for creating signed extensions for indirect runtimes.
Structs§
- A simplified version of signed extensions meant for producing signed transactions and signed payloads in the client code.
- An implementation of
SignedExtensionSchemausing generic params.
Traits§
- Trait that describes some properties of a
SignedExtensionthat are needed in order to send a transaction to the chain.
Type Aliases§
- The
SignedExtensionSchemaforBridgeRejectObsoleteHeadersAndMessages. - The
SignedExtensionSchemaforpallet_transaction_payment::ChargeTransactionPayment. - The
SignedExtensionSchemaforframe_system::CheckEra. - The
SignedExtensionSchemaforframe_system::CheckGenesis. - The
SignedExtensionSchemaforframe_system::CheckNonZeroSender. - The
SignedExtensionSchemaforframe_system::CheckNonce. - The
SignedExtensionSchemaforframe_system::CheckSpecVersion. - The
SignedExtensionSchemaforframe_system::CheckTxVersion. - The
SignedExtensionSchemaforframe_system::CheckWeight. - The
SignedExtensionSchemaforpolkadot-runtime-common::PrevalidateAttests. - The
SignedExtensionSchemaforRefundBridgedParachainMessages. This schema is dedicated forRefundBridgedParachainMessagessigned extension as wildcard/placeholder, which relies on the scale encoding for()or((), ()), or((), (), ())is the same. So runtime can contains any kind of tuple:(BridgeRefundBridgeHubRococoMessages)(BridgeRefundBridgeHubRococoMessages, BridgeRefundBridgeHubWestendMessages)(BridgeRefundParachainMessages1, ..., BridgeRefundParachainMessagesN)