Porovnat revize

...

3 Commity

Autor SHA1 Zpráva Datum
Mykola Siusko d8dd93c68c
Update Scoringmodel_techies.md 2023-11-09 23:13:48 +01:00
Mykola Siusko 6519de1130
Update Scoringmodel_techies.md 2023-11-09 23:07:10 +01:00
Mykola Siusko 8c689bb83b
Update Scoringmodel_techies.md 2023-11-09 23:05:58 +01:00
1 změnil soubory, kde provedl 17 přidání a 2 odebrání

Zobrazit soubor

@ -78,6 +78,21 @@ _Validity track covers GitHub, Product-readiness, Team, Docs, Audit._
| DAO structure (if applied) | + |
| How centralized is the protocol governance? [Railgun_ governance docs](https://docs.railgun.org/wiki/rail-token/protocol-governance) | + |
**Traceability**
example:
1. Use @Railway_xyz to send a private transfer to a 0zk address through a Relayer.
2. 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.
https://t.co/PqkUJWwmPD
* This is a 0zk -> 0zk transaction (sending tokens from one #DeFi user to another. You'll note that the scan has a from address but this is simply a Relayer address that pays gas to process the on-chain computation).
* User communications with a Relayer are passed via through the @waku_org p2p gossip network, so Relayers can't know a particular message origin. In other words, even here #privacy was a big consideration throughout the tech stack not just on Etherscan.
* 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.
# Backlog
## General
@ -120,5 +135,5 @@ from community
* use a packet inspection tool such as #Wireshark to check all packets coming into your machine and going out
* using something like https://charlesproxy.com to see all the traffic
* Android: Feel free to test it at @ExodusPrivacy, a friendly service to investigate Android apps.
* Android: check @fdroidorg and verify the “no anti-features” tag. Weve worked hard to remove dependency on third-party services and strictly require users consent before opting-in to sharing information. [Example](https://f-droid.org/en/packages/com.nighthawkapps.wallet.android/)
* Android: Feel free to test it at [Exodus Privacy](https://exodus-privacy.eu.org/en/), a friendly service to investigate Android apps.
* Android: check https://f-droid.org and verify the “no anti-features” tag (like dependency on third-party services). [Example](https://f-droid.org/en/packages/com.nighthawkapps.wallet.android/)