NOTICE: AMENDMENT TO THIS PROPOSAL
After Discussion with several community members, it was decided that we should place a set date of expiration for Conviction Voting if this proposals were to pass. Such a date would allow for transparency for the community at exactly when this transition would occur, and potential proposals could plan accordingly. The date agreed upon for this proposal is April 20th.
This means: All proposals will need to pass through CV by April 20th or they will risk getting stuck without passing.
Proposal to Sideline Conviction Voting in the TEC
This proposal has been developed in parallel with a larger set of proposals that are all part of a synchronized strategy to focus our mission and to create a path toward a more sustainable economic future. Please refer to the “Proposals Roadmap” forum post which serves as a contextual outline for this broader strategy.
The TEC has performed a wide range of experiments within governance, funding, culture, and engineering. Each experiment often comes with a review period to analyze whether or not a tool, process, or method is effective within the context of the Commons and its current goals and initiatives. The evolution of purpose within a Commons is an observation that Elinor Ostrom referenced through her investigations on the use of Adaptive Governance, referring to the ability of individuals and organizations to modify the scope and structure of the institutions that shape their decisions and behavior.
As we continue to utilize her work to guide us in the Stewardship of the TEC, this proposal will be reviewing the use of Conviction Voting and providing an argument for restricting its use as we continue to develop our governance system and provide a more sustainable path for our economic future.
Understanding the Problems
The governance process within the TEC has been managed through three different voting mechanisms: off-chain Snapshot Voting for cultural/ideation decisions, Tao voting for smart-contract parameter changes, and Conviction Voting for the management of our common pool.
For those of you that need a refresher on how Conviction Voting works, there are good resources here, here, and here. The idea for Conviction Voting is to provide a method for a continuous aggregation of community preferences among a large set of proposals that could better guide funding decisions.
While the parameters of Conviction Voting have remained the same, the reality of the funding environment has changed dramatically since the TEC’s launch and we have learned a great deal about the dynamics of putting Conviction Voting to work. However, as a community, we have done nothing to adjust to these realities.
Additionally, there are both contextual and procedural concerns associated with the use of Conviction Voting that limits our much needed control over the common pool at this early stage of our development.
The justification for sidelining our CV module is centered around two broad observations:
1.) Inflows & Market Conditions
The Conviction Voting Module was designed in part, as a method to accelerate the flow of funds from the organization and solve the problem of well-funded DAOs sitting on their treasury. For the TEC, this design has not come to fruition largely due to our lack of inflows into the common pool via income streams and/or $TEC token utility. T
The current bear market conditions are exacerbating this problem and placing the common pool at risk of depleting itself very quickly. The Conviction Voting module is permissionless and allows for proposals to remain in the gardens for as long as necessary until they are passed. This feature of Conviction voting is by design and under the right conditions provides a sustainable method for distributing common pool funds.
However, under current market conditions, and our lack of consistent inflows into the common pool, the use of Conviction Voting has forced the need to have more strict control over access to these funds while we continue to develop utility for the $TEC token and work to replenish the common pool. This need is essential for the longevity of the TEC and its mission.
2.) Conviction Voting Processes
The reality of our current funding environment has also exposed some technical and procedural concerns associated with Conviction Voting that have allowed proposals to be passed very easily without any form of mitigating options.
In an ideal environment, we would see many proposals entering the gardens at one time, and token-holders would have the option of placing their conviction behind the proposal of their choice. The time it takes for a proposal to pass depends on several parameters including the amount of tokens staked behind the proposal, the Effective Supply (the cumulative amount of $TEC tokens actively voting on proposals), and the amount of funds being requested.
The Effective Supply parameter in particular creates significant challenges when there is a lack of proposals available to vote on, as it dictates the rate at which conviction grows. The more tokens voting, the longer it takes for a proposal to pass. The inverse is also true, as we have seen, allowing for single proposals with minimal support to be passed very quickly when the effective supply is low.
In addition to this issue we hold concerns regarding the validity of proposals that remain open indefinitely with no support, a lack of enthusiasm around voting behaviors, and the attention required among token-holders to utilize our Conviction Voting module effectively.
For those of you who want to take a look at how CV works when you alter these parameters, we encourage you to play around with the configuration dashboard.
While we fully support and intend to reintroduce the use of Conviction Voting in the future, we are proposing to make our CV module ineffective at allocating funds from the common pool in the short-term until we start to see a steady inflow of funds replenishing the common pool. We will do this by reducing the Spending Limit parameter to 0, which removes the possibility for common pool fund distribution through CV.
What does this mean for funding proposals?
The new Token Engineering Grants Program will allow the TEC to fund smaller-scale public goods. This new grant-making program builds on Gitcoin’s Allo protocol, enabling the TEC to run its own quadratic funding rounds and use our limited common pool funds as a matching fund stimulus for catalyzing donations from a much broader community.
We will then use Tao Voting as the main method for making larger funding requests from the common pool. Tao Voting will make it a bit more challenging to pass proposals and will skew toward fewer and bigger proposals that will require some community organizing and stakeholder engagement in order to pass. Examples of these types of funding include operating budgets for the Token Engineering Academy and the TEC itself.
Unlike Conviction Voting, the Tao Voting module provides a time-boxed, “Yes/No” voting template with the following parameters:
Support Required: 85%
Minimum Quorum: 10%
Vote Duration: 5 Days
Delegated Voting Period: 3 Days
Quiet Ending Period: 3 Days
Quiet Ending Extension: 2 Days
Execution Delay: 0.5 Days
While Tao Voting has always been able to allocate funds from the common pool, its normalized use-case was to modify our smart-contracts, and thus its parameters weren’t necessarily chosen to optimize for funding requests. Due to its change in primary use-case, we will need to evaluate how these parameters work with a set of initial proposals.
We intend to use this proposal along with the other proposals within the “Proposals Roadmap” thread to determine whether or not we maintain these parameters, change them, or create a separate instance of Tao Voting for the purpose of funding requests.
Execution of this Proposal
Once we have gone through the advice process (this forum post will remain up for discussion for a period of 5 days), we will set-up a series of on-chain proposals.
As the first step, we will use the Token Engineering Grants Program funding proposal as a test of our Tao Voting module. This will allow us to make sure all participants on the coordination team are capable of submitting a Tao proposal, and serve as the first test to see how the Tao Voting module works for allocating funds from the common pool using our existing parameters.
The second step, and the one being approved by this proposal, will be to change the Spending Limit Parameter in the Conviction Voting module to 0. This move will effectively shut off Conviction Voting for allocating funds from the common pool and prevent any additional submissions of CV proposals as we make the shift to Tao Voting.
The next step will be to run three more Tao Voting tests, using the other proposals outlined in the “Proposals Roadmap”. Once all of these have been successfully executed, the coordination team will assess the experience and come back to the community with recommendations for tuning Tao Voting parameters based on what we have learned using it to govern funding decisions for the TEC. The Coordination Team will then also use the tests to provide the community with a process for submitting funding requests through Tao Voting.
Thank you for your time and attention!