In order to ensure further security, the
bluzelle network makes use of Proof Of Stake (POS) consensus mechanism where
nodes stake the bluzelle native token(BNT) and receive network fees in form of BNT as an incentive for maintaining the
network.(for a step by step description on how to stake on the bluzelle
platform,read my other article here). However,
the entire network nodes do not need to reach a consensus before data can be
retrieved because there is no single state on the network, rather the consensus
model is applied on a swarming level ensuring that the swarms of node storing
data each reach a localized consensus using the custom bluzelle proof algorithms.
In addition
to the above, the bluzelle platform created an incentive-disincentive system called
the karma index. The karma index is a score that describes how well behave a
producer is. A producer is a client that is allowed to own and run one or more
nodes. A producer’s karmic index increases or decreases in relation to the
performance of the producer. For example, when one node out of the multiple
nodes run by a producer performs poorly or well, the producer’s karmic index
reduces overboard and vice versa, then the producer will need to increase or
decrease his stake of the bluzelle native token accordingly. The amount of BNT
a producer is expected to stake is directly proportional to the number of nodes
the producer runs and indirectly proportional to his karmic index. The wisdom
behind the karma strategy is to keep the network safe, secure, maintained as
well as improve performance through economic incentive.
More so,
to prevent Sybil attacks which arises
from the freedom of adding nodes to the network which can allow a malicious
syndicate of hackers to potentially add so many nodes to the network thereby
hijacking the network and staging a 51% attack on the network. The strategy
adopted by bitcoin and ethereum against Sybil attack is making the addition of
a new node to the network highly expensive through Proof Of Work (POW) so that
a body trying to stage such attack will find it unprofitable because it will
need to pay expensively for power as well as for powerful processors.
Bluzelle
prevent Sybil attack with the adoption of Proof Of Stake (POS) consensus where
nodes put up their BNT stake to participate in the network. This stake is a
participation fee as well an economic disincentive from bad behavior as bad
actors are economically penalized, blacklisted and removed from the network.
The karmic index is another veritable tool for this purpose. More so, nodes
that mislead the swarm location effort will be systematically tracked down
through the kademila distributed hash table redundancy method. When a CRUD
request to a swarm is made, all nodes in that swarm perform the request. The
node swarm membership rules make it statistically impossible that multiple
nodes collude to game the system and yet deliver consistent data because nodes
are linked to swarm by the network but nodes do not choose the swarm they want
to link to. This makes it impossible for a Sybil attacker to control majority
of nodes within a swarm.
Lastly, in
order to prevent the byzantine general’s fault which is a situation where one
or some part of a computing network component (nodes) fail(s) or when there
exist information asymmetry as to the faulty component within a computer
network. Bluzelle’s default action hence its strategy is that whenever there
exist corrupted, inconsistent and misleading data, such data set are not added into
the system of any node, hence the database. Also, the redundancy in CRUD
request aforementioned, help catch inconsistency whether intentional or otherwise,
and the system only need to ignore such data.
This is the byzantine general’s fault algorithm adopted by
bluzelle to make the system byzantine fault tolerant.
The above is a simplification of the technology of bluzelle
which allows the project to earn the award of
Technology Pioneer from the World Economic Forum and why it is a
blockchain project to be watched out for in 2020 and beyond.
If you have not read
the part 1 of this write up, click here
Comments
Post a Comment