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
Currently for sudo driven validator updates, we simply reuse the validator update from cometbft. We should wrap this information inside our own custom action and add the ability to set a name.
In order to do this we will also need to add storage of the validator names within the app state machine. Currently these are only set in genesis, and there is no information app side. We should have this information as well as an ABCI query for it.
Because InitChain (cometbft docs) does not pass this information over to the app side, this could create some oddities of behaivior. It may make sense to pass all validator information through the app state & ignore the validator information stored in genesis to avoid oddities with unset names.
┆Issue Number: ENG-883
The text was updated successfully, but these errors were encountered:
Currently for sudo driven validator updates, we simply reuse the validator update from cometbft. We should wrap this information inside our own custom action and add the ability to set a name.
In order to do this we will also need to add storage of the validator names within the app state machine. Currently these are only set in genesis, and there is no information app side. We should have this information as well as an ABCI query for it.
Because
InitChain
(cometbft docs) does not pass this information over to the app side, this could create some oddities of behaivior. It may make sense to pass all validator information through the app state & ignore the validator information stored in genesis to avoid oddities with unset names.┆Issue Number: ENG-883
The text was updated successfully, but these errors were encountered: