Slashing Shards

The windows in the front were broken, black elliptical objects rolling toward us and making the scream of the wind shouting - the room was full of smelling fog. "Low!" I said. My reaction is to those who have been fighting, but no matter how unfamiliar we know we need to leave. Nothing will happen. The old man quickly picked up a silk scarf that looked like a hand from the back of the counter and marched over the object. He moved us to use his head behind him, and never turned his eyes off the ones on the floor, the floor began to spin slowly.

Please gently touch the broken slash and debris stretching along your chin so that you can calculate the burning time. A fiercely enthusiastic shine on my fingertips, I felt my thought was uncontrollable and moved my fingers one by one. When I drag the other side of my chin, the flame keeps itching and the patterns and patterns are rubbed into my skin. Scars, scars. I need to pay attention as the temporary slim feel of rusty lines is decorated to tell a mystery to my skin. As they whispered to my ear, I clasped their story and made them closer to their story, this is something I would not want to hear. There is something better not to say.

In Hashgraph, each piece is independent and has the shared state of all the contents (message, storage, status of each account / balance) that you know. When a transaction occurs between clients of different fragments, after the first invocation fragment reaches an internal agreement, it passes the entire shared state along with the encrypted evidence to the second fragment. In addition to the state itself, the message also includes a (block) address book chain, each address book containing the public key of all the tile members, each address book being hashed by members of the previous address book. This creates an address book history chain up to the signature (origin) of the first address book, so the node will not lie to the shared state of that fragment. The first signature is also the name of the ledger (ledger ID).

Please take a quick look at Part 1 of network fragmentation. In the last article, I proposed the concept of network fragmentation. Due to network segmentation, Zilliqa divides the mining network into small groups called slices, respectively. Each fragment can process transactions in parallel, resulting in high throughput. For security reasons, fragments must be large enough (eg over 600 nodes). Zilliqa performs network fragmentation using PoW. Alert readers may notice that the above fragment size is much smaller than regular block chain P2P networks such as Bitcoin and Ethernet where the network consists of tens of thousands of nodes. So why can Zilliqa use the same consensus protocol (like Bitcoin / Ethernet) and do it on each fragment? In addition, aggregation among fragment members can be reached quickly, since fragment size is much smaller than regular networks.