-
Notifications
You must be signed in to change notification settings - Fork 1
old Quarum
While the entire network is decentralized, there is a segmented unit of central authority called The Quorum.
At its core, it uses generation of a computed amount of Forward Error Correction pre-generated, set aside, and broken up into shards so that only once a majority of the desired/precomputed percentage is acquired, the data can be reconstructed.
If you're familiar with the DNS root registry, essentially a handful of different companies and organizations all run root servers. In The Revolution Network, there will be a central, non-profit legal body and effective board of directors responsible for the data integrity of the network.
Almost everything that will pass over the network will be contained in the bright block store. However, The Quorum has a unique role.
Let's say that User Mallory wants to go run amok on the network and post terrible or illegal things. She is entitled to do so. Free speech is what it is. However, certain things like yelling Fire in a crowded place you can't say. Moreover people just don't like some things. We need a mechanism to be able to let people say things anonymously and yet be able to hold them to account if they've ultimately run afoul of the network code of conduct and/or the law.
When Mallory joined the network, she may have registered aliases she's allowed to use (unique). User Mallory wants to post anonymously. She can either use a registered identity with the system that maps back to her original account (think of these like alias accounts), or she can just erase her identity data. Although the post will show the registered identity, no one not in the Quorum will be able to know those aliases. This is essentially part of the user database. The map of user aliases is stored encrypted in the block store and only Quorum members will have the knowledge of the magnet links to identities.
In TCP/IP, we break data down into packets. Any post on the network ultimately has a header a bit like a TCP/IP header. It has a source and a destination. We will use a technique called Forward Error Correction in order to do a little trick. Normally when you post, the section for your user ID must exactly match the user ID/key you authenticated with or The Revolution Network will allow you to enter one of your registered aliases (simple map) or even erase the ID entirely, but not before generating a chunk of error correction data data that gets stuck on the end which contains enough duplicate data to reconstruct errors in the source information. We generate the checksum with the actual entity/key ID of the user doing the post, before manipulating it to an alias ID or empty. The server accepting the message must inspect the message, ensure the identity is registered to the key or be anonymous and that the user is still entitled to use the network in that capacity. The message is accepted and the forward error correction data is split up into equal pieces amongst the Quorum Members.
The Quorum is a sharded authority. Nothing can be accomplished without a majority vote.
The Quorum is effectively a world government. Each shard keeper must then break that shard up according to their bylaws and then safeguard all that data as the independence of the network depends on keeping the governing bodies nonpartisan and able to make informed decisions together. Together. For those in the back: TOGETHER. With majority votes. Digital contracts on shards.
Lets say Mallory's virus or bad content goes in the network a while and is reported or a FISA warrant is issued. At this point, the Quorum must take a vote whether to turn over the identity according to the bylaws, rules of the countries involved, etc. If the answer is Yea, then the Quorum member provides their chunk of the sharded data. Without a majority of Quorum members, the identity can not be reconstructed.
At some point the FEC data on the posts could even be expired and deleted. It might be stored separately so this can happen. Once the "statute of limitations expires" that data could be deleted and the original identity never recovered.
This section has now provided a means to Identify, Authenticate and Moderate users in the network.
Next we get into the Reputation system, and ultimately how your Reputation is your Valuation.
TOC | Intro | 1 - Arch | 2 - Auth | 3 - Quorum | 4 - Identity/Reputation | 5 - Contracts/Crypto
Documentation updated regularly. You can pull the revision history if you check out the wiki's git repo.
Please consider joining. Doesn't matter if you're new to coding or crypto. I/We can help! Devel & Collab