Whitepaper - Maidsafe With Cover

On the SAFE network, the following rules ensure a trusted group:
• It is hard to have a vault with a particular address (the address of a new vault will be
defined by the network using the hash of the vault’s credentials). In addition, each
time a vault is switched off and then rejoins the network, it will be assigned a new
address. Furthermore, the node will not be considered a full functional vault until the
verification period is complete.
• When a request is emitted from a group, all group member’s signatures will be attached.
On the receiver side, a routing level find closest verification will be carried out to
verify the senders are really closest nodes to the target. In addition, the public keys
for the nodes will be downloaded from the network to validate signatures.
• The close group is not formed in a deterministic way (i.e. based on XOR distance as
defined by Kademlia only). The close group of a target will only be formed when the
target goes to the network. Unless the target is pre-known, it cannot tell whether two
nodes are close.
• For sensitive data like currency or transaction, there is an additional level of protection :
chained group. Chained group means the target is not only handled by the group
around it, but also is managed by the other group chained to the target. The chain is
established in a determistic way once the target is known, which allows verfication by
public.
• The exchange of a vault between different users is not allowed. It is possible for a vault
not to be linked to an account (unowned) and then linked to an account later (owned).
However, once linked that vault cannot be detached.
Furthermore, there is the RUDP [ref RUDP] layer which encrypts communications between
nodes to prevent the message content from being secretly modified by a third party. This
ensures the request reflects the real intention of the sender.
Once the majority of the nodes inside the group have sent out a consistent request, it shall