I’d like to update you with the results of the onboarding application evaluations that took place on Wednesday April 6th, 2022.
Evaluation Results
The Lido Node Operator Subgovernance Group (LNOSG) decided to nominate 5 applicants for the proposed shortlist.
Shortlisted applicants have been asked to confirm their desire to join the Lido on Polygon operator set. In case they do not reply affirmatively timely, or for some other reason cannot join this round, they will not be onboarded and will need to re-apply in a future round.
Considerations regarding Polygon, Validator Slots, and Onboarding
In its onboarding application, Lido requested that applicants to respond whether they:
a) Had a Polygon validator slot and were willing to temporarily transfer it to Lido (a technical requirement until Lido on Polygon v2 comes out);
b) Did not have a Polygon validator and thus could only onboard if a slot were provided by Lido;
c) Had a Polygon validator slot but were not able/willing to temporarily transfer it to Lido, and thus could only onboard if an additional slot were provided by Lido or once Lido on Polygon v2 was out.
Since Lido did not have any slots available at the time of onboarding evaluation, applicants who answered b) or c) above basically could not be provided slots. As such, the LNOSG decided to defer the detailed ranking of these applicants until the next onboarding round, at which point Lido on Polygon v2 may be live or slots may be available. All applications were reviewed however, and various LNOSG members had general remarks regarding the difficulty of running a performant Polygon validator. It was also noted that prospective future applicants (especially those without experience validating on Polygon or even running Polygon nodes) would be advised to build this experience as soon as possible.
During the meeting on Apr 6 2022, the LNOSG decided to propose the following applicants for inclusion into our node operator set for the Polygon protocol (in alphabetical order):
The proposed shortlist includes some operators with smaller teams. The LNOSG discussed and ultimately felt that it was an opportune time (especially since there is no slashing currently on Polygon) to support smaller organizations who have shown commitment to the chain and the willingness to lend the validator slot.
You can find the full PDF with summary statistics and the recordings of the introduction and conclusion to the LNOSG evaluation meeting on our NOM public drive . Due to the privileged/confidential nature of some of the information provided in some of the applications, the portion of the call where applications were discussed in detail was not recorded.
Both shortlisted and non-shortlisted applicants have been emailed notifying them of the results. Where relevant, applicants who were not shortlisted also received comments regarding potential ways to improve their application in future rounds should they wish to reapply. If for some reason you applied but did not receive an email, please reach out to [email protected].
Governance voting
A snapshot will be proposed in the coming days and the link will be added here: Snapshot. The snapshot will be for the inclusion of the 5 (or fewer, in case applicants cannot continue) Polygon Operators. Should the DAO disagree with any of the proposed applicants, request additional information, or otherwise request additional input for the onboarding, the LNOSG will reconvene to propose a next course of action.
Next Steps
Following DAO approval, I will coordinate with the Lido on Polygon team to onboard the new node operators onto Lido on Polygon’s mainnet operator set. The estimated timeline for the new node operators to be fully on mainnet is sometime in April.