Crate pezkuwi_subxt_core 

subxt-core

A #[no_std] compatible subset of the functionality provided in the subxt crate. This contains the core logic for encoding and decoding things, but nothing related to networking.

Here’s an overview of the main things exposed here:

• blocks: decode and explore block bodies.
• constants: access and validate the constant addresses in some metadata.
• custom_values: access and validate the custom value addresses in some metadata.
• storage: construct storage request payloads and decode the results you’d get back.
• tx: construct and sign transactions (extrinsics).
• runtime_api: construct runtime API request payloads and decode the results you’d get back.
• events: decode and explore events.

Re-exports

pub extern crate alloc;

pub use config::Config;

pub use error::Error;

Modules

blocks

Decode and iterate over the extrinsics in block bodies.

client

A couple of client types that we use elsewhere.

config

This module provides a Config type, which is used to define various types that are important in order to speak to a particular chain. BizinikiwConfig provides a default set of these types suitable for the default Bizinikiwi node implementation, and PezkuwiConfig for a Pezkuwi node.

constants

Access constants from metadata.

custom_values

Access custom values from metadata.

dynamic

This module provides the entry points to create dynamic transactions, storage and constant lookups.

error

The errors that can be emitted in this crate.

events

Decode and work with events.

ext

Re-exports of some of the key external crates.

runtime_api

Encode runtime API payloads, decode the associated values returned from them, and validate static runtime API payloads.

storage

Encode storage keys, decode storage values, and validate static storage addresses.

tx

Construct and sign transactions.

utils

Miscellaneous utility helpers.

view_functions

Encode View Function payloads, decode the associated values returned from them, and validate static View Function payloads.

Structs

Metadata

Node metadata. This can be constructed by providing some compatible frame_metadata which is then decoded into this. We aim to preserve all of the existing information in the incoming metadata while optimizing the format a little for Subxt’s use cases.