Originally, blockchain was conceived as the underlying technology for Bitcoin by Satoshi Nakamoto (an alias for the unknown inventor(s)?) in October 2008. This was not the first time; however, the idea of cryptographically securing a chain of data blocks had been described. There were multiple publications throughout the 1990s by several authors, sometimes in parallel. In the late 1990s and at beginning of 2000, the first publications arose which talked about a decentralized digital currency and a theory of cryptographically secured chains. Two important names generally acknowledged for inventing the intellectual precursors of the technology are Wei Dai and Nick Szabo.

It wasn't until 2008, however, when these concepts resulted in the creation of the first blockchain. It was accomplished in the publication of the white paper Bitcoin: A Peer-to-Peer Electronics Cash System, by Satoshi Nakamoto, which can still be obtained at http://www.bitcoin.org/bitcoin.pdf. This white paper describes the concept behind the underlying technology that eventually became the blockchain.

Just three months after the publication of the white paper, the code for Bitcoin was released in a freely available, open source format, on January 9, 2009.

The Bitcoin network itself started on January 3, 2009, when Satoshi Nakamoto used the code to "mine" the first Bitcoins. A few days later, the first transaction took place. In the months that followed, the Bitcoin network gained more and more attention and membership, which led to the first official currency rate on October 5, 2009. At that time, one Bitcoin (or BTC) was worth about $ 0.76 (USD), which was based on an equation that included the electricity cost that a computer node required to generate a Bitcoin. At the time of this writing, June 7, 2018, a Bitcoin is worth about 7,693.50 USD, but its all time high has been 19,783.06 USD. Finally, on February 6, 2010, individuals could buy and sell bitcoins using the newly established dollar currency exchange. In that same year, the market cap exceeded $1 M USD because of increased member participation, and within three years' time, the market cap surpassed $ 1B USD. A more detailed history can be found at http://www.historyofbitcoin.org.

The timeline of the history of Bitcoin and blockchain

Remember, this book is not solely about Bitcoins, but rather about the technology behind it. If we fast forward in time, we will see the rise of many alternative blockchain-based currencies. Because the Bitcoin core code is open source, any knowledgeable individual can start a new coin by changing this code. Thus, you can understand why there are a number of alternative coins, but the one that stands out is Litecoin (https://litecoin.org).

Litecoin is one of the initial cryptocurrencies that followed Bitcoin and was introduced on October 7, 2011. It also is open sourced. It is a fork of the Bitcoin core code, meaning an alteration of the current code (or protocol) to change the rules–released by Charlie Lee, a former Google employee. Litecoin can be viewed as the silver to Bitcoin's gold, as the overall volume is higher and the price is lower. Litecoin is primarily distinguished from Bitcoin by a decreased block generation time (2.5 instead of 10 minutes), an increased maximum number of coins, and a different hashing algorithm. Don't worry if you do not understand these concepts yet, because I will touch on all of them in the upcoming chapters.

Some other honorable mentions include Dash, Zcash, and Ripple. Dash (https://dash.org) defined itself as being the more secretive version of Bitcoin, as it offers greater anonymity by making transactions through its decentralized network almost untraceable. Zcash (z.cash), on the other hand, claims to provide security and/or privacy based on the selective transparency of transactions by making such details as sender, recipient, and amount, private. All of these cryptocurrencies are adaptations of the original Bitcoin core code, or they take the concepts behind this code and create something totally new. Ripple (https://ripple.com), technically a public blockchain, stands out the most as it specifically focuses on banks. It is an interesting example, as though it is a publicly based platform, it is privately controlled through central ownership and the code is closed sourced. This enables banks to settle cross-border payments in real time and at a lower cost.

Once again, we will move forward in time to the year 2015. Starting then, several start-ups appeared that researched the use of the blockchain for very different purposes. One of the most well-known is Ethereum, which is an open source, public blockchain-based platform for distributed computing. One of the distinguishing features of Ethereum are smart contracts. A smart contract is a (scripting) functionality designed to facilitate contractual agreements using a Turing-complete virtual machine. This means that it has conditional branching (for example, "if" and "goto" statements, or a "branch if zero" instruction). Because Ethereum is still a public blockchain, it provides its own cryptocurrency called "Ether" to compensate participants who help perform computations on the platform. In Chapter 5, Blockchain 101 - Security, Privacy, and Smart Contracts, we will go through these agreements in great detail.

Some of the well-known cryptocurrencies and platforms based on blockchain code

Up until this point, I have only discussed public blockchains. After 2015, this changed, as numerous software was made publicly available to run your own private blockchain network. Public blockchains, such as Bitcoin and Ethereum, are terrible when it comes to exchanging information because of the high transaction cost. Private blockchains were introduced to solve the problems related to these costs. Moreover, they are designed to provide more privacy and openness by managing the blockchain user permissions.

There are a couple of private blockchains, some are cloud-based while others run on-premises. There are companies, such as Deloitte's Rubix and Eris Industries' Monax, which sell turnkey solutions for private blockchains directly to businesses. Monax, for example, offers out-of-the-box SDKs for the Finance, Insurance, and Logistics industries. Other companies, such as Microsoft and IBM, offer Blockchain as a Service (BaaS) on their own cloud infrastructure. Both run Hyperledger Fabric (hyperledger.org). Microsoft runs Ethereum as well. Microsoft also offers private blockchain nodes packaged as Azure Quickstart Templates (azure.microsoft.com/en-us/resources/templates/?term=blockchain).

Since 2016, the number of vendors that provide open source software to run your own private blockchain has increased. One that is already mentioned is Hyperledger Fabric. It is part of the umbrella project Hyperledger, which was originally started by the Linux Foundation in early 2016. The project offers multiple open source blockchains and tools from different contributors, each providing different mechanisms and features. The available tools include a composer (package management) and an explorer (analytics). Blockchains within Hyperledger Fabric are built to run on Linux, but they can also run on macOS and Windows, using Docker (docker.com).

A strong competitor of Hyperledger is MultiChain (multichain.com). MultiChain goes the desktop route, deploying a private blockchain on a desktop, even in a Windows environment. It is also open source and allows rapid design, deployment, and operation of private blockchains according to your custom specification. With MultiChain, it is possible to create multiple types of data streams including key-value or identity databases.

For the implementation of our blockchain, we will look more closely at two private blockchains in Chapter 8, Ethereum Versus Hyperledger, and what makes them different from each other.

Major companies such as Visa, Capital One, NASDAQ, and Philips are now investing in the various available blockchain platforms and implementing them in their daily businesses. The following figure shows the highlights in the history of blockchain:

The book's goal is to illustrate the capabilities of the blockchain and show how these can be applied across the Oracle Red Stack. The book will introduce concepts and technologies that will allow you to implement your own blockchain in an Oracle environment. It will not go into the technical details of implementing and setting up your own private blockchain, but it will touch upon the basics. The book also covers five major industries, and it will provide examples of how the blockchain is used for projects in these industries. It will also help guide you as to where more information can be found, as a single volume can't possibly cover every aspect of the technology behind blockchain.

The book has been divided into four parts as follows:

The following is a more detailed explanation of each chapter in each of these parts.

The approach I have adopted in this book is worth explaining. If you read the section about the target audience, you’ll note that I'm not only aiming at the developer community, but at a wider customer audience that uses Oracle. To help me do this, I have set up some parameters to help you understand why things have been done a particular way. Note the following:

This book seeks to support a broad range of readers, from line-of-business managers to software architects and developers. The first two chapters are especially useful for individuals who want to know what might be the effects of the blockchain on their business. Besides the high-level overview at the start, the book covers technical aspects of the blockchain such as the building blocks of a typical blockchain network.

Together, we will explore the impact of adding a blockchain to your current IT architecture. Finally, this book is intended for developers, and I will go through the process of setting up and running your own blockchain on the Oracle Autonomous Cloud Service and extend by connecting to an on-premises blockchain network. The implementation part is mostly done on the cloud service available on the Oracle Cloud, but the smart contract we develop can be deployed on any Hyperledger Fabric blockchain network.

For most parts of the book, you don't need anything beyond what is mentioned in this section. It goes through all of the things that you'll need to implement a blockchain yourself. I have taken the approach of using free services and tools wherever possible. I will explain in greater detail the different tools and services throughout the book, but let's start by introducing what is needed at minimum:

func main() {
  err := shim.Start(new(InsuranceChaincode))
  if err != nil {
    fmt.Printf("Error starting chaincode - %s", err)
  }
}

[default]
exten => s,1,Dial(Zap/1|30)
exten => s,2,Voicemail(u100)

exten => s,102,Voicemail(b100)
exten => i,1,Voicemail(s0)

$> curl -sSL https://goo.gl/6wtTN5 | bash -s 1.1.0
$> sudo dpkg -i ~/Downloads/code_*.deb; sudo apt -f install -y

Feedback from our readers is always welcome.

General feedback: If you have questions about any aspect of this book, mention the book title in the subject of your message and email us at [email protected].

Errata: Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you have found a mistake in this book, we would be grateful if you would report this to us. Please visit www.packt.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details.

Piracy: If you come across any illegal copies of our works in any form on the Internet, we would be grateful if you would provide us with the location address or website name. Please contact us at [email protected] with a link to the material.

If you are interested in becoming an author: If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, please visit authors.packtpub.com.