This is the fifth of a series of articles aimed at unpacking the contents of KIRA Improvement Proposals 71-87, which will encompass 5 sets of articles. In Set 1 we covered:
This is the second article of the second set - which lays out the structure of KIRA’s onchain governance.
Councilors
Governance proposals on KIRA are created and voted upon by a permissioned subset of accounts, called Councilors. Any KIRA account that has at least one whitelisted permission or role (allowing them to create proposals or vote) is considered a Councilor.
Claiming Councilor Seat
Before any governance member can create proposals or vote, they must first “claim” their Councilor seat, in similar manner to how Validators claim their validator seat. This action will be considered an acknowledgement of KIRA Code of Conduct. When claiming, the user must supply the following information, which will be persisted in the Identity Registrar:
-
username - (required), friendly governance member name, MUST be globally unique (just like moniker).
- It should NOT be possible to remove moniker or username from globally reserved unique Identity Registrar entries, even through governance process.
-
Both moniker and username must have minimum 4 characters (non whitespace).
- Once set, it should NOT be possible to delete or wipe moniker and username.
-
description - (optional), a longer description of the Councilor.
-
social - (optional), comma-separated URL list of any social profiles such as Twitter, Telegram, etc.
-
contact - (optional), email address, URL, or another emergency contact.
-
avatar - (optional), URL to .SVG image or GIF.
Councilor Statuses
Only Councilors who have been actively participating in governance will be able to vote on new proposals. If a Councilor will be absent or unable to carry out his role in governance, he must first signal a period of planned absence to the network, or his account will be flagged as inactive.
Just like in the case of Validators, Councilors have statuses that determine their ability to perform their role of creating proposals and voting.
-
active - Default state after claiming seat. Implies Councilor ability to vote and create proposals.
-
waiting - Default state after permission to vote or propose is assigned to the KIRA account. This status is only applied to Councilors who have not yet claimed their seats.
-
inactive - Councilor stopped voting on proposals but didn’t signal to the network any planned absence.
-
paused - Councilor signaled planned absence.
-
jailed - Councilor is barred from executing any of his permissions (not just voting).
Ranking
Similarly to Validator ranking, the Councilor ranking system will be used to apply changes to statuses and collect statistics that can be utilized by network governance to determine which network actors fulfill their assigned roles. Note that the ranking of Councilors and Validators will be totally independent and will have separate logic.
Councilor activity is tracked via a ranking system that increments on participation in or abstention from proposal voting. Councilors who exceed the maximum allowance for consecutive abstentions will have their statuses changed to inactive, upon which they’ll need to reactivate their seats to be regain their governance permissions. If necessary, a governance proposal can be passed to globally reset all ranks and abstention counters simultaneously.
How This Benefits KIRA Participants
By limiting only an active subset of permissioned accounts to participate in network governance as councilors, KIRA ensures secure governance in line with its Code of Conduct from actors with reputational stake. Councilors are the custodians of KIRA governance. It is necessary that they perform their roles actively and in good faith.
Stay tuned for the next set of articles on staking within KIRA - covering the modules that enable frictionless implementation of economic primitives such as restaking derivatives.
Follow KIRA on our social platforms to stay in the loop with what we’re building:
WEB | X | GITHUB | TELEGRAM | DISCORD