Fejoa: The Portable Privacy-
Preserving Cloud

Why not a distributed network?

April 15, 2018    Blog Post

One question you may ask is “Wouldn’t it be possible to use a distributed network to find Fejoa nodes that migrated to a new service provider?”. The short answer is yes, it would be possible. However, as you can guess, there are some downsides with this approach.

First, you need a distributed network. This in itself is not much of a problem but requires that somebody is maintaining the distributed network, i.e. runs the bootstrap nodes of the network.

Secondly, a single distributed network is not enough. In some cases you don’t want to depend on a single “centralized” distributed network. For example, if a certain network has some flaws or is maintained by a malicious party you may want to use an alternative network. Moreover, you may want to run Fejoa in a private network environment but a single network would make interaction with users from other networks impossible. Users would be confined to a single network and would not be able to find users who migrated to a different network.

Fejoa is designed to be as flexible as possible and to be independent of a 3rd party. For this reason it does not rely on a distributed network but simply tracks the last known location of a Fejoa node. However, this does not prevent Fejoa from leveraging distributed networks. For example, the location of a Fejoa node could be pointing to a distributed network. In this way Fejoa can keep track of user across different distributed networks and when a contact chooses to join a different network, users from other networks would still be able to find this contact.