Open shawntabrizi opened 1 year ago
This issue has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/weight-v2-discussion-and-updates/227/4
This issue has been mentioned on Polkadot Forum. There might be relevant details there:
This issue has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/polkadot-release-analysis/1026/2
I would also consider paritytech/polkadot-sdk#209 as critical part of considering this done.
Here is a tracking issue for all the steps I can think of, before we need to start going through all the various runtime logic, and actually use the new multi-dimensional weights v2.
RefTimeWeight
https://github.com/paritytech/substrate/pull/12157Ord
from the one dimensional weight type paritytech/substrate#12183any_gt
any_lt
all_gt
all_lt
(and the equal to variant)any_*
orall_*
. This is super important, because it could lead to bugs if incorrectly implemented, and we have 2 dimensional weights.sp-weights
paritytech/substrate#12219#[compact]
, and include that in the migration: https://github.com/paritytech/substrate/issues/12149benchmark overhead
https://github.com/paritytech/polkadot-sdk/issues/384Once we get to that point, we will need to double check our logic around benchmarking and PoV, and we can open a new tracking issue for that.