substrate-api-client
substrate-api-client copied to clipboard
scs
Library for connecting to substrate API over WebSockets
- is the current example enough? - would it make sense to provide extra benchmark funktions for easy benchmarking?
Currently, only the tungstenite client offers something in that direction. Jsonrpsee sadly does offer any easy reconnection yet. See https://github.com/paritytech/jsonrpsee/issues/678 or https://github.com/paritytech/jsonrpsee/issues/949 Tricky: How to avoid endless loops? A node...
Should be estimated again after #382
Reasoning: Examples will be no longer configurable after merge of https://github.com/scs/substrate-api-client/pull/242. But it would be still handy to be able to run the api client with different chains from time...
Implement password encryption in the CLI, as decribed [here](https://github.com/scs/substrate-api-client/wiki/Concept:-Commandline-wallet-with-decent-security#password-protection) also consider this original comment from @brenzi on this task: the current use of the keystore doesn't provide good devX, because...
Currently, when printing metadata, the constants are printed in their encoded state: ``` Name: DbWeight, Type: RuntimeDbWeight, Value[64, 120, 125, 1, 0, 0, 0, 0, 0, 225, 245, 5, 0,...
There are a few string and value interpretation in the rpc clients (mostly ws-client and tungstenite) that should be unit tested. See PR disscussion: https://github.com/scs/substrate-api-client/pull/662#discussion_r1384520652
Work to upgrade node to version 1.0.6 temporary helper to fix https://github.com/integritee-network/parachain/issues/75 DO NOT MERGE (but keep it for reference)
Currently, every `compose_extrinsic!` call, calls the substrate storage. There's already a workaround for this by using `ccompose_extrinsic_offline!`, but it sure would be nice, to have a nonce cache that caches...