Enhanced Security in DVT API Flow

Old Flow:

Previously, the DVT API allowed clients to send both the unsigned transaction data and the deposit data in the same method. While this was efficient and fast, it posed potential security risks. Incorrect data could be registered on SSV, leading to penalties for validators when depositing the stake amount.

New Method:

To address these security concerns, the DVT API flow has been redesigned to ensure maximum security and robustness for our clients.

Clients will now follow a two-step process:

1. Validator Registration: Clients send a validator request and receive transaction data to complete the registration on the SSV network using the Check Status Request method.
2. Deposit Execution: After registration, clients send another request using the newly added Get Request Deposit Data method to retrieve the deposit data and execute the deposit transaction.
   This redesigned process includes a verification step to ensure the validator is correctly registered, thus protecting client funds from potential risks.

Introduction of SSV White-Label Node Solution

We are excited to introduce a unique solution within the DVT space: the SSV White-Label Node.

Key Benefits:

1. Dedicated SSV Nodes: Clients can register their validators on dedicated SSV nodes, enhancing security and regulatory compliance.
2. Cost Efficiency: This solution reduces the amount of $SSV required by over 93%.

The flexibility of the DVT API allows for retrieving dedicated SSV node IDs based on the client's API key. Clients can request to enable this solution to our product team. Upon confirmation, private SSV nodes will be set up and automatically retrieved when new validator requests are sent via the DVT API.

These updates mark a significant improvement in the security, efficiency, and compliance of our DVT API, reinforcing our commitment to providing the best service to our clients.