Proposal: Expanding the Simple DVT Module

@Mol_Eliza @KimonSh
Thank you so much for the clarifications. We will comment on each topic as below.

On 1. How can we mitigate the risk of DVT protocols have?

We believe that there’s no need for having other risk solutions such as insurance. We fully agree that implementing DVT itself is a form of risk mitigation, and the formula @Mol_Eliza provided made it much clearer.

We are concerned about software vulnerabilities, including update timing. The current approach for mitigating the risk of software updates may not be effective, as an attacker would likely wait until all clusters are onboarded to exploit vulnerabilities, rather than attacking when only one-third of the clusters are onboarded.

However, as the two risk scenarios can be covered with the current cover fund, and since the extreme scenario is nearly impossible to realize, having the cover fund would be enough to move DVT forward.

Thank you so much for the detailed explanation again.

On 2. What would be the targeted revenue for DVT NOs?

It seems like each DVT NO will earn roughly ~€228/month based on the provided numbers and our calculation, considering the fact that each cluster has 7 NOs at the moment.
If that is true, we believe the target should be a bit higher, as there are costs other than the hardware itself, such as network cost and human operation cost.

We can focus on provide competitive yields in the later stage, but we see the need for providing better yields than the one proposed from the early phase, given the fact that the current target might not even cover the costs involved.

On 3. How will we choose ANO?

We understand the initial onboarding process. We would appreciate details on future plans, including additional onboarding or replacements of ANOs, which should be desirable for keeping the quality of ANOs.

On 4. Where does 3.5% of share come from then?

Thank you for the clarification provided. We are clear on this matter now.

1 Like