Block decoding failure is recurring in Westend.

[makkanlover]

The issue of failed block decoding that occurred previously has resurfaced in the Westend Asset Hub.

The affected blocks are the following four blocks. As before, information for these blocks could not be confirmed via Subtrace Portal.

13440239
13440261
13440262
13440294

Subtrace Portal
https://polkadot.js.org/apps/#/explorer/query/13440239

I understand this was resolved in v16.4.7, but I'm using version 16.4.9 and find it odd that this issue is occurring.

This would be problematic if it happens on Mainnet. Do you have any idea what might be causing it?

logs

[ERROR] default - Error: createType(SignedBlock):: Struct: failed on block: {"header":"Header","extrinsics":"Vec<Extrinsic>"}:: Struct: failed on extrinsics: Vec<Extrinsic>:: createType(ExtrinsicV4):: createType(Call):: findMetaCall: Unable to find Call with index [218, 168]/[218,168]

[josepot]

The PAPI console can decode all these blocks without any issues:

13440239
13440239
13440261
13440262
13440294

Also, I think that I know what's the reason why the PJS console is not able to decode these blocks: it's almost certainly because they contain transactions that use a foreign asset as the asset of the ChargeAssetTxPayment extension. We can clearly see that on the PAPI console:

I really, really, really hope that we get the financing needed to improve and finish the PAPI console, so that we can finally deprecate the PJS one 🤞.

[TarikGul]

The PAPI console can decode all these blocks without any issues:

13440239 13440239 13440261 13440262 13440294

Also, I think that I know what's the reason why the PJS console is not able to decode these blocks: it's almost certainly because they contain transactions that use a foreign asset as the asset of the ChargeAssetTxPayment extension. We can clearly see that on the PAPI console:

I really, really, really hope that we get the financing needed to improve and finish the PAPI console, so that we can finally deprecate the PJS one 🤞.

+1

[makkanlover]

@josepot @TarikGul
I understand why it can't be verified on Subtrace, thank you.

However, that's not the core of the issue.
On my end, when executing getBlock using the Polkadot-API, I'm encountering the error “Struct: failed on block” as initially reported.
I tried upgrading to the latest v16.5.4 (v16.5.5 wasn't published on npm yet), but the problem remains unresolved.

Given that a runtime update handling this ETH is scheduled for mainnet today, I consider this situation urgent.

[awpzh]

is this issue somehow related #6208 ?

[josepot]

is this issue somehow related #6208 ?

yes