Sebastian Kunert

> (Okay, a little bit harder if you need the transaction, but generally not impossible). I mean that was the interesting part, I know that the state proof goes into...

I will warp sync a new kusama node on a dev machine and see if I can find anything fishy.

I was able to reproduce this. As a quick recap, we do not prune blocks that have `FinalityNotifications` or `ImportNotifications` floating around. Only when the [`UnpinHandle`](https://github.com/paritytech/polkadot-sdk/blob/efc2132fa2ece419d36af03c935b3c2c60440eb5/substrate/client/api/src/client.rs#L402-L403) is dropped, the block...

Not an expert on this topic, but afaik we are grossly overestimating the weight consumption of some of our relay chain inherents. If we look at the average kusama block,...

@sandreim I don't think this error is related to this PR. Error is probably related to https://github.com/paritytech/polkadot-sdk/pull/7375, either your node or runtime is probably outdated. There was a bug for...

> > The changes here should be backward compatible. The main point of friction is the ParachainInherent, where new runtimes expect a different format. I am keeping the [legacy version](https://github.com/paritytech/polkadot-sdk/blob/524f9f40f450c27edbe61a838a5d6c6cf64a6cf9/cumulus/primitives/parachain-inherent/src/lib.rs#L64-L64)...

@michalkucharczyk @bkchr I think this is ready for one more round.

``` 2025-04-15 12:16:00.241 WARN tokio-runtime-worker sc_service::client::client: [Parachain] Block import error: State Database error: Too many sibling blocks at #11446699 inserted ``` This too many sibling blocks error is supposed to...

Afaik on westend we are using potato hardware. So did the node update maybe trigger some operation that just took ages due to bad hardware? I find it suspicious that...

I like the direction. Overall, we have one million CLI args and it can be overwhelming, so it seems like a good idea to summarize them. Should be stick to...