Update Scoringmodel.md

Web3privacynowplatform/Scoringmodel.md

@@ -49,3 +49,26 @@ _Reference_: https://tosdr.org
 **Centralisation level (incl KYC)**
 
 Reference: https://kycnot.me/about#scores
+
+On-going community research (survey) within the privacy experts - all answers on how to score services privacy (non-redacted):
+- read the documentation
+- ask about its weaknesses from competitors
+- try to trace a transaction
+- Precise description of the concrete privacy properties. Privacy is complicated so if they don't say exactly what they protect, then its likely vapor
+- Usability - for end users or in the developer experience if it is a B2B project.
+- Validation by trusted and respected independent scientists and researchers
+- Open source
+- Good and comprehensive documentation
+- There is a way to verify the code I think is running, really is running e.g. attestation service
+- Ability to run part of the service and verify for myself
+- Other tooling to verify e.g. block explorers 
+- Reputation of team
+- Open source/FOSS
+- Minimal to no metadata capture
+- Doesn’t sell your data
+- Non-vague, and non-intrusive privacy policy
+- protects against global passive adversary
+- does not implement kyc or aml
+- strong secure anonymity tech
+- ideological team
+- not funded by big US VCs like a16z