You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So far, we have not made use of the try_state hooks which are part of the try-runtime feature. It provides checks which should ensure that the state of the pallet is consistent and correct. Usually, these checks should check all of the invariants that are expected to be held on all of the storage items of some particular pallet. This hook should not alter any storage though.
This issue should serve as an entry point and only be closed once we have try_state implemented for all pallets or decided certain pallets don't need it.
Description
So far, we have not made use of the
try_state
hooks which are part of thetry-runtime
feature. It provides checks which should ensure that the state of the pallet is consistent and correct. Usually, these checks should check all of the invariants that are expected to be held on all of the storage items of some particular pallet. This hook should not alter any storage though.This issue should serve as an entry point and only be closed once we have
try_state
implemented for all pallets or decided certain pallets don't need it.Research/based on
How will this affect the code base
What are foreseen obstacles or hurdles to overcome?
try_state
is only usable on a per-pallet level. See Allow runtime-wideTryState
checks paritytech/polkadot-sdk#235The text was updated successfully, but these errors were encountered: