Update Readme.md

Web3privacynowplatform/scoringmodel/Readme.md

@@ -73,7 +73,6 @@ _Product feature_:
 **Session**	
 
 Answers
-
 - There is the Session code audit	
 - See what's being said in (non-paid) media: reviews, articles, etc.
 
@@ -87,8 +86,7 @@ _Product feature_:
 
 **ZKBob**
 
-Answers
-
+Answers:
 - whether the solution forces users to preserve their privacy or if it's the user's responsibility. For example, Tornado Cash increases anonymity by requiring users to deposit a specific amount but doesn't require using different addresses for withdrawals	
 - zkBOB doesn't force specific amounts or address usage, but encourages the use of new withdrawal addresses by rewarding them with a small amount of native coins that can be used in the next transaction to pay for gas.	
 - How the components of the protocol communicate with each other and if users can replace any components is another important aspect.	
@@ -116,15 +114,20 @@ Answers:
 - you can start by reading Litentry’s explainers first	
 - then maybe then read through other privacy solutions to make the comparison?
 
-**BrightID**	
+**BrightID**
 
+Answers:
 - You could rationalize from the fact that it does not ask you for any personally identifying information directly, so there is nothing to preserve and keep it safe in its infrastructure.	
 - technical things you could ask a technical person you trust to look at its oss code.				
 
 **Swarm**	
+
+Answers:
 - reading our whitepaper, which provides a comprehensive overview of Swarm's technology and how it achieves privacy		
 
 **Railgun**	
+
+Answers:
 - Use @Railway_xyz to send a private transfer to a 0zk address through a Relayer. 	
 - Examine the "receipt" of that transfer on etherscan or arbiscan.  You will not find: (1) sender, (2) receiver, (3) token or (4) amount anywhere in the transaction receipt.	
 - There's a ton a technical person can do to verify but there's also a litmus test of #privacy that anyone can do. https://t.co/PqkUJWwmPD	
@@ -139,11 +142,13 @@ Answers:
 
 **Penumbra**	
 
+Answers:
 - maybe look for people you trust that are able to analyze the technical solution for its privacy merits and then get their opinion ? it's prob difficult to analyze a technical protocol with a non-technical analysis.	
 - what you're asking about relates to a more holistic assessment of a protocol and its attributes, so that should be within the scope of a research function moreso than a security audit function.				
 
 **HOPR**	
 
+Answers:
 - FOSS. Free & Open Source Software is the foundation that enables you to check whatever you want. The hoprd client is released under GPLv3 license that allows you to do that (and also modify and re-distribute) hoprd freely: GitHub"	
 - Code quality. Open source code should be readable to be helpful to you! To that end we enforce code quality via linters for Typescript
 https://github.com/hoprnet/hoprnet/blob/df7bc88517329472adbfe73bd4a22bddd5cfbcc9/package.json#L46… and for our Rust code: https://github.com/hoprnet/hoprnet/blob/master/rustfmt.toml…
@@ -157,12 +162,14 @@ https://medium.com/hoprnet/basics/home"
 
 **Waku**	
 
+Answers:
 - rfc.vac.dev is a good start. The RFC repository contains the specification of Waku and other protocols. In terms of @ethstatus's privacy claims. It is good to first look at the base layer: @waku_org
 - The RFCs describe the protocol and also contains security assumptions/guarantees section."	
 - The target audience are researchers and maintainers of Waku implementations. Not the easiest thing to read!
 
 **Rotki**	
 
+Answers:
 - Don't think u can. Gotta trust either me or someone who can read code	"The simplest thing a non-techie person can understand is:
 - Local application with all data stored in a local encrypted database (private by design)"	
 - Opensource, so your techy friend can see we are not lying. It really isn't complicated imo.
@@ -172,26 +179,31 @@ https://medium.com/hoprnet/basics/home"
 
 **Webb**	
 
+Answers:
 - you need to analyze the data they create through transactions. If that data (and metadata) can be analyzed for patterns then that can help define the degree of privacy of the solution.	
 - For our bridge solution, this is akin to rebuilding the tx graph and seeing if flows through such a graph can be identified. The main actions in our system are deposit, transfers, and withdrawals. We use the same zero knowledge proof based ideas to make it harder to track…				
 
 **Boring protocol**	
 
+Answers:
 - The "no logs" claims are generally very ambiguous. We make a point to know as little as technically possible about our users. We only know the bare minimum required to make the network function. 	
 - All we know is your wallet pubkey, with which we issue and assign to a network key.				
 
 **Lit protocol**	
 
+Answers:
 - State of Network is available right here:  https://t.co/sgaOX5SPga		
 
 **Alter network**	
 
+Answers:
 - "Try the #dapp and join the chatroom for @AlterDapp community	
 - "You can check out this video to see how to create an account on mobile: https://youtu.be/ZgpCHDnR9WU"	
 - The discord has a lot of resources as well, depending in what you need.	
 
 **Sons of crypto**	
 
+Answers:
 - We have no (google) analytics or tracking	
 - We do not run any backend	
 - We will have built in mixers	
@@ -201,16 +213,19 @@ https://medium.com/hoprnet/basics/home"
 
 **Orbis**	
 
+Answers:
 - You can check our open-sourced SDK, but that would require people to read some code :) https://t.co/iiA7lSaDdn		
 
 **Nighthawk Wallet**	
 
+Answers:
 - "It’s been a while since @NighthawkWallet APK was analyzed for privacy concerns. Feel free to test it at @ExodusPrivacy, a friendly service to investigate Android apps. 	
 - You can also obtain the @NighthawkWallet APK built with @fdroidorg and verify the “no anti-features” tag. We’ve worked hard to remove dependency on third-party services and strictly require users’ consent before opting into sharing information: https://t.co/YwYd4RUeVh	
 - Anti-Features are organized into “flags” that packagers can use to mark apps, warning of possibly undesirable behaviour from the user’s perspective, often serving the interest of the developer or a third party: https://t.co/LEaBIh8LV7"			
 
 **KILT Protocol**	
 
+Answers:
 "KILT preserves privacy in the same way paper or plastic credentials do:
 
 1. they are not stored on any central entity but totally decentralised in the wallets of their owners. 
@@ -219,73 +234,92 @@ https://medium.com/hoprnet/basics/home"
 
 **Onionclub**	
 
+Answers:
 - actually privacy is by default on our platform. It's not an option! 
 - So, every user will have this enabled and if they want to be doxxed then they need to jump through some hoops.		
 
 **Sismo**
 
+Answers:
 - Here are the public resources we have around the core of our ZK systems: 
 - Commitment mapper https://docs.sismo.io/sismo-docs/technical-concepts/commitment-mapper…
 - Hydra-S1 ZK Scheme https://docs.sismo.io/sismo-docs/technical-concepts/hydra-zk-proving-schemes…"	
 - Privacy & Security FAQ (the less technical part): https://t.co/M3eVLoYeUK"				
+
 **Krebit**	
 
+Answers:
 - Privacy-preserving: your credential's claims are stored encrypted off-chain. Self-sovereign: you control the access conditions to read your private data	
 - This is possible thanks to @LitProtocol and @ceramicnetwork		
 
 **Puma browser**	
 
-One of the reasons we started focusing more on enabling novel use-cases like ENS/HNS/IPFS and others is because it's really easy to demo in 10-15 seconds and prove, vs privacy is much harder to both demo and prove beyond company reputation.					
+Answers:
+One of the reasons we started focusing more on enabling novel use-cases like ENS/HNS/IPFS and others is because it's really easy to demo in 10-15 seconds and prove, vs privacy is much harder to both demo and prove beyond company reputation.	
+				
 **Hideyour.cash** 
 
+Answers:
 - We’re in the process to conduct a security audit with a full report when going to mainnet.	
 - Our code is open source in case you wanna ask someone from your trust.	
 
 **Spook**	
 
+Answers:
 - If you’re non-technical you won’t be able to verify it yourself.
 - You need this information from a trusted source that has done the job of checking its privacy.				
 
 **Elusiv**	
 
+Answers:
 - Once we are live, detailed docs including our whitepaper will be released!	
 - you can expect more explanatory content covering various topics around privacy, ZKPs, MPC and more.
 				
 **Beam**	
 
+Answers:
 - You can read Beams whitepaper	
 - I also recommend reading the Documentation	
 - you can reach me here on Twitter, on Telegram @maxnflaxl or on Discord Maxnflaxl#8141		
 
 **Findora**	
 
+Answers:
 Dapps using our privacy SDK will allow their users to transact with privacy. The evidence can be found on our block explorer when one attempts to view the details.				
 
 **Leo wallet**	
 
-Here's a talk by our co-founder/CTO discussing Zero-Knowledge Proofs in general and some features our wallet utilizes to increase privacy (e.g. single-use addresses): https://t.co/BLeKu2ghmS		
+Answers:
+- Here's a talk by our co-founder/CTO discussing Zero-Knowledge Proofs in general and some features our wallet utilizes to increase privacy (e.g. single-use addresses): https://t.co/BLeKu2ghmS		
+
 **Scala**	
 
-You should probably start here: https://wiki.scalaproject.io and if you have questions send us a DM.				
-
+Answers:
+- You should probably start here: https://wiki.scalaproject.io and if you have questions send us a DM.			
 **Media network**	
 
+Answers:
 - Thanks to the blockchain and smart contracts, your personal and payment information is always secure. 	
 - Communication between clients and providers is always encrypted.	
 - The client only needs to disclose the origin (i.e., the back-end IP) for the CDN marketplace and the Legacy dCDN.		
 
 **Privacy & Scalability**	
+
+Answers:
 - one approach might be looking at the public data from the system. If you see user identifiers being used only once that's perhaps helpful? But a non-technical person doesn't know if identifiers are true random, or if they're backdoored somehow.	
 - With the unirep protocol we're building an explorer that shows all the things happening in the system. So a user could see their epoch keys and attestations and see how they're distinct in the system. One thing we might do is write what can and can't be determined about the different identifiers.				
 
 **Automata**	
 
+Answers:
 - You should go to the very beginning of the medium articles. There is explained how the architecture works:	
 - https://medium.com/atanetwork/whats-automata-i-the-last-puzzle-piece-to-web-3-0-ea8a0af5840e
 https://medium.com/atanetwork/whats-automata-ii-protocol-overview-witness-7c1fc2232655
 - https://medium.com/atanetwork/whats-automata-iv-conveyor-93c9335e4f43"			
 
-**Aleo**	
+**Aleo**
+
+Answers:	
 - I'd start with the official Blog articles: www.aleo.org/post/welcome-to-aleo
 https://www.aleo.org/post/zero-knowledge-primitives-by-aleo	
 - Hi! there are so many info you can find in blog articles :Laughheart:  unofficial! 
@@ -293,12 +327,14 @@ also there are so many videos on this topic you can find in 📸┃user-content
 
 **MASQ**	
 
+Answers:
 - Join our beta testing group and simply try it for yourself!	
 - You can run any local and in-browser IP tests you want, and use other tools to see how the data is transported to and from your machine.	
 - As a non-techie the first start is simply check an IP checker website while using		
 
 **Lokinet**	
 
+Answers:
 - user education would absolutely be how. 
 - To be fair lokinet's docs arent really there rn, it's always on the todo list and never really gets done.	
 - once you do all the user education you can, you get to the point where you see that privacy is more of a bonus to seal the deal than a primary feature from the perspective of the consumer grade user.	
@@ -307,10 +343,12 @@ also there are so many videos on this topic you can find in 📸┃user-content
 - i am sure there are ones for netflow data too not just dns. 			
 
 **ActiList**	
-We are running on the Secret Network blockchain, you can check out http://SCRT.network for more information.			
 
+Answers:
+We are running on the Secret Network blockchain, you can check out http://SCRT.network for more information.			
 **Cheqd**	
 
+Answers:
 - You can start by learning about verifiable credentials, decentralised identifiers(DID), and the concept of Self-Sovereign identity.	
 - cheqd is quite technical, and in order to understand why it is privacy preserving, you'll need to get familiar with some terms.	
 - "You can also learn more about each of the components of the network, the credential types, co clots of payment rails and verification by visiting our learn pages
@@ -319,10 +357,12 @@ https://t.co/8OQ0Fav16W" ("Concepts of payment rails")
 
 **PirateChain**	
 
+Answers:
 Look at the block explorer and see if you can figure out how much ARRR is in a wallet...	
 				
 **Obscuro**	
 
+Answers:
 - we'll build tools that have been audited by trusted authorities to verify attestation of software versions along with audits showing the software doesn't leak privacy
 - although superficial, our block explorers will demonstrate privacy"	
 - anyone can run a node and use simple network tools to verify data flowing is encrypted
@@ -331,29 +371,36 @@ Look at the block explorer and see if you can figure out how much ARRR is in a w
 
 **SendingMe**	
 
+Answers:
 - you can visit  @Sending_Network account to learn more about what is under the hood	
 - our GitBook is pretty easy to read even if you are not techie :)				
 
 **Mysterium Network**	
 
+Answers:
 - we would recommend our docs: https://docs.mysterium.network	
 - "Also here is a study on decentralized VPN (featuring us) by @NorthwesternU, thread + paper here :https://twitter.com/MysteriumNet/status/1619616182964994049"				
 
 **nix-bitcoin**	
 
+Answers:
 - For one, you need to be fairly technical to setup nix-bitcoin at this point.	
 - One important aspect is whether all outbound connections are tunnelled through Tor by default. 
 - You could check the generated configuration files. For example, make sure that proxy=127.0.0.1:9050 is in fact set in /var/lib/bitcoind/bitcoin.conf.				
 
 **Litecash**	
 
+Answers:
 - Litecash is the first fork of BEAM and we tweaked the fees to zero, and less congested to keep lightning fast transaction along with a sustainable coin supply for mass adoption while keeping inflation resistance. 	
 - Our privacy is built on the mimblewimble protocol which is unique compared to other privacy protocols. Litecash transactions are not held on a ledger and disappear as opposed to other methods of scrambling or clustering which could actually be decoded with new wave super computers.	
 - if a transfer does not complete due to a wrong address or defunct wallet, funds get sent back to the sender within 24 hours ensuring no lost coins. 			
 
 **Black Box**	
+
+Answers:
 - For the transactions anonymizer, privacy is preserved when the onchain link between SENDER and RECEIVER wallets is broken or untraceable.					
 
 **Ergo**	
 
+Answers:
 - Ergo has the flexibility to implement privacy in various use cases. Although it is not a privacy-oriented blockchain, Sigma Protocols allow privacy-oriented dApps like ErgoMixer, or private side-chains, to obfuscate specific transactions  https://t.co/KVNIk8amD1