-
Notifications
You must be signed in to change notification settings - Fork 707
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extrinsic accepted by the node but not included into the block #5313
Comments
I tried the TX in chopsticks and it works. Maybe some changes in the TX pool? cc @paritytech/sdk-node. Encoded TX
|
Not an expert on this topic, but afaik we are grossly overestimating the weight consumption of some of our relay chain inherents. So in none of the blocks I looked at there would be enough space for your xt. There are some efforts in progress to reduce the weight declaration, maybe @ordian or @eskimor have more details. I don't think there is a workaround at the moment to get it in with that weight. |
#5082 is the fix and will reduce the Kusama para inherent weight to ~50%. Unfortunately I also don't think there is any workaround. |
Summary
I've been trying to debug the issue with the extrinsic submission on Kusama relaychain. Extrinsic weight I am submitting is
679_460_495_220
and the max extrinsic weight fromsystem.BlockWeights::perClass.normal.maxExtrinsic.refTime
is1_479_875_294_000
. The node accepts the extrinsic and propagates it to other nodes: I can see it in the pending list if I queryauthor.pendingExtrinsics()
. However the extrinsic never included into the block and finally expires due to mortality.What might be the issue?
What I also noticed it somehow depends on the weights: if I tweak the algorithm it might break after the next runtime upgrade.
Here is an example of the extrinsic. I took it from
author.pendingExtrinsics()
. It must also include metadataHash - not sure why polkadot.js displays it asnull
Extrinsic example
The text was updated successfully, but these errors were encountered: