API doc: bit.ly/ratedAPIdoc
Rated is building reputation for machines. We offer a solution to the poor contextualization of validator quality and infrastructure set visibility problems. This solution is centered around reputation scores for machines and their operators, and a set of enterprise grade data pipelines maintained by a neutral third party, starting with the Ethereum Beacon Chain.
Lido wants to extend its protocol to accommodate solo stakers. in order to make it happen Lido would like to create on-chain proxy mechanisms to possibly identify “solo stakers” and any metrics that represents their level of validation performance; Lido would use these mechanisms to identify likely candidates for the first onboarding round of solo-stakers, prior to more permissionless entry.
Some more detail on the set of requirements below:
Produce a set of criteria that will make up the “solo staker filter”
Produce a list of indices that fulfill said criteria; the list should contain not only addresses, but also additional information about them, such as:
a. Some indication of confidence level for which indexes are more or less likely to be a solo staker
b. Identifier if a staker is using Rocketpool / Dappnode / Avado
c. Performance metrics CL & EL metrics
Co-design approaches to reach out to solo stakers together with Lido contributors.
Window for delivery: between wk1 and wk2 of March 2023 for (1) and (2) and by end-April 2023 for (3) above.
Scope of work and deliverables
We propose the following cadence and deliverables:
- Rated to produce a methodology for the “solo staker filter”. This will incorporate, but won’t be limited to the following considerations;
- Defining who Rated has high confidence of being a professional node operator (based on our extensive existing library, and incremental clustering work we will do to fit more validator pubkeys into these material profiles) and excluding them from the list
- Using all available Beacon Chain data (e.g. graffiti) and the Rated library of mappings to attribute the highest degree of association of that staker with an appropriate communication channel.
- Using EL data to associate validator associated identifiers (e.g. deposit address) with off-chain comms hubs (e.g. POAP collections etc)
- Bonus: Filtering through our Networking Layer monitor (currently in development–we have relatively high confidence in singling out solo operators from that dataset)
- Lido to review and give feedback
- Rated to iterate and deploy methodology to the RatedDB.
- Rated to produce a solo-staker index dataset in csv form; this should include
- some indication of confidence level for which indexes are more or less likely to be a solo staker
- identifier if a staker is using Rocketpool / Dappnode / Avado
- performance metrics CL & EL metrics
Delivery: 6 weeks from approval
- Joint blog where we talk about the design of the methodology, implementation thereof and interesting findings (expected and unexpected).
- Co-design approaches to reach out to solo stakers together with Lido contributors.
Delivery: 4 weeks after delivery of Phase 1
We briefly deliberated on whether a Phase 3 makes sense, that involves Rated running the proposed methodology on an ongoing basis and maintaining related API endpoints. While interesting, given the additional overhead we are deferring this for discussion after completion of Phases 1 & 2.
The bid proposal
We are proposing a fee of $60,000 in nominal value for Phases 1 & 2. We are deferring Phase 3.
We propose a 1:2 split in the fulfillment of the nominal value of the fee, in terms of LDO:DAI.
- 1/3 of the total grant size in LDO tokens to be fulfilled upon acceptance of the proposal from LEGO.
- The LDO/USD exchange rate should be computed as the 14-day moving average of LDO/USD closings, dating backwards from the date of approval, referenced from Coingecko.
- 2/3 of the total grant size in DAI is fulfilled upon completion of the final deliverable.
We’re all very excited to embark with Lido on yet another adventure and help the DAO get that much closer to achieving its goal of hardening its operator set and the ruleset that governs it!!