<h2>
<a name="authors-1" href="#authors-1"></a>Authors</h2>
<p><a href="/u/tracheopteryx">@tracheopteryx</a> <a href="/u/substreight">@Substreight</a> <a href="/u/franklin">@franklin</a> <a href="/u/vooncer">@vooncer</a> <a href="/u/anderson">@anderson</a></p>
<h2>
<a name="summary-2" href="#summary-2"></a>Summary</h2>
<p>Temporarily empower the Multisig members to make basic, limited operational decisions including budgetary expenditures, protocol grants, and hiring for six months, as we prepare a more robust governance architecture.</p>
<h2>
<a name="abstract-3" href="#abstract-3"></a>Abstract</h2>
<p>The proposed change would allow Multisig members to make personnel &amp; budgetary decisions for no more than six (6) months. Any budget is to be proposed to governance for approval. This change would allow operational decisions to be made at a rapid pace for the next six (6) months. During this six-month term, the Multisig will be responsible for facilitating the creation and transition to a multi-DAO structure. These powers, as well as members of the Multisig, can be removed or modified by governance at any time.</p>
<h2>
<a name="motivation-4" href="#motivation-4"></a>Motivation</h2>
<p>In this nascent stage of Yearn’s lifetime, it is crucial to make rapid decisions in order to establish a strong foundation. Structure and support needs to be quickly built around Andre’s development speed in order to ensure the success of the protocol. This proposal formalizes administrative roles that will serve as a foundation for the protocol’s transition to a multi-DAO structure in the near term.</p>
<h2>
<a name="specification-5" href="#specification-5"></a>Specification</h2>
<h3>
<a name="overview-6" href="#overview-6"></a>Overview</h3>
<p>This proposal grants the Multisig operational authority on the following decisions for six (6) months from implementation:</p>
<ul>
<li>
<p>Determining and distributing protocol grants.</p>
</li>
<li>
<p>Determining and distributing community grants.</p>
</li>
<li>
<p>Determining and distributing legal + DAO consultation grants.</p>
</li>
<li>
<p>Identifying and executing key hires listed on the attached budget.</p>
</li>
<li>
<p>Identifying and engaging security firms.</p>
</li>
<li>
<p>Identifying and engaging analytical firms.</p>
</li>
<li>
<p>Continue executing yVault strategy changes until a dedicated team can take over.</p>
</li>
<li>
<p>Facilitating UI &amp; front-end development.</p>
</li>
<li>
<p>Facilitating business development and integrations.</p>
</li>
</ul>
<p>This proposal does not grant the Multisig:</p>
<ul>
<li>
<p>Authority over YFI token or emissions.</p>
</li>
<li>
<p>Leadership powers beyond those described above.</p>
</li>
<li>
<p>Any powers over the YIP process or governance.</p>
</li>
<li>
<p>Authority over the composition of the Multisig group – any changes to Multisig signers will need to be approved by governance.</p>
</li>
<li>
<p>The power to ignore or hinder any approved YIPs or the governance process in general.</p>
</li>
<li>
<p>The power to create a legal entity.</p>
</li>
</ul>
<h3>
<a name="rationale-7" href="#rationale-7"></a>Rationale</h3>
<p>Forum Poll (202 votes)</p>
<ul>
<li>
<p>78% “Yes, empower the Multisig”</p>
</li>
<li>
<p>22% “No, find a better solution”</p>
</li>
</ul>
<p>Important objections raised in the forum poll argued against moving to a foundation model and overly centralizing powers. Here is how we’re learning and adjusting from this feedback:</p>
<ul>
<li>
<p>Clarification that this proposal is not for a foundation model and that the yearn governance DAO will retain its dominant authority including the ability to modify or remove the multisig’s members or powers via future on-chain votes.</p>
</li>
<li>
<p>A deeper discussion about decentralization, governance, and the urgency for this YIP to pass can be found in this thread: <a href="https://gov.yearn.finance/t/understanding-decentralization-prioritizing-an-operations-team/3396">Understanding Decentralization &amp; Prioritizing an Operations Team <span>22</span></a>.</p>
</li>
<li>
<p>Clearer limitations on the multisig’s authority detailed above to be controlled via smart contract.</p>
</li>
</ul>
<h3>
<a name="technical-specification-8" href="#technical-specification-8"></a>Technical Specification</h3>
<p><strong>For:</strong> Empower the Multisig for six (6) months.</p>
<p><strong>Against:</strong> No changes.</p>
<h3>
<a name="proposed-budget-9" href="#proposed-budget-9"></a>Proposed Budget</h3>
<p></p><div><a href="https://europe1.discourse-cdn.com/business20/uploads/yearn/original/1X/109173bf5576b6673639aab5b21ddfd5f095783a.png"><div>
<span>Budget</span><span>817×652 15.6 KB</span>
</div></a></div><p></p>
<h2>
<a name="discussions-10" href="#discussions-10"></a>Discussions</h2>
<aside>
  <div>
    <div><span></span></div>
    
    <a href="https://gov.yearn.finance/t/empower-the-multisig/2891">Empower the Multisig</a> <a href="/c/proposals/vaults/9"><span></span><span></span><span>Vaults</span></a>
  </div>
  <blockquote>
    Summary: 
Decision making is moving too slowly and unable to keep up with the pace of development. I propose that we turn the MultiSig into an operating council for a six-month period, giving the group authority on basic operational decisions such as budgetary expenditures, protocol grants, and hiring. 
Abstract: 
The proposed change would allow MultiSig members to make determinations on how to spend a budget, which will be approved by the community. This change would allow operational decisions…
  </blockquote>
</aside>

YIP 41: Temporarily Empower Multisig 
  Authors 
  @tracheopteryx   @Substreight   @franklin   @vooncer   @anderson  
 
  Summary 
 Temporarily empower the

YIP 41: Temporarily Empower Multisig

<h2>
<a name="summary-1" href="#summary-1"></a>Summary</h2>
<p>Replace the three least active multisig signers with new people. After an <a href="https://twitter.com/bantg/status/1533222650838908928">open call <span>39</span></a> and careful consideration, we’ve selected three candidates: 0xngmi, monoloco, and lefteris.</p>
<h2>
<a name="motivation-2" href="#motivation-2"></a>Motivation</h2>
<p>The multisig has been effectively operating as 6 of 6-7 with two signers being inactive and another one too busy with his own project. We appreciate their service, but we got to a threshold where we need another rotation. Here are the signing rates over the last two months, since 2022-04-13 till 2022-06-13.</p>
<pre><code>owner
klim       100.0
cp0x        99.0
banteg      98.0
daryl       91.0
mariano     88.0
leo         77.0
--- <span>cut</span> here ---
vsh         39.0
devops       6.0
ryan         2.0
</code></pre>
<h2>
<a name="specification-3" href="#specification-3"></a><strong>Specification</strong>
</h2>
<p>Replace vsh, devops, ryan with 0xngmi, monoloco, and lefteris.</p>
<h2>
<a name="signal-vote-4" href="#signal-vote-4"></a>Signal vote</h2>
<div><div><div>Replace 3 multisig singers?</div><ul><li> <span>Yes</span></li><li> <span>No</span></li></ul></div><div><div><div><span>27</span><span>voters</span></div></div><ul><li>
                
                <span>Results will be shown on <strong>vote</strong>.</span>
               </li></ul></div><div></div></div>

YIP 41: Temporarily Empower Multisig

YIP-68: Rotate multisig signers

Got something to add?