Bigna Härdi

Additionally: In general, the api-client is programmed to be very adaptable. So in the very specific case of the `MetadataHashCheck`, if someone uses an older version of the `GenericAdditionalSigned`, one...

> Always create a release for a new polkadot release No new releases for polkadot bugfix releases unless there are known issues Agreed. In this case, we can increase the...

Regarding the current backport with the Merkelized Metadata : This would mean that we remove the build flag in the next polkadot release. Correct?

We already support some of the newer API Functions. The question for this task to answer: - [ ] Which old JSON RPC functions can we deprecate? - [ ]...

Hello [chungquantin](https://github.com/chungquantin) I will check this tomorrow or the day after. Just to make sure: What is your use case? I'm guessing you don't want to simply print them, but...

I have not found any hooks exposed by the polkadot relaychain in the metadata. Though it is quite big and I may have missed something. But you can easily check...

As there has not been any activity and the original frame-metadata is fully accessible, I'm closing this issue. If you still have some questions, feel free to reopen.

With V5 and the Extrinsic Horizon, the extrinisc params get a much more important standing and probably need to be adapted a lot mroe than they have been. More infos...

Status: Issue is still open on Parity side: https://github.com/scs/substrate-api-client/actions/runs/10679457509/job/29598719257?pr=801

Yes, we should definitely change our release name as well. Suggested branch name: `polkadot-stableXXXX` or `polkadot-stableXXXX-X` (exactly the same as the one Parity uses). What do you think? As crates.io...