MOAC - The Multi-layer blockchain architecture for commercial application.
A brief look into blockchain Sharding.
In today's blockchain ecosystem there seems to be one single issue across projects, and that is blockchain bloating and transaction speed. For instance there was a recent attack on the Ethereum blockchain that increased the transactions fees for everyone on the chain by simply spam submitting high-gas fee transactions on a smart contract moving around tokens that were worth nothing. Further back, there was also the CryptoKitties incident that saw the price of a single transaction on the ETH blockchain rise to close to $20. These and numerous other incidents ($50 transactions on Bitcoins at Christmas 2017 during the massive bull-run) prove that there needs to be a solution that not only lowers the cost of fees for normal users on the chain, but also means that performance will not be hit if a DAPP running on the blockchain goes viral.
This is where the process known as 'Sharding' comes into play. Essentially, sharding involves dividing all of the nodes on the blockchain into multiple different subgroups, these subgroups then work independently, executing processing tasks that would have otherwise been completed by the mainchain, this means that it frees up resources to ensure that a steady TPS (Transaction-per-second) speed is kept, and that end users will not see any significant hits to the network if a single DAPP is using alot of processing power and resources.
However, MOAC isn't simply relying on sharding to keep things moving, at the base layer the chain will also have PoW mining. This ensures that the data is consistent and validated by multiple sources simultaneously. At the base layer of MOAC, it's split into two different types on nodes. 'V-nodes' and 'SCS nodes'. SCS nodes are the ones that are responsible for the sharding aspect of the blockchain, each one will be in constant communication with a V-node, this ensures that the SCS nodes can obtain globally consistent information, and ensure that the tasks they are processing are in fact correct and not taken by another subgroup of the SCS nodes.
Each of the SCS nodes has a number of features that they use to assist the mainchain.
Each and every SCS node has it's own memory, which is used for processing.
SCS nodes can be integrated with a consensus mode such as POS or PBFT.
The block generation time for SCS nodes can vary from that at the lower level (PoW mining), this means that the processing rate can be further improved by a rapid block cycle.
SCS nodes periodically flush the result to the lower level to achieve the stated global consistency, this means that the PoW miners and the SCS nodes will be at a constant state of sync, ensuring high
Unlike with other sharding methods such as that of ETH, MOAC will be different as it is primarily adopting a contract-driven mode of sharding. This means that a contract will correspond to a system shard, so when a contract is created, the corresponding quantity of nodes will be randomly selected from the pool of available nodes to form together into a subgroup that will execute this contract. The contract length can be deemed in the shard, and once a node has finished it's work on an existing contract, it will be assigned back to the pool of available nodes, ready to be picked up and utilised in additional sharding subgroups later on down the road.
This can be seen below in the MOAC sharding flow diagram below:
I hope you enjoyed this brief look into the MOAC teams sharding, and how it is going to vary from that of other projects. It looks like it's going to be an exciting time to be a part of the MOAC community.
Social media channels
For more information and to access the whitepaper, checkout their website here: https://moac.io/
Or if you would like to follow their various social media channels, you find them below:
Twitter: https://twitter.com/moac_io
Telegram: https://t.me/moacblockchain
Medium: https://medium.com/@moac_io
Reddit: https://www.reddit.com/r/MOAC/
Facebook: https://www.facebook.com/moacchain/
