We propose that DFINITY implement proposals 55651 - Periodic Confirmation of Neuron Followees and 38985 - Enable Manual Voting throughout the Entire Voting Period before implementing proposal 48623 - Compounding Maturity Proposal.
A very important driver for wanting to prioritize proposals 55651 and 38985 over 48623 is that they will have a bigger impact on the decentralization of the IC. Proposal 55651 seeks to ensure that voting rewards are distributed to neurons whose owners meet a minimum standard of active participation, which is simply to confirm their Followee selections every 6 months, instead of neurons that were configured by default to follow DFINITY at genesis. Proposal 38985 seeks to allow all neurons owners to vote manually at any time during the Voting Period even if their Followee(s) has already voted. Both of these proposals are directly aligned with the ethos of active and decentralized NNS governance and the purpose of the tokenomics incentives. Proposal 48623 seeks to help neuron owners avoid incurring a tax burden. In the process of addressing this issue, the changes will also add a lot of new voting power to the NNS from ICP that is currently sitting in large genesis neurons as maturity and it will influence ICP price with the modulation function. These are not the primary objectives of NNS governance and tokenomics incentives. Hence, prioritization of proposals 55651 and 38985 over proposal 48623 seems to be more closely aligned with governance objectives at this time.
Over the past year, the NNS voting community has passed many proposals related to the NNS, including:
Dashboard NNS Proposal Links - (Note the % are out of those who voted, not total staked voting power)
 Enable Manual Voting throughout the Entire Voting Period (Passed 2022-01-11 with 91% approval)
 Periodic Confirmation of Neuron Followees (Passed 2022-04-24 with 90% approval)
 Motion Proposal for NNS Neuron ID Indexing (Passed 2022-03-12 with 74% approval)
 Compounding Maturity Proposal (Passed 2022-03-14 with 51% approval)
Even though Compounding Maturity Proposal was, and still is one of the most controversial and close governance proposal votes to pass the NNS (51% approval vs. 49% reject), the DFINITY foundation has chosen to prioritize and deliver this proposal first.
Adding on, the @jwiegley, the original DFINITY engineer who was put in charge of the original Compounding Maturity Proposal, has since left DFINITY and publicly come out against the implementation of this proposal on the developer forums.
First off, no organization, team, or employee works well being micro-managed, and most NNS voters believe in the vision and capability of DFINITY to deliver on their roadmap, as they have proven the ability to do so (good job DFINITY! ).
However, when a proposal driven and passed by the voters passes the NNS, there is some expectation that this proposal is eventually worked on, but there is currently no mechanism or guarantee that DFINITY will actually implement that proposal.
What voters see right now is that the Compounding Maturity proposal, which was the top priority of the head of DFINITY, is being prioritized in front of other proposals that passed earlier and with much higher approval. In fact, those other proposals have not even been given places on the roadmap.
In fact, 7 out of all 8 of @dominicwilliams replies on these forums until now have been with respect to the Compounding Maturity Proposal Profile - dominicwilliams - Internet Computer Developer Forum
If the implementation of proposals passed by the NNS is truly just dependent on “top down C-suite level management”, and decision making that puts their own priorities first over those of the voters, it actually shows that the NNS is not decentralized. In fact, all this shows that we are all operating under the facade of a decentralized vote.
This has even larger implications in the value of your ICP as a governance token - is it just worth the compute cycles from burning, or does your voting power actually matter? Can your vote actually drive DFINITY to implement and deliver any proposal, especially one that passed the NNS 6 months ago by a wide approval margin?
This will not be something that we in the community expect the voters to do often. We don’t want to push DFINITY to context switch on a whim, or to micro-manage them as stated before → that would kill innovation and their vision.
In this case, we’re asking voters in the community to push back on the internal prioritization of a highly controversial proposal, criticized by its original implementer, that barely passed the NNS, and has been dictated and driven by a single person from the very start.
We’re asking voters to publicly say that they want DFINITY to take proposals that the IC governing body has passed convincingly, and to prioritize that work in the DFINITY roadmap.
We’re asking voters to publicly push DFINITY to take the following into account when they prioritize proposals:
The chronological order in which they were passed
The approval percentage associated with the NNS vote
The backwards-compatibility of the change, and the friction/pushback that it would cause within the community.
- (1 week) Community reviews comments, asks questions, provides actionable feedback
- Community votes to accept or reject the proposal