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
We can keep shard shuffling for testing on forknet, but it is not critical and can be disabled for mainnet launch. It will help with keeping the network needs due to state sync under control as chunk producers will continue to track the same shard through different epochs.
Follow-up work to investigate and re-enable shard shuffling (likely with less frequent shuffling) will be tracked in #11201.
The text was updated successfully, but these errors were encountered:
Per #11190, move the shard-assignment shuffling feature for chunk
producers to nightly.
Also enable this feature for mocknet together with stateless validation
to exercise the state sync code path more often. Note that the guarding
for the feature in nightly/prod is different from mocknet, as we use
mocknet to exercise (stateless validation) features in between prod and
nightly.
After this change, shard shuffling will be activated in the following
cases:
1) In "nightly", it will be active by default, since we move the feature
among the set of nightly features and update the protocol version
accordingly (143).
2) In "mocknet", it will be active by default, as we enable it directly
when chain id == "mocknet".
3) In all other networks (including "mainnet", "testnet", and
"statelessnet"), it will be disabled by default and will only be enabled
(later) explicitly by moving the feature from nightly to stable protocol
version.
Compiling the binary with or without "statelessnet_protocol" will not
have any effect on the enablement of the feature (instead need to
compile with "nightly").
See related thread here.
We can keep shard shuffling for testing on forknet, but it is not critical and can be disabled for mainnet launch. It will help with keeping the network needs due to state sync under control as chunk producers will continue to track the same shard through different epochs.
Follow-up work to investigate and re-enable shard shuffling (likely with less frequent shuffling) will be tracked in #11201.
The text was updated successfully, but these errors were encountered: