The current documentation only describes the minimum viable product for the governance module. Future improvements may include:
BountyProposals
: If accepted, aBountyProposal
creates an open bounty. TheBountyProposal
specifies how many Atoms will be given upon completion. These Atoms will be taken from thereserve pool
. After aBountyProposal
is accepted by governance, anybody can submit aSoftwareUpgradeProposal
with the code to claim the bounty. Note that once aBountyProposal
is accepted, the corresponding funds in thereserve pool
are locked so that payment can always be honored. In order to link aSoftwareUpgradeProposal
to an open bounty, the submitter of theSoftwareUpgradeProposal
will use theProposal.LinkedProposal
attribute. If aSoftwareUpgradeProposal
linked to an open bounty is accepted by governance, the funds that were reserved are automatically transferred to the submitter.- Complex delegation: Delegators could choose other representatives than their validators. Ultimately, the chain of representatives would always end up to a validator, but delegators could inherit the vote of their chosen representative before they inherit the vote of their validator. In other words, they would only inherit the vote of their validator if their other appointed representative did not vote.
- Better process for proposal review: There would be two parts to
proposal.Deposit
, one for anti-spam (same as in MVP) and an other one to reward third party auditors.