A spectre is haunting cosmos — the spectre of governators. All the powers of the hub have entered into a holy alliance to exorcise this spectre: Pupm0s and SG1, Cosmostation and Nostradamus, Kitteh’s Radical Osmonauts and Jovian police-spies.
Where is the party in opposition that has not been decried as gocernistic by its opponents in power? Where is the opposition that has not hurled back the branding reproach of governators, against the more advanced opposition delegators, as well as against its reactionary validators?
I couldn’t resist, plus we finally have a forum worthy of creative work so there we go
As I understand it, there has been talk of creating a system that allows for a novel type of political representative in cosmos. In Cosmos there are two types of vote power, consensus vote power and governance vote power. Governatists are suggesting that we separate the two of them.
The idea is laid out here by Jim Yang, And I think that he’s among the people who has thought most about this concept.
Personally, I don’t feel that he’s got it quite right yet but I don’t think that he thinks he’s got it yet either.
Because of my arrogance and experience, I think I might have it approximately correct, and so I’m going to lay out a separation of powers that can also overlap so as not to infringe upon the rights of validators, who are in fact simply account addresses on the chain, anyone can be a validator.
IRL, separation of powers is most easily observed in The design of the United States federal government, which features a legislative branch that makes laws, an executive branch that sets direction, and a judicial branch that enforces law.
For the time being, and to produce a workable prototype, we will skip the judicial branch, but there have obviously been times when a judicial branch would be useful, please place a mental bookmark here.
Delegators determine both consensus vote power and governance vote power. It makes good sense that they may wish to choose a different political representative than the people operating their infrastructure.
There are most certainly infrastructure operators who may wish to just operate infrastructure, and not have the obligation of dealing with political matters, or even to not have blame placed upon them, for not dealing with political matters.
However, there are also times when the involvement of infrastructure operators is of paramount importance, like software upgrade proposals and client update proposals.
And now, the separation is revealed.
Governators should have governance vote power in all matters that do not pertain to infrastructure operation.
- Grant funding
- Matters of direction and procedure
- Incentive balancing
- Partnerships with other chains
- New initiatives that do not relate directly to infrastructure operation
Consensus vote power should remain full (governators have no say here) by the governators on the following matters:
- Software upgrade proposals
- Client update proposals
- Other proposals which may not yet have been introduced, that deal strictly with infrastructure operation
- Proposals to slash validators
- Parameter changes that would affect the validators set, like the adjustment of minimum commissions, The downtime window, the downtime slash and the equivocation slash
In the system, validators can be governators. Governators can also be validators. Because the cosmos has had thousands of completely electoral fraud free Mass scale governance decisions, and because validators and governators are not necessarily individuals, but could be groups of individuals, there is no need to have separation between governators and validators.
With that said, validators should be able to choose not to be governators, if that is what they desire, and governators should be able to choose not to be validators, if that is what they desire. In the present state, there are some validators who are governators and validators, and governance is an expected activity of all validators. With this in mind, I wish to move to define the duties of validators and governators.
Validators will have a clearly defined technical role that is focused on network security.
Validators and their delegators can be slashed for non participation in software upgrade governance proposals and client update governance proposals.
The abstain option can be removed,
veto must be retained because it mirrors consensus.
Non-technical validators who use VAAS can stop validating, and just governate or just stop.
Governators and their delegators can be slashed and and governators can be tombstoned for non participation in governance.
The abstain option can be removed.
Veto is not needed here because these changes should not affect consensus.
There can be an unlimited number of governators because governation does not require running a node or participating in consensus.
The governator role will not require an understanding of blockchain operations, software engineering, network health and security and things like that although those are probably helpful traits, they are no longer a hard requirement.
These will be baked into the CLI once the governator software is completed so that anyone making a create validator transaction or a create governator transaction must declare one or both oaths.
I, an osmosis validator, swear to uphold the integrity of the state of the osmosis blockchain and to participate in the approval or disapproval of software upgrades and client updates. I will check the code diligently and I will at all times fiercely predict the integrity of osmosis. I will step aside if I am unable to fulfill these duties.
I, an osmosis governator, swear to use my skills to advance the interests of the osmosis blockchain and its community at all times. When making decisions that concern osmosis, osmosis shall be paramount in my eyes. I will step aside if I am unable to fulfill these duties.
Now that we have defined roles, and we have looked into the reality that there are certain situations where it is extremely important for validators to represent delegators, and we have dealt with the reality that on the osmosis blockchain, every account address should be able to perform every possible role, we can see that validators can be governators, governators can be validators, and that some validators and governators may choose to opt out of one role.