edgecase
To be entirely just in our estimate of other ages is not difficult - it is impossible. Even what is passing in our presence we see but through a glass darkly. The mind as well as the eye adds something of its own, before an image, even of the clearest object, can be painted upon it.
~ J A Froude
Author: StJohn Piano
Published: 2019-04-21
Datafeed Article 104
This article has been digitally signed by Edgecase Datafeed.
This article has been digitally signed by its author.
786 words - 136 lines - 4 pages





Blockchain is a powerful new technology. It can be used to tackle several difficult problems:

1) Distributed data storage and synchronisation

2) Auditable data history

3) Transaction authentication


Various solutions to these problems are already in use, but blockchain weaves these solutions into a single tool.


There is another problem, a very difficult one:

4) Data synchronisation between untrusted counterparties [0]


Usually, problem 4 is solved by some aspect of the physical universe that humans are unable to ignore. Examples: Gold bars (we agree that gold is valuable because it is scarce and hard to counterfeit), physical force (we agree to pay you tribute because your army is much larger than ours).


The first blockchain, Bitcoin, solves all four of these problems at the same time. Problem 4 is solved very expensively via the enormous expenditure of computer processing power. The result of solving these problems is that the Bitcoin blockchain allows its users to have a distributed, synchronised, auditable, authenticated, and trustless record of ownership of bitcoin amounts.


Bitcoin is a public blockchain. Anyone can join it (add processing power to the network) and use it (create transactions that alter its data).


The normal existing solutions to problems 1-3 are:
- For problem 1: Backup systems that regularly copy data from a database and store it in one or more secondary databases. Hashes or hash trees are used to check synchronisation. Examples: Archive all the code files in a software project and transfer the archive to another system. Dump the contents of a PostgreSQL database to a file and transfer the file to another system.
- For problem 2: Patch systems, where data is never deleted, but only altered by applying patches to the existing data in a linear sequence. The entire history of the data can be replayed from the beginning. Examples: Git version control, continuous archival of PostgreSQL write-ahead logs.
- For problem 3: An authentication system, in which transactions (i.e. changes to the data) are linked to an identity. Examples: Digital signatures (signing the transaction with public-key cryptography), username + password access to a remote system on which the transaction is created. Note that username + password access to Internet-connected systems functions on top of a digital signature system.


Some organisations may want to operate private blockchains. These can be used to solve any combination of problems 1-3, or all of them together.


A private blockchain could be useful when:
- The organisation needs to store and manage important data.
- The organisation is large - not all of its agents know each personally.
- The organisation has multiple branches that need to have a single consistent data record so that they can cooperate effectively.
- The history of a particular datum must be completely replayable from the beginning.
- For any change to the data, it is necessary to know which agent within the organisation made it.


The organisation will need to operate a web of trust, in order to track the identities of the organisation's agents, to control their ability to add new transactions to the blockchain, and to audit their decisions.


The blockchain design could vary somewhat, depending on the application. In some cases, it may only be necessary to store a year's history for data, rather than the entire history.


If the application produces a lot of data very rapidly, this is not a good candidate for a private blockchain. A blockchain-based solution generally be slower and more resource-intensive than a standard solution.


A further consideration is the permissions system that will control access to the data on the private blockchain. There may be some transparency advantage from allowing anyone on the Internet to view the data, but this can be expensive.


Example situations in which a private blockchain could be the right solution:
- Tracking shipping containers as they move between ships, ports, and countries. A port agent would create a transaction that stated that a particular container had arrived in that port.
- A land registry. The blockchain would be an updateable record of who owned which property.
- A contract archive. It might be useful for all legal firms within a particular jurisdiction to use a single distributed record of important contracts.










[start of footnotes]


[0]
People often say that Bitcoin permits agreement between "unknown" counterparties, but this is only because people are used to thinking of human faces, names, voices, etc as identities. In the Bitcoin world, public keys are identities, and these are in fact known. When someone adds a new transaction to the blockchain, the public key with which they make the signature is included. This must be so, else other parties could not verify the signature. So, in Bitcoin, counterparties are known, but not necessarily trusted.

[return to main text]

[end of footnotes]