Update Readme.md
This commit is contained in:
Mykola Siusko
GitHub
rodič
deaac0cbd9
revize
ee7c5d3c87
|
|
@ -114,16 +114,29 @@ Answers:
|
|||
- you can start by reading Litentry’s explainers first
|
||||
- then maybe then read through other privacy solutions to make the comparison?
|
||||
|
||||
_Observations_:
|
||||
|
||||
_Product feature_
|
||||
|
||||
|
||||
**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.
|
||||
- technical things you could ask a technical person you trust to look at its oss code.
|
||||
|
||||
_Observations_:
|
||||
|
||||
_Product feature_
|
||||
|
||||
**Swarm**
|
||||
|
||||
Answers:
|
||||
- reading our whitepaper, which provides a comprehensive overview of Swarm's technology and how it achieves privacy
|
||||
- reading our whitepaper, which provides a comprehensive overview of Swarm's technology and how it achieves privacy
|
||||
|
||||
_Observations_:
|
||||
|
||||
_Product feature_
|
||||
|
||||
**Railgun**
|
||||
|
||||
|
|
@ -138,13 +151,25 @@ Answers:
|
|||
- The To address is simply the RAILGUN smart contract on @0xPolygon in this case. So nothing is revealed about the recipient.
|
||||
- The value that exchanged hands? #Private
|
||||
- Try to decode the input data for the transaction? It's all #encrypted.
|
||||
- So how much money exchanged hands here? Well, the short answer here is - it's #private. Only the sender and recipient will know. There will be #zeroknowledge about it unless they choose to reveal the transaction information."
|
||||
- So how much money exchanged hands here? Well, the short answer here is - it's #private. Only the sender and recipient will know. There will be #zeroknowledge about it unless they choose to reveal the transaction information.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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.
|
||||
- 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.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**HOPR**
|
||||
|
||||
|
|
@ -160,6 +185,12 @@ https://twitter.com/hoprnet/status/1572601550379311104
|
|||
- Check out our HOPR Basics series for more details:
|
||||
https://medium.com/hoprnet/basics/home"
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Waku**
|
||||
|
||||
Answers:
|
||||
|
|
@ -167,6 +198,12 @@ Answers:
|
|||
- 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!
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Rotki**
|
||||
|
||||
Answers:
|
||||
|
|
@ -175,31 +212,61 @@ Answers:
|
|||
- Opensource, so your techy friend can see we are not lying. It really isn't complicated imo.
|
||||
- To be 100% sure read code
|
||||
- But it does not take an expert to understand that an application that you download, run locally and keeps all data locally is 1000x more private than a webapp
|
||||
- We have been brainwashed to calling webapps, as ""apps"" now."
|
||||
- We have been brainwashed to calling webapps, as ""apps"" now.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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…
|
||||
- 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…
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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.
|
||||
- All we know is your wallet pubkey, with which we issue and assign to a network key.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Lit protocol**
|
||||
|
||||
Answers:
|
||||
- State of Network is available right here: https://t.co/sgaOX5SPga
|
||||
- State of Network is available right here: https://t.co/sgaOX5SPga
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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.
|
||||
- The discord has a lot of resources as well, depending in what you need.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Sons of crypto**
|
||||
|
||||
|
|
@ -209,19 +276,37 @@ Answers:
|
|||
- We will have built in mixers
|
||||
- We dont know or what to know who or where users are. For non-techie that would not be straight forward.
|
||||
- Perhaps using something like https://charlesproxy.com to see all the traffic. Still fairly techie though.
|
||||
- For devs all of our code is open source on github, anyone can read it.
|
||||
- For devs all of our code is open source on github, anyone can read it.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Orbis**
|
||||
|
||||
Answers:
|
||||
- You can check our open-sourced SDK, but that would require people to read some code :) https://t.co/iiA7lSaDdn
|
||||
- You can check our open-sourced SDK, but that would require people to read some code :) https://t.co/iiA7lSaDdn
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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"
|
||||
- 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"
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**KILT Protocol**
|
||||
|
||||
|
|
@ -230,7 +315,13 @@ Answers:
|
|||
|
||||
1. they are not stored on any central entity but totally decentralised in the wallets of their owners.
|
||||
2. users decide for what reason they share a credential with whom.
|
||||
3. one can share credentials partially" A DID is created on the user‘s device. Like your blockchain keypair. It’s an identifier like your face, your fingerprint or your signature. It’s not issued by any entity. This way it’s always decentralised and does not have a decentralisation status.
|
||||
3. one can share credentials partially" A DID is created on the user‘s device. Like your blockchain keypair. It’s an identifier like your face, your fingerprint or your signature. It’s not issued by any entity. This way it’s always decentralised and does not have a decentralisation status.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Onionclub**
|
||||
|
||||
|
|
@ -238,43 +329,85 @@ 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.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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"
|
||||
- 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
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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
|
||||
- This is possible thanks to @LitProtocol and @ceramicnetwork
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Puma browser**
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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.
|
||||
- Our code is open source in case you wanna ask someone from your trust.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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.
|
||||
- You need this information from a trusted source that has done the job of checking its privacy.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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.
|
||||
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Beam**
|
||||
|
||||
Answers:
|
||||
|
|
@ -282,20 +415,45 @@ Answers:
|
|||
- I also recommend reading the Documentation
|
||||
- you can reach me here on Twitter, on Telegram @maxnflaxl or on Discord Maxnflaxl#8141
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Leo wallet**
|
||||
|
||||
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
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Scala**
|
||||
|
||||
Answers:
|
||||
- You should probably start here: https://wiki.scalaproject.io and if you have questions send us a DM.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Media network**
|
||||
|
||||
Answers:
|
||||
|
|
@ -303,12 +461,24 @@ Answers:
|
|||
- 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.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Automata**
|
||||
|
||||
Answers:
|
||||
|
|
@ -317,6 +487,12 @@ Answers:
|
|||
https://medium.com/atanetwork/whats-automata-ii-protocol-overview-witness-7c1fc2232655
|
||||
- https://medium.com/atanetwork/whats-automata-iv-conveyor-93c9335e4f43"
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Aleo**
|
||||
|
||||
Answers:
|
||||
|
|
@ -325,6 +501,12 @@ https://www.aleo.org/post/zero-knowledge-primitives-by-aleo
|
|||
- Hi! there are so many info you can find in blog articles :Laughheart: unofficial!
|
||||
also there are so many videos on this topic you can find in 📸┃user-content our community has so many contributions and rich diversity of content
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**MASQ**
|
||||
|
||||
Answers:
|
||||
|
|
@ -332,6 +514,12 @@ Answers:
|
|||
- 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
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Lokinet**
|
||||
|
||||
Answers:
|
||||
|
|
@ -342,10 +530,23 @@ Answers:
|
|||
- net usage statistics tools from projects like pihole provide great visualizations for some of it.
|
||||
- i am sure there are ones for netflow data too not just dns.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**ActiList**
|
||||
|
||||
Answers:
|
||||
We are running on the Secret Network blockchain, you can check out http://SCRT.network for more information.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Cheqd**
|
||||
|
||||
Answers:
|
||||
|
|
@ -355,11 +556,23 @@ Answers:
|
|||
https://t.co/8OQ0Fav16W" ("Concepts of payment rails")
|
||||
- As a final note, you'll find a range of useful content and project progress on our blog. If you have any questions, you can jump on our official telegram channel or tweet us: https://t.co/wHRkrrJ3F0"
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**PirateChain**
|
||||
|
||||
Answers:
|
||||
Look at the block explorer and see if you can figure out how much ARRR is in a wallet...
|
||||
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Obscuro**
|
||||
|
||||
Answers:
|
||||
|
|
@ -369,18 +582,36 @@ Answers:
|
|||
- Provide education on how TEEs preserve privacy and the things to look out for"
|
||||
- We'll deploy a game with significant funds that can only be won by breaking Obscuro's privacy. As long as the game isn't won, users can be confident privacy remains intact.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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 :)
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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"
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**nix-bitcoin**
|
||||
|
||||
Answers:
|
||||
|
|
@ -388,6 +619,12 @@ Answers:
|
|||
- 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.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Litecash**
|
||||
|
||||
Answers:
|
||||
|
|
@ -395,12 +632,30 @@ Answers:
|
|||
- 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.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**Black Box**
|
||||
|
||||
Answers:
|
||||
- For the transactions anonymizer, privacy is preserved when the onchain link between SENDER and RECEIVER wallets is broken or untraceable.
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
||||
**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
|
||||
- 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
|
||||
|
||||
_Observations_:
|
||||
-
|
||||
|
||||
_Product feature_
|
||||
-
|
||||
|
|
|
|||
Načítá se…
Odkázat v novém úkolu