Sharding technology faces many challenges, such as problems in cross-Shard interaction and status explosion, how does MultiVAC fix that?
BEN_MultiVAC last edited by BEN_MultiVAC
This question is more technology-orientated, for sure.
We're the first to adopt asynchronous collaboration in terms of cross-Shard collaboration. Different Shards are equivalent and parallel. Strictly speaking, our cross-Shard collaboration guarantees the eventual consistency of cross-Shard transaction by adopting the strategies of Monotonic consistent and read-your-writes. The asynchronous collaboration makes sure our Shards never block each other. The data miners exchange among Shards only are block header that is very concise and fast. Such cheap cost of cross-Shard makes efficient scale-up possible.
As for state explosion, storing state in a distributed way, we actually did it. And a system can never tamper with the data. We employ separation strategy between data storage and control. Only servers can store data, but they don't have the right to control or change the data. Miners have the absolute power to control the data, so they can check and examine the data. But it is not necessary for them to store the data. It is an interactive storage strategy.
In our storage strategy, the one who stores data is more like internet providers, such as telecom and Unicom- provide bandwidth for users (here is hard disk), but they can't control what data you transmit (or store).
The cross-Shard interaction and data storage strategy, coined by MultiVAC, have many distinct differences with others in this field. Our Sharding solution is also received many technological experts recognition. So we believe that we will bring you a great experience after our mainnet launch.