Skip to content
This repository has been archived by the owner on Jan 6, 2020. It is now read-only.

Commit

Permalink
Update birthday_paradoxsybil_attack.md
Browse files Browse the repository at this point in the history
  • Loading branch information
NLambert committed Apr 6, 2015
1 parent b5d7110 commit 1c50194
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion en/attacks/birthday_paradoxsybil_attack.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ While it is not possible to deliberately position the malicious Vaults around a

The SAFE Network requires all requests be processed by at least two groups of Vaults.

A MaidSafe client passes a request to its 4 Data managers, who verify the request based on the client’s signature. The request is then passed to a deterministically selected group of 4 other Vaults which also verify the request based on its signature.
A SAFE Network client passes a request to its 4 Data managers, who verify the request based on the client’s signature. The request is then passed to a deterministically selected group of 4 other Vaults which also verify the request based on its signature.

By deterministically selecting the second group of Data managers, this attack no longer holds true for the SAFE Network, since it is not possible for the attacker to gain control over a Vault by simply surrounding it.

Expand Down

0 comments on commit 1c50194

Please sign in to comment.