►
Description
A virtual meetup hosted by Hyperledger Pune focused on a technical discussion about Hyperledger Fabric and deploying smart contracts.
Speakers
Gari Singh – Hyperledger Fabric Maintainer & CTO IBM Blockchain Platform
Mark Parzagnat - Global Technical Architect lead IBM Blockchain Platform
----
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 #HyperledgerMeetups #Blockchain
A
This
is
a
blockchain
hike
to
production
network
series
organized
by
hyperledger
and
pune
hyperledger
india
and
ibm
also
contributed.
So
in
this
four
week
series
in
the
previous
two
sessions,
we
discussed
about
the
blockchain
production
network
and
globally
in
india
and
sf
as
fake,
and
this
upcoming
two
session.
A
We
have
technical,
deep
dive
in
the
hyperledger
fabric
and
for
this
session
we
have
gary
singh
and
mark
and
the
galician,
having
all
of
you
know,
he's
a
cto,
ibm,
blockchain
platform
and
contributor
and
maintenance
of
the
hyper
fabric
he's
also
a
member
of
technical
string
committee
who
will
direct
the
hyperledger
product,
hyperledger
projects
roadmaps
and
he's
quite
active
in
the
rocket
chat,
hybrid
rocket
chat
fabric
mailing
list
and
I
think
stack
overflow
and
wherever
you
face
any
issue.
So
he
is
going
to
respond
in
the
both
the
platforms.
A
B
Great
thanks
very
much
so
let
me
try
to
share
my
screen
here.
Hopefully,
people
can
can
see
what
I've
got
going
on
here.
All
right
that
is
weird
all
right.
There
we
go.
Can
everybody?
Can
you
guys
see
that
I
guess
I'll
ask
the
moderators
but
yeah
all
right,
so
yeah,
okay
yeah,
so
I'm
only
gonna
take
about
you
know
20
minutes
or
so
so
this
will
kind
of
be.
You
know
a
whirlwind
you
know
pass
through,
but
yeah.
B
So
I'm
gonna
break
this
up
into
two
sections
to
talk
a
little
bit
about
what
we've
got
going
on
on
the
fabric
perspective
and
then
obviously
related
to
fabric.
What
we've
been
doing
on
the
the
ibm
side
from
a
platform
perspective,
I'm
going
to
focus
today
on
the
latter
half
of
the
kind
of
road
map,
I've
kind
of
just
picked
out.
A
couple
of
you
know
kind
of
key
features.
My
assumption
is,
most
people
know
fabric.
B
B
B
So
we
actually
I'm
going
to
talk
about,
like
I
said
private
data,
but
we
actually
have
put
out
several
updated
samples
on
how
to
use
some
of
the
more
advanced
capabilities
of
a
fabric
in
terms
of
privacy,
endorsement
policies
that
are
actually
really
relevant
for
tokens.
Token
swaps,
asset
transfers,
so
those
are
all
under
you
know:
github.com
hyperledger
fabric
samples,
so
I'm
gonna
cover
those
today
and
then
I'll.
Just
give
you
a
quick,
a
quick
thing
on
what
we've
got
coming
on
the
on
on
the
future
side.
B
B
You
know
just
enhancing
our
current
capabilities,
we'll
be
taking
a
look
at
some
options.
Around
bft
from
an
ordering
service
perspective.
I'll
talk
about
raft
a
little
bit
later.
One
big
you
know
feature
that
we
have
coming.
You
know
one
of
the
things
that
wasn't
a
problem
but
becomes
a
problem.
Now
that
we
have
a
lot
of
people
actually
running,
you
know
real
networks
is
ledger,
checkpoint
and
pruning,
so
we
need
the
ability
for
people
to
basically
kind
of
checkpoint
and
archive
their
ledger.
B
B
B
B
But
it
does,
it
does
kind
of
mess
things
up
a
bit,
but
hopefully
that'll
stop
yeah
with
that
being
said,
I
will
you
know,
move
move
forward
here,
so
you
know
what
have
we
been
doing?
Some
from
you
know,
what
are
the
key
things
that
I
wanted
to
highlight
from
you
know
fabric
you
know
2.x,
so
one
just
a
refresher
for
for
people
who
may
not
be
familiar
with
fabric,
the
the
quick
and
dirty
view
fabric
has
a
unique
model.
I'd
say
from
a
perspective
of
how
we
process
transactions.
B
We
essentially
have
what
we
call
endorsements
endorsements
are
essentially
a
set
of.
You
know:
policies
really
signatures
who's
required
to
actually
agree
on
the
result
of
on
the
result
of
a
transact,
a
smart
contract
execution
and
really
the
output
of
a
smart
contract
is
a
state
change
right.
So
really,
what
we're
talking
about
is
updating
some
type
of
state
somewhere
and
we
will
have.
We
can
have
policies
that
are
that
are
actually
set.
B
You
know
on
the
chain
code
level,
I'll
talk
a
little
bit
later
about
a
few
other
enhancements
that
we've
made.
You
could
also
set
policies
on
state
and
now
one
of
the
other
new
features
that
I'll
talk
a
little
bit
about
on
the
private
data
side
is,
we
can
actually
set.
We
can
actually
set
policies
on
kind
of
collections,
so
endorsements
collect
that
up
that
all
happens
before
we
actually
commit
anything.
B
We
send
that
to
the
order
and
then
the
order
will
send
it
to
the
peers,
and
then
we
will,
you
know,
execute
our
commit
right,
which
will
basically
validate
the
transaction,
make
sure
it's
well
formed.
It
actually
checks
your
endorsement
policy
at
that
time.
So,
if
you
didn't,
if
you
didn't
have
enough
people
agree,
according
to
the
policy
agree
on
the
result,
we
will
not
commit
the
state
change
and
then
we
have
the
ability
to
send
out
events
so
that
the
reason
I
mention
that
here
is
that's
important.
B
One
thing
that
I
like
to
highlight,
because
I'm
not
sure
you
know
I'm
sure
most
people
are
aware
of
this,
but
again
a
lot
of
people
started
earlier
when
fabric
first
came
out
for
a
distributed
fault,
tolerant
kind
of
order.
We
were
using
kafka.
We
still
support
that,
although
you'll
notice
in
the
2.x
release
notes
that
we've-
actually,
you
know
deprecated
support
for
kafka,
so
once
we
get
to
like
the
3.x,
you
know
releases
sometime
next
year.
That
would
go
away
on
the
good
news
side.
B
B
B
You
know
multiple
ledgers,
if
you
will
in
the
old
architecture,
while
we
could
support,
you
could
actually
have,
for
example,
a
peer
and
that
peer
could
actually
communicate
with
channels
from
multiple
ordering
services.
Typically,
you
know
people
ended
up
building
a
single.
You
know
somebody
running
an
order
or
a
set
of
ordering
nodes,
and
then
that
would
manage
you
know
all
the
different
channels.
B
You
know
on
that.
I
will
reside
an
interesting
feature
that
when
we
started
looking
at
from
a
a
raft
perspective
is
that
while
there
can
still
be
a
single
cluster
of
raft
nodes,
so
you
can
do
the
normal.
You
know
raft
is
a
two
f
plus
one
for,
however
many
faults
you
want
to
support
faulty
nodes.
You
want
to
support,
you
know,
figure
out
the
total
number
you
need.
So
if
you
want
one
faulty
node,
it's
two
f
plus
one
which
equals
three
you
can.
B
You
can
I'm
sure
everything
we
did
in
math,
but
you
know
you
may
get
to.
Let's
say
you
wanted
three
faulty
nodes,
you
get.
You
know
seven
nodes.
The
interesting
thing
that
we
added
in
with
the
raft-based
stuff
is
that
on
a
per
channel
basis,
even
if
I
have
in
this
case
six
but
let's
just
say
I
had
seven
raft
nodes,
you
actually
have
the
ability
to
distribute
channels
across
different
clusters,
different
subsets
of
those
raft
nodes.
B
So
this
is
one
of
the
you
know,
big
things
that
I
like
to
highlight
this,
because
I'm
not
sure
a
number
of
people
are
aware
of
this
moving
forward.
Actually,
in
our
you
know,
in
the
2,
maybe
it's
2.3
release,
which
will
probably
be-
I
guess
it
is
fourth
quarter
now
so
likely,
sometime
in
late
october
or
november,
some
somewhere
in
the
somewhere
in
mid
I'll,
say
mid
to
late.
You
know,
fourth
quarter,
we're
actually
gonna.
B
So
from
this
perspective,
you
could
actually
have
a
single
ordering
node
and
it
can
be
actually
be
part
of
multiple
raft
clusters
and
those
raf
clusters,
don't
know
about
each
other.
So
this
is
a
pretty
you
know
again,
a
pretty
powerful
feature
and
again,
you
know,
starts
to
move
us
away
from
this
notion
of
saying,
hey
that
we
have
a
even
though
we
have
the
distributed
ordering
service,
it
was
still
kind
of
a
centralized
piece
right.
There
was
still
this
ordering
service
that
all
peers
kind
of
talked
to
in
this
model.
B
You
could
actually
get
to
the
point
where
every
organization
could
actually
run
a
peer
and
an
order,
a
note,
and
you
could
actually
join
up
with
different
organizations
and
parties
without
having
to
go
through
a
central
administration
of
an
overall
ordering
service.
So
that
feature
there's
a
rfc
out
there
in
the
fabric
dash
or
hyperledger
github.com
hyperledger,
slash
fabric.rfcs.
B
B
And
this
is,
you
know
you
can
you
can
obviously
architect
things
in
ethereum
to
you
know,
have
a
have
a
something
that
manages
state
and
then
a
contract
around
that
that
calls
the
state
and
then
you
can
use.
You
know
the
naming
service
to
create
a
new
contract
that
calls
the
same
state,
but
you
have
to
you
know,
think
about
that.
You
know
well
in
advance
with
with
fabric
we've
always
had
the
ability
to
actually
update
chain
code
right.
B
We
had
a
kind
of
a
separation
between
the
the
chain
code
and
it
maps
to
an
actual
namespace
right.
So
the
data
would
stay
persistent
in
the
namespace,
but
you
could
actually
upgrade
the
version
of
the
chaincode
and
then
you
can
actually
change
the
policy
around
chaincodes
as
well
right.
You
could
actually
say
that
for
this
particular
chaincode
it
requires
you
know
three
out
of
five
members
to
actually
sign
or
endorse
it,
but
there
were
if
there
were
a
few
gaps.
B
You
know
in
that
there
was
kind
of
a
super
admin
and
a
few
other
things
within
within
the
2.x
life
cycle.
We
actually
have
we've
actually
adopted
a
model.
That
is
way
more.
That
is
much
more
like
the
channel
model.
So
from
from
that
and
I'll
have
a
few
charts
on
this,
but
but
essentially
you
actually
have
to
collect
a
number
of
signatures
to
actually
deploy
or
instantiate
whatever,
whatever
you
want
to
call
it
of
an
actual
chain
code.
This
is
this
is
a
so
this
is
good.
B
You
can
of
course,
go
back
the
same
policy
of
any
admin
can
do
it
if
you
want
that,
but
now
you
can
actually
say
hey
before
a
chainco
new
chaincode
version
gets
deployed.
I
actually
need
you
actually
will
be
required
to
have.
You
know
this
many
signatures
the
default
is
defined
on
the
channel
level.
B
Oh
also,
you
had
to
have
technically
you
had
to
have
the
exact
same
bits
and
bytes
deployed
which
was
kind
of
a
difficult.
If
you
didn't,
you
know,
build
everything
the
same
way.
So
what
we
did
in
200
is
we
actually
separated
this
all
out.
So
in
theory,
it's
actually
possible
to
have
the
same
chain
codes
for
the
same
same
logic.
You
could
actually
three
different
people
could
have
it
written
in
three
different
languages.
C
B
Other
kind
of
key
thing
that
we
added
was
now
you
can
update
endorsement
policy
without
having
to
update
the
actual
chain
code
itself,
so
this
is
actually
a
very
powerful
construct
as
well
and
again.
Approving
that
is
is
a
workflow
that
can
again
require
multiple
signatures.
So
in
the
current
case
a
single
party
could
actually
update
the
endorsement
party,
the
endorsement
policy
in
the
new
model.
You
can
actually
restrict
that
to
say
that
again,
it
must
be
a
majority
of
the
of
the
channel
admins.
B
The
other
thing
that's
not
on
here
is:
we've
always
had
this
on
the
on
channel
policies,
so,
for
example,
on
a
channel
you
could
actually
say
that
for
to
update
the
to
update
the
channel
information
required
a
majority
of
things,
and
then
you
know
so
majority.
If
you
had
five
members,
it
would
dynamically
calculate
a
majority
as
being
three
out
of
five.
If
you
added
seven,
you
could
still
keep
majority
and
it
would
be
you
know,
four
out
of
seven
and
so
on
and
so
forth
within
chain
code.
It
was
always
explicit.
B
So
if
there
were
so,
if
you
wanted
three
out
of
five,
you
would
literally
say
three
out
of
these
five
and
it
was
a
static
definition.
So
if
I
added
two
more
members
to
the-
and
that
was
you
know,
you're
trying
to
your
goal
is
majority.
If
I
added
two
more
members
to
the
channel
and
deployed
the
chain
code
to
them,
the
endorsement
policy
was
still
actually
three
out
of
five
and
then
you'd
have
to
actually
update
the
endorsement
policy.
With
the
life
cycle,
we
actually
again
have
the
the
the
notion
of
majority.
B
Can
work
or
you
know
other
other
things
like
it.
So
in
that
particular
case
it'll
always
be
it's
dynamically
calculated
based
on
actual
channel
membership.
So
that's
you
know.
That
was
one
of
the.
I
think
big
innovations
for
us.
A
big
big
kind
of
update
that
we
made
and
again
I
like
to
you,
know,
call
these
out,
because
I
think
these
become
important
points
as
logic
goes
on
I
mean
this
is
probably
one
of
the
you
know.
B
Most
people,
we
do
see
people,
you
know
adding
members
and
networks
kind
of
growing,
but
a
majority
of
stuff
is,
you
know,
adding
new
chain
code,
updating
new
versions
of
chain
code,
because
rules
change
logic,
change
may
have
had
an
error
and
again
we
think
that's
one
of
the
key
differentiators
for
us
I'll
just
go
through
this
kind
of
quickly.
We
have
a
new.
B
A
new
package
command
packages
are
now
actually
much
simpler,
underneath
the
covers
they're,
actually
just
standard
gzip
files
or
both
tar
tar
balls
with
a
gzip
tar
files.
So
again
it
becomes
much
easier
for
people
if
you
want
to
actually
open
it
up
and
inspect
it
before
before.
These
were
serialized
protobufs,
which
was
a
pain
again.
We
still
have
the
install
operation.
The
nice
thing
on
install
is
that
it'll
actually
build
your
chain
code.
First
now
we
used
to
have
this
error.
B
Some
people
might
have
noticed
you
could
install
your
chain
code
and
then
someone
might
try
to
instantiate
it
and
it
might
fail
on
instantiation,
because
I
don't
know
you
were
missing
a
dependency,
something
wrong
with
your
machine
out
of
resources.
So
now
on
install,
we
will
actually
do
a
build
as
well
to
verify.
So
you
will
know
immediately
whether
or
not
you
have
an
error
or
issue
with
the
chain
code.
B
We
then
have
the
ability
to
once
it's
installed.
All
members
must
approve
the
chaincode
definition.
I'll
explain
how
this
works,
but
essentially
the
underlying
functionality
here
is
a
set
of
kind
of
private
data
collections
that
are
tied
to
individual
organizations,
which
are
we
call
those
implicit
implicit
collections.
You
don't
need
to
define
them
on
the
fly
and
this
this
basically
allows
the
ability
for
you
to
basically
collect
votes
across
the
blockchain.
B
Finally,
once
there's
enough
enough
signatures
meeting
the
policy,
somebody
can
commit
the
chanco
definition,
and
now
this
would
be
similar
to
instantiate
and
then
on
upgrade
go
through
the
same,
go
through
the
same
process.
Right,
if
you
needed
to
and
again
this
can
be
done
for
again,
you
don't
necessarily
have
to
repackage
the
chain
code.
You
could.
B
Actually,
you
know
you
could
actually
just
be
updating
policies
as
well,
and
so
I
know
I'm
going
to
give
mark
some
time,
so
I'm
just
going
to
go
kind
of
through
this
kind
of
quickly
but
another.
This
was
another
kind
of
big
feature
that
I
wanted
to
sort
of
call
out
and
the
reason
why
I
mention
these
is
because
these
really
expand
the
realm
of
use.
Cases
that
you
can
actually
do
so.
B
The
other
thing
I
should
mention
is
that,
with
private
data
collections,
you
know
you
always
kind
of
had
to
know
membership
ahead
of
time.
Those
were
all
sort
of
deployed
out
there
and
you
could
run
into
a
you
could
run
into
a
interesting
issue
that
you
still
had.
You
still
would
have
to
have
enough,
because
endorsement
policy
was
essentially
set
at
a
chain
code
level
for
collections
or
private
data
in
in
1.4.x
life
cycle.
B
You
actually
have
to
make
sure
that
you
still
end
up
with
enough
endorsers,
even
if
there's
not
enough
people
in
the
collection,
which
is
tricky
as
well
so
within
within
the
2.x
model,
actually
within
2.x,
actually
doesn't
even
matter
on
the
life
cycle.
We
actually
added
the
ability
to
now
have
endorsement
policies
on
collections,
so
now
you
can
actually
create
a
private
collection,
and
a
collection
is
really
for.
Those
who
don't
know
is
really
a
subspace
within
within
within
a
ledger
right.
B
So,
while
a
legend
may
have
ten
members,
you
may
create
a
collection,
a
kind
of
a
private
collection
and
that
private
collection
may
only
contain
three
out
of
the
out
of
the
ten
members.
So
now
we
can
actually
set
the
endorsement
policies
on
the
collection
levels
themselves.
So
again
this
this.
This
really
helps
to
enhance
your
overall
of
privacy,
because
now
I
don't
ever
have
to
send
it
to
any
peer
that
didn't
have
a
need
to
know
for
the
data.
B
And
now,
if
I
needed
to
share
the
actual
data
with
somebody
else,
I
can
now,
you
know
either
add
somebody
to
that
collection
or
I
can
move
it
to.
I
can
move
it
to
another
collection,
but
the
proof
of
that
that
it
was
correct
is
still
from
the
hash
that
you
that
you
had
existing
in
your
actual
up
for
the
for
the
collection,
the
implicit
collection,
even
if
you
didn't
have
the
data.
So
this
allows
you
to
do
that.
More
sort
of
selective
reveal
that
you
know
that
you
can.
B
You
can
actually
add
people
kind
of
to.
You
can
actually
grant
access
to
a
specific
piece
of
kind
of
state
via
this
moving
across
kind
of
collection
model,
and
that's
really
the
that's
really.
What
this
one
kind
of
just
shows
you
about
is
this.
This
kind
of
this
is
the
next
ability
here
right,
because
the
hashes
are
all
there.
You
now
have
smart
logic
that
says
hey.
I
want
to
give
you
I
want
to
in
your
chain
code.
B
It
would
just
be
kind
of
a
transfer
model,
and
you
would
you
would,
of
course,
always
select.
You
know
what
collection
it
came
from.
You
could
verify
that
the
values
were
correct
by
the
hash
and
the
chain
code
itself,
because
you
have
you
have
access
to
get
those,
and
now
you
have
access
to
the
real
estate
in
a
new
collection
which
now
contains
multiple
members,
and
you
know.
Lastly,
this
is
more
for
people
who
are
operators
out
there.
B
You
know
we
have
a
lot
of
people
who
want
to
run
stuff
on
a
hyperledger
fabric
on
kubernetes,
one
of
the
big
one
of
the
things
that
we
found
was
chain
code
always
required.
Docker
and
for
a
while
this
was
okay,
you
could
use
some
tricks,
like
you
know,
by
mount
the
the
docker
socket
on
a
kubernetes
node.
Of
course
this
becomes
problematic
when
you
move
to
modern
versions,
later
versions
of
kubernetes
that
no
longer
use
the
docker
socket.
B
So
then
you
have
to
go
to
things
like
running
docker
and
docker,
or
you
know
remote
docker
host
anyway.
Needless
to
say,
we
now
have
support,
for
you
know
external
chain
code.
People
can
build
custom
builders
that
you
can
choose
to
basically
launch
and
launch
your
chain
code.
However,
you
want
to,
however,
you
want
to
you,
could
choose
to
launch
it
as
a
pod.
You
could
choose
to
launch
it
as
a
binary
executable.
You
could,
you
know,
build
it.
However,
you
want
and
launch
it.
B
So
that's
that
and
then
I'm
just
going
to
go
kind
of
quickly
through
through
here
a
little
little
plug
for
ourselves.
So
on
the
mark's
going
to
talk
about
the
use
cases
here,
so
I
won't
get
into
that.
But
you
know
a
lot
of
what
we've
learned
and
built
from
and
in
the
platform,
and
what
mark
will
talk
about
too?
As
contracts
comes
from,
you
know
all
these
networks
and
customers
that
we've
been
working
with
over
the
years.
B
I
just
want
to
highlight
real
quickly
what
we
do
from
a
you
know
ibm
perspective.
So,
as
I
mentioned,
there's
a
lot
of
policies
in
fabric
right,
channel
policies,
endorsement
policies,
adding
orders,
removing
orders
managing
specifications
et
cetera.
So
what
we
chose
to
do
from
the
kind
of
blockchain
platform
perspective
was
really
was
really
built,
something
that
that
was
designed
to
facilitate
the
same
use
of
your
same
hyperledger
fabric
code.
B
So
we
don't
change
hyperledger
fabric,
it's
just
open
source
fabric,
but
we
wanted
to
offer
a
whole
bunch
of
governance,
management
and
operational
capabilities
so
and
you'll
notice
that
probably
why
some
of
the
stuff
that
we
do
that
you
know
is
on
the
kubernetes
we've
just
seen.
Most
people
wanted
to
use
kind
of
kubernetes.
B
So
just
a
couple
of
things,
many
people
think
so
I
like
to
dispel
a
few
myths.
One
we
only
use.
We
don't
build
a
special
version
of
fabric,
we
actually
just
fabric
itself,
we
compiled
from
from
from
pure
hyperledger
source
code
hyperledger
fabric
source
code.
We
have
allowed
our
platform
now
to
run
anywhere
on
any
type
of
kubernetes
platform,
so
you
can
run
it
on.
B
So
you
know
this
was
really
the
the
kind
of
deploy
anywhere
model
we
really
wanted
to.
We
think
kubernetes
is
the
way
forward.
It's
just
the
easiest
way
to
orchestrate
all
the
different
components
you
need
and
again
this
really
just
says
that
you
can
move
around
from
from
cloud
providers
to
container
providers
etc.
B
There's
no
there's
no
lock-in,
and
even
if
you
started
on
you
know,
and
even
from
the
perspective,
if
you
started
with
ibm
our
stuff,
if
you
truly
wanted
to
move
away
from
us
to
somebody
else
again,
you
can
just
connect
up
fabric
nodes.
Add
a
new
or
you
know
you
can
do
things
like
add
new
ordering
nodes,
remove
the
old
ordering
nodes
you
know
set
up
a
new
pier,
have
it
go
talk
to
and
the
existing
or
the
new
ordering
service
and
you're
basically
ibm's
out
of
the
way
from
a
tooling
perspective.
B
You
know
I
we've
been,
you
know:
we've
been
putting
out
visual
studio
code,
again,
visual
studio
code
itself,
our
our
plugin
for
visual
studio
cloud
code
is
open
source.
It
works
with
both
ibm
blockchain
platform
and
whatever,
whatever
other
hyper,
electro
fabric
images.
You
want
to
work.
It
allows
you
to
quickly
iteratively
test
and
you
know,
develop
and
test
smart
contracts
on
we.
If
you
you
know,
if
you
use
our
platform,
we
provide,
you
know
full
support
for
it.
B
If
not
it's
you
know
open
source
community
based
and
then
you
know,
lastly
I'll
focus
on
oh.
This
is
really
just
kind
of
where
we
allow
you
to
see
everything
you
can
maintain.
You
know
credentials
maintain
your
nodes.
You
can
choose
to
deploy
peers
cas
orderers.
You
can
manage
nodes
that
are
remote
from
here.
B
So
that's
really
what
we've
kind
of
focused
on
on
the
overall
kind
of
operator
perspective.
The
latest
capabilities
that
will
be
coming
soon
are
really
around
governance
and
the
chain
code.
The
fabric
20
chain
code
lifecycle,
I
mentioned
as
you
can
see,
it
requires
you
to
collect
a
bunch
of
signatures
and
workflow
same
thing
for
channels,
so
we
have
the
ability
for
consoles
to
connect
to
other
consoles
and
basically
collect
all
of
those
signatures
and
make
things
easy
for
you
to
do,
and
you
know
the
the
top
features
I'll
just
call
out.
B
So
we
added
in
support
for
raft.
So
again,
while
while
we
have
the
ability
to
add
remove,
you
know
raft
nodes
within
fabric,
as
we
mentioned.
Some
of
these
can
be,
you
know,
you
know,
there's
some
complexities
there.
So
we've
built
nice
sort
of
tooling
around
that
we
generally
tend
to
stay
on
the
latest
versions
of
fabric.
You
know,
as
they
come
out
and
I'll
adopt
them
in
there
we're
on
147
and
211.
Now
we'll
move
to
149
and
221.
B
B
A
B
B
B
So
when
it
sort
of
connects
back
you
could
you
could
possibly
combine
the
feature
of
creating
chain
code
as
a
server
with
that,
and
if
you,
if
you
had
load
balancing,
you
might
be
able
to
load
balance
against
it,
but
nobody's
ever
really.
I'm
we've
never
really
tried
that,
but
yeah.
We.
We
realized
that
there's
kind
of
a
one-to-one
binding
of
a
chain
code
to
cinco
to
appear
due
to
the
way
that
it
connects
up
to
it.
Okay,
okay,.
A
B
B
So
essentially
we
take
a
dump
of
the
latest
values,
the
latest
the
current
values
of
every
key
in
the
state
database,
and
we
essentially
take
a
dump
of
that
create
a
hash
for
that,
and
then
we
actually
use
that
hash
as
the
beginning
of
a
kind
of
a
new
checkpoint
block.
So
once
you
have
that
you
can
then
archive
all
the
rest
of
the
blocks
prior
to
that
block,
you
know
you
might
want
to
keep
them
around,
but
from
all
practical
purposes
you
get
a
new.
It's
essentially
a
new
genesis.
B
A
Okay-
and
so
I
have
my
personal
questions
because
I
have
using
fabric
from
last
four
years-
is
starting
with
0.5,
while
working
with
ibm.
So
there
are
a
couple
of
rfcs
like
there's
a
modular
crypto
module,
like
suppose,
currently
suppose
the
ssh
256
or
some
kind
of
that
one.
So
when
the
it
will
support
the
different
crypto
modules.
B
B
Yeah,
I
think
so
we
kind
of
I
mean
we
sort
of
have.
We
obviously
had
that
m14,
but
it
didn't
work
out
as
well.
So
yeah
we
have
to
go.
That
rfc
requires
a
a
bunch
of
work
to
actually
go
through
and
figure
out
where
we
want
to
where
all
the
different
plug
points
are.
If
it's,
if
it's
specific
to
just
like
the
signing
and
stuff
like
that,
that's
a
little
bit
easier.
B
It
gets
more
complicated
if
people
want
to
change
things
for
like
tls,
but
yeah
I'd
expect
us
to
wrap.
You
know,
I'd
expect
a
design
in
the
next
couple
months
and
then
hopefully
it's
going
to
be
too
hard
to
to
implement
yeah,
and
if
you
have
specific,
you
know,
features
or
whatever
that
you're
sort
of
looking
at,
because
also
it
may
be
possible
to
actually
just
add.
B
Yeah
I
mean
there's
ursa,
but
that's
really
more,
like
the
implementation
side
yeah.
I
think
the
other
thing
we're
looking
at
is
you
know
one
other
module.
We
support.
You
know
the
pkcs11
stuff,
but
obviously
we
only
support
that
underneath
for
the
standard
crypto
that
we
have
we're
looking
at,
maybe
one
other
option
where
we
might
just
abstract
out
the
to
make
calls
to
sign
so.
A
A
B
A
B
Oh,
the
the
which
one,
the
wasm
support
or
the
yeah
so
yeah
that
one
so
we're
we're
also
doing
another
experiment
on
the
wasm
side
to
to
see
to
plug
it
in
first,
we
want
to
check
out
also
plugging
it
in
where
we
used
to
have
plugins.
So
we
have,
like
you
know,
validation,
plugins,
endorsement,
plugins,
etc.
So
that
should
we're
gonna
start
kicking
that
work
off
soon
too.
B
The
problem
with
you
know
wasm
is
just
making
sure
that
we
can
actually
that
it
can
stand
up
under
concurrent
use
and
things
like
that.
So
but
again,
I
I
expect
that
over
the
next
few
months,
that
that
should
that
that,
should
you
know
mature
more
for
us,
I'm
a
big
fan
of
it.
It'll,
probably
end
up
being
rust.
First
go:
go
is
trickier
right,
maybe
rust
and
assembly
script,
probably.
B
Yeah
I
mean
it
turns
out,
we
don't
really
it
turns
out.
We
don't
necessarily
really
even
need
fab
token.
I
think
that
was
a
you
know.
I
think
we
you
know
tried
it
out.
We
probably
never
should
have
released
it.
I
think
I
would
you
know,
advise
people
to
kind
of
take
a
look
at
the.
So
what
we're
really
doing
is
doing
a
lot
more
of
showing
people
how
they
can
actually
do
assets
and
tokens
with
fabric.
B
I
think
we
threw
people
off
when
we
didn't
when
we
said
fab
token,
and
then
you
know,
I
think
if
you
know
as
any
gaps
come
up,
you
know
you
know
if
we
need
to
add
anything
in
validation,
we
will
so
I
don't
think
we
will
actually
have
anything
called
fab
token
per
se.
Again,
I
think
it's
you
know
we
looked
at
it
as
saying
hey,
look.
We
actually
have
most
of
the
building
blocks
here,
and
especially
some
of
the
stuff
that
we've
now
added
on
the
privacy
side.
B
A
B
B
Side,
yeah
yeah
I
mean
we
just
make.
I
mean
we,
maybe
we
may,
but
I
guess
there's
no
commitment
right,
more
or
less.
It
just
says
that
we
won't
be.
You
know
we're
not
committing
to
going
back
and
fixing
you
know
to
fixing
bugs
on
there.
I
think
you
know
people
really
probably
should
start
moving
forward
to
to
2.x,
but
it's
an
important
point.
Actually
you
bring
up
right.
I
think
you
know
one
piece
of
advice
I
have
for
people.
Is
you
really
need
to
keep
moving
forward
with
fabric?
B
You
know,
I
think,
getting
stuck
on
older
versions
right
you
have
to.
You
have
to
always
think
about.
You
know
point
in
time
and
then,
where
you're
going
right
and
what's
going
to
be
around
by
when
you
get
there
right,
I
think
sometimes
people
start
out
on
a
project
and
then
it's
like
three
or
four
months
and
we
might
already
have
another
release.
We
are
gonna
slow
down
a
little
bit
on
like
you'll,
see
like
on
like
2.x
like
so
like,
for
example,
we
probably
rushed
two
one
and
two
two
we
well.
B
We
wanted
to
get
that
long-term
support.
So
that's
why
2-2
came
out,
but
we
were
doing
quarterly.
We're
probably
no
longer
going
to
do
quarterly.
You
know
it'll,
probably
be
every
four
to
five
months
with
like
previews
in
between
you
know.
We
found
that
you
know
people
like
to
pick
up
collections
of
features
at
a
time
rather
than
incremental
features
and
plus
you
know,
we
don't
want
everybody
to
have
to
upgrade
like
every
every
every
every
month.
Right.
A
B
Yeah,
although
it's
I
mean
most
of
the
stuff's
compatible,
still
compatible
right,
even
moving
to
2.x
right,
that's
in
there,
but
I
just
think
yeah
I
mean
if
you
can
keep
you
know
on
some
of
the
keeping
up
with
some
of
the
improvements,
but
even
you
know
I
I
think
moving
it
even
on
those
sort
of
you
know,
1-4
and
whatever
you
know
timeline,
but
I
think
people
should
start
moving
to
you
know
2.x.
You
know
at
this
point.
A
A
C
Hey
everybody
yeah
a
lot
of
great
conversation
and
everything
in
there.
I'm
just
gonna
kind
of
feed
off
of
what
gary
was
talking
about
a
bit
and
show
show
you
in
an
accelerated
fashion,
how
to
actually
get
started
really
quickly
with
using
hyperledger
fabric
and
as
gary
showed,
we
have
that
that
chart
that
stack
architecture
that
has
hyperledger
fabric
at
its
core
in
the
ibm
blockchain
platform
of
that
set
of
tools
and
and
the
abilities-
and
he
touched
on
ansible
he
touched
on
the
vs
code.
C
I
want
to
talk
about
that
entire
end-to-end
story
a
bit.
So
first,
I'm
going
to
show
you
a
little
bit
about
the
ibm
blockchain
platform.
So
you
can
see
it
kind
of
live,
so
I'm
running
live
here.
Then
I'll
show
you
some
of
the
front
end
and
then
I
will
show
you
some
of
the
back
end
pieces
to
to
really
complete
that
entire
story,
and
so
here
is
exactly
what
gary
was
showing
on
a
couple
of
slides.
Let
me
actually
try
to.
C
Hopefully
this
doesn't
get
too
bad,
but
I'm
going
to
decrease
this
a
little
bit.
So
this
is
an
active
live
running
network.
Gary
showed
a
slide
that
had
one
specific
set
of
nodes
in
here,
you
can
see
all
of
the
fabric
nodes
that
make
up
a
hyperledger
network.
A
hyperledger
fabric
network
are
here
and
available
to
create,
so
you
can
just
simply
add
whatever
particular
node
that
you
want
to
to
your
organization
and
it's
simple
a
few
clicks
of
a
button.
C
You
can
select
if
you
want
to
use
an
hsm,
your
particular
resources
that
you're
going
to
allocate
to
the
containers
of
the
ca
and
all
of
the
the
regular
database
settings
and
then
simply
do
a
click
add
here
and
it
will
go
out
and
deploy
wherever
you're
doing.
That
and
again
you
can
deploy
this
anywhere.
So
you,
as
gary
said
you
can
deploy
this
on-prem.
You
can
deploy
it
on
any
kubernetes,
1.15
or
higher.
C
So
you
know
aks
eks
wherever
you
want
to
go
and
we
have
the
ability
to
not
only
see
the
peers,
but
you
can
check
out
all
of
the
channels
and
all
of
the
information
that's
associated
say
in
these
particular
channels,
including
the
members
on
the
channel.
You
know
the
ordering
service
that
it's
connected
to
so
on
and
so
forth
and
again
I'm
talking
really
fast,
because
I
know
that
we're
running
out
of
time,
but
you
can
see
all
of
the
smart
contracts
that
you
have
installed
and
instantiated.
C
It
also
gives
you
a
nice
little
flag.
As
gary
was
saying.
One
of
the
features
and
and
great
things
about
fabric
is
that
you
can
update
the
contracts
independent
of
the
other
pieces
so
right
here
it
tells
you
that
you
have
an
installed
contract.
That
is
above
the
version
that
you
have
instantiated,
so
you
can
simply
click
that
and
move
those
up.
You
have
all
of
your
identities
in
your
wallet
and
all
of
your
msp.
Yes,
I
know
everybody
loves
msp
as
a
name,
and
here
they
all
are
so.
C
This
is
exactly
where
gary
was
saying
you
can
you
can
bring
in
the
nodes
and
look
into
specific
consoles
and
gather
all
of
your
nodes
that
you
have
access
to
and
actually
see,
what's
happening,
you
do
that
by
downloading
the
connection
profile
and
then
importing
it
into
that
other
console.
So
it's
really
simple
really
easy
to
use,
and
you
can
see
how
quick
it's
done
now.
We
have
a
bunch
of
information
here
under
getting
started.
C
I
would
say
if
you
kind
of
go
into
the
development
piece
and
the
deploy
piece
of
the
smart
contracts,
then
you're
really
kind
of
thinking
in
that
developer
mindset
and
a
lot
of
good
information
and
videos.
Here
and
then
here's
your
operator
type
of
pieces
of
how
you're
actually
going
to
build
your
your
network
out
how
you're
going
to
manage
it,
how
you're
going
to
continue
to
operate
and
and
grow
your
resources
along
with
your
actual
consortium.
C
So
that's
a
quick
run
through
on
the
platform,
and
so,
if
you
think
about
what
you're
doing
here,
you're
getting
an
easy
to
use
tool
set
to
manage
everything
that
you
want
to
do
with
with
the
untouched
unaltered
hyper
ledger
fabric
code
base
that
we
build
upon.
Not
only
that
but
you're
also
getting
people
like
gary
standing
side
by
side
with
you
supporting
your
efforts
as
you're
moving
down.
C
So
it's
a
big
big
deal
when
you
have
folks
that
have
the
knowledge
no
fabric
inside
and
out
to
to
be
standing
along
and
helping
you
on
your
journey.
So
this
is
what
I
would
consult:
consider
kind
of
that
that
middle
to
the
the
right
side
or
the
operator
to
the
grow
side
of
the
journey.
I
want
to
talk
a
little
bit
about
the
beginning
side.
So,
as
we
were
talking
about
earlier,
you
have
the
vs
code.
C
Extension
here
is
the
vs
code
extension
with
one
of
our
quick,
starter
or
accelerators
that
we're
calling
our
blockchain
accelerator
patterns
or
or
whatever
you
want
to
may
call
it.
These
are
real
little
applications
with
the
chain
code
and
everything
you
need
to
get
a
sample
up
and
running,
and
so
you,
you
can
get
the
chain
code.
You
can
get
the
app
you
can
just
run
it
locally.
You
can
connect
it
to
ibm,
blockchain
platform
network
or
or
whatever
you
want
to
do,
and
it's
really
easy
to
to
do.
C
When
you
get
the
code,
you
usually
have
your
your.
You
know.
You've
got
your
client
side.
You've
got
your
server
side,
you
get,
as
I
mentioned,
all
of
the
basic
chain
code
and
a
lot
of
it
uses
the
same
thing.
That's
kind
of
built
out
when
you
use
the
vs
code.
Extension
tutorials
when
you're.
If
you've
not
used
the
vs
code
plug-in.
Yet
you
you
do
a
couple
of
things.
The
first
thing
it
does.
Is
it
downloads
an
entire
version
of
hyperledger
fabric
and
it
runs
it
on
your
local
machine?
C
So
this
gives
you
the
ability
to
create
smart
contracts
iterate
on
it,
continue
to
submit
transactions
to
your
local
environment,
get
it
right
and
then
you
can
connect
your
extension
to
an
external
network
that
can
be
a
a
fabric,
native
fabric
community
edition
or
the
ibp
network,
and
then
you
can
install
and
instantiate
the
chain
code
from
there
and
submit
transactions
against
that.
So,
if
you're
thinking
from
a
developer
standpoint,
this
is
your
front
end
or
your
beginning
point
of
where
you're
going
to
start
to
actually
do
real
things
going
through
that
tutorial.
C
I
would
say
it's
going
to
probably
take
you
about
35
to
minutes
to
an
hour
to
go
through,
because
it's
going
to
walk
you
through
all
of
these
different
functions
right,
you
know,
query
an
asset.
Do
you
know
check
your
assets?
Do
you
know,
query
everything,
add
users,
everything
that
you
need
to
do
in
a
very
basic,
smart
contract
after
you
do
that
you
can
build
pocs
through
this
within
just
a
couple
of
minutes
right,
because
all
you're
basically
doing
is
a
three-stroke
method
and
then
naming
your
asset.
C
It
will
give
you
the
basics
out
there.
You
can
even
go
out
and
get
some
of
like
dave,
enyart's
advanced
sample
chain
code,
which
is
really
high
grade
examples
of
stuff.
That
could
be,
I
mean
virtually
production
grade
types
of
chain
code
out
there
alter
that
to
what
you
need,
and
then
you
have
moving
into
true
production
and
it's
all
just
very
easily
done
now,
when
I
was
talking
about
the
different
aspects
of
the
vs
code
extension
when
you,
when
you
get
it,
this
is
the
little
symbol
for
the
ibm
blockchain
platform.
C
You
can
see
here
this
first
little
box,
that's
your
smart
contract
piece
that
will
package
all
of
the
open
projects
that
you
have
and
also
keep
a
history
of
all
of
the
chain
code
that
you
have.
I
am
now
upgrading
there.
We
go
all
right,
so
you
can
see
right
here.
I
have
a
list
of
different
chain
codes
that
I
have
packaged
up
and
ready
to
go.
Here
are
the
different
gateways
that
I
can
actually
log
into
so,
for
instance,
I
can
log
into
my
local
gateway
here
you
can
see.
C
I
have
three
different
gateways
that
are
all
ibp
or
ibm
blockchain
platform
gateways
that
are
they're
connected
to
once.
This
actually
connects
I'll,
be
able
to
oops
I'll
be
able
to
get
into
the
oh
still.
Logging
up
hang
on
all
right
once
that
comes
in
I'll,
come
back
to
this
in
a
second
but
I'll
show
you
that
I
can
actually
see
all
of
the
channels
and
bits
that
are
in
there
and
let's
see,
I
want
to
actually
show
you
talking
about
the
patterns.
C
C
When
I
say
code
patterns,
if
you
go
out
and
just
search
for
ibm,
blockchain
platform
code
patterns,
this
is
going
to
be
renamed
to
accelerators,
because
code
patterns
is
kind
of
a
weird
thing,
not
not
really
understand
what
that
means.
Necessarily,
but
you'll
see
we
have
all
of
again.
These
are
all
free
to
take
free
to
use
different
little
assets
for
different
types
of
things.
We
have
everything
from
say,
e-voting
to
basic
supply
chain
to
iot
devices,
to
simple
assets.
C
Let's,
let's
look
at
this
one
actually
build
a
an
asset,
digital
asset
and
manage
it.
When
you
go
into
this,
this
will
give
you
several
things.
It
gives
you
your
code,
which
I
didn't
mean
to
click
on,
but
gives
you
your
code
from
your
code,
the
git
repo,
so
you
can
grab
all
the
all
of
it
right
here.
You
can
click
on
a
intro
and
a
demo,
and
basically
that's
the
developer
of
this
particular
demo.
C
They
walk
you
through
exactly
what
it
looks
like
and
how
to
do
it
and
a
setup
of
how
to
do
the
network
and
then
in
here
you'll
see
exactly
the
entire
flow
of
everything
that
you're
gonna
use.
So
you're
gonna
have
to
build
out.
You
know
a
little
mail
server.
Let's
get
some
cloud
object:
storage
that
of
course,
the
ibm
blockchain
platform,
node,
etc,
and
you
can
see
you
have.
C
The
user
gives
you,
the
the
the
app
the
actual
back-end
server
the
network
and
all
built
on,
of
course,
kubernetes
and
in
this
layer,
and
then
the
the
information
that
you
can
build
out
as
an
operator,
and
it
gives
you
everything
you
need
here
in
your
step-by-step
flow,
to
build
this
entire
thing.
Now
this
will
take
you
probably,
I
would
say,
maybe
an
hour
and
a
half
to
two
hours
to
do,
because
there's
quite
a
bit
of
of
set
up
and
getting
of
different
services.
C
C
C
Gives
you
a
list
of
all
the
digital
assets
that
we
currently
have
on
the
ledger
and
who
has
actually
the
the
current
owner
can
do
different
things
with
it?
I
can
add
different
ones.
So,
if
I
say
I
want
to
upload
a
new
a
new
asset,
I
just
have
to
find
something.
Hopefully
I
don't
pick
a
big
zip
file
like
I
have
before.
C
Guy
go
back
and
you'll
see.
This
is
what
I
just
uploaded.
You
get
the
that
the
asset
identity
you
get
it
when
I
put
it
on
and
you
can
do
alterations,
I
can
transfer
it
to
other
people.
You
get
the
idea
right,
so
it
gives
you
a
nice
basic
apple
application
built
on
the
hyperledger
fabric
code
base.
Here's
another
one.
I
know
that
a
lot
of
people
in
the
the
us
are
very
interested
in
this
one
right
now
presidential
elections
would
say
so
we
have
by
register
yeah.
C
C
One
of
the
key
things
around
this
is
so
I've
just
registered
this
voter.
If
I
actually
try
to
re-register
this
user
you'll
see
it
actually
checks.
So
that's
a
key
thing
right.
There's
a
lot
of
discussions
about
fraud
in
voting
which
is
currently
going
on,
gives
you
kind
of
a
quick
little.
Who
do
you
want
to
actually
vote
for?
So
you
put
that
in
there
you
validate,
who
you
actually
are
put
the
the
poll
in
check.
It
out
says
it's
there.
C
C
So
now
I've
showed
you
really
quick,
the
middle
part,
which
is
the
ibm
blockchain
platform,
the
front
end,
which
is
the
vs
code
extension
or
you
can
use
code
ready,
workspaces
that
is
also
available
and
on
the
back
end
or
the
front
end
the
ansible
piece
that
that
was
discussed
earlier.
So
if
you
go
out
to
ansible
galaxy,
you
can
do
a
quick
search
for
the
ibm
blockchain
platform.
C
And
you'll
be
able
to
see
the
the
downloads
that
you
want
here
to
be
able
to
run
ansible
scripts.
This
will
help
you
tremendously.
When
you're
doing
stuff
say
you
want
to
do
stuff
out
on
the
ibm
cloud.
You
want
to
bring
up
and
tear
down
networks,
really
quick.
Just
to
do
tests
create
these
playbooks
use.
C
Ansible
it'll
help
you
a
tremendous
amount
and
you
don't
have
to
keep
networks
up
and
running
and
just
you
know,
exhaust
your
your
resources
for
no
reason
so
all
right,
I
got
it
all
in
with
one
minute
to
spare.
So
hopefully
this
gave
you
a
quick
overview,
I'm
almost
out
of
breath,
but
wanted
to
show
you
all
this.
Are
there
any
questions
or
comments
from
anybody
that
I
may
have
missed.
C
Yeah
yeah
yeah,
so
basically
we're
just
using
the
the
connection
profile
and
it's
using
apis
to
connect
in
at
the
end
of
the
day,
so
yeah,
please,
please
check
these
these
accelerators
out,
you're,
gonna
love
them.
There's
many
different
use
cases
out
there
we're
actually
starting.
So
if
you
develop
some
use
cases,
we
want
to
get
these
guys
out
on
there.
C
So
if
you
want
to
advertise
some
of
your
work-
and
you
know
promote
yourself
as
as
a
good
contributor
and
developer
of
some
of
these,
please
feel
free
to
to-
let
me
know
I
will
help
you
get
this
stuff
posted
out
there.
We're
making
some
big
changes,
we're
creating,
what's
called
an
ibm,
blockchain
community
so
similar
to
what
you
see
under
the
hyperledger
umbrella
for
everything.
That's
fabric
related
you're,
going
to
see
a
community
on
ibm
for
everything.
C
Any
other
questions
or
comments,
and
if
you
want
to
know
more,
we
have
a
bi-weekly
web
series
that
barry
mosekowski
and
I
host.
We
talk
about
some
of
the
different
features
and
stuff.
Of
course
we
follow
everything
that
happens
in
the
community,
so
as
it's
released
into
the
community,
we
try
to
get
it
into
ibp
as
quickly
as
possible,
as
gary
mentioned,
and
we
try
to
show
the
new
features
and
functions
and
things
of
that
nature
on
that
webcast
series.
So
please
join
us.
C
You
can
follow
me
at
meetmarkp,
on
twitter
and
and
I
usually
post
those
those
times
and
dates
and
the
topics
that
we're
going
to
be
talking
about.
So
we
have
that
as
well.
We
have
office
hours
again
through
the
community,
so
we're
here
for
you
and
that's
what
we
want
to
do.
We
want
to
help
support
you
through
your
your
complete
journey
here.