►
From YouTube: Exploring the Relationships Between a Blockchain Reference Architecture, Design Patterns and ...
Description
... Governance
Mohan Venkatamaran & Isaac Kunkel, Chainyard
This session will review a blockchain reference architecture that has been developed based on experience with Hyperledger Fabric. The presentation will first provide an overview of the reference model noting blockchain specific elements. It will then identify several specific technical and business patterns that are supported by the reference architecture. It will finish up by demonstrating how this blockchain specific reference architecture takes a holistic perspective of the solution, including both technical and business governance, for consideration during the design phase.
The reference model itself has dozens of elements which are grouped by business, users, application, tools and platform services. Within the platform services, we see sub-groupings of common and blockchain specific elements.
Patterns will include 8 design patterns that facilitate the development of blockchain solutions include several smart contract specific patterns.
The presentation will work to tie the importance of considering both technical and business governance into the design elements of the solution.
0:00 Introduction
1:16 ABOUT CHAINYARD
4:07 INTRODUCTION
5:52 CORE PRINCIPLES OF ARCHITECTURE
8:17 BLOCKCHAIN REFERENCE MODEL
17:30 CONSORTIUM GOVERNANCE REFERENCE ARCH
23:24 SECURITY & DEPLOYMENT REFERENCE MODEL
25:57 SYSTEMS ARCHITECTURE REFERENCE MODEL
27:04 BLOCKCHAIN ANALYSIS REFERENCE
29:13 HYPERLEDGER FABRIC - DATA DESIGN PATTERNS
32:14 PEER - CHANNEL - CHAINCODE PATTERNS
34:41 BLOCKCHAIN DESIGN AND CODING PATTERNS
37:22 NETWORK CONFIGURATION PATTERNS
38:57 BLOCKCHAIN BUSINESS PATTERNS
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #Blockchain
A
Thank
you
very
much
for
joining
us
this
late
in
the
day
after
a
long
two
days,
I
hope
we,
we
value
your
time
and
I
hope
you
guys
can
walk
away
with
a
lot
of
good
information.
But
that
said,
we
do
have
a
tremendous
amount
of
information
to
look
at
we're
going
to
do
specifically
Mohan
it's
going
to
do
a
deep
dive
into
only
several
areas
and
the
rest
of
it's
pretty
much
a
survey.
A
I
am
Isaac
uncle
I'm
with
chain
yard
chain
yards
and
IT
people
company,
and
we
are
based
in
Research
Triangle
Park
North
Carolina
I'm,
with
joined
by
my
esteemed
colleague,
Mohan
van
catamaran
who's,
our
CTO
a
little
bit
about
our
topic
today,
we're
gonna
be
talking
about
different
reference.
Architectures
we're
gonna
be
talking
about
technical
and
business
patterns
as
well
as
an
area
that
we're
going
to
touch
on
is
consortium
building
and
governance.
A
We've
seen
all
of
these
things
coming
together
in
projects
that
we've
been
working
on
over
the
last
three
years,
and
so
this
is
pretty
much
a
survey
of
what
we've
learned,
what
we've
done
and
what
we've
coalesced
into
into
these
slides.
Today,
a
little
bit
about
chain
yard,
as
I
said,
we're
based
in
North
Carolina
we're
about
50
people
now
80
percent
in
North,
Carolina,
20
percent
in
Hyderabad
India.
A
We
have
deep
expertise
and
blockchain,
specifically,
we've
been
working
with
fabrics
since
its
inception.
We
were
fortunate
enough
to
partner
with
IBM
in
the
early
days
of
the
beginning
of
the
hyper
laser
project,
and
we
came
into
the
labs
with
them
to
help
them
to
start
with
building
their
their
CI
CD
pipeline
to
put
out
the
quarterly
releases.
Obviously,
it
took
a
while
to
get
the
quarterly
releases
that
started
last
year,
happy
to
say
that
1.4
was
released.
Today
we
do
focus
on
permission.
Blockchains.
We
often
get
asked
about
crypto
ideas.
A
We
tend
to
give
to
people's
our
opinions
and
thoughts
on
that,
but
the
projects
we've
done
over
the
last
three
has
evolved
in
based
on
permission
blockchains.
We
specifically
focus
on
the
value
that
we
believe
blockchain
will
bring
to
enterprises
as
we
continue
to
move
forward
all
right.
We
have
done
some
work
in
the
theory
'm
as
well.
A
Much
of
that
has
been
in
the
government
sector
and
we've
studied
quorum
and
corta
alongside
those
we
think
all
of
those
will
tend
to
dominate
going
forward
and
that's
why
we,
you
know,
we've
put
some
effort
into
all
of
those
we've.
We've
worked
on
a
variety
of
platforms
and
in
industries,
but
the
ones
that
we
focus
on
and
and
invest
in
our
supply
chains.
You've
seen
an
awful
lot
of
those
use
cases
over
the
last
two
days
in
manufacturing
and
transportation,
specifically,
is
where
we
focused.
We
are
hyper,
ledger
members
and
active
contributors.
A
I'm
happy
to
say
that
within
the
next
quarter,
you'll
hear
a
product
that
we're
launching
in
the
supply
chain,
space
called
trust
your
supplier
and
we've.
You
know
the
last
year
has
been
tremendous
amount
of
nothing
but
the
the
governance
side,
the
consortium
billing
side,
the
original
prototype
was
done
over
a
year
ago,
so
as
I
know
that
we
have
a
lot
to
go
through.
Mohan
is
going
to
go
through
most
of
it
at
the
end,
I
will
come
back
to
the
business
patterns.
A
B
B
Got
it
so
good
evening?
Everyone
I'm
really
very
happy
to
be
here
to
see
such
a
big
crowd.
It
is
a
little
bit
intimidating
for
me,
but
let's
fight,
let's
see
how
I
can
do
a
good
job
here.
So
what
we
have
done
is
like
project
after
project.
We
learned
the
hard
way.
As
Isaac
said
you
know,
I
have
14,
you
know,
consultants
in
IBM,
blockchain
labs.
All
they
do
is
test
the
fabric
before
it
goes
into
the
community
and,
along
with
that,
we
learned
a
lot
of
stuff.
Like
the
first
project.
B
We
started
without
a
participant
in
the
network
for
a
customer,
and
it
turned
out
to
be
very
difficult
for
us
to
take
it
to
production,
because
new
members
would
refuse
to
join
because
they
thought
the
first
member,
it's
all
very
proprietary
to
the
first
member.
So
we
learned
that
in
the
next
project
we
learned
that
we
have
to
have
at
least
two
members
in
the
consortium
before
the
project
really
can
take
off
successfully
and
that's
a
pattern
we
continued
and
as
Isaac
says,
you
know
like
a
lot
of
this
is
based
on
our
learnings.
B
We
can
quickly
put
together
solutions
for
our
customers
and
I'm,
sharing
our
knowledge
with
you
all
and
and
I
hope
it
is
beneficial
the
methodology
or
the
approach
that
we
follow
may
apply
to
you.
It
may
not
apply
to
you
as
well,
or
it
may
be
a
modified
approach
that
suits
you.
So
one
of
the
first
things
that
we
said
when
we
set
out
to
build
solutions
and
whatever
we
built
today
is
we
said
we
applied
a
set
of
core
principles.
We
said
like
we
will
build
only
on
fabric,
so
that's
all
chosen
platform.
B
If
not
if
the
customers
choice
is
aetherium,
we
will
do
that.
The
second
is,
we
do
want
to
utilize
Identity
and
Access
Management.
It
is
easy
to
read
I'm
just
gonna
skim
through
this,
but
we
set
up
a
set
of
what
do
you
call
core
principles
into
any
application
that
we
are
going
to
design
in
whether
it's
aetherium
or
whether
it
is
fabric?
So
we
laid
this
out,
but
most
of
the
experience
from
aetherium
has
been
distilled
into
the
fabric
space.
So
that's
so.
B
If
I
move
on
to
the
next
one
I
have
45
slides
I
want
to
see
how
I
can
pace
it
nicely.
So
the
first
thing
is
like
what
we
did
is
like.
Whatever
we
learnt,
we,
we
learned
that,
in
order
to
enable
a
customer,
we
have
to
follow
a
very
orderly
pattern
of
analyzing
the
business
case
of
identifying
the
opportunity,
and
then,
from
that
point
onwards,
how
do
I
take
that
opportunity
to
a
strategy
and
an
implementation?
B
So
we
started
with
the
blocks
in
reference
model,
and
so
it
helped
us
a
lot
and
then
we
figured
that
when
our
product
is
going
into
production,
the
consortium
became
the
biggest
issue,
meaning
like
customer.
You
know
that
the
contractual
agreements
with
the
legal
lawyers
on
both
sides
and
then
finer
details
of
what
we
should
do
and
what
we
should
not
do.
Who
owns
the
court?
So
we
went
into
governance
and
we
said
these
are
the
steps
we
need
to
do
in
order
to
establish
governance.
B
But
then,
when
we
were
doing
governance,
one
of
the
parties
said
like
have
you
done
code
scanning
security
scanning?
How
are
we
sure
that
the
network
that
you
have
built
is
actually
secure?
So
we
said:
okay,
let's
hire
an
outside
company
to
do
a
security
analysis
of
our
solution
and
there
came
a
security
deployment
model
and
then,
from
that
point
onwards,
it's
like
it's
not
blockchain
alone.
There
are
many
participants
in
this
network
whether
it
is
sa
P
Arriba.
B
They
are
all
part
of
the
ecosystem
of
a
solution,
so
we
need
to
know
end-to-end
system
architecture
and
when
we
got
all
this
together,
I
had
to
train
our
analyst
what
they
do
so
we
we
said
this
is
an
analysis,
reference
model
that
the
analysts
can
go
and
work
with
our
customers.
So,
let's
warn
to
the
very
first
one.
You
know
this
is
the
simplest
representation
of
a
reference
of
a
reference
model.
B
It
looks
at
the
business,
the
user,
the
blockchain
and
the
application
and
other
services
that
need
to
be
in
the
ecosystem
and
what
it
help
does
is
it
provides
us
a
logical
path
to
decompose
the
entire
entire
customer
issue
into
very
easy
to
understand
what
pieces
do
we
need
to
actually
analyze
and
develop
and
code?
So
we
understood
fabric
where
you
and
then
we
learned
that
your
organizations
organizations
should
have
peers,
so
we
laid
this.
This
is
a
very
high-level
piece
and
the
next
slide
is
going
to
be
a
little
intense.
B
Let's
see
what
it
says,
okay,
so
this
is
our
reference
model.
Okay,
when
we
go
to
a
customer,
okay,
what
you
can
see
is
on
the
top.
You
see
that
we
have
to
do
the
business
analysis
thoroughly
like
you
have
to
have
a
business
model.
We
learned
that
you
can't
go
with
the
technology
and
then
later
on,
try
to
figure
the
business
model.
We
made
that
mistake
in
one
of
the
projects
and
then
later
on,
trying
to
justify
what
the
business
model
is.
B
So
we
have
to
know
what
the
opportunities
and
from
there
the
business
architecture
and
then
take
on
how
do
I
design
and
deliver
this
right.
So
that's
very
first
in
our
in
our
model,
our
business
analyst
work
through
a
design
thinking
process
with
the
customer
with
all
the
stakeholders,
and
then
we
lay
this
out
once
it
is
done.
You
know.
B
So
we
have
to
understand
who
the
participants
are.
We
then
focus
on
technical
participants.
You
know
so
in
some
of
the
solutions
that
we
built
a
node
operator
need
not
necessarily
be
an
organization.
You
know
what
we
noticed
is
that
we
could
have
a
technical
node
which
can
do
things
like
management
or
analytics
or
anything
else.
You
know
even
key
management
so
because
those
are
not
owned
by
any
specific
organization,
but
they
are
part
of
the
network.
So
the
solution
as
we
expanded-
and
we
talked
to
many
architects.
B
We
found
that
there
are
peers,
some
of
the
some
of
the
organizations
and
their
peers,
our
business
participants,
and
some
of
them
are
technical
participants
in
the
same
network,
and
then
we
looked
at
other
users.
You
know
there
are
you
know,
system
and
human
users,
so
there
are
users
who
are
systems,
there
are
human
users,
and
then
there
are
passive
users
are
external
like
in
the
solution
we
build.
There
could
be
an
auditor
who
has
nothing
to
do
with
the
blockchain,
but
is
an
adviser
and
sometimes
uses
the
application,
and
so
they
need
credentials.
B
So
are
there
you
know
active
users
versus
passive
users
who
are
they?
You
know
internal
and
external
human,
then
governance
members.
So
there
could
be
governance
members
in
the
network
we
build,
they
have
nothing
to
do
with
the
blockchain,
but
they
may
be
investors.
They
may
have
voting
powers
so
that
other
members
who
need
credentials
on
the
network
then
go
on
into
roles
and
responsibilities
for
each
one
and
what
is
their
access
control
mechanisms
and
the
next
one?
B
We
I'm
dwelling
a
little
bit
longer
on
this,
but
then
the
rest
of
it
I
will
move
a
little
faster,
but
you
know
on
the
blockchain
side,
you
know
we
have
to
look
at
all
the
assets
that
we
do.
You
know
the
model.
Technically.
What
transactions
are
we
dealing
with?
What
kind
of
events
the
system
has
to
generate?
Then
information
management
right?
What
is
the
information
model?
You
know
like
what
is
the
data
that
I'm
gonna
store
on
the
chain?
What
are
the
data
that
I'm
going
to
store
off
chain?
B
What
is
the
data
that
has
to
be
private,
etc,
etc?
Like
what
is
confidential
so
that
whole
analysis,
then
we
look
at
all
the
contracts
that
we
need
to
build
the
contract
templates.
So
we
learned
that
in
aetherium,
I
could
have
contract
templates
and
I
could
dynamically
fire
a
contract
at
runtime.
So
we
said
like:
let's
see
how
to
do
that.
So
you
know
reference
model.
We
have
contract
templates
and
we
use
that
then
business
rules.
B
You
have
to
know
all
the
business
rules
that
need
to
be
implemented
on
the
contract
or
off
contract,
and
then
you
go
down,
you
know.
What
are
the
policies
policies
are
universally
applicable
like
passwords
are
to
be
changed
every
as
so
often
our
credentials
are
to
be
changed
every
so
often.
So
what
policies
are
there
and
then
in
the
network?
Look
at
audit
and
compliance
so
many
of
the
projects
we
have
done.
They
involve
audit
and
compliance.
Show
me
your
transaction
history.
Show
me
what
kind
of
audits
have
you
implemented?
B
Can
you
prove
to
me
so
and
so
so
are
there
any
audit
and
compliance
requirements
then
look
at
Oracle's
and
integration,
so
there
are
solutions
in
which
we
actually
communicate
with
external
Oracle's,
which
might
be
things
like
you
know,
exchange
rates
or
that
could
be
integrations
like
si
P
Arriba
Salesforce,
some
of
which
we
have
done
so
what
kind
of
integrations
are
required?
So
an
enterprise
solution
is
not
just
a
blockchain
self-contained.
You
have
to
talk
to
a
bigger
ecosystem,
then
tokenization
in
one
of
the
solutions.
We
are
doing.
B
Actually,
it's
a
hyper
ledger
project,
but
we
learned
how
to
organization
works
with
ERC,
20
and
so
on
and
so
forth.
So
in
the
solution
you
know,
tys
trust
your
supplier.
We
actually
issue
credits
of
you
know:
credits
in
the
form
of
ERC
20
tokens
that
we
implemented
on
top
of
hyper
ledger
so
that
we
can
issue
credits
to
verifiers
and
others.
And
that's
so.
We
learned
that
organization
has
to
be
analyzed
properly.
What
kind
of
tokens
are?
B
They
are
the
asset,
tokens
utility
tokens,
crypto
tokens
and
then
last
but
not
least,
documents
what
documents
do
I
need
to
save
as
part
of
my
architecture,
you
know,
if
that
is
an
invoice,
do
I
need
a
copy
of
the
invoice
toward
externally
a
hash
of
that
document.
Physical
document
on
the
chain,
so
this
is
like
a
complete
analysis
of
what
all
I
need
to
do
in
order
to
build
a
full
solution.
B
And
finally,
you
is
you
know
in
every
application,
everybody
loves
our
UI
if
they
don't
know
what
is
happening
behind
the
scene,
and
so
we
increasingly
noted
that
UI
UX
expertise
is
essential
for
all
the
apps
that
we
have
developed.
So
there's
a
presentation,
layer
and
then
there's
mobile
Ouya.
You
know
mobile
UI
and
then
there
is
the
application
components,
because
an
application
talks
to
the
blockchain,
but
it
also
talks
to
other
pieces.
So
if
you
take
this,
this
is
the
core
of
our
reference.
B
In
order
to
build
anything,
we
need
to
do
this
level
of
analysis
at
the
bottom.
You
can
see
a
lot
of
other
pieces.
Like
you
know.
What
is
the
pieces
in
the
block
that
I
need
to
have?
Then
there
is,
you
know
what
kind
of
API
services
and
integrations
I
have
to
provide.
These
are
platform
services
like
if
I
do
AWS,
we
are
licensing
AWS
services
like
key
management
and
so
on
and
so
forth.
So
what
are
the
things
on
the
platform
that
I
really
need
to
license?
B
Some
of
it
is
self-explanatory,
but
we
spent
a
lot
of
time
looking
at
what
is
what
HSM
technologies
are
available,
because
the
customer
is
very
cost-conscious,
so
we
did
a
lot
of
evaluations.
So
we
realized
that
in
our
platform
we
need
to
consider
what
kind
of
HSM
and
key
management
services
that
we
need
to
utilize.
You
can
move
on
to
the
other
areas.
You
can
see
what
is
my
off
chain
storage
technology
going
to
be?
What
is
my
document
storage
technology
going
to
be?
What
is
my
application
and
analytics
engine?
B
Because
the
solution
we
develop
has
got
an
integration
into
an
analytics
engine
so
whether
we
use
Watson
or
whether
I
use
tensorflow?
What
does
a
customer
prefer
and
then
on
the
right
block?
In
the
complete
side,
we
actually
built
reusable
components,
because
every
project
I
have
login
I,
have
session
management.
I
have
crypto
encryption
decryption,
so
this
whole
set.
We
built
pre-built
components
so
that
when
I
go
to
a
customer,
some
of
these
things
I
don't
have
to
keep
reinventing.
B
B
What
is
our
you
know,
development
environment
going
to
be
what
kind
of
you
know,
system
management
tools
so
on,
and
so
so
with
this
you
know
what
I'm
gonna
do
is
I'm
gonna
shift
to
the
next
one,
which
is
like
we
learned
that
we
had
to
build
a
consortium,
and
you
know
we
started
off
early
trying
to
figure
out
what
is
consortium
building
mean?
You
know
so
and
realize
that
when
our
foot,
when
our
first
product
is
going
out,
we
got
to
work
with
a
variety
of
lawyers,
and
everything
is
like
a
homeowner's
association.
B
If
you
work,
if
you
live
in
the
United
States,
my
neighborhood
has
a
homeowner's
association.
There
are
bylaws,
there
are
rules
and
I
have
to
behave
according
to
the
rules
that
the
homeowners
association
has
put
together.
They
treat
all
of
us
as
consortium
members
right,
so
we
use
the
same
principles
and
we
noted
that
first
thing
in
building
consortiums
is
you
have
to
have
your
bylaws
or
articles
of
engagement
between
all
your
participants?
B
So
there
are
investors
who
want
to
invest
in
your
solution,
and
then
there
are
consortium
members
who
actually
want
to
be
a
member
of
your
consortium.
So
at
the
top
we
have
like
governance
processes,
governance,
structure,
financial
model
and
incentive
model
is
the
high
level
components
at
the
bottom.
We
have
technical
components
so,
right
now
we
are
negotiating.
What
is
the
service
level
agreements?
How
you
know?
What
is
your
disaster
recovery?
How
are
you
going
to
support
me
if
there
is
a
bug?
What
is
your
ticketing
system?
B
These
are
the
issues
that
are
common
in
traditional
applications.
We
are
facing
that
with
our
own
product
and
even
with
the
solutions
that
we
have
supported.
So
we
came
up
with.
Let's
see
what
are
the
different
pieces
that
we
need
to
do
right,
so
we
looked
at
it's
a
governance
process.
You
know
I
need
to
have
workflow,
you
know
so
suppose
a
new
member
wants
to
join
the
consortium
and
the
existing
members
have
a
process
right
fill
up
this
form
you
get.
B
You
know,
you
know
we
have
to
verify
the
credentials
of
the
new
member
who
wants
to
join
the
consortium
bead
and
organization.
We
then
how
to
issue
them
credentials.
We
have
to
issue
them.
You
know,
like
you
know,
how
do
we
enroll
them?
You
know
how
do
we
activate
them
on
the
network
so
on
and
so
forth?
So
there's
this
whole
membership
model.
Then
there's
governance
structure.
You
know
who
are
the
members
of
the
network?
What
are
their
voting
powers?
You
know
which
members?
What
are
their
roles
and
responsibilities
on
this
on
this
governance
team?
B
What
are
their
voting
authorities?
What
are
the
segregation
of
duties,
so
our
lawyer
was
asking
is
all
the
questions
actually
when
we
were
sitting
with
them
a
couple
of
weeks
ago
he's
like
the
guy
who
developed
the
court.
Does
he
have
access
to
github?
There's
a
person
who
had
access
to
github?
You
know
most
of
the
three.
You
know
he
was
questioning
us
on
all
of
things,
and
so
we
looked
at
segregation
of
duties.
B
Then
financial
model-
you
know
there's
so
many
POCs
built,
but
there
is
no
financial
model
who
is
going
to
pay
for
the
network?
You
know
how
is
the
revenue
that
you
collect
on
the
network
being
going
to
be
distributed?
How
are
you
going
to
collect
the
revenues?
What
kind
of
tokens
are
you
going
to
issue
so
we
we,
you
know,
went
through
the
process
and
listed
that
this
is
something
essential.
When
we
look
at
governance
and
then
on
the
right
side,
you
see
technical
operations
management.
B
How
do
I
ensure
SLA,
so
they
SLA
that
one
of
the
consortium
members
who
wants
to
join
our
network
said
I
want
ninety-nine
point:
nine,
nine,
nine
three
nines
right,
so
we
then
so
in
order
to
meet
that
SLA,
we
have
to
figure
out
whether
we
have
the
right
number
of
nodes,
whether
if
in
one
load
goes
down,
will
the
other
node
be
affected?
What
is
their
transaction
through
point
to
guarantee
on
an
average
99.999%
quality
of
service,
so
configuration
management
issue
management?
You
know,
disaster
recovery
account
management,
service
management.
B
These
are
all
like
standard
items
on
operations
management,
then
standards
and
guidelines.
You
know
like
when
somebody
wants
to
put
a
new
contract
into
their
network.
Then,
are
there
any
standards
and
guidelines
that
they
need
to
follow?
What
are
the
infrastructure
policies?
Suppose
I
want
to
bring
my
own
node
into
the
network
and
I
want
to
bring
my
own
server?
Is
there
any
guidelines
in
terms
of
what
should
be
its
sizing?
What
should
be
the
memory?
What
should
you
know
stuff
like
what
should
be
installed
on
it?
What
should
not
be
installed?
B
So
those
are
all
considerations
on
standards
and
guidelines.
Then
we
look
at
audit
and
controls.
What
kind
of
audits
are
there?
You
know
like?
There
are
artists
for
Sox
compliant,
that
is
artists
for
regular
HIPPA
compliance
or
what
are
the
other
things,
and
do
we
have
any
tools
that
can
detect
malicious
behavior
or
you
know,
non-compliance
and
finally,
change
management,
it's
very
essential
because
in
the
initial
stages
we
are
releasing
1.1
1.1
11.1
2
into
the
environment,
because
there's
a
lot
of
change
as
testers
come
in
and
they're
testing
our
solution.
B
So
how
do
you
manage
all
these
changes?
You
know,
so
we
have
governance
contracts
in
some
of
the
solutions
we
built.
We
built
contracts
that
are
not
directly
impacting
the
solution,
but
their
governance
car.
There
are
smart
contracts
that
sit
in
front
of
the
application
contracts
run
on
the
blockchain
and
ensure
that
governance
aspects
are
happening
and
then
smart
contracts
itself
Sochi.
How
do
you
manage
that
the
smart
contracts
and
as
well
as
your
regular
contracts,
who
do
who
does
who
has
to
sign
off
on
it,
have
all
the
parties
agreed
to
it?
B
Okay,
so
this
is
like
a
there.
We
notice
that
that
big
model
cannot
be
done
on
one
day.
So
when
we
worked
with
one
of
the
projects
we
had
to
time
it,
so
what
do
I
do?
You
know
this
is
very
important
in
the
solutions
you
build.
It
is
a
case
by
case
in
some
solutions
you
may
do
all
of
it.
Some
of
it
is
very
important,
and
some
of
it
is
not.
So
what
do
we
build
in
the
first
three
months?
And
what
do
we
do?
B
You
know
what
do
we
do
before
before
we
go
into
production?
We
should
have
the
articles
of
engagement
and
we
should
have
the
network
operations
and
other
things
taken
care
of
like
what
is
your
support
model?
You
know,
and
what
is
your
operations
team
going
to
look
like
what
is
their
operations
procedures?
Those
are
all
before
you
go
into
production,
but
once
you
go
into
production,
what
would
you
do
in
the
first
three
months?
What
should
you
have
in
place
in
the
next
six
months
and
what
should
you
have
in?
B
There
is
12
to
24
month
period.
So
this
is
what
it
lays
out
skipping
to
the
next
one
I'm
going
to
skip
this
a
little
bit.
But
what
I'm
going
to
say
is
when
we
looked
at
security,
our
lawyers
and
the
security
audit
company
started
a
question
as
like:
who
are
the
officers
in
your
company?
What
kind
of
authority
they
have
you
know?
Are
they
all
like?
Have
they
all
signed?
Nda
documents
with
the
with
a
company?
Have
you
had
an
NDA
with
the
network
participants?
So
they
started
to
question
us
in
all
different
directions.
B
So
we
said
like.
Let
us
look
at
everything
that
needs
to
be
really
looked
at
in
terms
of
security,
so
you
have
to
have
insider
threat
is
the
biggest
threat
in
in
the
network,
and
so
you
know
we
have
to
when
your
lawyer
works
with
you
or
when
you're
working
with
your
consortium
members,
you
got
to
look
at
who
are
your
key
threats?
It's
mainly
insider
threats,
a
guy
who
knows
the
smart
contracts
very
well
is
the
biggest
threat.
So
you
have
to
have
things
in
place.
B
Look
at
whether
your
use
of
security
is
in
place.
How
are
you
managing
your
keys?
You
know:
do
your
keys
leave
out,
so
I
did
some
of
the
work
for
the
US
federal
government,
and
so
they
have
NIST
standards
and
then,
when
I
was
talking
with
the
NIST,
you
know
consultant
he
was
saying
like
new
yorkese
ever
leave.
B
How
long
are
they
in
memory
so
because
these
measuring
the
window
of
time
when
the
keys
can
be
in
memory,
and
can
somebody
steal
it
so
he's
asking
me
questions
like
how
are
you
securing
it
so
that
there
is
no
man-in-the-middle
attacks,
so
we
said
like.
Let
us
look
at
how?
How
are
we
securing
the
keys?
Are
the
keys
ever
leaving
a
container
and
coming
out
or
are
we
sending
the
encrypted
encryption
and
decryption
functions
into
the
you
know
into
the
into
the
key
management
service
tokens?
How
are
you
securing
your
tokens?
B
How
are
you
securing
you
know
your
databases
off
chain
on
chains,
so
there
was
a
big
question
like:
where
is
your
data
store?
You
know
if
you
do
gdpr,
you
know,
and
there
are
certain
rules
that
I
learnt
is
like
certain
countries
want
the
data
to
be
in
the
nodes
that
are
in
their
country
specific
data
center,
so
that
you
would
face
and
then
how
are
you
securing
them?
So
that
was,
you
know
on
you
know
off
chain
data,
especially
your
configuration
files.
B
You
know
if
you
look
at
fabric
or
even
if
you
look
at
its
helium
networks,
there
are
so
many
configuration
files
and
there
are
other
files
that
you
need
to
secure.
Then
how
are
you
securing
an
application
because
that
is
user
facing
you
know
what
kind
of
controls
have
you
put
in
place?
And
finally,
how
are
you
securing
your
smart
contracts?
You
know?
Are
they
exposed?
Who
all
have
authorization
which
ports
are
they
running
on?
Are
the
endpoints
visible
I,
you
know,
so
those
are
kind
of
things
that
we
had
to
go
through.
B
And
finally,
you
know
if
you
are
to
put
your
entire
solution
together.
You
have
to
look
at
the
big
picture
right,
so
blockchain
is
only
one
end
of
the
spectrum,
but
my
clients
would
like
to
connect
to
the
blockchain
using
their
own
clients
that
they
weren't
a
design
or
they
would
like
to
use
clients
that
we
specifically
give
them.
You
know
if
I
work
with
large
customers
they
want.
They
want
the
API
layer
so
that
they
can
integrate
it
into
their
photos.
B
B
You
know
like
if
I'm
exposing
s
ap
services,
I'm
using
micro
services
as
a
way
of
exposing
functions
to
the
blockchain
network
or
to
our
application
and
finally
on
the
extreme
left,
is
like
how
am
I
connecting
to
s
AP
in
a
secure
manner?
How
am
I
connecting
to
Arriba
how
am
I
connected
Salesforce?
How
am
I
connecting
to
anything
else?
That's
an
enterprise
apps
that
kind
of
like
tells
us.
You
know
what
we
really
build.
Our
solutions
on
and
this
little
piece
tells
us
like.
B
This
is
our
blockchain
reference
architecture
for
doing
analysis,
and
we
already
covered
this
before
so,
and
this
is
a
piece
of
the
reference
architecture
that
our
business
analysts
go
and
we
have
detailed
X
on
what
we
actually
asked
questions
when
we
work
when
our
analysts
work
with
the
business
participants
like
in
the
business
model,
we
have
a
series
of
14
questions.
Similarly,
you
know
when
you
study
the
organization's,
we
ask
questions
like:
are
they
going
to
operate
a
node
not
operate
a
node?
If
they
are
operating
a
node
between
two
organizations?
B
Do
they
need
a
secure
channel
non
secure
channels?
A
lot
of
things
I'm
going
to
move
into
I
do
not
know
the
time
check
got
15
more
minutes.
So
let
us
see
design
patterns.
You
know
so
one
of
the
biggest
things
in
a
fabric
its
fabric
gives
you
so
many
features
that
sometimes
you
could
get
lost
right.
So
one
of
the
things
is
like
you
know:
where
do
I
store
my
data?
You
know
this
is
a
common
question
in
every
application
that
gets
asked
and
then
like
how
do
I.
B
You
know
how
many
chain
code
should
I,
have
multiple
chain
codes
on
a
single
channel
or
should
I
spread
the
chain
codes
into
multiple
channels.
You
know
how
many
channels
should
I
have
between
two
nodes.
You
can
do
all
kinds
of
things
in
fabric
and
you
can
get
completely
lost.
A
real,
complicated
fabric
solution
can
be
multiple
nodes.
Multiple
chain
cause
multiple
channels
between
the
same
two
nodes.
In
fact,
in
one
of
the
solution
there
were
multiple
channels
between
inside
the
same
node.
B
B
And
then
we
have
faced
now
as
the
network
expands
in
fabric
and
a
new
participant
wants
to
come,
but
they
want
to
expand
the
network
on
their
side,
but
not
be
part
of
this
portion
of
the
network,
because
in
fabric
a
channel
is
like
a
private
blockchain
and
you
can
have
many
private
blockchains
on
the
same
network
and
they
won't
all
be
isolated
but
communicate
as
needed
and
last,
but
not
the
least
the
business
patterns.
So
let
us
see
what
we
did
in
in
in
data
design
patterns.
B
So
when
we
started
to
analyze
and
many
of
the
projects,
we
noticed
that
there
is
data
that
goes
into
a
public
ledger
that
every
member
of
the
network
wants
to
see
transparent.
There
are
channels
in
which
there
is
privacy
between
two
parties
on
the
network.
They
are
public,
but
they
are
only
visible
to
those
two
parties.
Then
we
have
like
private
information.
Okay,
where
do
I
store
private
information.
That
is
very
specific
to
a
particular
organization,
and
then
there
is
confidential
information
that
needs
to
be
encrypted.
B
And
finally,
there
is
like
off
chain
information
like,
for
example,
GDP.
Our
data
cannot
be
on
the
Block
scenes,
though,
and
there
are
also
application,
specific
information
that
drives
your
blocks
in
solution.
So
how
do
we
store?
So
we
came
up
with
a
very
simple
way
of
looking
at
it.
What
we
said
is
like
you
know:
if
I
have
three
parties
right
organization,
one
two
three
and
all
the
data
is
public.
Then
I
need
a
single
channel
between
all
of
them.
B
B
Now,
if
our
collection,
where
do
r1
and
r2
share
public
data
and
r3
r4,
then
I
would
have
two
channels
between
between
the
organization's,
so
I
mean
this
is
kind
of
like
a
decomposition
of
our
decision
tree
if
I
have
something
that
is
where
let
us
say
Prai,
you
know
that
is
partially
private
right
and
then
I
have
collections
that
are
like
confidential,
that
it
could
be
confidential
data
purely
confidential
confidential
data
that
actually
sits
on
the
ledger.
In
that
case,
I
have
to
use
encryption
in
fabric.
B
You
can
use
techniques
like
sending
transient
I
know
you
can
use
transient
data
to
go
into
the
block.
You
know
as
and
you
can
send
the
keys
in
and
you
can
have
your
actual
payload
coming
through
another
channel.
So
you
can
do
all
these
things.
If
it
is
private
in
fabric,
you
can
use
site
DB.
So
I
can
use
all
these
multiple
methods
by
which
I
can
feed
the
data.
If
I
use
the
keys
on
the
payload
itself,
then
it'll
be
visible
on
the
ledger,
so
you
don't
want
that.
B
So
how
do
I
do
that
and
then
so?
Finally,
you
have
like
site
DB,
because
the
data
is
private,
secure
Keys
uses
it
very
effectively
and
we
have
used
it
in
some
trade
finance
applications.
I
do
not
want
to
know
how
much
I
bid
on
it,
but
it
is
private
to
me
between
me
and
my
party,
but
I
do
not
want
to
expose
my
coat
in
trade
finance
right.
The
suppliers
invoice.
You
know
the
buyers
invoice
is
exposed
by
the
supplier.
Me
gets
bids
from
different
financial
institutions.
B
You
if
that
data
is
very
private,
you
don't
want
it
on
the
ledger,
the
bit
information,
then
you
can
utilize
site
DB,
which
is
available
in
fabric,
so
so
private
data
on
site,
DB,
and
if
the
data
is
PII,
you
know
personally
identifiable
information.
Then
you
put
it
off
chain
right.
So
that
is
like
kind
of
how
we
have.
We
do
our
data
modeling
a
little
bit
and
the
other
thing
is
like
channels.
You
know
you
can
have
many
channels
between
two
parties.
There
are
many
cases
I'm
going
to
just
use.
B
One
example
in
this
pattern
like
let
us
say
you
know
high
availability.
So
often
it
comes
up.
You
know
people
don't
want
to
pay
for
nodes.
I
do
not
know
how
many
of
you
have
actually
costed.
How
much
your
POC
costs
right
appear
if
I
were
to
use
fabric
and
I
know
that
well,
an
organization
cost
you
a
thousand
dollars
and
then
a
peer
cost.
You
a
thousand
dollars
per
month.
So
technically
speaking,
if
there
are
two
organizations,
two
thousand
dollars
upfront
cost
and
then
two
thousand
per
month.
B
So
there
are
people,
there
are
organizations
that
want
to
invest
in
peers,
but
there
are
some
organisation
one
invest
so
I.
If,
in
the
first
pattern,
I
could
have
two
peers
that
a
particular
organization
hosts
org
one
and
R
two
has
only
one
node,
but
it
trusts
or
two.
So
if
there's
a
failure
on
any
of
the
nodes,
at
least
I
have
activity
still
going
on,
but
the
still
depends
on
how
you
model
your
endorsement
policies
and
so
on
and
so
forth
right.
So
that
way
you
can
see
high
availability.
B
You
know
to
you,
know
both
organizations,
don't
trust
each
other.
So
I
have
two
peers
on
each
side.
Then
the
next
model
is
like
network
with
management
peers.
So
there
are
two
nodes
which
are
organizational
Ledger's
and
then
there
are
two
management
peers
that
can
store
additional
ledger
information,
like
audits
and
others.
That
should
not
be
visible
to
all
the
other
organizations,
but
it
is
visible
only
to
the
network,
so
you
can
do
similar
models.
B
B
But
technically,
when
I
worked
with
etherium,
you
could
actually
slice
your
functions
into
smaller
bits:
manageable,
smart
contracts,
you
can
do
the
same
thing
in
fabric,
and
so
you
can
do
c1,
c2
c3
as
multiple
chain
cores
running
on
it,
and
the
beauty
is
that
each
one
of
those
smart
contracts
can
talk
to
each
other
and
update
each
other's
ledger.
If
you
want
to
separate
them
completely,
then
you
can
have
multiple
channels
and
each
one
up.
B
Let
us
say
there
are
two
organizations
they
use
the
same
smart
contract,
but
they
want
to
isolate
their
Ledger's
out
for
other
purposes.
Right
like
then,
I
could
have
multiple
channels
with
the
same
chain.
Code
running
on
the
same
Channel
I
could
also
have
multiple
chain
codes
running
on
different
channels.
B
Gonna
skim
through
this
and
then
coding
I'm
going
to
go
here
and
some
other
patterns
be
used.
If
I
use,
aetherium
I
can
actually
have
all
the
addresses
inside
a
registry
and
I
can
figure
out
at
runtime,
which
change
which
smart
contract
is
running
whereby
the
address
and
I
can
actually
communicate
with
contracts.
You
know
I
can
build
a
registry,
so
we
in
some
of
the
projects
we
have
multiple
chain
codes,
so
I
need
to
have
an
effective
way
of
managing
them.
B
So
we
do
use
a
registry
pattern
in
which,
but
in
in
unlike
a
tinea,
where
I
can
model
this
inside
as
a
smart
contract,
we
model
this
outside
on
the
nor
J's
client.
We
have
a
registry
contract
in
which
every
chain
code,
what
is
running,
what
is
its
github
location,
is
a
to
register
there
and
I
can
actually
use
that
model
to
do
a
runtime
install
a
instantiation
because
you
can
instantiate
chain
code.
You
know
from
your
client.
B
So
if
I
wanted
a
nut,
if
I
use
the
template
pattern,
I
want
chain
code,
one
and
I
want
to
reinstate
chain
code.
One
again,
I
can
look
at
the
registry,
get
a
copy
of
the
code
instantiated
and
deployed
on
any
channel,
so
I
can
use
registry
patterns.
I
can
use
the
routing
patterns
if
I
have
a
workflow
on
my
application
and
depending
on
the
workflow,
it
has
to
call
chain
code
one
two,
three:
four:
we
can
use
the
routing
pattern.
I
learnt
another
thing
in
is
helium.
B
Is
you
actually
isolate
our
data
contracts
from
business
contracts
simply
because
you
want
to
actually
preserve
the
data
all
the
time?
You
know,
sir,
if
you
do
chain
code,
you
can
upgrade
chain
codes,
but
actually
the
data
moves
from
chain
code
version
1.1
to
1.2,
but
what
I
learnt
while
doing
a
tedium
project
says
you
can
separate
our
data
as
a
separate
contract.
It
maintains
all
the
data
in
the
ledger
and
business
contract
only
does
business
functions,
so
you
can
isolate
our
data
versus
business.
That
way.
B
Changes
in
your
business
logic
will
not
impact
your
data.
You
know
those
changes
and
data
structures
can
actually
impact
your
data
structures,
but
if
you
are
storing
everything
in
JSON
structures,
it
doesn't
really
matter.
You
can
continue
using
this,
so
there
are
some
workflow
patterns.
We
came
up
with
dynamic,
instantiation
I
said:
I
can
look
at
the
registry
and
dynamically
instantiate
contracts.
We
can.
B
We
wrote
our
own
contracts
for
governance,
which
may
you
know
which
manages
contract
rules
and
permissions
management
so
that
as
soon
as
a
transaction
comes
from
node
SDK,
it
hits
the
verifier
contract,
which
verifies
if
that
function
is
executable
or
not,
and
then
only
route
set
to
the
appropriate
contract.
You
know
that
is
supposed
to
run
that
function.
You
also
use
the
adapter
because
in
supply
chain,
especially,
there
is
a
lot
of
data
that
is
common
to
many
different
contracts,
but
you
had
to
translate
them
from
one
format
to
the
other.
B
So
you've
done
some
of
that.
You
know,
then
I
ran
into
some
of
the
network
configuration
patterns
right,
it's
a
very
simple
network.
Everyone
shows
us
the
POC
with
four
nodes
and
a
single
Channel
right
I
would
like,
but
we
are
gone
into
complexities,
because
what
happened
is
we
started
that
way,
and
this
is
actually
an
actually
example
of
a
procurement
application.
But
and
what
happened
is
one
of
the
ends
of
the
note
said?
B
I
want
to
now
expand
my
own
network
I
I'm,
a
I'm,
a
bi
am
a
supplier,
but
I
have
affiliate
suppliers
I
do
not
want
to.
You
know,
make
visible
my
affiliates
to
you,
so
they
expand
on
the
left
and
each
one
of
them
could
have
their
own
node
and
have
separate
Ledger's.
Each
affiliate
could
be
on
a
separate
note
and
have
a
separate
channel
so
that
they
can
isolate
their
Ledger's,
and
so
they
can
expand
on
one
side
or
sometimes
that
are
very
small
affiliates.
B
They
don't
wanna
operate
a
note,
so
they
come
together
and
then
they
decide
that
I
will
use
Nord
C
as
a
trusted
anchor,
and
we
all
will
trust
it,
and
so
affiliates
could
work
with
a
single
anchor,
node
or
affiliates
could
have
their
own
nodes.
So
a
couple
of
different
ways
by
which
we
have
approached
as
our
first
app,
we
got
two
of
our
applications.
I've
finished
24
months.
You
know,
we've
been
working
on
it
for
24
months,
since
you
know
August
of
2016.
B
So
as
the
network
expands,
we
have
to
make
sure
that
the
network
can
scale
and
expand,
so
many
of
the
other
ones
are
like
how
does
it
scale?
And
finally,
how
will
it
look
like
this
and
each
one
can
then
keep
expanding
there?
So
you
can
see
it's
like
a
truly
distributed
network
and
finally,
I
mean
in
all
the
negotiations.
We
have
a
big
problem.
You
know
the
customers
want
to
know
where
the
opportunity
is.
We
waste
a
tremendous
amount
of
time
three
three
months
and
I'm
deals
with
most
of
the
customers
all
the
time.
A
Right
so
respecting
your
time,
I
know
we're
right
at
the
ED
here
edge
here.
I
will
just
do
a
tell
you
why
we
think
the
business
patterns
are
important
and
then
we'll
all
just
give
you
the
survey
of
them.
These
are
all
things
that
you
guys
have
seen
read
about.
These
are
ones
that
we've
happened
to
have
the
fortune
of
working
on
as
well
and
and
you've.
Seen
tremendous
examples
of
many
of
these.
Some
have
multiple
patterns
within
them.
I
can
think
of
every
ledger.
A
Trade
lens,
IBM,
food
trust,
I
know
all
of
us
have
multiple
these
patterns,
but
everything
from
identity
management
and
the
work
being
done
with
sovereign
and
indie
is
great.
Border
trade
is
huge
digital
asset
registry,
auditing
compliance,
financial
settlement
system
of
record
data
and
document
management,
secure
trade,
finance
disputes
and
reconciliation,
provenance
asset
track
and
trace.
Again,
nothing
you
haven't
read
about.
We
got
a
little
bit
more
detail
on
each
of
these.
A
You
know
the
just
typical
enterprises
and
we
have
to
start
talking
to
about
consortium,
building
and
thinking
about
how
to
decentralize
it
in
some
way,
and
you
can
still
have
some
traditional
models
or
the
SAS
models
and
all,
but
you
want
to
you,
want
to
build
the
trust
through
some
descendant
some
centralization
mechanism.
You
want
to
solve
data
problems
with
solutions
that
solve
data
problems,
and
we
want
to
make
sure
that
we're
positioning
them
so
if
they
do
leverage
blockchain,
that
is
solving
a
problem
today
and
also
positioning
them
for
more.
A
You
know
features
in
the
future,
so
they
can
continue
to
take
advantage
of
blockchain
in
other
areas
of
their
business.
And
that's
one
of
the
reasons
we
we
love
fabric
is
that
it
is
pluggable,
and
we
do
know
that
this
is
very
nascent
technology
and
it's
going
to
continue
to
evolve
and
that
that
pluggable
nature
is
going
to
make
the
investment
that
companies
do
today
pay
off
more
in
the
future
than
having
to
throw
away
everything
and
start
over
each
time.
A
A
B
B
You
know
secure
words
and
stuff
like
that.
We've
done
what
equal
compliance,
where
audit
ability
of
you
know
of
a
manufacturer
to
our
distributor
to
a
end
customer.
There
are
so
many
other
examples
we
can
use.
We
have
done
trade
finance
so
just
curious.
Can
you
provide
some
metrics
on
these
projects,
like
how
many
participants
are
in
this
consortium?
How
many
nodes
they're
running
like
how
many
locations
in
etc?
So
you
can
take
the
biggest
one.
B
Yes,
so
you
know
so
our
own
network,
you
know,
so
that's
the
solution
we
are.
Having
is
two
nodes
right
now:
okay,
which
is
going
into
production.
We
have
three
companies
that
are
signed
up,
but
the
thing
is
like
before
a
node
can
operate,
I
have
to
finish
the
memorandum
of
understanding
and
other
things,
the
legal
obligations.
B
So,
even
though
there
are
far
you
know,
I
can
say
one
two
three
four
five
members
have
signed
up
the
legal
contracts
before
they
can
come
on
board
is
taking
us
time,
so
that
would
be
our
own
trust,
your
supplier,
on
the
network.
Ultimately,
we
expect
15
nodes
when
all
of
them
sign
up
and
we
will
have
at
least
20,000
suppliers
overall
to
begin
with,
you
know
so
by
the
end
of
2019
or
the
first
quarter
of
this,
that
many
we
expect
them
to
sign
up
as
passive
users.
B
They
won't
operate
notes
for
I,
told
two
of
the
networks.
I
showed
you
where
I've
saying
scalability,
they
started
off
with
two
nodes,
which
means
they've
the
procurement
application,
especially
the
client
and
their
supplier.
It
started
off
too
and
now
what
happened,
as
others
have
expressed
interest
the
the
the
supplier
said:
I
want
to
expand
the
network
to
my
this,
so
we,
the
supplier,
is
negotiating
with
their
suppliers.
They
go
through
the
same
process,
so
we
know
you
know
that
that's
how
it
is
going
to
expand
so
day,
one.
B
It
starts
centralized
somewhat
and
as
the
network
grows,
that's
when
it
gets
truly
decentralized.
So
this
is
the
teething
problem
in
getting
production
networks
up
and
running.
It's
not
like.
You
cannot
put
fight,
I
have
a
final
network
and
I
can
put
finals,
you
know,
but
that
doesn't
mean
anything.
A
B
Yeah,
you
know
so
I'm
a
to
have
certified
architect.
Okay,
so
some
of
my
thought
process
is
always
toga.
I
need
to
know
what
the
business
does
and
then
how
does
it
translate
into
different
layers
right
so
application
information
in
this?
But
then
we
said
the
blockchain
is
not
in
TOGAF
yet
and
when
we
go
to
customers
when
we
saw
those
layers
have
to
be
understood.
You
know
the
workbook
includes
like
when
we
do
data
analysis.
We
say
is
this
confidential?
B
Is
it
proprietary
to
organisation
1
or
is
common,
so
we
do
the
whole
nine
yards
of
analysis
so
that
first
few
layers
actually
helps
us
to
crystallize
the
solution
all
right,
but
when
we
talk
to
sa
P
we
are
negotiating
actually
I
mean,
like
your
question,
was
that
so
we
have
to
work
with
s
a
P
and
a
civvy
architects,
and
we
try
to
negotiate
what
the
data
is.
Gonna
be
whether
there's
an
Oracle
that
will
be
provided
by
them,
or
do
we
create
the
API
sand?