The knowledge of segmented chain depends on the main chain;
The existing backbone will modify its underlying protocol when it is implemented, and it needs hard bifurcation.
Side chain, state channel
The state channel is a technology, the core idea of which is to allow the execution of off-chain transactions, and only need to record the state of the channel when it is opened and closed on the blockchain. At the same time, what happens in a state channel still maintains very high security and finality; If there is any problem, you can still choose to go back to the main chain.
For example, if A wants to transfer 1000 small BTCs to B, its working mode is probably: first, open a payment channel between A and B, and record the opening of the channel on the blockchain. Through this payment channel, you can keep it open at any time, for days, weeks, and ten years, and then make a transaction of 1000.
When A and B want to close the channel, they only need to write the final state of the transaction generated on the channel on the blockchain. This technology has existed for several years. Last year, the side chain technology was realized on Bitcoin through Lightning Net.
Subchain
When it comes to sub-chains, the first topic that can't be avoided is MOAC chain, which is the abbreviation of the mother of ten thousand chains. Chinese translation means "the mother of ten thousand chains" or "Nuwa chain". This is the third generation public chain whose main network has been online. It is the first to break through the current industrial problems such as asynchronous contract calling, contract fragmentation processing and global cross-chain, and the contract processing speed far exceeds the current intelligent contract platforms such as Ethereum.
The appearance of sub-chain is a revolutionary change. If we consider the ecology of MOAC, which is like a GitHub for development, then the sub-chains can become a function library, so that the sub-chains can share with each other. And various sub-chains that provide services, because of different services, must have role segmentation. For example, provide a sub-chain of IPF, focusing on storage; Provide the sub-chain of zksnarks, focusing on the operation speed. So, how to use scs with the same configuration to support different sub-chains? How can you do different things with the same * * * algorithm and the same block speed? So you need professional people to do professional things, then the sub-chain can be defined and created according to your different needs.
Of course, sub-chains and side chains are very different. On the one hand, the side chain is designed for micro-transfer, and it cannot provide the function library of ink chain and the function of mutual call. On the other hand, the side chain can be directly defeated, but the parent chain must be attacked instead of the child chain. Double flowers will definitely not appear, because the parent chain solves global consistency here, mainly because the scale of the underlying vnode is limited by the mining profit of the currency price, but the scale of scs can be infinitely expanded under the promotion of application. Mok MOAC is to solve the dispute between V God and BM, maintain the security of decentralization and improve the scalability.
In fact, Mok is a supplement to Ethereum and is compatible with Ethereum. In the debate between V God and BM, V God is right to criticize EOS for being too centralized, and BM is right to criticize Ethereum for its lack of expansion ability. It is also the right choice for V God to seek slicing to solve the problem. Mo Ke, in fact, has achieved what V God wanted to do for several years but failed to do (of course, there are more innovations), which proves that the scalability problem can be solved without sacrificing decentralization. I hope all the forces of Ethereum, especially ConsenSys, will cooperate with the writers.