Again, truly impressed by the level of attention this is receiving, never expected such responsiveness, which is a good thing !

Allow me to add the steps that should happen BEFORE the ones per your guidance Ecuamobi:

- if a DT member believes there is reason to do a negative vote, he reaches out in PM to the project team
- if he doesn't get feedback in an acceptable timeframe, he checks with other channels to reach the team or checks with the community
- if he feels ignored or obtains feedback that leaves him with no other option than to do a negative vote, he first reflects about the impact of the negative vote (ref the red warning visible to entire community and new users)
- if he concludes the facts are leaving no doubt that things are pointing at a potential scam and a red warning is valid, he lists the facts clearly

And from there we roll into your guidance for the project team receiving a negative vote, to which I agree entirely and now understanding how DT voting works, will be applied in the future.

Again, pls read the initial thread question at the end and consider if it is something to be looked at further, to be clear I launched this thread questioning how you/we can limit the impact if the above steps are not respected by a DT member.