Discussion

In chapter 2, the author describes Hyperledger Fabric and its components. Create a new thread, choose one of the Hyperledger design principles described in chapter 2, and explain why your chosen design principle is important to a successfully enterprise blockchain implementation. I’m interested to read what YOU learned from this week’s reading. Do NOT submit a research paper. Tell me what you think.

Then think of three questions you’d like to ask other students and add these to the end of your thread. The questions should be taken from material you read in Chapter 1 or 2. You’re not trying to test each other, but you are trying to start a discussion.

Finally, go to three other students’ threads and post comments, answering at least one of their questions.

You must do the following:

1) Create a new thread. As indicated above, choose one of the Hyperledger design principles described in chapter 2, and explain why your chosen design principle is important to a successfully enterprise blockchain implementation. Then think of three questions you’d like to ask other students and add these to the end of your thread. The questions should be taken from material you read in Chapter 1 or 2. You’re not trying to test each other, but you are trying to start a discussion.

2) Select AT LEAST 3 other students’ threads and post substantive comments on those threads. Your comments should answer AT LEAST one of the questions posed in the thread and extend the conversation started with that thread. Make sure that you include the question in your comment so I can see what question you’re answering.

ALL original posts and comments must be substantive AND ORIGINAL. (I’m looking for about a paragraph – not just a short answer.) Do not plagiarize!! Use your own words.

Professor Michael Solomon

BLCN 532
Blockchain development

Chapter 2

Chapter 2

• Exploring

Hyperledger

Fabric

• Frameworks, tools, and
building blocks

• Component design

• Sample transaction lifecycle

• Governance in business
networks

Fundamentals
of the

Hyperledger
Project

• Open source technology
development

The Linux Foundation

• Open source project
• Purpose is to advance cross-

industry blockchain

Hyperledger

Open
Source /

Open
Standards

Lower cost of software
consumption

Innovation and extensibility

Sustainable development and
innovation stream

Security and reliability

Speeds up development and
market adoption

Hyperledger Frameworks

Iroha – mobile
development projects

Sawtooth – focus is
versatility, includes a new
consensus algorithm
(Proof of Elapsed Time)

Burrow – meets the
Ethereum Virtual
Machine (EVM)
specification

Fabric – general
blockchain foundation

Indy – support for
independent identites

Frameworks
and Tools

Hyperledger
Tools

Explorer – view blockchain data

Cello – implements a blockchain
service

Composer – collaboration tools for
blockchain development

Quilt – integration protocol

Caliper – blockchain benchmark
tool

Blockchain building blocks

Hyperledger Fabric Components

Principles of
Hyperledger

Design

MODULAR AND
EXTENSIBLE
APPROACH

INTEROPERABILITY FOCUS ON SECURE
SOLUTIONS

TOKEN AGNOSTIC
APPROACH

FOCUS ON RICH
AND EASY-TO-USE

APIS

Hyperledger Fabric Reference Architecture

Hyperledger Fabric Runtime Architecture

Advantages
of

component-
based
design

Separates development design from
runtime

Discerning between design imperatives
and deployment capabilities

Incorporates network design principles

Addresses channel design principles

Adopts Hyperledger Fabric composer
model-driven development

Journey of a Sample Transaction

Hyperledger Fabric Actors

Developer Interaction

Governance

Body that establishes rules

Blockchain governance is
distributed

• Degree of distribution depends on
cooperation between nodes

Aspects of blockchain
governance

• IT governance (risk)

• Network governance

• Business network governance

Summary

• Hyperledger Fabric – modular
blockchain

• Understanding the modular
approach and main
components is important

• Transaction flow

• Endorsement

• Ordering

• Validation

• Governance is necessary to
maintain blockchain network
operation

Professor Michael Solomon

BLCN 532
Blockchain development

Chapter 1

Chapter 1

• Blockchain – Enterprise and
Industry Perspective

• Definition

• Building solutions

• Blockchain applications

• Enterprise design principles

• Business considerations

What is a
blockchain?

Immutable ledger for
recording transactions

• Distributed network

• Untrusting peers

Public blockchain
(permissionless)

• Anyone can access without first
getting permission

Private blockchain
(permissioned)

• Owner permission required
before access

Blockchain
basics

• Consensus protocol
• Proof of Work (PoW) is

popular

Public

blockchain

• Access restricted based on
identity

Private blockchain

• Mandatory execution of
programmable logic

Smart contract

Comparing blockchain to centralized

Core
building
blocks

• Shared ledger

• Cryptography

• Smart contracts

•

Trust

system

Fundamentals of secure transactions

Blockchain use cases

Good fit
for

blockchain

• Applications that:

• adhere to trade, truest, and
ownership

• fundamentally transactional
in nature

• Business networks that are
comprised of non-
monopolistic participants

Enterprise considerations

Transaction
requirements

• Ability to verifiably transfer
item of value

Trade

• Assurance of any asset’s owner
• At a point in time

Ownership

• Agreement that transactions
are valid

• Persistent integrity

Trust

Blockchain
technology

Trust system

• Consensus

• Mining

• Public ledger

Private communication on
open network

• Cryptography and encryption

Non-repudiation

• Identity and transparency

Blockchain
Business
Drivers

Consensus
models

Control and
governance

Digital asset
generation

Authority for
issuance

Security
considerations

Blockchain Design Principles

Principles
for

adoption

• How well does the solution map
to, and support, business
activities?

Business blueprint

• Does the technology provide the
utility required to run the
business?

Technology blueprint

• Does the proposed solution
integrate with legacy and
external systems?

Enterprise integration

Summary

• Adopting blockchain
technology requires balance

• Legacy processes must not
be disrupted

• May encounter additional
regulatory obstacles

• Disruption can be good, but not
always comfortable