The reason a private blockchain cannot work stems directly from that statement. It is not the fact that there is a chain of hashes that secures the chain, it is the fact that there are hashes that are
public.
The
SPV chain allows people external to the miners to maintain a list of attestations. They can do this without having the full file. In collapsing the
Merkel tree to a single hash value, you can encapsulate the entire stream of transactions in a single hash. In this, any alterations may be detected. Where you do not have a public chain, it is simple to run multiple chains simultaneously and thus to be able to do the Enron or Bernie Madoff scam. That is, an organisation could simply and easily run multiple sets of books.
----
The reason
section 3 of the Whitepaper states that bitcoin is a timestamp server is that a hash has to be publicly validated by multiple parties at a point in time to be part of a security protocol.
_The solution we propose begins with a timestamp server. A
timestamp server works by taking a hash of a block of items to be timestamped and widely publishing the hash, such as in a newspaper or Usenet post [2-5]._
It is for this reason that the bitcoin White Paper states the nature of proof:
_The timestamp proves that the data must have existed at the time, obviously, in order to get into the hash. Each timestamp includes the previous timestamp in its hash, forming a chain, with each additional timestamp reinforcing the ones before it._
Without some form of public attestation, without the hash being publicly recorded, there is no security. The solving of a proof of work puzzle is not what secures the network. As stated, this can provide no security on its own. There is no way to market the value of the token unless it is traded in a public system and openly. Without such a value, any party can set up a system that appears to be valid at face value and yet runs multiple copies with every possible history. This is why system such as hyper ledger and any other private blockchain are incredibly foolish. They are less secure than a native Oracle database with write controls enabled.
The peer network and bitcoin is designed to distribute the block hashes widely. Every single SPV user would have a copy and the base for the
timestamp server would become universalised. Unlike multiple chains,
a single source of truth could then evolve. In this, it becomes possible to set up protocols that linked to identity that would ensure a single sub- chain of private transactions that could be provably linked to an original start point or Genesis foundational point that would be associated with private transactional data.
It is not the nodes fighting to gain distributed hash rate but rather the mere fact that the hash exist publicly an action may be taken on that hash. The
public nature of the hash is what makes it possible to use it as an
attested value. Hash cannot guarantee something existed at a point in time. A hash that is publicly displayed and that can be widely attested by people, not computers, in a court of law is secure. The failing people managed to avoid is that
bitcoin is designed around legal evidential principles requiring humans and not machines. Machines store the data, humans make an attestation that they had the copy and that they can prove that it existed at a time
Bitcoin in this manner acts in a methodology and knowledges to publishing a statement in a newspaper. Where copies of that newspaper are widely distributed, stored on microfiche, held by people in a manner that is provable, the copy in that physical paper may be used in an evidential basis. Likewise, the publication of hash that can be collapsed through the hash of a hash allows the ordering and chronological time stamping of an event to occur.
This is how bitcoin sold the double spending problem. The first hash in chronological order is correct. Any further double spends are rejected......"
CSW
Nov 14, 2019
https://metanet-icu.slack.com/archives/C5131HKFX/p1573721687274800?thread_ts=1573721307.272200&cid=C5131HKFX