An attacker could spam the network with fake proofs and overload the system. This is combated by forcing nodes to hold large amounts of data. One would need a lot of computing power to spam the network.


Spam

An attacker could also attempt to erase part of the data on the network. This is combated by the multi-faceted proof system and random selection of nodes. 


Partial Erasure

If an attacker were to know the randomly selected bytes, they could delete the bytes that are not going to be checked. They could also inject transactions at the end of the block to steal from the network. This is combated by the use of cryptographic hashes. A created hash would differ from the others.


Collusion with PoH Generator

An attacker could overwhelm the system by creating too much work for the CPUs and GPUs to process. This would make it difficult to serve the network as not all transactions would be processed.

Denial of service

Spam

Partial Erasure

Collusion with PoH Generator

Denial of service

University of Michigan - Ann Arbor

The proof of history generator publishes a hash to be used for encryption and selecting the random bytes. The hashes are published periodically and depend on the encryption time.

Hash Selection on Solana

Solana - A new architecture for a high performance blockchain

The PoH generator only keeps track of the number of replication proofs. A super majority of validators on the network are to validate the proof of replication findings. A single packet of all verifications is sent to the network. The packet then verifies all the proofs using a specific hash generated by the PoH generator. 


Learn Before

Related

Learn After