►
From YouTube: No Pain, No Blockchain: Reducing the Complexity of Network Deployment - Ed Kazmierczak, Penta Global
Description
No Pain, No Blockchain: Reducing the Complexity of Network Deployment - Ed Kazmierczak, Penta Global
Many enterprise blockchain service providers have made exciting advances toward helping their end users onboard more seamlessly into blockchain environments through fully managed deployment and the provision of familiar, intuitive UI and user experience.
Despite its upside for end users, abstracting technical complexity out of the deployment experience usually comes at the cost of a user's personal control over defining, refining, and managing the parameters of their own private network and/or associated node, a convenience fee that's too high for most non-end user subsets of the blockchain community, such as:
a) dApp Developers
b) Solutions Architects & Ecosystem Managers
c) Enterprise DevOps Teams
For these users, a sizeable accessibility & usability gap exists at the initial stages of network deployment, where a multitude of steps are required to complete network & node configuration, genesis file initialisation, additional tool/service integrations etc.
Some of the most commonly cited barriers associated with this arduous process include:
a) Poorly organised/disjointed, lacking, or non-existent documentation
b) Incoherence and excessive coupling of setup modules
The purpose of this ThinkTank is to harness the collective wisdom of the diverse, talented group of people in the room to discuss, ideate, and explore solutions that address the following problem statement:
"Many would-be facilitators, builders, and adopters of enterprise blockchain solutions currently struggle to navigate the complexities of initial network setup and deployment."
We welcome all HLF members who feel passionate about this topic, from technical engineers and researchers, to product owners/managers, business analysts, solutions specialists, marketers, and everyone in between!
----
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 #HyperledgerGlobalForum2020 #Blockchain
A
A
So
today,
what
I
want
to
talk
about
a
bit
is
the
sort
of
projects
that
we
do:
the
sort
of
projects
that
we've
deployed
the
kind
of
lessons
that
we've
drawn
from
those
projects.
Some
of
the
factors
that
we've
had
to
grapple
with
in
doing
those
projects-
and
maybe
we
can
explore
some
of
the
some
of
the
technology
initiatives
that
we
we
can
think
of
going
forward.
A
A
A
What
we
wanted
to
do
it.
What
we
wanted
to
get
out
of
it
was
just
to
see
how
easy
it
was
going
to
be
in
a
real
world
deployment
to
take
some
IOT
senses,
put
them
with
the
coffee
shipment
and
track
that
coffee.
From
start
to
finish,
and
if
you
look
at
the
photos
there,
that's
a
shipment
of
coffee,
that's
what
it
looks
like.
We
don't
quite
have
that
many
sensors,
but
we
did
actually
manage
to
get
enough
to
put
it
in
several
bags.
A
And,
interestingly
enough,
we
also
tried
to
compare
two
different
kinds
of
sensors
and
to
get
their
data
and
to
see
how
easy
that
data
was
to
load
up
and
put
on
a
blockchain
there.
We
go
and
just
to
just
to
convince
you
that
we
actually
did
do
this
here
are
the
results
we
had.
Some
surprises,
the
first
surprise,
was
that
the
coffee
didn't
actually
go
to
Florida.
A
But
that's
okay,
our
solution.
Now
tracking
solution
worked,
we
got
all
the
way
to
this
place
called
Canada
at
the
north
of
the
US
I
believe
when
it
got
there.
Here's
the
interesting
thing
to
me.
We
got
two
thousand
three
hundred
and
eighty
one
data
points,
but
we
got
two
thousand
three
hundred
and
eighty-one
data
points
from
Colombia
from
Panama,
from
the
Bahamas,
from
somewhere
around
the
east
coast
of
the
US
and
from
Toronto.
A
A
The
technology
is
often
last
minute
quick
pipeline.
We
have
to
do
things
quick.
Our
problems
are
now
how
to
take
that
idea
and
how
to
take
the
germ
of
that
idea,
how
to
deploy
it
at
scale
over
many
projects
and
a
question.
That's
been,
that's
been
really
on
my
mind
in
the
last
in
the
last
few
months,
as
we
go
forward,
is
how
do
we
tool
to
blockchain
to
scale
blockchain
technology.
A
A
Thought
I'd
also
show
you
another
project
that
we've
done:
we've
deployed
a
loan
fractionalization
project,
so
the
project
is
tracks
the
ownership
of
chain
of
title
of
lives.
This
is
basically
an
asset
asset
tracking
kind
of
blockchain.
We've
deployed
that
the
blockchain
technology
itself
is
very
standard,
but
here's
our
challenge.
With
this
project
we
had
to
integrate
blockchain
with
an
existing
enterprise,
an
existing
business
and
so
immediately
that
raises
questions
of
well.
How
do
you
do
that,
both
at
the
technological
level
and
at
the
business
level,
and
so
at
the
technology
level?
A
We
had
to
work
out
solutions
of
how
we
would
how
we
would
basically
integrate
with
their
business
systems
and
take
the
data
that
they
wanted
us
to
take
without
being
too
invasive
on
their
business
systems,
and
then
we
actually
had
to
solve
a
whole
lot
of
business
problems
who
has
ownership
of
the
data
and
when,
as
soon
as
the
data
crosses
the
line
from
their
business
to
our
business.
So
now
it's
in
our
custody
we're
responsible
for
that
data.
Even
though
it's
on
a
blockchain
we've
taken
on
a
certain
amount
of
risk.
A
A
A
Sorry
there
we
go
so
this
example
is
a
couple
of
just
two
of
the
deployments
that
we've
done.
Those
block
chains
are
running
they've
been
running
for
about
a
year
now,
and
so
in
the
spectrum
of
the
types
of
projects
that
people
do.
What?
Where
do
we
sit?
There's
lots
of
different
kinds
of
project
that
you
can
do
we
sit
over
here.
A
A
A
A
We've
learned
some
lessons
out
of
that
and
just
before
I
go
on
to
those
lessons.
Not
all
of
our
deployments
are
on
hyper
ledger
fabric.
We
actually
have
some
deployments
on
hyper
ledger
fabric,
but
we've
also
used
the
theorem
and
we've
also
used
big
chain
DB.
Why
hey?
Let
me
start
by
saying:
let
me
start
by
saying
I
like
actually
like
hyper
legend.
Hyper
ledger
has
a
lot
of
appeal
to
me.
A
Hyper
ledger
has
peel
because
you
can
get
a
good
ordering
of
blocks
without
having
to
go
through
a
proof-of-work
consensus
or
proof
of
state
consensus,
or
any
of
these
complicated
consensus
mechanisms
for
social
governance.
I
can
understand
why
those
are
there,
but
for
people
like
me
who
just
want
it,
who
just
are
dealing
with
data
and
complicated
data
situations,
sometimes
being
able
to
get
the
data
onto
the
chain
quickly
without
the
need
for
consensus
is
a
good
thing.
A
Hyper
ledger
gives
you
that,
but
in
our
previous
deployments
or
in
our
previous
attempts
at
deploying
with
hyper
ledger,
we've
ran
into
some
issues
the
kinds
of
projects
that
we
do
are
often
exploratory.
We
don't
do
a
lot
of
projects
that
say
right,
I'm,
going
to
invest
a
million
bucks
into
this
blockchain
because
it's
going
to
be
our
company's
future
for
the
next
50
million
years.
A
A
I
sometimes
get
rung
up
by
my
CEO
and
he
says:
I've
got
a
new
contract
for
you
and
he'll,
give
us
the
time
frame
and
I'll
politely
say.
Oh,
let
me
think
about
that
and
I'm
really
thinking
to
myself.
You
want
what,
when
our
deployments
are
short
and
so
but
hyper
ledger,
Piper
ledger
fabric
itself
has
a
complex
design
space.
A
A
A
A
Most
of
those
points
on
that
slide
are
related
exactly
to
that
point
yeah,
when
we
were
playing
with
hyper
ledger,
the
documentation
still
needed
a
little
bit
of
work
and
there
wasn't
the
tooling
available
that
there
is
today
hey
now.
That's
changed,
though,
because
I've
looked
around
I've
looked
around
the
theater,
upstairs
I've
looked
around
some
of
the
trade,
some
of
the
here
the
booths
upstairs
and
the
tooling
is
definitely
improving.
There's
some
good,
tooling
and
I
think
with
that
sort
of
tooling,
we
can
start
to
deploy
blockchains
a
lot
quicker.
A
So
here
are
some
of
the
interesting
lessons
that
we've
pulled
out
of
those
projects,
those
projects
on
the
first
slide
and
the
table
and
those
two
deployments
for
llama
cetera
and
our
loan
fractionalization
yeah
for
us.
Realistically,
most
applications
are
small
they're
going
to
be
less
than
10
nodes,
you're
gonna
be
yeah.
A
A
One
organization
10
peers,
we
will
get
so
I'll
take
them
aside.
We
will
get
sometimes
one
organization
with
multiple
departments.
So,
for
example,
you
know
there
would
be
an
organization
with
three
different
departments
and
you
might
want
to-
and
you
might
want
to
give
each
department
three
peers
in
order
to
create
some
kind
of
fault
tolerance
within
each
unit
in
each
department.
But,
generally
speaking,
our
customers
haven't
quite
worked
out.
B
A
Can
I
get
back
to
that
question
because
I
think
that's
a
very,
very
interesting
question
and
there's
no
there's
not
a
simple
answer
to
that
question:
yeah
the
whole
the
whole
idea
of
how
do
you,
if
I
may,
if
I
may,
there's
a
there's
a
real
question
of
how
do
you
generate
trust
in
the
network
if
you've
only
got
one
organization
signing
and
I
think
that's
a
very
interesting
question,
but
we
I'd
like
to
move
on
and
we
can
get
back
to
that.
If
that's
okay.
A
A
What
do
I
mean
by
that?
It
involves
people
interacting
with
people
mediated
by
our
tech
and
the
mediation
and
the
mediation
can
be
either
through
contracts
as
our
loan
fractionalization,
where
people
are
dealing
with
assets
and
they're,
buying
and
selling
assets
and
splitting
up
assets
and
that's
mediated
through
our
technology.
A
A
It,
what
we're
doing
at
the
moment
is
we're
working
with
the
number
one
coffee
producer
in
Colombia
to
try
and
solve
this
exact
problem
with
their
marketing
team,
and
it
is
still
a
problem
we
have
to.
We
have
to
find
ways
of
showing
people.
This
is
a
socio-technical
system.
Don't
forgive
me
if
the
fine
waves
are
showing
people
that
they
can
trust
what
they're
purchasing,
because
it's
being
validated
or
the
data
that
they're
relying
on
has
been
validated.
A
Following
on
from
that
point,
the
blockchain
is
not
the
center
of
our
universe.
It's
a
part
of
a
larger
system
that
creates
trust
around
the
data
and
in
creating
trust
around
the
data
we
have
to
find.
We
have
to
be
able
to
acquire
the
data.
We
have
to
be
able
to
work
with
that
data.
We
have
to
put
it
on
the
blockchain
and
then
we
have
to
be
able
to
get
it
off
again
and
those
channels
have
to
be
trusted
as
well
as
the
blockchain.
A
A
A
A
When
you
have,
when
you
do
these
kinds
of
deployments,
we're
often
doing
short-term
deployments
they're
exploratory,
we
really
do
need
to
have
good
design
and
sometimes
good
design
patterns
for
these
block
chains.
When
I
say
good
design,
I'm
talking
about
some
good
design
patterns,
especially
when
you're,
integrating
and,
of
course,
the
other
thing
we
would.
We
really
do
want
to
have
his
good,
tooling,
tooling,
that
you
can
actually
rapidly
prototype
with
and
make
things
happen
with
quickly.
A
So
let
me
quickly
think
about
a
little
bit
about
design.
We
need
good
design,
good
design
patterns.
I
haven't
got
any
in
mind
at
the
moment.
I've
got
a
bunch
of
experiences.
Some
of
them
have
worked.
Some
of
them
have
been
a
little
bit
more
interesting,
but
here
are
some
of
the
things
you
have
to
consider
anyway,
a.
A
Lot
of
these
come
down
to
being
able
to
take
the
problem
and
blockchain
arise
it.
Oh,
let
me
let
me
let
me
explain
that
a
lot
of
that
a
lot
of
these
bullet
points
come
down
to
being
able
to
say
if
I
have
to
deal
with
trusted
data
and
I
have
and
I'm
going
to
use
a
blockchain
to
deal
with
that
trusted
data
and
to
hand
people
trust
back.
Then
these
are
some
of
the
design
decisions.
You've
got
to
think
about
a.
A
Couple
of
these
have
caused
me
personally,
a
bit
of
a
bit
of
tension
or
an
up
tension,
but
we've
had
to
grapple
with
them.
We've
had
to
grapple
with
some
of
these
things.
Smart
contracts
are
a
thing
that
we've
actually
had
to
grapple
with,
hopefully
Joe.
As
you
know,
everything
is
a
smart
contract,
and
so
we
have
to
design
smart
contracts
to
put
the
data
on
the
chain.
A
A
Alright,
so
some
customers
will
simply
say:
hey
I,
don't
want
to
know
you
the
blockchain
guys
you
deploy
it,
you
manage
it.
The
risk
is
yours.
We
don't.
We
just
will
give
you
the
data.
You
hand
us
back
the
hashes,
we're
happy.
Other
customers
will
say,
wait
a
minute.
How
do
I
trust
that
you're
doing
the
job
right?
How
do
we?
How
do
we
trust
you,
the
blockchain
company,
that
you
haven't
done
anything,
and
so
we
have
to
say,
okay,
what
will
share
nodes.
A
A
We
haven't
got
too
many
projects.
We
do
that.
Yet
most
of
our
customers
have
been
happy
to
say
you
take.
The
risk
is
here
it
is,
but
we
are
getting
to
the
point
where
people
are
starting
to
call
for
more
transparency
in
the
process
and
if
there
is
transparency
in
the
process,
well,
we'll
let
you
manage
some
of
the
nodes
yourself
and,
along
with
that,
we
have
different
signing
keys
for
different
nodes.
So
we
know
who
signed
what
transaction
and
when.
A
And,
of
course,
we'd
love
to
be
able
to
design
to
requirements.
We
love
to
be
able
to
know
what
we're
doing
most
of
the
time
our
projects,
our
exploratory,
like
the
llama
center
project,
where
the
requirements
aren't
particularly
known
in
advance,
they
emerge
as
the
project
goes
and
again
it
would
be
nice
to
be
able
to
say
right.
We've
got
these
number
of
validator
knows:
we've
got
these
number
of.
We've
got
this
number
of
proposed
or
nodes,
but
it's
often
the
case
of
let's
deploy.
A
A
B
A
And
so
designs,
the
first
of
our
big
issues.
The
second
of
our
big
issues
was
tooling
and
development
tools
are
out
there
p'tee.
You
know
I'd
love
to
have
tools
which,
where
we
can
just
rapidly
configure
and
deploy
test
nets
or
better
still
rapidly
configure
and
deployed
knits
on
customer
sites,
because
that's
what
we
need
to
do.
We
need
to
do
that,
especially
in
this.
A
Where
we're
in
this
exploratory
phase,
we
used
hyper
legend
composer
for
a
while
that
was
nice,
I
believe
that's
deprecated
now,
but
if
we
could
get
if
we
could
get
some
things
like
hyper
ledger,
composer,
we've
called
a
hicap
hyper
ledger
composer.
A
plus
I'll
give
an
A+,
but
if
we
can
get
something
like
hyper
ledger
composed
of
where
we
can
actually
prototype
smart
contracts,
simulate
Network
behavior
get
an
idea
of
what
we're
going
to
deploy
before
we
actually
deploy
it
on
a
customer
site.
Great
that'd
be
great
for
us.
A
And
I
know
that
docker
and
kubernetes
are
already
an
integral
part
of
hyper
ledger,
but
I'm
too
old
to
mess
with
here
I'm
too
old,
to
mess
with
the
Amaral
files
and
if
we
can,
if
we
can,
if
we
can
do
the
same
kind
of
work
and
the
same
kind
of
orchestration,
that
those
tools
do
but
from
a
much
much
friendlier,
much
more
transparent
platform.
That
would
be
great
for
people
like
us.
A
Okay,
oh
and
I
thought
I'd
quickly
show
you
the
kind
of
tool
stack
that
we
use.
This
is
all
of
the
tools
that
we
use,
except
for
the
ones
that
I
haven't
shown
you,
but
it's
a
fairly
vanilla
kind
of
stack
and
in
fact,
we've
kept
it
vanilla.
We've
kept
it
absolutely
simple
for
a
reason,
and
the
reason
is
we
want.
We
want
to
be
robust.
We
don't
want
to
have
any
excitement
in
our
lives.
We've
already
got
too
much.
So
let's
keep
things
robust.
Let's
keep
things
predictable.
A
We've
grappled
with
smart
contracts,
we
don't
deploy
smart
contracts.
In
fact,
we've
tried
I've
tried
to
keep
smart
contracts
or
the
involvement
of
smart
contracts
fairly
simple
in
the
deployments
that
we've
done.
What
am
I
concerns
are
security
and
I
guess
this
is
where
my
security
and
high
integrity
systems
background
kicks
in,
because
when
we
look
at
when
we
look
at
the
sort
of
code
that
we
build
I
can
guarantee
the
state
of
my
hyper
ledger
deployment
at
the
start
of
a
smart
contract.
A
I
can
guarantee
the
post
condition
at
the
end,
but
I
don't
know
what
the
invariants
are
in
the
middle
I.
Don't
know
if
somebody
to
pull
if
somebody
deploys
a
smart
contract
on
our
one
of
our
platforms,
I
can't
guarantee
that
they're
not
taking
data
off
that
platform.
I
can't
guarantee
I,
don't
think
I
can
I,
don't
think
I
can
guarantee
that
we
don't
do.
We
don't
have
anything
else
going
on
in
that
time.
A
A
So
this
is
this,
is
this
is
an
ongoing
thing
as
soon
as
you've
decided
to
put
smart
contracts
onto
a
chain
and
those
smart
contracts
circulate
around
different
nodes,
I've
lost,
if
they're,
not
all,
on
our
system,
that
I've
effectively
lost
control.
That
worries
me
so
we've
been
grappling
with
with
exactly
how
far
we
should
go
down
the
smart
contract
line
and
how
and
where?
A
A
Forward
here
are
some
of
the
things
that
that
we
think
going
forward.
It's
about
contract
development,
dashboards,
some
interesting,
tooling
I-
would
love
to
get
I,
would
love
to
get
some
interesting,
computer-aided
design
tools
into
the
community
so
that
we
can
actually
really
start
to
accelerate
the
way
that
we
deploy
and
do
our
applications
and
I'm
about
to
wind
up.
So
we'll
leave
some
time
for
questions,
but
if
I
could
put,
if
I
could
put
one
desire
or
one
wish
up
there
to
finish.
A
A
Well,
we
would
it's
so
much
of
this
comes
down
to
the
the
user
requirements.
We've
been
working
with
hyper
ledger.
We've
been
working
with
our
own
Penta
Network
we'd
like
to
see
those
block
chains
come
up
platform
blockchain
as
a
service.
Often
simply
ties
you
to
a
platform
and
we
like
to
be
independent.
A
A
A
B
A
A
Let
me
take
it.
Let
me
take
a
leaf
out
of
software
engineering
tool
book,
so
we've
got
good
computer-aided
design
tools,
we
can
visually
layout
software
designs
networks
and
basically
start
to
get
templates
up
and
even
do
some
simulation
work
to
run
through
some
of
the
some
of
the
logic
we
could
do
the
same
here.
A
Rapid
prototyping
tools,
things
that
you
can
a
tools
where
you
can
actually
deploy
very
quickly
and
just
get
an
idea
of
whether
that
network
is
run
simulate
smart
contracts,
hyper
legit,
the
sort
of
things
that
hyper
ledger
composer
was
doing,
but
possibly
could
do
better.
That's
the
sort
of
tooling
I
would
like
to
see
at
the
moment
at
the
moment.
I'm
really,
our
focus
is
really
on
deployment
tools.
A
When
we
operationalize,
we
have
to
move
on
to
operate
operation
or
monitoring
and
dashboards,
but
at
the
moment
it's
mostly
deployment
and
for
your
second
question,
I'm,
just
quickly
having
a
look
at
our
time
here.
Yes,
one
minute,
we
may
have
to
finish,
we
may
have
to
finish
out
in
the
corridor:
gdpr
CCPA
privacy.
A
Yes,
it's
a
good
legislation
or
a
bad
legislation.
It's
here
to
stay,
we
have
to
deal
with
it.
How
can
we
deal
with
it?
Well,
blockchain
gives
us
a
very,
very
good
way
of
dealing
with
it,
and
but
we
have
to
be
very,
very
careful
in
how
we
do
it
and
I
think
that's
our
session
ended
we'll
happy
to
talk
further
in
the
corridor.