<p><a name="civilized"></a></p>
<h2>
<a name="this-is-a-civilized-place-for-public-discussioncivilized-1" href="#this-is-a-civilized-place-for-public-discussioncivilized-1"></a><a href="#civilized">This is a Civilized Place for Public Discussion</a>
</h2>
<p>Please treat this discussion forum with the same respect you would a public park. We, too, are a shared community resource — a place to share skills, knowledge and interests through ongoing conversation.</p>
<p>These are not hard and fast rules, merely guidelines to aid the human judgment of our community and keep this a clean and well-lighted place for civilized public discourse.</p>
<p><a name="improve"></a></p>
<h2>
<a name="improve-the-discussionimprove-2" href="#improve-the-discussionimprove-2"></a><a href="#improve">Improve the Discussion</a>
</h2>
<p>Help us make this a great place for discussion by always working to improve the discussion in some way, however small. If you are not sure your post adds to the conversation, think over what you want to say and try again later.</p>
<p>The topics discussed here matter to us, and we want you to act as if they matter to you, too. Be respectful of the topics and the people discussing them, even if you disagree with some of what is being said.</p>
<p>One way to improve the discussion is by discovering ones that are already happening. Spend time browsing the topics here before replying or starting your own, and you’ll have a better chance of meeting others who share your interests.</p>
<p><a name="agreeable"></a></p>
<h2>
<a name="be-agreeable-even-when-you-disagreeagreeable-3" href="#be-agreeable-even-when-you-disagreeagreeable-3"></a><a href="#agreeable">Be Agreeable, Even When You Disagree</a>
</h2>
<p>You may wish to respond to something by disagreeing with it. That’s fine. But remember to <em>criticize ideas, not people</em>. Please avoid:</p>
<ul>
<li>Name-calling</li>
<li>Ad hominem attacks</li>
<li>Responding to a post’s tone instead of its actual content</li>
<li>Knee-jerk contradiction</li>
</ul>
<p>Instead, provide reasoned counter-arguments that improve the conversation.</p>
<p><a name="participate"></a></p>
<h2>
<a name="your-participation-countsparticipate-4" href="#your-participation-countsparticipate-4"></a><a href="#participate">Your Participation Counts</a>
</h2>
<p>The conversations we have here set the tone for every new arrival. Help us influence the future of this community by choosing to engage in discussions that make this forum an interesting place to be — and avoiding those that do not.</p>
<p>Discourse provides tools that enable the community to collectively identify the best (and worst) contributions: bookmarks, likes, flags, replies, edits, and so forth. Use these tools to improve your own experience, and everyone else’s, too.</p>
<p>Let’s leave our community better than we found it.</p>
<p><a name="flag-problems"></a></p>
<h2>
<a name="if-you-see-a-problem-flag-itflag-problems-5" href="#if-you-see-a-problem-flag-itflag-problems-5"></a><a href="#flag-problems">If You See a Problem, Flag It</a>
</h2>
<p>Moderators have special authority; they are responsible for this forum. But so are you. With your help, moderators can be community facilitators, not just janitors or police.</p>
<p>When you see bad behavior, don’t reply. It encourages the bad behavior by acknowledging it, consumes your energy, and wastes everyone’s time. <em>Just flag it</em>. If enough flags accrue, action will be taken, either automatically or by moderator intervention.</p>
<p>In order to maintain our community, moderators reserve the right to remove any content and any user account for any reason at any time. Moderators do not preview new posts; the moderators and site operators take no responsibility for any content posted by the community.</p>
<p><a name="be-civil"></a></p>
<h2>
<a name="always-be-civilbe-civil-6" href="#always-be-civilbe-civil-6"></a><a href="#be-civil">Always Be Civil</a>
</h2>
<p>Nothing sabotages a healthy conversation like rudeness:</p>
<ul>
<li>Be civil. Don’t post anything that a reasonable person would consider offensive, abusive, or hate speech.</li>
<li>Keep it clean. Don’t post anything obscene or sexually explicit.</li>
<li>Respect each other. Don’t harass or grief anyone, impersonate people, or expose their private information.</li>
<li>Respect our forum. Don’t post spam or otherwise vandalize the forum.</li>
</ul>
<p>These are not concrete terms with precise definitions — avoid even the <em>appearance</em> of any of these things. If you’re unsure, ask yourself how you would feel if your post was featured on the front page of the New York Times.</p>
<p>This is a public forum, and search engines index these discussions. Keep the language, links, and images safe for family and friends.</p>
<p><a name="keep-tidy"></a></p>
<h2>
<a name="keep-it-tidykeep-tidy-7" href="#keep-it-tidykeep-tidy-7"></a><a href="#keep-tidy">Keep It Tidy</a>
</h2>
<p>Make the effort to put things in the right place, so that we can spend more time discussing and less cleaning up. So:</p>
<ul>
<li>Don’t start a topic in the wrong category.</li>
<li>Don’t cross-post the same thing in multiple topics.</li>
<li>Don’t post no-content replies.</li>
<li>Don’t divert a topic by changing it midstream.</li>
<li>Don’t sign your posts — every post has your profile information attached to it.</li>
</ul>
<p>Rather than posting “+1” or “Agreed”, use the Like button. Rather than taking an existing topic in a radically different direction, use Reply as a Linked Topic.</p>
<p><a name="stealing"></a></p>
<h2>
<a name="post-only-your-own-stuffstealing-8" href="#post-only-your-own-stuffstealing-8"></a><a href="#stealing">Post Only Your Own Stuff</a>
</h2>
<p>You may not post anything digital that belongs to someone else without permission. You may not post descriptions of, links to, or methods for stealing someone’s intellectual property (software, video, audio, images), or for breaking any other law.</p>
<p><a name="power"></a></p>

Community Guidelines    
 
   This is a Civilized Place for Public Discussion 
 
 Please treat this discussion forum

Community Guidelines

<p>The first quarter of LEGO has come to an end following 3 months of exciting ecosystem developments.</p>
<p>The following is a proposal to continue LEGO and to continue funding developments and initiatives which benefit Lido and the greater liquid staking ecosystem.</p>
<h3>
<a name="what-is-lego-1" href="#what-is-lego-1"></a>What is LEGO?</h3>
<p>LEGO - the Lido Ecosystem Grants Initiative - 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>The first 3 months of LEGO can be read about in more detail here: <a href="http://research.lido.fi/t/legos-first-three-months/786">LEGO's first three months</a>.</p>
<p>A number of exciting initiatives were funded, including:</p>
<ul>
<li>A Uniswap v3 LP helper</li>
<li>An Immunefi big bounty</li>
<li>Lido liquid staking for Solana in collaboration with Chorus One</li>
<li>A Lido content translation initiative and more.</li>
</ul>
<p>We were allocated 240,000 LDO and spent <a href="https://gnosis-safe.io/app/#/safes/0x12a43b049A7D330cB8aEAB5113032D18AE9a9030/balances">28,040 LDO <span>3</span></a>, which is about 11.68%. Whilst this is somewhat inefficient, a foundation has been laid for LEGO to expand upon and more decisively allocate our resources.</p>
<h3>
<a name="moving-forwards-2" href="#moving-forwards-2"></a>Moving Forwards</h3>
<p>By continuing with LEGO, we aim to expand upon our early successes and drive Lido developments further through unique collaborations and developer initiatives.</p>
<p>For the coming 3 months, we propose the following changes to how LEGO is structured to enhance intensity and efficiency of the program:</p>
<ul>
<li>Top up LEGO multisig to 240,000 LDO by sending 123,250 LDO from treasury.</li>
<li>Keep the current LEGO council as an entity that gets to decide on boulders and helps prepare mountain-sized grants.</li>
<li>Expand the number of people who manage personal allocations (10 thousand LDO) and can ack pebble-sized grants up to 20 individuals, with LEGO council being in charge of said expansion.</li>
</ul>
<p>We predict the following changes to grow the scope of LEGO initiatives and improve the speed at which initiatives are processed.</p>
<h3>
<a name="voting-3" href="#voting-3"></a>Voting</h3>
<p>The vote to continue LEGO will run on Lido Snapshot from August 10th to August 12th, with Snapshot link to be added here: <a href="https://snapshot.org/#/lido-snapshot.eth/proposal/QmbXWbFhYRxU4gPEJ8pjZNd1CzpQp3B21yXjpKVwWjYvru">Snapshot <span>13</span></a>.</p>

LEGO: A proposal to continue LEGO for the forthcoming quarter The first quarter of LEGO

LEGO: A proposal to continue LEGO for the forthcoming quarter

<p>This is a draft of the program for funding Lido ecosystem development with grants from the Lido Treasury. The program has different frameworks for different kinds of contributions.</p>
<p>The goal of the Lido Ecosystem Grants Organisation is to allow fast and unimpeded resolutions on small-sized grants while maintaining efficiency and accountability for big developments. The program starts small but will grow over time.</p>
<h2>
<a name="purpose-of-lego" href="#purpose-of-lego"></a>Purpose of LEGO</h2>
<p>The mission of the Lido Ecosystem Grants Organization (LEGO) is to provide valuable resources to contributors who help to improve Lido. 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>
<h2>
<a name="improvement-classifications" href="#improvement-classifications"></a>Improvement classifications</h2>
<p>Grants administration is a subjective process that cannot be easily automated, and thus I propose an Organization that balances nimbleness with accountability.</p>
<p>Improvements should be sorted into four different piles by expected size and impact:</p>
<h3>
<a name="a-sand-grain" href="#a-sand-grain"></a>a. Sand grain</h3>
<p>This category combines all contributions that are nice to have, yet not detrimental, whilst also not being too costly and whose quality can be easily evaluated by a single person.</p>
<p>An improvement is a sand grain if:</p>
<ul>
<li>it is something nice to have for Lido</li>
<li>it’s no big deal if it doesn’t get delivered at all</li>
<li>grant won’t cost Lido more than 150 RAI (~$500 atm)</li>
<li>it can be specced and evaluated by a single person in the course of two days in total</li>
</ul>
<p>An example of a sand grain is a Dune Analytics dashboard that compares day-over-day deposits of various liquid staking protocols.</p>
<h3>
<a name="b-pebble" href="#b-pebble"></a>b. Pebble</h3>
<p>Pebbles are non-critical, small things that are beneficial for Lido but not so trivial to call a sand grain.</p>
<p>An improvement is a pebble if:</p>
<ul>
<li>it doesn’t fit into a sand grain</li>
<li>it’s not a big deal if it gets delayed or abandoned to a different contributor</li>
<li>it won’t cost Lido more than 1500 RAI (~$5000 atm)</li>
<li>it’s a few days total across a few persons to spec and evaluate at most</li>
</ul>
<p>An example of a pebble is a StakingRewards-like smart contract that would allow incentivizing stETH deposits into Maker.</p>
<h3>
<a name="c-boulder" href="#c-boulder"></a>c. Boulder</h3>
<p>Boulders are big, important things that are imperative to be carried out by experts and thoroughly evaluated by core contributors.</p>
<p>An improvement is a boulder if:</p>
<ul>
<li>it doesn’t fit into a pebble</li>
<li>it should be delivered on time and with good quality</li>
<li>it should be supported by Lido over a long period of time</li>
<li>it won’t cost Lido more than 10000 RAI (~$35000 atm), excluding audits</li>
<li>spec and evaluation alone are significant undertakings</li>
<li>it requires an external audit</li>
</ul>
<p>An example of a boulder is an implementation of withdrawal protocol for stETH.</p>
<h3>
<a name="d-mountain" href="#d-mountain"></a>d. Mountain</h3>
<p>Mountains are critical improvements to Lido that have a significant impact on its growth, security, operations, etc.</p>
<p>An improvement is a mountain if:</p>
<ul>
<li>it doesn’t fit into a lake</li>
<li>it offers a significant change in growth, security or operations of Lido</li>
</ul>
<p>An example of a mountain is the liquid staking protocol for Polkadot.</p>
<h2>
<a name="lego-committee" href="#lego-committee"></a>LEGO committee</h2>
<p>My proposal is to delegate six people to act as LEGO committee members (reffered below as LEGO persons). They will have a significant autonomy over grants up to a boulder size, as long as they stay within allotted budget, but will have to clear mountains and overdrafts with the main governance body.</p>
<h3>
<a name="three-month-budget" href="#three-month-budget"></a>Three-month budget:</h3>
<p>The LEGO will have a max quarterly aggregate budget of up to 240000 LDO, divided into individual budgets of 15000 LDO for each LEGO committee member, and 150000 LDO of shared budget for the full LEGO committee voting as a body. Budget and caps to be reassessed after the end of a quarter.</p>
<p>While the goals and priorities of the grant program will be thoroughly discussed and reviewed by the community through public discourse, the decision to start LEGO by operating as a small committee is to ensure that the application and decision process will be efficient and predictable, so applicants have clear objectives and timely decisions.</p>
<p>All LEGO persons are equal in power and workload, but have different specialties (e.g. there’s a BI-focused LEGO person, incentive programs-focused LEGO person, etc).</p>
<p>At the end of three months committee makes a report on the grants program and a retrospective on how to improve it.</p>
<h2>
<a name="methodology" href="#methodology"></a>Methodology</h2>
<ul>
<li>
<strong>Sand grains</strong> can be handled by a single LEGO committee member out of their personal budget as they see fit.</li>
<li>
<strong>Pebbles</strong> require a second LEGO committee member to agree to the grant approval and participate in the evaluation of the results.</li>
<li>
<strong>Boulders</strong> require majority approval of the LEGO committee.</li>
<li>
<strong>Mountains</strong> should be applied for using a regular governance process.</li>
</ul>
<p>If a LEGO committee member exhausts his or her individual quarterly budget, they can still propose to the full committee that sand grains and pebbles receive grants out of the shared portion of the budget, but will need to obtain approval of a majority of the LEGO committee members. If the committee runs out of a shared budget, they can request an extension from the governance.</p>
<h3>
<a name="committee-compensation" href="#committee-compensation"></a>Committee Compensation</h3>
<p>We propose every LEGO committee member be compensated <strong>35 LDO/hr capped at 20 hours/week</strong> unless they agree to operate pro bono. This compensation, along with the budget, will be allocated to the LEGO multisig from the Lido treasury. In keeping with the committee’s commitment to the community, compensated hours and duties will be logged publicly and transparently.</p>
<h3>
<a name="priorities" href="#priorities"></a>Priorities</h3>
<p>Initially, the program aims to start narrow in scope, funding peripheral ecosystem initiatives, such as targeted bounties, hackathon sponsorships, and other low-stakes means of building out the Lido dev ecosystem. Over time, if the program proves effective, the grant allocations can grow in scope to include, for example, core protocol development.</p>
<h3>
<a name="applications-and-ongoing-grants" href="#applications-and-ongoing-grants"></a>Applications and ongoing grants</h3>
<p>LEGO maintains a list of bounties (things that are nice to have for Lido, along with an estimated class), and a list of ongoing grants in <a href="https://docs.google.com/spreadsheets/d/1WWYpKbOBR20rZZEuycWYegxAIswSG7LkcvOKpdoPDbw/edit#gid=172089462">this spreadsheet <span>61</span></a>.</p>
<p>If you have an idea that would like to be funded that is not on the bounties list, contact a LEGO committee member who is on point for your idea. They will talk to you about your contribution and help you to fill out the application, which will consist of answers to the following questions:</p>
<ul>
<li>Title: What is the grant application about?</li>
<li>Author(s): Who will be working on the proposal?</li>
<li>Purpose: How will it aid the Lido ecosystem? Why is it important?</li>
<li>Perceived classification: What do you think the classification should be?</li>
<li>Summary: A brief summary of the grant application</li>
<li>Details: Detailed description of the grant application, timelines, expenses estimates, grant payment schedule.</li>
</ul>
<p>If it’s a sand grain or pebble, it’s likely you will get a grant quickly and efficiently.</p>
<p>For boulders and beyond you’ll have to work with the committee and/or larger Lido governance, which takes time and effort. LEGO will try to make sure it chooses the best teams for grants of this size.</p>
<h3>
<a name="life-after-application" href="#life-after-application"></a>Life after application</h3>
<p>After a grant application is submitted, LEGO committee members will evaluate and discuss the application and ultimately be responsible for determining whether the application should be supported. For sand grains and pebbles that process is very simple and frictionless, involving one or two members at most, while bigger grants will require some back and forth.</p>
<p>The LEGO committee members will determine the details of the application, those being:</p>
<ul>
<li>Classification</li>
<li>Funding/costs</li>
</ul>
<h4>
<a name="funding" href="#funding"></a>Funding:</h4>
<p>LEGO committee members will determine the fair evaluation for the costs of funding for a grant application. The funding costs will be correlated to the classification of the grant application, larger-sized applications will be funded more than smaller-sized applications.</p>
<h2>
<a name="conclusion" href="#conclusion"></a>Conclusion</h2>
<p>If this proposal is successfully approved, LEGO will start accepting applications beginning on the date it gets voted in.</p>
<p>This program is meant to be the most nimble MVP of a LEGO initiative. While the multi-sig committee comes with trust assumptions about the members, our hope is the community will approve this limited engagement to get the ball rolling in an efficient structure.</p>
<p>A signal vote for the LEGO is now live on Snapshot!</p>
<h2>
<a name="honorary-mentions" href="#honorary-mentions"></a>Honorary mentions</h2>
<p>Uniswap grants program for inspiration and structure.<br />
Netlify code review process for inspiration on issue importance classification.</p>

Project: Lido Ecosystem Grants Organization This is a draft of the program for funding Lido

Project: Lido Ecosystem Grants Organization

<h1>LIPs</h1>
<p>Lido Improvement Proposals (LIPs) describe standards for the Lido platform, including core protocol specifications, client APIs, and contract standards.</p>
<h2>Contributing</h2>
<ol>
<li>Review <a href="https://github.com/lidofinance/lido-improvement-proposals/blob/develop/LIPS/lip-0.md">LIP-0 <span>53</span></a>.</li>
<li>Fork the repository by clicking “Fork” in the top right.</li>
<li>Add your LIP to your fork of the repository. There is a <a href="https://github.com/lidofinance/lido-improvement-proposals/blob/develop/lip-X.md">template LIP here <span>12</span></a>.</li>
<li>Submit a Pull Request to lido’s <a href="https://github.com/lidofinance/lido-improvement-proposals">LIPs repository <span>21</span></a>.</li>
</ol>
<p>Your first PR should be a first draft of the final LIP. It must meet the formatting criteria enforced by the build (largely, correct metadata in the header). An editor will manually review the first PR for a new LIP and assign it a number before merging it. Make sure you include a <code>discussions-to</code> header with the URL to a new thread on <a href="https://forum.lido.com/">forum.lido.com <span>7</span></a> where people can discuss the LIP as a whole.</p>
<p>If your LIP requires images, the image files should be included in a subdirectory of the <code>assets</code> folder for that LIP as follow: <code>assets/Lip-X</code> (for Lip <strong>X</strong> ). When linking to an image in the LIP, use relative links such as <code>../assets/Lip-X/image.png</code> .</p>
<p>When you believe your LIP is mature and ready to progress past the WIP phase, you should ask to have your issue added to the next governance call where it can be discussed for inclusion in a future platform upgrade. If the community agrees to include it, the LIP editors will update the state of your LIP to ‘Approved’.</p>
<h2>LIP Statuses</h2>
<ul>
<li>
<strong>WIP</strong> - a LIP that is still being developed.</li>
<li>
<strong>Proposed</strong> - a LIP that is ready to be reviewed in a governance call.</li>
<li>
<strong>Approved</strong> - a LIP that has been accepted for implementation by the Lido community.</li>
<li>
<strong>Implemented</strong> - a LIP that has been released to mainnet.</li>
<li>
<strong>Rejected</strong> - a LIP that has been rejected.</li>
<li>
<strong>Withdrawn</strong> - a LIP that has been withdrawn by the author(s).</li>
<li>
<strong>Deferred</strong> - a LIP that is pending another LIP/some other change that should be bundled with it together.</li>
<li>
<strong>Moribund</strong> - a LIP that was implemented but is now obsolete and requires no explicit replacement.</li>
</ul>
<h2>Validation</h2>
<p>LIPs must pass some validation tests. The LIP repository ensures this by running tests using <a href="https://rubygems.org/gems/html-proofer">html-proofer <span>1</span></a> and <a href="https://rubygems.org/gems/lip_validator">lip_validator <span>2</span></a>.</p>
<p>It is possible to run the LIP validator locally:</p>
<pre><code>gem install lip_validator
lip_validator <span>&lt;<span>INPUT_FILES</span>&gt;</span>
</code></pre>
<h2>Copyright</h2>
<p>Copyright and related rights waived via <a href="https://creativecommons.org/publicdomain/zero/1.0/">CC0</a>.</p>

Lido Improvement Proposal Process LIPs 
 Lido Improvement Proposals (LIPs) describe standards for the Lido platform

Lido Improvement Proposal Process

<h2>
<a name="summary-1" href="#summary-1"></a>Summary</h2>
<p>A proposal to engage a <em>Master of Validators</em> (the “Service Provider”) for Lido, including proposed duties, compensation, and incentive awards.</p>
<h2>
<a name="motivation-2" href="#motivation-2"></a>Motivation</h2>
<p>As Lido rapidly grows (increasing TVL, expanding validator set, introduction of staking solutions for new networks), there are increasing challenges in coordinating Lido community participants, aligning operational strategies across networks, and ensuring that node operators are performing according to expectations. Thus, a <em>Master of Validators</em> role is needed for Lido.</p>
<h2>
<a name="objectives-responsibilities-3" href="#objectives-responsibilities-3"></a>Objectives &amp; Responsibilities</h2>
<p>The objectives of the <em>Master of Validators</em> would be to help Lido grow the node operator community, work closely with organizations looking to or already running nodes for Lido on different networks, establish governance and incident response processes, and help the DAO implement a strategy to work towards its goals of decentralization and trustlessness.</p>
<p>Responsibilities would include helping Lido:</p>
<ul>
<li>manage Lido’s node operator community across networks. Track uptime and other node operator performance metrics and communicate with node operators to inform them about upgrades, their performance, and to troubleshoot issues. Collect feedback and help to create and document best practices with the goal to improve the reliability and security of Lido’s node operators;</li>
<li>create an efficient and transparent process for onboarding new node operators and distributing deposited assets among them;</li>
<li>develop and execute a strategy of decentralization for the node operators set, together with the Lido Node Operator Subgovernance Group. Organize, document, and do external communications for this group that is tasked with evaluating new operators and representing node operators in the overall DAO power structure; ,</li>
<li>onboard new networks to Lido. Find and encourage suitable candidates to expand Lido to other networks with a staking mechanism by supporting them in the process including e.g. creating a proposal to Lido, finding the initial validator set, figuring out and connecting them with potential integration partners, etc.</li>
</ul>
<h2>
<a name="compensation-4" href="#compensation-4"></a>Compensation</h2>
<p>The proposed recurring compensation for the to be provided by <em>Master of Validators</em> has two components:</p>
<ol>
<li>Cash compensation of $10,000.00 per month, payable in DAI from Lido, to be paid at the end of every calendar month.</li>
<li>Token-based compensation of 120,000 LDO from Lido, effective as of the ratification date of a corresponding candidate proposal, and structured to vest over three years as follows:</li>
</ol>
<ul>
<li>40,000 LDO, vesting on the 12-month anniversary of continuous service to Lido;</li>
<li>and ~3,333.33 LDO, vesting upon completion of each subsequent month of continuous service to Lido.</li>
</ul>
<p>The service-based vesting outlined above represents a contingency for each of the described periods; thus, if the individual quits or is terminated before completing the first 12 months of service, they would have earned no LDO. If they quit or are terminated during month 13, they would have earned 1/3rd of the total possible LDO (40,000) but would not have earned the rest of their potential LDO compensation (80,000). There are no further lockups on fully vested LDO (i.e., once they vest in some # of LDO, they can sell that # of LDO at any time).</p>
<h3>
<a name="one-time-sign-on-costs-5" href="#one-time-sign-on-costs-5"></a>One-time sign-on costs</h3>
<p>A one-time welcome payment of 10,000 DAI, to be disbursed within one month of ratification of this proposal, with the purpose of compensating the candidate for:</p>
<ul>
<li>legal and administrative expenses related to the provision of the required services (approx. 70% of the payment),</li>
<li>cost of hardware associated with the provision of the required services (laptop computer, mobile telephone) (approx. 30% of the payment).</li>
</ul>
<h3>
<a name="compensation-of-expenses-related-to-provision-of-service-6" href="#compensation-of-expenses-related-to-provision-of-service-6"></a>Compensation of expenses related to provision of service</h3>
<ul>
<li>Travel &amp; Expenses: Lido will either pay for or retroactively compensate the Service Provider for expenses related to travel for participation in industry events and team or DAO off-sites, within reason and subject to approval by the DAO or any duly ratified delegate.</li>
<li>Tooling/Software: Lido will either pay for or retroactively compensate the Service Provider for access or subscriptions to tooling/software relevant to the provision of the required services, within reason and subject to approval by the DAO or any duly ratified delegate.</li>
<li>Miscellaneous expenses (e.g. gas costs): Lido will retroactively compensate the Service Provider for other miscellaenous costs incurred in the provision of the required services, within reason and subject to approval by the DAO or any duly ratified delegate.</li>
</ul>
<h2>
<a name="oversight-nature-of-service-7" href="#oversight-nature-of-service-7"></a>Oversight; Nature of Service</h2>
<p>The Service Provider will provide periodic updates to the DAO through posts in the forum. The Service Provider is an independent contractor with respect to the DAO in all respects, including with respect to the provision of the services provided as <em>Master of Validators</em> and such services may be terminated by either the Service Provider or the DAO at any time, and without payment of penalty, upon thirty (30) days written notice.</p>

Define Core Contributor Role for Lido: Master of Validators 
  Summary 
 A proposal to engage a

Define Core Contributor Role for Lido: Master of Validators

The Road to Trustless Ethereum Staking [Discussion] On December 1st, 2020, Ethereum began its transition

The Road to Trustless Ethereum Staking [Discussion]

<p>Lido is a staking solution that provides a tokenized version of your staked token while you are staking. This staking token (e.g. stETH) is compatible with DeFi and allows you to simultaneously stake tokens while also participating in on-chain lending or trading.</p>
<p>Lido maintains a set of node operators who are responsible for running the validators that support tokens staked with Lido. The addition and removal of node operators will be voted on by Lido community governance.</p>
<p>In the case of Ethereum, when you stake with Lido your ETH is staked with an operator within this set. This is chosen through a round-robin allocation based on the remaining availability within each validator’s slot. However, given the nature of stETH, it ends up not mattering since rewards and slashings are socialized across all stETH holders.</p>
<p>Lido’s node operators are voted on by the DAO to ensure that the values of node operators are aligned with the values of the Lido DAO. The reputation and past performance history as the best-in-industry of those interested in being operators is important because they are responsible for validating the tokens staked via Lido.</p>
<p>To apply to be a Lido Node Operator, please follow the process outlined below:</p>
<ul>
<li>Visit the <a href="https://enchanted-direction-844.notion.site/Lido-Node-Operators-19ca4a3e7553421486cd3e8be314bb03">Node Operator Landing Page <span>1.7k</span></a>
</li>
<li>Submit an application via the Google Forms link for the protocol that you are interested in being a node operator for.</li>
</ul>
<p>Following successful submission of the above information, the Lido Node Operator Sub-governance Group (LNOSG) will review and evaluate your application and submit a list of recommended applicants to the Lido DAO for approval.</p>
<p><strong>Please note</strong>: The Lido DAO is ultimately responsible for all additions and modifications to the Lido Node Operator set; the LNOSG only serves to make proposals.</p>