Welcome to the Origin Bridge Server.

The Origin Bridge Server connects the old world to the new. Visit our Github or Docs to learn what this is about.



Purpose of the bridge server:

Most traditional web APIs, such as those from Facebook and Twitter, can only interact with a centralized server located at a specific domain. A decentralized application, like our Origin Demo DApp, doesn't need to "live" on a particular server. (In fact, you can load it from any IPFS gateway!) Thus, in order for the DApp to use an "old world" API, it needs a Bridge Server!

DApps runing on Origin can connect to the Bridge Server of their choosing in order to enable the following functionality which is either impossible or impractical to do directly onchain, including:

Indexing

Searching, browsing or filtering results is impractical to do either onchain or in the browser. DApps can connect to a bridge-server to solve this problem. The bridge server will index the blockchain and related JSON content that is stored on IPFS into a quickly queriable format to make searching and filtering results possible from DApps.

Identity

We need a centralized server that can handle tasks like issuing identity attestations and decryptying data that is returned from third-party services like Civic. We also need proxies for fetching public data from services like Facebook and Twitter which require authentication keys.

Notifications

There is currently no practical way to get email or text notifications when your bookings are made without a centralized monitoring service that can send you a text or an email to let you know about listings you care about.


Bridge Environments

You can connect to and use our hosted Bridge Server at bridge.originprotocol.com. The develop branch of this repo is available at dev.bridge.originprotocol.com.

So, what will you do with the bridge server? Let us know in our engineering channel on discord!