Zilliqa (ZIL) price, performance and general information

Play Now: https://luckygames.io/?ref=23473521

Safe 11x LuckyGames Strategy: https://youtu.be/AeJGKPPlOgo

A "51% Attack" occurs when the attacking side, that can be represented by a comparatively small number of miners, has a "controlling stake" of the total hash rate, that is, computing capacity. As a result of the attack, the miners gain control over the entire network and can create blocks at their discretion.

51% Attack is not a myth. Ethereum Classic / TOP-30 cryptocurrency was attacked at the beginning of January 2019. Millions were stolen, the network was frozen, price dived down... Each blockchain needs protection from a 51% attack.

Here are some original examples of realization anti-51% Attack by Komodo, Ziliqua and Credits.

Komodo

Komodo Platform’s delayed Proof of Work (dPoW) security mechanism protects chains with the power of the Bitcoin hash rate. To put it simply, the dPoW mechanism stores backups of Komodo blockchain onto the Bitcoin ledger.

An attacker would need to take down both the BTC and KMD networks before they could alter, disrupt, or destroy the backups of your blockchain. The network will not accept a version of the blockchain that doesn’t match the most recently notarized backup. Blockchain synchronization occurs every ten minutes, the window of opportunity for an attack to take place is impractically small.

Komodo is immune to a 51% attack as long as Bitcoin.

Zilliqa

Since many blockchains have gotten very close to violating the 51% assumption in the past, Zilliqa decided to go with a stronger assumption. In Zilliqa, the assumption is that less than 1/3 of the hashing power is under the control of the adversary.

If one gets to control more than 1/3 of Ziliqa, then the shard momentarily stops proposing new blocks. However, this does not mean that the protocol gets stalled forever. The reason is that there will be other shards that continue to submit blocks. If the number of victim nodes is less than 1/3, the protocol will function without any issue. If the number is higher, then the protocol will replace the affected nodes. And that will be a repeating trusted process. Zilliqa network consensus is not allowing 1 participant to own more than 1/3 of the network.

Credits
Credits use its own Credits Decision Consensus Algorithm (CDCA), which is a combination of other algorithms and it featured for mixed data validation and processing in the blockchain.

On the Credits platform, the choice of nodes is based on the Delegated Proof of Stake (DPoS) algorithm. There are rounds when DPoS mechanism selects the random list of nodes to participate in consensus. It is impossible to predict in advance which of the nodes will be selected for participation in consensus.

During each round the list of nodes changes, the frequency of the rounds is five rounds per second. These rounds are asynchronous, the new one starts to run before the previous one is completed. The asynchronous process of rounds generation leads to the situation when more than 51% of nodes can't be selected. This makes attack 51% impossible at all.

Projects mentioned here on Reddit:

Komodo - r/komodoplatform

Zilliqa - r/zilliqa

Credits - r/CreditsOfficial