16 releases (9 breaking)

0.39.0 Feb 5, 2025
0.38.0 Oct 24, 2024
0.37.0 May 28, 2024
0.35.0 Mar 21, 2024
0.30.1 Jul 25, 2023

#42 in #parity

Download history 38605/week @ 2024-10-28 55284/week @ 2024-11-04 42805/week @ 2024-11-11 38867/week @ 2024-11-18 40877/week @ 2024-11-25 35003/week @ 2024-12-02 41741/week @ 2024-12-09 32629/week @ 2024-12-16 9475/week @ 2024-12-23 17303/week @ 2024-12-30 32902/week @ 2025-01-06 51139/week @ 2025-01-13 42938/week @ 2025-01-20 35530/week @ 2025-01-27 42893/week @ 2025-02-03 45544/week @ 2025-02-10

170,860 downloads per month
Used in 31 crates (via subxt)

Apache-2.0 OR GPL-3.0 and GPL-3.0-or-later…

66KB
1K SLoC

subxt · build Latest Version Documentation

Subxt is a library for interacting with Substrate based nodes in Rust and WebAssembly. It can:

  • Submit Extrinsics (this is where the name comes from).
  • Subscribe to blocks, reading the extrinsics and associated events from them.
  • Read and iterate over storage values.
  • Read constants and custom values from the metadata.
  • Call runtime APIs, returning the results.
  • Do all of the above via a safe, statically types interface or via a dynamic one when you need the flexibility.
  • Compile to WASM and run entirely in the browser.
  • Do a bunch of things in a #[no_std] environment via the subxt-core crate.
  • Use a built-in light client (smoldot) to interact with chains.

Usage

Take a look in the examples folder or the examples folder for various smaller or larger subxt usage examples, or read the guide to learn more.

Downloading metadata from a Substrate node

Use the subxt-cli tool to download the metadata for your target runtime from a node.

  1. Install:
cargo install subxt-cli
  1. Save the encoded metadata to a file:
subxt metadata -f bytes > metadata.scale

This defaults to querying the metadata of a locally running node on the default http://localhost:9933/. If querying a different node then the metadata command accepts a --url argument.

Subxt Documentation

For more details regarding utilizing subxt, please visit the documentation.

Integration Testing

Most tests require a running substrate node to communicate with. This is done by spawning an instance of the substrate node per test. It requires an up-to-date substrate executable on your path.

This can be installed from source via cargo:

cargo install --git https://github.com/paritytech/polkadot-sdk staging-node-cli --force

Real world usage

Please add your project to this list via a PR.

  • cargo-contract CLI for interacting with Wasm smart contracts.
  • xcm-cli CLI for submitting XCM messages.
  • phala-pherry The relayer between Phala blockchain and the off-chain Secure workers.
  • crunch CLI to claim staking rewards in batch every Era or X hours for substrate-based chains.
  • interbtc-clients Client implementations for the interBTC parachain; notably the Vault / Relayer and Oracle.
  • tidext Tidechain client with Stronghold signer.
  • staking-miner-v2 Submit NPos election solutions and get rewards.
  • polkadot-introspector Tools for monitoring Polkadot nodes.
  • ink! Smart contract language that uses subxt for allowing developers to conduct End-to-End testing of their contracts.
  • Chainflip A decentralised exchange for native cross-chain swaps.
  • Hyperbridge A hyperscalable coprocessor for verifiable cross-chain interoperability.
  • pop CLI The all-in-one tool for Polkadot development.

Alternatives

substrate-api-client provides similar functionality.

License

The entire code within this repository is dual licensed under the GPL-3.0 or Apache-2.0 licenses. See the LICENSE file for more details.

Please contact us if you have questions about the licensing of our products.

Dependencies

~22–37MB
~612K SLoC