Identified DVT Clusters (IDVTC) is designed for DVT Clusters and creates a more capital-efficient path for independent stakers who are willing to identify themselves and operate validators collaboratively via DVT. This approach combines the trust properties of ICS with the operational resilience of DVT, aligning incentives for small independent operators who share validator rewards within a cluster.
To be included in the list, applicants must meet all the criteria and be approved by the CSM Committee.
Cluster composition and proof of independence
- One CSM operator can be a participant in only one IDVTC.
- A DVT cluster must consist of 4 independent participants.
- Each participant must have an approved ICS application (or must be an ICS operator).
- Keys must be generated via DKG with artifacts including:
- cluster-lock.json file for Obol clusters.
- proofs.json file for SSV clusters.
- The cluster formation requires signatures from each member, linking their ICS identity to the cluster.
- The cluster must provide a contact information Lido contributors can use in case of issues with the DKG verification.
- Operators must agree to enrol in monitoring via DVT provider specific tooling (e.g. Obol Grafana metrics, automatic SSV Network metrics).
Obligation to run DVT
- IDVTC operators must run validators using Obol or SSV.
- IDVTC operators must generate the keys via DKG ceremony and provide proof of the output.
- Switching DVT providers is allowed as long as it remains within the approved set and is reported/observable (will require exit-enter procedure).
Downgrade policy
If an IDVTC is detected and reported by the CSM committee as not using DVT (or otherwise failing type requirements):
- The operator’s type is downgraded.
- The operator fee and bond requirements are changed accordingly to a default CSM type, which will likely cause ejection of some of the keys due to them becoming unbonded. CSM Committee can also consider downgrading participants’ ICS type in case such violation is committed.
Replacing a cluster member
Identified DVTCs may replace participants over time (e.g. if someone stops operating), while keeping the cluster within the IDVTC operator type requirements.
If a participant is replaced:
- The new participant must be another ICS-approved participant.
- No participant may be a member of more than one IDVTC at the same time.
- The cluster must submit a new 4-signature cluster statement.
- Monitoring must remain in place for all nodes.
ICS <> IDVTC compatibility
One CSM operator can have only one Node Operator of the ICS type, as well as be a participant in only one IDVTC.