<p>Lido’s grant initiative - LEGO - has completed its first year! In this post we will summarize the main achievements of the first year and propose the continuation of the initiative for another year.</p>
<h3>
<a name="what-is-lego-1" href="#what-is-lego-1"></a>What is LEGO?</h3>
<p>LEGO - the Lido Ecosystem Grants Organisation - is a framework by the Lido DAO to fund initiatives which help benefit and grow the Lido ecosystem. It is designed as a straightforward process through which external contributors can seamlessly gather the funding and resources required to act on their concepts.</p>
<p>By rewarding talent early with developer incentives, bounties, and infrastructure support, LEGO acts as a catalyst for growth and helps to maintain Lido as a leading and most useful liquid staking protocol in the whole space.</p>
<p>You can learn more about LEGO and apply for funding by visiting <a href="http://lego.lido.fi/">lego.lido.fi <span>14</span></a>.</p>
<h3>
<a name="what-have-we-achieved-2" href="#what-have-we-achieved-2"></a>What have we achieved?</h3>
<p>The previous year for LEGO was dynamic and full of diverse proposals and changes in our team. The LEGO committee grew in number and the grants provision tempo increased to match this.</p>
<p>Below are some of the most prominent proposals which received support:</p>
<ul>
<li>
<a href="https://research.lido.fi/t/lido-for-solana-proposal-by-chorus-one/527/10">First mountain-sized proposal <span>5</span></a> to develop ‘Lido for Solana’.</li>
<li>A grant to David Mihal for the work on a <a href="https://research.lido.fi/t/lego-lido-steth-uniswap-v3-pool/509">incentivizable UNIv3 pool <span>3</span></a> for wstETH/ETH pair.</li>
<li>Sponsorship of the <a href="https://rss.com/podcasts/stakingrewards/">Staking Rewards <span>2</span></a> and <a href="https://newsletter.banklesshq.com/">Bankless</a> podcasts.</li>
<li>Promotional campaign launched with<a href="https://www.argent.xyz/"> Argent Wallet</a>.</li>
<li>A <a href="https://rabbithole.gg/">Rabbithole <span>1</span></a> quest to grow the active Ethereum staking community.</li>
<li>Sponsorship and participation of Devconnect event in Amsterdam.</li>
<li>Provided a grant for <a href="https://research.lido.fi/t/compensating-security-assessment-costs-for-lido-on-x-projects/1717/13">security assessment of Lido-on-X projects <span>2</span></a>
</li>
</ul>
<p>And this list continues with a huge number of other satisfied proposals which all collaborate on making the staking community grow. You may find more details in our quarterly LEGO reports in the corresponding pages on <a href="https://lego.lido.fi/lego-quarterly-reporting">lego.lido.fi <span>2</span></a> which we will continue to publish with each quarter passed.</p>
<h3>
<a name="next-steps-3" href="#next-steps-3"></a>Next steps</h3>
<p>To continue the growth of LEGO and to continue positive dynamics we propose:</p>
<ul>
<li>To continue the program for another year.</li>
<li>Introduce quarterly LEGO budget management via Easy Track motions (in case of any requests for over budgeted grants - proposals at research forum followed by Snapshot voting).</li>
<li>Continue publishing quarterly reports for better transparency and accountability</li>
<li>Snapshot voting to be held <strong>from 20th till 24th of June</strong> and, if successful, Easy Track motion to be created for LEGO’s multisig wallet top up for another quarter of operation.</li>
</ul>
<p>For more information on proposals shared with LEGO, visit <a href="http://research.lido.fi/">research.lido.fi <span>12</span></a>.</p>

LEGO: a proposal to continue the initiative for another year Lido’s grant initiative - LEGO - has

LEGO: a proposal to continue the initiative for another year

<h2>
<a name="motivation-1" href="#motivation-1"></a>Motivation</h2>
<p>Day-to-day DAO operations require significant flexibility &amp; safety at the same time. To some extent and use-cases gnosis multisig wallets provide for both and are used widely across different parts of Lido DAO operations. The proposal outlines general rules under which those multisig wallets will be used in operations. Lido DAO can also promote and encourage this policy adoption by other cooperating 3rd parties.</p>
<h2>
<a name="general-rules-2" href="#general-rules-2"></a>General rules</h2>
<p>Generally, every multisig under Lido DAO ops workstream should have (please see <strong>Special cases</strong> for exceptions or additional rules set):</p>
<ol>
<li>At least 3 signers.</li>
<li>At least 50%+ threshold.</li>
<li>For multisigs holding $1m+ — at least 7 signers.</li>
<li>For multisigs holding rights and roles — at least 3/5 setup.</li>
<li>Multisigs holding funds should set<a href="https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c"> Lido Agent contract <span>3</span></a> as <a href="https://app.safe.global/settings/spending-limits">beneficiary <span>1</span></a> with unlimited allowance on tokens the wallet is funded with.</li>
</ol>
<h2>
<a name="public-process-3" href="#public-process-3"></a>Public process</h2>
<p>Multisig use, while being highly flexible, requires transparency for DAO members &amp; general public.</p>
<ol>
<li>Every multisig should have a<a href="http://research.lido.fi"> research.lido.fi <span>2</span></a> forum post with stated purpose &amp; “operating rules” of the wallet, along with the 1) address; 2) list of signer addresses.</li>
<li>Address of the multisig must be listed in<a href="https://docs.lido.fi/deployed-contracts/#lido-dao-multisigs"> https://docs.lido.fi/deployed-contracts/#lido-dao-multisigs <span>4</span></a> section.</li>
<li>Signers “apply” by sharing the<a href="https://docs.lido.fi/guides/address-ownership-guide"> proof of the address ownership <span>4</span></a> in the forum post’s comments.</li>
<li>Any changes in signers list must be announced in the “multisig forum post” along with another proof of address. Unless it is explicitly specified that signers are fixed, the multisig signers can be rotated, but track record must be made publicly available.</li>
<li>
<a href="https://docs.lido.fi/deployed-contracts/#emergency-brakes-multisigs">Emergency brake multisigs <span>7</span></a> and<a href="https://docs.lido.fi/deployed-contracts/#emergency-brakes-multisigs"> LEGO multisig <span>7</span></a> signers list can be changed only after DAO snapshot.</li>
<li>No change in multisig signers should 1) lower the absolute number of signers below DAO-vetted one; 2) lower the signing threshold. If this is required, those changes must be passed through the <a href="https://snapshot.org/#/lido-snapshot.eth">Lido DAO Snapshot vote <span>2</span></a>.</li>
</ol>
<h2>
<a name="special-cases-4" href="#special-cases-4"></a>Special cases</h2>
<ol>
<li>Any LEGO wallet changes are to be approved by the DAO through Snapshot vote.</li>
<li>Any<a href="https://docs.lido.fi/deployed-contracts/#emergency-brakes-multisigs"> Emergency Multisigs <span>7</span></a> changes are to be approved by the DAO through the Snapshot vote (last Emergency Multisigs update could be found on<a href="https://research.lido.fi/t/emergency-brakes-multi-sig-upgrade/2608"> the forum <span>1</span></a>).</li>
<li>Unless it’s mentioned explicitly, multisigs managed by Lido-on-X (non-Ethereum Lido protocols) teams aren’t subject to this policy.</li>
<li>Lido DAO contributors can employ specific ad-hoc multisigs for operations. In case of not holding any rights and roles and not being funded by the DAO directly such “convenience wallets” need not conform to the above process. The main use-case for such wallets are “gas fund” for dev &amp; ops teams.</li>
</ol>

LEGO: a proposal to continue the initiative for another year

Lido DAO ops multisigs policy

Got something to add?