web3privacy
/
web3privacy
zrcadlo https://github.com/web3privacy/web3privacy.git
1
0
Rozštěpit 0
Zdrojový kód Úkoly Balíčky Projekty Vydání Wiki Aktivita

Update Scoringmodel.md

This commit is contained in:
Mykola Siusko 2023-02-04 14:03:41 +01:00 odevzdal GitHub
rodič 8bf0e49d09
revize 4011254f20
V databázi nebyl nalezen žádný známý klíč pro tento podpis
ID GPG klíče: 4AEE18F83AFDEB23
1 změnil soubory, kde provedl 9 přidání a 6 odebrání
Zobrazit statistiky Stáhněte soubor záplaty Stáhněte rozdílový soubor Rozbalit všechny soubory Sbalit všechny soubory

15
Web3privacynowplatform/Scoringmodel.md
Zobrazit soubor

@ -63,12 +63,15 @@ _Questions to be observed_
- is it decentralized and based on opensource technology ?
# Take 2
1) much the users in control of their data disclosure? (Scale 1-10)
2) how well commnity feedback and evaluation is built into product dev? (the less -» the more centralised it is -» the smaller the % of it staying private without the collectiv intelligence. this is like the web3privacynow - platform part actually, for sales but also i found this really relevant.
2/b) is there a community bug / security bounty program / platform?
3) how much transparent disclosure is avaliable on the tech and company - like smart contract audits, security audits,source of financing?
4) how private the tech stack it uses on all layers. from hardware to l3/l4 etc. how well it is disclosed what they built on and where they host stuff, or if the tech is decentralised like nym - is there avaialbe dashboard data about this?
5) product roadmap and release flexibiity - this is harder one, and I'm not sure it makes sense. what i mean is its also important to have a clear vision but at the same time to react to current needs / bugs / fixing vulnerabilities. maybe its redundant with no2 and no2b
| Question | Observation |
| ------------- | ------------- |
| much the users in control of their data disclosure? | (Scale 1-10) |
| how well commnity feedback and evaluation is built into product dev? | the less -» the more centralised it is -» the smaller the % of it staying private without the collectiv intelligence. this is like the web3privacynow - platform part actually, for sales but also i found this really relevant. |
| is there a community bug / security bounty program / platform? | yes, no |
| how much transparent disclosure is avaliable on the tech and company - like smart contract audits, security audits,source of financing? | yes, no |
| how private the tech stack it uses on all layers. from hardware to l3/l4 etc. how well it is disclosed what they built on and where they host stuff, or if the tech is decentralised like nym - is there avaialbe dashboard data about this? | yes, no |
| product roadmap and release flexibiity - this is harder one, and I'm not sure it makes sense. what i mean is its also important to have a clear vision but at the same time to react to current needs / bugs / fixing vulnerabilities. | maybe its redundant with no2 and no2b |
# Take 3
1. What are the trust assumptions the user has by using the platform?