Multiple Validator Consensus Key

tendermint repo issue : https://github.com/tendermint/tendermint/issues/4076 I wrote this post to fuel up the discussion in the community about this feature. Please share ideas and opinions! Context This issue deals with more general and easier inclusive approach to active-active validator setup across the globe without relying on trustness on KMS softwares about preventing double-signing. Related discussion here( https://github.com/tendermint/tendermint/issues/1758 ) Since this feature brings very significant structural changes on Tendermint codebase, it should be well discussed and reviewed, and it should be a long term goal. Multiple Validator Consensus Keys • a validator operator mapped with a consensus identity pubkey which does not have private key.(doesn’t matter if it has one) this consensus identity key is only for identifying validator and not for vote signing. • validator register(and also can edit) multiple ordered consensus “voting” keys which belongs to the consensus identity key. these voting keys can sign votes on behalf of the consensus identity key(thus validator operator). registering and editing the list of voting keys can be done via…

Excerpt (1192 of 2514 characters). Read the whole post on the forum ↗