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
-**summary**: The maximum number of entries to keep in the set id to session index mapping.
173
+
174
+
Since the `SetIdSession` map is only used for validating equivocations this value should relate to the bonding duration of whatever staking system is being used (if any). If equivocation handling is not enabled then this value can be zero.
-**summary**: The maximum number of electing voters to put in the snapshot. At the moment, snapshots are only over a single block, but once multi-block elections are introduced they will take place over multiple blocks.
-**summary**: The amount of the unpaid reward that gets deducted in the case that either a skeptic doesn't vote or someone votes in the wrong way.
779
+
### votingPeriod: `u32`
780
+
-**interface**: `api.consts.society.votingPeriod`
781
+
-**summary**: The number of blocks on which new candidates should be voted on. Together with `ClaimPeriod`, this sums to the number of blocks between candidate intake periods.
759
782
760
783
___
761
784
@@ -778,10 +801,6 @@ ___
778
801
779
802
Note: `HistoryDepth` is used as the upper bound for the `BoundedVec` item `StakingLedger.claimed_rewards`. Setting this value lower than the existing value can lead to inconsistencies in the `StakingLedger` and will need to be handled properly in a migration. The test `reducing_history_depth_abrupt` shows this effect.
-**summary**: Maximal number of bytes that a key can have.
834
+
835
+
FRAME itself does not limit the key length. The concrete value must therefore depend on your storage usage. A [`frame_support::storage::StorageNMap`] for example can have an arbitrary number of keys which are then hashed and concatenated, resulting in arbitrarily long keys.
836
+
837
+
Use the *state migration RPC* to retrieve the length of the longest key in your storage: <https://github.com/paritytech/substrate/issues/11642>
838
+
839
+
The migration will halt with a `Halted` event if this value is too small. Since there is no real penalty from over-estimating, it is advised to use a large value. The default is 512 byte.
0 commit comments