3 ms·
> Regarding Sybil, nodes define their own trust relationships, so membership is open but not automatic. Thanks for clarifying! So you're expecting people to
by eMGm4D0zgUAVXc7 6y ago
> Regarding Sybil, nodes define their own trust relationships, so membership is open but not automatic.
Thanks for clarifying!
So you're expecting people to
- manually add peers to be able to use the network.
- manually monitor the said peers for if they do malicious transactions, and manually ban them if yes.
Right?
How is this supposed to work considering that:
- most users won't care about manually adding peers. They'll just add EVERYONE who offers to be added so they can be done with it and use the system.
- most users probably won't even understand what a malicious transaction is in the first place.
- the few who do will for sure not have the time to monitor a network which does dozens or in the future even thousands of transactions per second.
This seems just humanly impossible, there's by no means sufficient human time available to manually monitor a P2P network's content if the said content is super boring and complex.
If it were a distributed social network you could expect people to e.g. manually flag spam because using a social network implies reading the posts contained in it.
But manually reviewing money which strangers send to each other is boring as hell, who will do this?
- comex 6y agoAs far as I can tell, "nodes define their own trust relationships" is true only when considering the protocol at an abstract level, or if you're building the code yourself. As a concrete end user using the Signal client, you don't actually get to define your own trust relationships; the app is just hardcoded to trust a specific list of servers, albeit somewhat protected by SGX. Please correct me if I'm wrong.