storj-archived / sips

Storj Improvement Proposals.
GNU General Public License v3.0
14 stars 11 forks source link

Decentralized bridges #22

Open MeijeSibbel opened 6 years ago

MeijeSibbel commented 6 years ago

Start thinking/compiling a plan on how federated bridges would work and how it could be implemented.

The way i see this being implemented is that some of the Storj services will be offloaded to volunteers who run a package like a Bitcoin full node on a server, they then get a reward for running and maintaining this package. The main goal of this is to prevent the Storj network from crashing when the main Storj bridge goes down or even during bridge updates. These "min bridges" do not have to run all normal Storj bridge services, for instance i don't see a reason for these federated bridges to run a billing system, this should be handles by the main bridge. Setting up a federated bridge should be easy enough so that tech savvy people can start and maintain a bridge. The entire idea of this is to make sure Storj does not become a second AWS where if the main bridge goes down, so does the entire network.

ElanHasson commented 6 years ago

I am new to the project, but extremely fascinated by it. Please forgive my ignorance to the details of the implementation.

What if the bridge was part of being a farmer? Expose the rest apis on each farming node. Since it stores metadata, why not store that metadata on nodes (along side stored data), and allow all of that work to be truly distributed alongside the data it is coordinating.

braydonf commented 6 years ago

So two parts that can help move this forward:

omuzikaapexprogaming commented 6 years ago

Actually I would appreciate to run a dedicated bridge host on my HA cluster , only thing what has to be selfprooving is the requirements and rewards system of decentralized storj bridges .