# Weight V2 Discussion and Updates

**URL:** <https://forum.polkadot.network/t/weight-v2-discussion-and-updates/227>\
**Category:** Tech Talk\
**Tags:** frame\
**Created:** [August 31, 2022, 10:31am UTC](https://forum.polkadot.network/t/weight-v2-discussion-and-updates/227 "2022-08-31T10:31:58Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![shawntabrizi](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/shawntabrizi/32/14_2.png) [@shawntabrizi](https://forum.polkadot.network/u/shawntabrizi)\
**Post date:** [September 7, 2022, 10:45am UTC](https://forum.polkadot.network/t/weight-v2-discussion-and-updates/227/4 "2022-09-07T10:45:00Z")

</div>

The current work for Weights V2 can be tracked with this tracking issue:

> <https://github.com/paritytech/substrate/issues/12176>
>
> Here is a tracking issue for all the steps I can think of, before we need to sta…rt going through all the various runtime logic, and actually use the new multi-dimensional weights v2.
> 
> \- \[x\] deprecate \`RefTimeWeight\` https://github.com/paritytech/substrate/pull/12157
> \- \[\] Remove \`Ord\` from the one dimensional weight type #12183
> - \[\] implement \`any\_gt\` \`any\_lt\` \`all\_gt\` \`all\_lt\` (and the equal to variant)
> - \[\] go through each comparison operator usage, and CAREFULLY make sure that it uses the correct version of \`any\_\*\` or \`all\_\*\`. This is super important, because it could lead to bugs if incorrectly implemented, and we have 2 dimensional weights.
> \- \[\] Move some basic type definitions to a new crate called \`sp-weights\`
> \- \[\] Then, I think we can finally add the second field to Weight without any worry, and just some storage migrations
> - \[\] We should also make the fields of Weight \`#\[compact\]\`, and include that in the migration: https://github.com/paritytech/substrate/issues/12149
> - \[\] We will also need to make frame executive respect both weight fields, and behave correctly.
>     
> Once 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.

This does not encapsulate all the work, but will be most of the steps we need to take before everyone can start migrating their code in parallel.

---

_[View the full topic](https://forum.polkadot.network/t/weight-v2-discussion-and-updates/227)._