substrate-api-client
substrate-api-client copied to clipboard
scs
Library for connecting to substrate API over WebSockets
The goal of this task is to evaluate the possibilities to add light client functionality to the api-client. This includes: - Research existing light client libraries - Small PoC with...
We have full access to the metadata, but it's hardly used yet. Can we do more with that? E.g. like this comments suggests: https://github.com/scs/substrate-api-client/blob/7e5962bd2c9149f990b34aa25ad7bc7f6f92c868/compose-macros/src/lib.rs#L38-L39 Check out subxt example: https://github.com/paritytech/subxt/blob/master/subxt/src/tx/tx_client.rs#L56-L73
## Current issue Previously, a lot of input parameters were necessary to define the `Api` struct. That's no longer the case with our `Config`. So instead of directyl implementing a...
With https://github.com/scs/substrate-api-client/pull/541 we decode blocks with `OpaqueExtrinsic`. As this is not human readable, it would be nice for the users to still have a convenient function to decode the block...
There are still many not yet defined getter / extrinsic calls. For ease of use, one could implement more of such helper functions Check out substrate side rpc calls: https://github.com/paritytech/substrate/tree/7d233c2446b5a60662400a0a4bcfb78bb3b79ff7/client/rpc-api/src...
The method could provide a nice use case for the async functionality. At the moment the blocks are fetched in sequence but we could fetch them all at once and...
Implement the case: [2. Store the private key on the Yubikey. This means that we do not need the local storage anymore. ](https://github.com/scs/substrate-api-client/wiki/Concept:-Commandline-wallet-with-decent-security#2-store-the-private-key-on-the-yubikey-this-means-that-we-do-not-need-the-local-storage-anymore)
Implement 2FA with yubikey, as described [here](https://github.com/scs/substrate-api-client/wiki/Concept:-Commandline-wallet-with-decent-security#encryption-with-2nd-factor): - [ ] #485 - [ ] #486 See also @brenzi original comment on this task: support storage of substrate account keys protected...
As described in [1. Use a symmetric key to encrypt and decrypt the private key with the Yubikey.](https://github.com/scs/substrate-api-client/wiki/Concept:-Commandline-wallet-with-decent-security#1-use-a-symmetric-key-to-encrypt-and-decrypt-the-private-key-with-the-yubikey)
According to https://github.com/scs/substrate-api-client/pull/434#discussion_r1073174300: >I'm wondering if we couldn't also "move" these types into the trait? Do you think it's overkill or is there a specific reason not to do it?...