Book Image

Hands-On Blockchain with Hyperledger

By : Nitin Gaur, Luc Desrosiers, Venkatraman Ramakrishna, Petr Novotny, Salman A. Baset, Anthony O'Dowd
Book Image

Hands-On Blockchain with Hyperledger

By: Nitin Gaur, Luc Desrosiers, Venkatraman Ramakrishna, Petr Novotny, Salman A. Baset, Anthony O'Dowd

Overview of this book

Blockchain and Hyperledger technologies are hot topics today. Hyperledger Fabric and Hyperledger Composer are open source projects that help organizations create private, permissioned blockchain networks. These find application in finance, banking, supply chain, and IoT among several other sectors. This book will be an easy reference to explore and build blockchain networks using Hyperledger technologies. The book starts by outlining the evolution of blockchain, including an overview of relevant blockchain technologies. You will learn how to configure Hyperledger Fabric and become familiar with its architectural components. Using these components, you will learn to build private blockchain networks, along with the applications that connect to them. Starting from principles first, you’ll learn to design and launch a network, implement smart contracts in chaincode and much more. By the end of this book, you will be able to build and deploy your own decentralized applications, handling the key pain points encountered in the blockchain life cycle.
Table of Contents (20 chapters)
Title Page
Copyright and Credits
Packt Upsell

A model of the business network

Now that we've understood the types in the business network in natural language, let's see how they are defined technically. On the left-hand side of the Playground, select Model File.

 In this business network, there is only one model file that defines the participants, assets, transactions, and events. In a bigger application, we'd keep the information from different organizations in their own files, and often in their own namespace. It allows them to be kept separate but brought together when necessary. Let's see how namespaces work.


Our example uses a single namespace:

namespace org.acme.loc

This namespaces says that the type definitions in this file have been defined by the Acme organization's letter of credit process. All this is a short name! Use namespaces–they'll help you clearly separate, and more importantly, communicate, your ideas. It is recommended to use a hierarchical name so that it's clear which organizations in the network are defining...