substrate-api-client icon indicating copy to clipboard operation
substrate-api-client copied to clipboard

Library for connecting to substrate API over WebSockets

Results 72 substrate-api-client issues
Sort by recently updated
recently updated
newest added

It would be nice to have an example that works with WebAssembly. We should also have some tests that run a WebAssembly executable. Some of the existing examples might actually...

We would like to provide more functionality for webassembly targets. See the findings in #272. Ideally we could build the complete client unchanged: `cargo b --target wasm32-wasi` or `cargo b...

F8-newfeature
Q9-needsdesign

## Description When trying to subscribe the transfer events from rococo local chain, getting deserialise error ``` Codec(Error { cause: Some(Error { cause: None, desc: "Could not decode `RuntimeEvent`, variant...

Parity is working on a new JSON-RPC API. We should look into this and figure out if/how we want to support it. - Old API: https://polkadot.js.org/docs/substrate/rpc/#author - New API: https://paritytech.github.io/json-rpc-interface-spec/introduction.html...

Retracted tx status means that it had been included in a block which happens to be orphaned on a non-finalized fork. We saw this happening more frequently recently and actually...

Only for release to crates.io. Do not merge!

currently, only `allow_death`is supported. Even if we could compose our own extrinsics as we like, `keep_alive` would be a very common default way to transfer https://github.com/scs/substrate-api-client/blob/8efd549a772eb4d82b84fa93ff1f597f6d0bcac3/src/extrinsic/balances.rs#L42-L62

CC @haerdib @masapr It would be great if you could publish the client-keystore to crates.io as well Not sure if you want to rename it first to match the scheme:...

Lets see what CI says