Implementing chainID dependency for versioned constants #3370
Labels
consensus breaking
modifies block validity rules in a way that will break consensus unless all nodes update their rules
WS: Big Blonks 🔭
Improving consensus critical gossiping protocols
WS: V3 3️⃣
item is directly relevant to the v3 hardfork
As part of the knuu e2etests, we need to conduct tests under different values of the current versioned constant, specifically larger square sizes. Currently, the retrieval of these values depends on the app version. We previously attempted to introduce a new app version, namely the "testground" version. However, this required changes to the versioned module manager as well, to accommodate this new custom version and ensure correct behavior. This would result in introducing custom behaviors into the production code, which could increase the risk of errors for regular users.
To avoid such confusion and inadvertent mistakes, it has been decided to make versioned constants dependent on an additional parameter, i.e., chainID. Thus, while the app version remains unchanged, we can assign various values to the same constant based on the chainID.
The text was updated successfully, but these errors were encountered: