As you’ve expressed interest in utilizing DVT in the Curated Set with Obol or SSV via key splitting on mainnet via Lido, the following process is expected to be followed.

Scope & Validator Eligibility

• Curated Set Node Operators may opt in to intra-operator DVT (single entity running the cluster) using Obol and/or SSV.
• You may key-split up to the lesser of 1,000 validators or 20% of your currently active Lido validators via a key-splitting ceremony. (Additional DVT-based validators may be added to the depositable queue if created via a DKG flow.)
• Follow the DVT provider key migration procedures (SSV & Obol docs linked at the bottom).

Pre-Testnet Prep

Before starting on Hoodi, prepare and share with NOM:

1. Validator Identification – Which validator keys (indexes) you intend to key-split on testnet. For testnet, the preference is for you to use the oldest submitted indexes.
2. Procedure Description – Step-by-step process you will use on Hoodi and on mainnet (ceremony environment, threshold settings, key distribution, key storage, rollback steps, etc). The same process should be followed on mainnet and testnet, and should be based on the Obol / SSV guides + suggested best practices (linked at the bottom).

Submit the above in your Lido <> Node Operator channel and wait for explicit NOM approval to begin Hoodi testing.

Hoodi Test Requirements

You must:

1. Operate ≥1,000 validators on Lido-Hoodi testnet instance.
2. Key-split at least 100 validators (or 50/50 if using both) on Hoodi using your chosen DVT provider(s); keep them running via DVT on Hoodi for as long as you plan to run DVT on mainnet.
3. Notify NOM twice: (a) when migrating validators are taken offline to initiate the DVT transition & (b) when they re-activate using DVT.
4. Monitoring period: Allow for at least 24 hours of monitoring on Hoodi post-transition. If you have not previously participated in Simple DVT testnets, at least one successful block proposal from your Hoodi DVT validators should also be observed.
5. Test validator exits: After confirming with NOM that the monitoring period was sufficient, trigger validator exits for the first 5 key indexes utilized during the testing procedure.