Liu-Cheng Xu cef6d697b8 Expose the rpc client in Client (#267)
When we build a `Client` for a substrate chain, we can only access the
methods exposed in `Client` which does not cover all the RPC interfaces
in the chain, it's not feasible to request the methods like `chain_getKeys`
with `Client` only. The downstream user of this library has to build another
`RpcClient` for the uncovered RPC interfaces, which can be unneccessary.
2021-05-21 11:45:34 +01:00
2021-04-14 16:20:24 +01:00
2021-03-22 17:37:15 +00:00

subxt · build Latest Version Documentation

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

Usage

See examples.

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 executable binary substrate at v3.0.0 on your path.

This can be done by downloading the prebuilt binary:

curl "https://releases.parity.io/substrate/x86_64-debian:stretch/v3.0.0/substrate/substrate" --output substrate --location
chmod +x ./substrate
mv substrate ~/.local/bin

Or installed from source via cargo:

cargo install --git https://github.com/paritytech/substrate node-cli --tag=v3.0.0 --force

Alternatives

substrate-api-client provides similar functionality.

Subxt Client

By default the client builder will connect to a full node via rpc. The subxt-client helps embedding a light client directly. It can also be used to embed a full node. This is especially useful for testing and ci.

License

The entire code within this repository is licensed under the GPLv3. Please contact us if you have questions about the licensing of our products.
S
Description
No description provided
Readme 529 MiB
Languages
Rust 99.8%
Shell 0.2%