Arjan Zijderveld

With `substrate.get_metadata_call_functions()` and `substrate.get_metadata_call_function(pallet_name, function_name)`, for more info: https://polkascan.github.io/py-substrate-interface/#substrateinterface.SubstrateInterface.get_metadata_call_functions

> Would it be possible to implement some sort of keep-alive messages to the WS during subscriptions, or alternatively make it so only the "watch" part is retried, not the...

That is interesting, I wouldn't expect that would work.. Thanks for sharing

Yes it seems like a runtime specific issue (panic in the runtime WASM), it also happens when I post the same RPC request `payment.queryInfo` on PolkadotJS with that extrinsic. Maybe...

The `get_block_metadata` function depends on the `state_getMetadata` RPC call and that the results directly contains the hex-bytes (0x...). It seems for some reason that is not the case (apparently a...

Do you have a way for me to reproduce this error you are getting? Otherwise it will be very difficult for me to analyse this or give you pointers in...

For a certain block hash you can use: ```python total_issuance = substrate.query("Balances", "TotalIssuance", block_hash="0x11a4a00cfb10aa94884afc79d31b34bb212017449748a7a130d8015108a55cb4") print(total_issuance.value) ``` This will work for all storage functions, to query the state at the time...

I would like to debug this type for you, could you provide the metadata hex-bytes? (result of `substrate.rpc_request("state_getMetadata", [])`).

@dastanbeksamatov Is the call you want to compose already available on the testnet you provided? That would help me a lot to debug

I'm not familiar with all functionality of Polkadot.js, so you have to give more context what exactly your question is..