5.1 KiB

Surový Trvalý odkaz Blame Historie

Community feedback x our Scoring model 1.2 version.

Main goal: to have an MVP on how non-techies could analyze if the project is private or not (think of "IMDB" or "L2beat" for privacy)

Sub-goal: to have a more objective scoring model made in collaboration with the privacy community.

Context:

Persona: a web3 casual user without dev knowledge & privacy illiterate. He/she/they has limited time for research & needs to perform simple steps to ensure that service is private.
Assessment categories: we broke down analytics flow into 2 main categories: validity track (quick check-up) & DYOR (do your own research that requires more time & subjective opinion).

Sandbox: DeFi category that has been analyzed

How to use sandbox?

Read takeaways.
Give us feedback via general comments in the Community on Signal or make a Pull request here.
You can always explore 38 DeFi project' assessment here

Scoring model 1.2: validity track

Validity track covers GitHub, Product-readiness, Team, Docs, Audit.

Note: quick assessment helps to decrease privacy dark patterns from obscure language to test-net claiming it has a "state of art privacy".

We use % as a simplified way to prototype scoring model (from % to 100%). Later versions will include a mixmodel of %, yes/no assumptions & much complex observations.