Update Readme.md

Web3privacynowplatform/Briefs/Brief 2.0.md

@@ -0,0 +1,106 @@
+*Brief for a private web3-services*: please, follow general requirements to be highlighted on The Web3Privacy now platform.
+
+How it works:
+1. You fill a brief (at least "mandatory field").
+2. Our team reviews application.
+3. Verified data will be published at The Web3Privacy now platform.
+
+# Mandatory data
+
+## Basic info
+
+| Request  | Data point | 
+| ------------- | ------------- |
+| **Project name**  | add here |
+| **Logotype**  | add link |
+| **Website**  | add link |
+| **Short project description (1 sentence)** | add here |
+| **Blog** | add link |
+| **Twitter (X)** | add link |
+| **Support** | add links on Discord, Telegram etc |
+
+## Assessment info
+
+| Request  | Data point | 
+| ------------- | ------------- |
+| **Product-readiness** | specify state & date (testnet, mainnet; date D/M/Y) |
+| **Github**  | add link |
+| **Documentation**  | add link |
+| **Team**  | add link to a team page (website or GitHub) |
+| **Third-party audit**  | add links on actual audits + date D/M/Y |
+
+# Additional data (non-mandatory)
+
+**Token**
+| Request  | Data point | 
+| ------------- | ------------- |
+| **Do you have a token** | add here Coingecko link |
+
+**Socials**
+| Request  | Data point | 
+| ------------- | ------------- |
+| **Telegram** | add link |
+| **Discord** | add link |
+| **Other** | add link |
+
+**Docs**
+| Request  | Data point | 
+| ------------- | ------------- |
+| **Whitepaper** | add link |
+| **Litepaper** | add link |
+
+**Team**
+| Request  | Data point | 
+| ------------- | ------------- |
+| **List core contributors** | Github links | 
+
+**Funding**
+| Request  | Data point | 
+| ------------- | ------------- |
+| **How are you funded**  | self-funded, VC, donations, mixed | 
+| **List VCs backing you**  | if aplicable |
+| **List VCs round**  | if aplicable: pre-seed, seed, Series A, B,C | 
+| **Raised money** | add a public link | 
+
+**Github**
+| Request  | Data point | 
+| ------------- | ------------- |
+| **What licence is in use**  | add link to Github repo or a Docs page | 
+
+**Technology**
+| Request  | Data point | 
+| ------------- | ------------- |
+| **Technical specialisation**  | specify: ZK, account abstraction, mixnet etc | 
+| **Specify technology readiness**  | infra: testnet/mainnet, apps: MVP/beta/alpha | 
+| **Features**  | list 3 key tech features | 
+| **Encryption method**  | if aplicable: specify | 
+
+**Privacy**
+| Request  | Data point | 
+| ------------- | ------------- |
+| **Is it peer-to-peer**  | yes/no | 
+| **Complience**  | yes/no |
+| **KYC**  | yes/no |
+| **Privacy policy** | add link |
+| **Collected data**  | specify what data do you collect |
+| **Data sharing** | specify what data you share with third-parties |
+| **Sign-in requirments** | specify what data is needed to start using service |
+| **Identity integrations** | do you use third-party identity services (like ENS, Gitcoin Passport etc) |
+
+**Security**
+| Request  | Data point | 
+| ------------- | ------------- |
+| **Asset custody** | specify | 
+| **Upgradability**  | specify |
+| **Social dependency**  | team, CEO |
+| **Third-parties dependency** | specify |
+| **Technical dependency** | specify: Ethereum, ZK etc |
+| **Have you been audited by a third-party** | yes/no |
+| **What company audited** | specify (one &/or many) |
+| **When you were audited** | date: D/M/Y (one &/or many) |
+| **Add links to the audits** | here |
+
+**Roadmap (technical)**
+| Request  | Data point | 
+| ------------- | ------------- |
+| **Add types & dates of product-maturity** | specify testnet (infra), MVP (dApp): date D/M/Y; mainnet, beta | 

Web3privacynowplatform/scoringmodel/Survey/Readme.md

@@ -22,36 +22,18 @@ We asked 50+ privacy opinion leaders how they will attest privacy claims behind
 | further questions feel free to drop them in our discord | Discord serves as a two-way comms platform (but depends on the project) & it creates additional dependence of user on the core team | - |
 
 ## **Holonym**	
-
-Answers:
-- Check their website or docs	
-- If they vaguely say “data is kept private” and provide no explanation how, run	
-- If they provide an explanation, check with an expert or DYOR
-
-_Observations_:
-- "check" is a highly abstract action related to the website or docs -> extract value should be related to understanding "privacy"-validity markers
-- "private data explainers" needed to be defined within use-cases (case studies for the market)
-
-_Product feature_:
-- website checklist (1-2-3-4-5..., yes/no validity)
-- case studies "private data" explainers
-- DYOR (that's our platform)
+| Answers  | Observations | Product feature |  
+| ------------- |------------- |------------- | 
+| Check their website or docs | "check" is a highly abstract action related to the website or docs -> extract value should be related to understanding "privacy"-validity markers | website checklist (1-2-3-4-5..., yes/no validity) |
+| If they vaguely say “data is kept private” and provide no explanation how, run | "private data explainers" needed to be defined within use-cases (case studies for the market) | case studies "private data" explainers |
+| If they provide an explanation, check with an expert or DYOR | - | DYOR (that's our platform) |
 
 ## **Spinner cash**	
-
-Answers
-- code is law. 
-- So how about "don't trust, verify"?	But to verify, it would require certain technical skills... like reading source code 😅	
-- We hope to bring in 3rd party auditors at some point
-
-_Observations_:
-- the more ideological language is on the website - the harder to navigate the factual privacy features 
-- source code reading is a highly technical skill (moreover: Ethereum dev could struggle with Solana code & vice versa)
-- 3rd party list is needed here to be transformed into privacy signalling features
-
-_Product feature_:
-- missing 3rd party audit potential risks 101
-- 3rd party list (yes/no) from security audit agencies to independent security engineers (+their reputation 101 in later versions)
+| Answers  | Observations | Product feature |  
+| ------------- |------------- |------------- | 
+| code is law | the more ideological language is on the website - the harder to navigate the factual privacy features  | missing 3rd party audit potential risks 101 |
+| So how about "don't trust, verify"? But to verify, it would require certain technical skills... like reading source code 😅 | source code reading is a highly technical skill (moreover: Ethereum dev could struggle with Solana code & vice versa) | 3rd party list (yes/no) from security audit agencies to independent security engineers (+their reputation 101 in later versions) |
+|We hope to bring in 3rd party auditors at some point | 3rd party list is needed here to be transformed into privacy signalling features | - |
 
 ## **Session**