Skip to content
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.
Freddy Mercurial edited this page Jan 18, 2022 · 11 revisions

Welcome to BrightChain

BrightChain is the backbone of The Revolution Network.

It is both the storage and message passing system of the entire network. It will be designed to house every byte of data for the entire world one day. The goal is to store Everything in BrightChain.

It has lower overhead than blockchain and traditional P2P delivery.

It's core is based on The Owner-Free File System principle, but additional deduplication and anonymizing/security measures are taken, expirations and revocation tokens are added, etc.

On top of the BrightChain block store, we then build an entire distributed application infrastructure with digital contracts of these subchains and doing computational work on one or more blocks and storing the resultant blocks elsewhere. One of the main focuses will be a social network and reputation system, but there will be a place for voting on matters from sitewide to local to governmental to global.

The Big Picture

Check out the wiki page, "The Big Picture"

Docker Hub

Our GitHub flows now simul-push to two docker hub orgs/repos. Although BrightChain is a subset of The Revolution Network logically, these are just mirrored namespaces for now.

Example:

Sprints

Current

  • 12/19/21 - Sprint: Sagan-Roddenberry

    • Health has severely impacted all work. I am not contributing much anywhere.
  • Stardate 99055.69 {6/16/21} - Sprint: Sagan-Roddenberry

    • Engage!
    • I am working on a time-as-available basis and my sprints are not time boxed at the moment. Ideally would be 1-2w.
    • The current sprint's goal is to complete the work already begun without ticket management in place, which is basically trying to get to a place where blocks can be stored and made available on the block api website. You can pull and inspect any block on the chain-however they're all random data or highly correlated with random data. What you need is the right assemblage order of blocks, "recipe". This can itself be contained in a public block for public data, thus reducing your url down to a single request id. However, you can keep that final "recipe" to yourself. The data will all be out there, and kept for at least as long as you requested it.

Past

  • As of 6/16/21 - work was not being tracked and is probably still going to be spotty :)

Future (vaguely) Projected Milestones

  • Milestone 1: BrightChain block store / BCFS online with no costing implemented.
  • Milestone 2: authentication/login/account management, etc
  • Milestone 3: energy tracking/costing and possibly reputation maths
  • Milestone 4: brightchain vm / digital contracts