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
Among the three policies, Sticky policy is designed to anchor only one proposer. If this policy were to be not deprecated in the future, it would be beneficial to have a way to select a desired validator. If the Sticky policy is to be retained, it can be implemented based on the governance item rather than by adding a field to genesis.json, which would be overengineering.
The use case of the Sticky policy may vary depending on the desired purpose. In my case, specifically, this policy greatly reduces voting-related testing time. Say there are 100 validators and round-robin is used for proposer selection, when one validator votes, they have to wait for 100 seconds to insert the vote when they are supposed to generate a block in some round. This is quite time-consuming.
The text was updated successfully, but these errors were encountered:
Among the three policies, Sticky policy is designed to anchor only one proposer. If this policy were to be not deprecated in the future, it would be beneficial to have a way to select a desired validator. If the Sticky policy is to be retained, it can be implemented based on the governance item rather than by adding a field to
genesis.json
, which would be overengineering.The use case of the Sticky policy may vary depending on the desired purpose. In my case, specifically, this policy greatly reduces voting-related testing time. Say there are 100 validators and round-robin is used for proposer selection, when one validator votes, they have to wait for 100 seconds to insert the vote when they are supposed to generate a block in some round. This is quite time-consuming.
The text was updated successfully, but these errors were encountered: