Concept
Signaling proposals are a typical practice in blockchain governance activities. They provide a means for the community to gauge sentiment or reach consensus on a particular issue or suggestion without necessitating changes to the blockchain's state. However, these proposals simplify multifaceted issues into binary 'yes/no' votes, potentially distorting the accurate representation of varied community perspectives on complex issues. Additionally, they may slow down decision-making and introduce inefficiency to the overall governance process. Such potential drawbacks have led some projects, such as Ethereum and Celestia, to favor off-chain governance, a shift that arguably contradicts the decentralization principle.
Because of KIRA network's unique governance ranking system, the inclusion of signaling proposals adds another layer of complexity, potentially skewing the decision-making process as votes could be influenced more by score preservation than by authentic opinions. To circumvent these challenges, KIRA network introduces the Poll module, which offers a more inclusive and flexible mechanism for consensus. Unlike traditional signaling proposals, a Poll Proposal allows a select group of individuals to either present their own voting options or vote on pre-existing ones. This approach caters to a wide array of use cases and fosters a more accurate reflection of the diverse interests across various scenarios, such as agreeing on upgrade timeframes, selecting group administrators, or deciding on future changes to the network properties registrar.
Proposing & Voting Rights
For any users to initiate a Poll, the necessary permission, represented by the 
66, must be directly assigned to their account or embedded within a Role associated with their account. This permission is automatically granted to Councilors upon claiming their Councillor Seat. Contrary to KIRA Proposals, Polls do not have a corresponding voting permission. Rather, the user submitting the proposal determines which roles can vote on the particular Poll by setting up a whitelist.
66, must be directly assigned to their account or embedded within a Role associated with their account. This permission is automatically granted to Councilors upon claiming their Councillor Seat. Contrary to KIRA Proposals, Polls do not have a corresponding voting permission. Rather, the user submitting the proposal determines which roles can vote on the particular Poll by setting up a whitelist.Decision-Making Process
The decision-making process for the Poll module operates in line with the principles established by the Proposals logic, while accommodating the unique requirements of this module. This process is guided by the following key points:
Voting Eligibility: All whitelisted roles can cast a vote per poll. This vote can be changed later on by sending another voting transaction.
Vote Options: A single vote can correspond to one or many voting options, as outlined by the options.choices variable.
Custom Choices: Voters are permitted to cast custom choices if the options.count exceeds the options.values.length. Such custom choices are subsequently added to options.values, enabling other users to vote on them. However, each voter can only cast a vote for a specific option once.
Abstain and Veto: Regardless of the defined options.values, voters are allowed to vote abstain or veto. These are reserved values and don't have to match the options.type.
Proposal Timeline: Poll proposals do not have an enactment time. A proposal can neither pass, be rejected, nor vetoed before its voting_end_time time has elapsed, unless all eligible voters have cast their votes and the result is decisive.
Quorum Requirement: A poll necessitates a minimum number of votes, or a quorum, to be considered valid. The quorum is essential for ensuring adequate participation and representation in the decision-making process.
The poll minimum quorum percentage is the same as the proposal quorum, 33% by default and is configurable by governance via the vote_quorum network property.
The outcome of a Poll proposal is determined based on the following rules:
Other Relevant Network Properties
The following network properties establish limits over some of the Poll parameters:
The max_proposal_poll_option_size denotes the maximum character size of an individual Poll option and is set at 64 by default.
The max_proposal_poll_option_count sets the maximum number of custom options a Poll can have and is set at 128 by default.
The max_proposal_reference_size is used to indicate the maximum reference size in the poll and has a default value set at 512.
The max_proposal_checksum_size represents the maximum checksum size in the poll and is set to default at 128.
Parameters
Polls Parameters
PollOptions type
Vote Options ID
Polls Status
CLI syntax & examples
Each CLI command and proposal process in KIRA requires specific permissions. These permissions must be added to the account's whitelist or obtained as sudo permissions for direct changes. Refer to the 
Roles & Permissions documentation for more details. $SIGNER represents the transaction signer's account name or address. For instructions on setting common flags as environment variables, such as $FLAGS_TX and $FLAGS_QR, see the 
CLI flags configuration section
Roles & Permissions documentation for more details. $SIGNER represents the transaction signer's account name or address. For instructions on setting common flags as environment variables, such as $FLAGS_TX and $FLAGS_QR, see the CLI flags configuration sectionGovernance
N/A
Transactions
sekaid tx customgov
poll
create - Initiates the creation of a new poll.
vote - Cast a vote on an existing poll.
Create Poll
Create a new poll using the create command.
Flags
$TITLE: The title of the poll.
$DESCRIPTION: The description of the poll, it can be a URL, text, etc.
$REFERENCE: IPFS CID or URL reference to file describing the poll and voting options in depth.
$CHECKSUM: Reference checksum.
$OPTIONS: The options for the poll in the format variant1, variant2, ...
$ROLES: List of roles allowed to take part in the poll vote in the format role1, role2, ...
$COUNT: Maximum number of voting options that a poll can have.
$TYPE: Type of the options, all user supplied or predefined options must match its type.
$CHOICES: Define the maximum number of choices a voter can select.
$DURATION: The duration of the poll.
Bash
Copy
sekaid tx customgov poll create \
--from=$SIGNER $FLAGS_TX \
--title=$TITLE --description=$DESCRIPTION --reference=$REFERENCE --checksum=$CHECKSUM \
--options=$OPTIONS --roles=$ROLES --count=$COUNT --type=$TYPE \
--choices=$CHOICES --duration=$DURATION
Vote on a Poll
Cast a vote on an existing poll using the vote command.
Args
$POLL_ID: The ID of the poll you wish to vote on.
$POLL_OPTION: The option ID you are voting for.
Flags
$CUSTOM_VALUE: The custom poll value.
Bash
Copy
sekaid tx customgov poll vote $POLL_ID $POLL_OPTION \
--from=$SIGNER $FLAGS_TX \
--custom-value=$CUSTOM_VALUE
Queries
sekaid query
polls - Lists polls created by a specific address.
poll-votes - Lists all votes of a specific poll using its ID.
Query Polls by Address
Retrieve polls created by a specific address.
Args
$ADDRESS: The account address.
Bash
Copy
sekaid query polls $ADDRESS $FLAGS_QR | jq
Query Poll Votes by ID
Lists all votes for a specific poll using the poll’s ID.
Args
$POLL_ID: The unique identifier of the poll.
Bash
Copy
sekaid query poll-votes $POLL_ID $FLAGS_QR | jq