►
From YouTube: Creating your First Smart Contract on Hyperledger Fabric! - Swetha Repakula & Morgan Bauer, IBM
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Creating your First Smart Contract on Hyperledger Fabric! - Swetha Repakula & Morgan Bauer, IBM
When one thinks of blockchain, two technologies that come to mind are Bitcoin and Ethereum. Much of the knowledge has been focused on public networks, and less is known about the permissioned blockchain platforms out there like Hyperledger Fabric. Fabric is an open source blockchain platform that has been designed for corporate use cases. Morgan and Swetha will go through the architecture of Hyperledger Fabric detailing the transaction workflow, consensus mechanism, and smart contract capabilities. They will demonstrate how and end to end application could work on Fabric and in the process they will also talk about the benefits of a permissioned platform. Attendees will leave with knowledge to start developing on Hyperledger Fabric.
https://sched.co/NrvR
A
Hi,
thank
you
guys
for
coming.
I
know
it's
the
last
day
and
people
are
leaving.
So
thank
you
for
taking
time
to
come
up
here.
My
name
is
swetha
I
work
for
IBM
and
one
of
the
open-source
contributors
there.
This
is
Morgan
I'll.
Let
him
introduce
himself
in
a
second
I
previously
used
to
work
on
a
project
called
cloud
foundry
and
now
I
work
on
hyper
ledger
fabric
mostly
been
focused
on
a
piece:
the
fabric
EVM
integration
stuff.
So
we
have
questions
about
that.
A
Ok,
so
let's
get
started
before
I
dive
straight
into
fabric.
Let's
talk
about
hyper
ledger
as
it
as
a
foundation,
so
hyper
ledger
the
foundation.
That's
where
the
fabric
project
lies.
It
is
kind
of
a
greenhouse
of
different
blockchain,
like
frameworks
and
tools
and
we're
kind
of
relooking
at
how
we
want
to
classify
the
projects
that
come
under
it.
There
are
frameworks
up
there,
so
they
have
different
kind
of
different
things
that
make
them
unique
and
what
you
can
use
them
for,
and
then
you
have
tools
for
being
able
to
see
things
like.
A
How
do
you
deploy
stuff
like
cello
or
how
do
you
see
the
blocks?
I'm
not
gonna,
go
through
all
the
projects
because
of
time,
but
there
I
believe
two
more
projects
that
we
that
has
been
added
since
this
graphic
was
created
and
the
one
we're
going
to
talk
about
is
the
first
top
row.
Second
from
the
left,
hyper
leader
fabric.
A
So
as
we
dive
into
fabric
I
think
the
first
thing
that
is
very
unique-
and
this
is
I,
think
informative
in
terms
of
how
fabric
was
designed,
it
would
looked
at
business
and
enterprise
use
cases.
Those
are
the
types
of
problems
who
are
kind
of
solved,
so
fabric
is
designed
thinking
about
those
use
cases
and,
as
you
see,
the
design
choices
that
have
been
made.
Keep
that
in
mind
right.
It's
not
trying
to
solve
all
the
problems
out
there
for
blockchain.
It
is
kind
of
it
was
being
selective
of
what
it
was
looking
for.
A
A
I
believe
it
started
to
track
lettuce
here
in
China
actually,
but
the
whole
thing
started
off
because
someone
on
Walmart
brought
a
box
of
mangoes
and
said,
tell
me
where
these
came
from
now
it
took
them
about
two
to
three
months:
I
believe
to
figure
out
all
the
information
where
the
mangoes
came
from
what
plot
of
land
and
all
of
that
now
that
information
can
be
done
within
seconds
and
that's
a
huge
improvement
in
time
now.
Why
would
you
care
about
something
like
that?
A
One,
you
know
as
trends,
people
are
more
interested
to
figure
out
where
their
food
is
coming
from,
but
in
terms
of
corporations
like
Walmart
and
stuff,
when
you
have
contamination
or
ecoli
breakouts,
it's
better
to
know
which
set
of
the
produce.
Where
did
it
come
from
so
you're,
very
clear
about
which
retailers
have
that
produce
and
it's
easier
to
recall
and
recover
from
such
situations?
So
it
does
help
in
terms
of
improving
the
food
quality
overall
and
making
sure
that
the
good
and
the
best
stuff
is
what
is
sold.
A
So,
let's
kind
of
talk
about
fabric
fabric,
the
main
the
first
thing
that
I
think
is
very
important
to
understand.
It's
permissioned
now
permissioning
it's
kind
of
flexible
in
terms
of
what
you
want
to
do
so
permissioning,
it's
very
granular.
It
can
go
from
who's
allowed
into
the
network.
Who's
allowed
to
see
data
who's
allowed
to
run
a
smart
contract,
who's
allowed
to
read
the
data
from
a
smart
contract.
A
It's
highly
modular,
so
they're
different
pieces
or
different
areas
where
you
can
plug
in
things
that
you've
designed
or
created
yourself.
So
one
of
them
is
the
consensus
protocol.
The
underlying
protocol.
There
is
an
API
that
you
can
use,
so
you
can
bring
your
own
consensus
protocol
or
you
can
choose
which
one
you
want.
You
have
different
ledger:
op
options,
membership
services,
so
how
you
want
to
deal
with
identity
and
then
also
endorsement
and
validation,
and
we'll
talk
about
that.
A
little
bit
later.
A
Smart
contracts
are
written
in
general-purpose
languages,
so
there's
no
specialized
smart
contract
that
is
being
used
or
smart
contract
language
that
has
been
created
for
this
purpose.
So
we
support
Go,
Java
and
node
out-of-the-box.
If
you
want,
we
have
because
I
work
on
the
fabric,
EVM
integration
I
will
plug
that
in
here,
but
you
can
plug
that
in
and
also
get
some
solidity
contracts.
If
you
are
interested
in
that
privacy,
privacy
has
been
important
to
a
lot
of
enterprises
and
customers.
A
So
we
do
allow
features
like
private
data
for
your
chain
code
stuff
that
you
want
to
put
off
chain.
It's
all
kind
of
integrated.
There
is
no
mining
concept
in
fabric
and
we
don't
use
a
token
for
consensus.
So
those
are
two
things
that
are
there
one
of
the
unique
things
about
fabric
we
don't
use
any
of
those
things.
A
This
is
different
if
you've
heard
about
fab
token
again,
that
it
will
not
be
used
for
consensus
and
then
the
last
thing
that's
very
interesting
is
fabric
goes
through
this
xgq
order
validate,
which
means
we
execute
transactions.
Then
we
order
the
transactions,
and
then
we
validate
them,
which
is
different
from
the
I
think,
most
loft
chains,
which
order
transactions
and
then
they
execute,
and
with
that,
when
we
get
a
hand
it
off
to
Morgan.
B
Alright
I'm
going
to
try
and
very
quickly
go
through
a
high-level
overview
of
how
a
transaction
hila
will
review
of
the
architecture
of
a
fabric
deployment,
as
well
as
a
high
level
flow
of
the
path
transactions
and
blocks
will
take
through
the
network.
So
here
is
a
basic
fabric.
Architecture.
Diagram
key
things
to
see
are
the
arrangement
of
the
hyper
ledger
network
at
the
fabric
network
as
the
combination
of
the
order
and
the
peers,
as
well
as
the
membership
services
which
provide
the
identity
to
all
of
these
pieces.
B
All
of
the
appears,
the
orders,
the
clients
all
have
an
identity.
That
is
a
cryptographic
identity
that
can
be
provided
from
an
external
certificate
authority,
as
well
as
the
fabric
CA,
which
is
the
fabric
certificate
or
authority
that
you
can
run
in
the
network
to
not
in
the
network
but
as
part
of
the
as
part
of
a
running
network
that
is
provided
so
that
you
can
have
an
easier
way
to
manage
all
the
identities.
B
Let's
start
with
the
pier
the
pier
is,
your
is
analogous
to
a
node
in
most
other
blockchain
networks.
This
is
where
the
actual
ledger
is.
This
is
the
thing
that
has
the
blocks.
Look.
You
can
query
the
ledger
to
get
data
out
of
the
blocks,
as
well
as
the
chain
code
that
is
executed
when
you
provide
a
execution
request
to
the
network.
B
So
the
client
we
provide
SDKs
in
multiple
languages
to
interact
with
the
network
so
that
your
distributed
applications
have
congruent
in
many
different
languages
to
provide.
You
know
a
nice
user
experience
for
the
various
enterprise
people,
so
no
js'
or
node
Go
Python
Java.
There
are
many
clients
that
are
different
from
the
set
of
languages
that
are
supported
by
the
chain
code.
B
So
again,
we
have
the
everything
basically
resolves
around
a
smart
contract.
That's
what
executes
your!
That
is
what
execute
and
determines
the
the
reads
and
the
rights
and
the
the
input
and
output
for
everything.
So
that
is
what
your
developer
is
going
to
write,
they're,
going
to
write
a
a
chain
code
and
that's
gonna.
What's
going
to
be
agreed
upon
by
all
the
parties
and
the
developer
also
writes
the
again
the
client
application
that
uses
the
SDK
to
communicate
with
it
and
then
what
happens?
B
Is
the
smart
contract
interacts
with
the
ledger
state,
so
the
actual?
What
what
is
being
changed?
The
get
input
of
various
basically
straight
memory
addresses
is
the
into
the
ledger,
and
so
we
have
the
combination
of
the
world
state,
which
is
sort
of
an
optimization
that
lets.
You
know
what
the
state
of
any
particular
memory
value
is
at
any
pet.
B
And
all
of
this
there's
there's
multiple
different
kinds
of
events
that
come
out,
which
are
basically
notifications,
that
a
new
block
has
occurred.
New
transactions
have
a
curse
and
as
well
as
events
built
into
the
transactions
themselves,
so
that
during
execution
of
a
transaction,
you
can
be
notified.
B
That
is
basically
a
consists
of
reading
from
the
ledger
and
then
writing
to
the
ledger,
and
that
is
the
basic
concept
that
all
fabric
transactions
go
through,
so
we
record
those
and
those
that
is
what
makes
up
with
the
transaction
that
is
finally
written
back
as
well
in
the
ledger,
is
the
the
channel
configuration
will
discuss
channels
in
a
second,
but
basically
the
makeup
of
the
actual
who's?
A
member
and
the
sort
of
the
configuration
of
the
ledger
is
itself
written
into
the
ledger.
B
B
You
have
some
time
we're
gonna
go
through
the
definition
of
workflow
of
a
transaction
through
the
network
and
we're
gonna
see
three
different
pieces
here,
we're
going
to
see
the
the
committing
peers.
These
are
the
ones
that
contain
the
ledger,
so
they
have
the
blocks
and
they
have
the
they
basically
write
to
the
write
to
disk
the
current
state
of
the
world.
B
So
the
basically
every
peer
is
a
committing
peer
and
that
they
all
must
have
the
entire
blockchain
to
know
what's
down
on
it
and
execute
correctly,
but
only
some
are
necessarily
to
be
endorsing
peers,
and
this
depends
on
the
endorsement
policy
that
we
can
discuss
later,
and
so
these
are
split
up
basically
to
allow
more
scalability
in
that
you
don't
necessarily
need
the
same,
endorsing
peers
for
every
transaction
that
you
don't
necessarily
need.
Well,
you
everybody
needs
to
have
the
same
set
of
writing
right
right,
written
data.
B
B
They
just
get
transactions
from
clients
and
try
to
order
them
into
a
block,
and
so
again
everything
revolves
in
fabric
revolves
around
the
endorsed
order,
evaluate
or
execute
order
validate
where
the
execution
happens,
then
the
ordering
happens
and
then
finally,
the
validation
happens
at
the
end
that
determines
basically
which
part
of
the
execution
and
ordering
is
correct
and
finally
commits
it
to
the
ledger.
All
right.
So
here
is
a
network
diagram.
We
can
see.
We
have
three
endorsing
peers.
B
We
can
also
see
we
have
extra
committing
peers
as
P
3
and
P
4
that
don't
actually
execute
anything
and
we
can
see
the
endorsement
policy
is
that
the
three
endorsing
Peters
must
sign
it
and
the
other
peers.
We
don't
you
don't
care
about
they're,
not
actually
written
in
the
policy
they're,
just
not
explicitly
mention,
so
the
client
has
to
go
to
each
of
the
endorsing
peers
and
get
an
endorsement.
B
B
The
sort
of
basic
development
environment
version
is
called
solo
and
that's
just
a
single
node
with
no
fault
tolerance
whatsoever.
But
it's
intended
for
development
use.
There's
a
Kafka
back
service,
which
is
backed
by
a
separate
Kafka
service.
There
are
instances
of
Kafka
that
run
outside
of
the
order
process
itself,
and
now
we
have
a
built
in
from
one
for
one
version
of
fabric,
the
raft,
consensus
mechanism
which
runs
in
process
of
the
orders
and
is
more
scalable,
more
runnable,
the
more
easy
to
run.
B
B
So
some
more
details,
real
quick.
We
discussed
this.
We
discuss
the
different
ordering
services
of
solo
Kafka
raft,
the
newest
one
is
raft
and
we
like
to
use
it
I
believe
the
key
benefit.
There
is
not
just
the
built-in
and
not
requiring
a
separate
process,
but
that
the
organizations
required
for
the
orders
can
be
more
distributed
and
they
are
not
necessarily
a
solo
single
and
that's
all,
but
a
single
ordering
organization.
B
We
can
really
discuss
organizations
so
much,
but
they
can
be
spread
out
of
basically
among
all
of
the
organizations
that
are
involved
in
requiring
the
peers
to
be
endorsing
quick
bit
on
channels.
Basically,
channels
are
our
way
to
shard
the
ledger
in
two
different
non
related
pieces
so
that
you
can
enhance
the
scalability.
So
if
you
have
transactions
that
don't
have
anything
to
do
with
each
other,
you
can
basically
separate
those
out
into
separate
segments
of
the
ledger
and
not
require
them
to
interact
in
any
way
a.
B
Quick
quick
example
of
what
a
channel
looks
like
so
we
can
see.
Everybody
here
is
on
the
same
channel.
They
all
have
the
same
ledger.
They're
all
have
the
same
endorsement
policy.
They
all
have
the
same
smart
contracts
installed.
Then,
if
we
go
to
a
second
multi
channel
network,
we
can
see
that
there's
a
blue
ledger
and
red
ledger.
Ii,
1,
2,
&
3
have
a
blue
ledger.
B
As
long
as
the
contracts,
don't
you
don't
need
to
interact
across
the
various
Ledger's,
the
various
channels,
we
have
a
quick
bit
on
endorsement
policies
so
again,
endorsement
policy
is
basically
just
the
requirements
for
a
transaction
to
be
signed
and
has
that
having
been
executed
among
different
organizations.
So
when
you
have
different
organ,
is
different
organizations
involved
in
a
you
know,
agreement
of
a
smart
contract.
You
typically
want
to
spread
that
out
among
all
of
the
organizations
so
that
they
all
validate
and
execute
the
contract.
B
As
part
of
that,
we
have
again
chain
codes,
so,
basically,
even
internal
bits
of
fabric
are
implemented
as
chain
codes.
One
of
them
is
the
endorsement
chain
code
and
that's
the
thing
that
provides
the
signature
of
having
executed
a
smart
contract
and
once
it
goes
through
the
other
side,
you
can
actually
change
how
the
validation
works
as
well.
So
there's
the
validation
chain
code,
which
validates
the
endorsements
generated
at
the
earlier
step,
but
before
the
ordering
these
endorsements
and
then
after
the
ordering
once
it's
in
blocks,
that's
the
validation
step,
I.
A
People
in
the
back
can
you
read
that,
should
I
go
bigger,
bigger,
good,
okay,
so
or
because
of
time
I've
already
I'm
gonna
show
us
a
little
demo
with
a
sample
fabric
network
that
is
running
on
my
basically
on
my
machine
or
time.
I
have
already
deployed
it.
I
already
have
chain
code
installed,
so
all
we're
gonna
get
to
do
is
to
interact
with
it,
just
to
kind
of
show
you
guys
what
hasn't
been
done
before
so.
A
The
first
step
right
here
is
just
using
some
of
our
development
tools
to
generate
credentials
and
all
the
kind
of
cryptographic
material.
That's
needed
to
start
up
a
network,
we're
generating
the
Genesis
block,
writing
the
Genesis
block
and
then
we're
creating
a
new
channel.
The
channel
is
gonna,
be
my
channel.
That's
gonna
come
up
in
a
little
bit,
then
I've
just
started
the
network
by
the
way.
This
is
the
fab
car
example
on
hyper
ledger.
So,
if
you're
interested,
you
can
also
try
this
at
home.
A
We
have
basically
it
uses
docker
compose
under
the
hood
to
create
the
containers
and
what
we've
done
is.
We've
created
a
network
where
we
have
a
fabric
peer.
This
image
right
here
is
just
like
a
little
container
that
has
been
populated
with
all
the
credentials
that
are
being
used.
So
that
way
it's
easy
for
us
to
interact
with
the
network.
If
needed,
then
we
have
CouchDB,
which
is
the
underlying
database,
that
is
going
behind
our
peer.
That
was
this
the
first
container,
then
we
have
a
single
order.
It
is
using
solo.
A
A
I'm
gonna
do
this
and
you
can
see
before
I
was
showing
you
all
the
containers.
There
is
now
a
different
container
up
here.
That
was
not
in
the
output
before
and
that
is
the
fab
car.
That's
the
container
that
is
running
the
chain
code
I
have
previously
deployed
now.
Now
that
we've
set
it
all
up,
I'm
going
to
actually
show
you,
let's
start
playing
with
it
a
little
bit.
So
the
first
thing
I
want
to
do
is
go
through
and
show
you
guys
the
chain
code
itself.
A
So
the
JavaScript
we
have
a
new
kind
of
chain
code
life
cycle
model,
so
it's
making
this
a
lot
easier.
But
basically
you
just
have
to
extend
this
contract
object
and
then
in
your
functions,
you
take
this
context,
object
in
and
that
will
have
all
the
ways
you
can
interact
with
the
ledger.
So
we
have
a
few
functions
here.
We
have
a
knit
ledger:
fab
cars,
basically
like
an
inventory
system
of
different
cars
with
their
owners
and
some
details
about
them.
So
we
have
a
function
to
kind
of
pre
populate
the
ledger.
A
Then
you
can
query
a
specific
car.
You
can
create
a
new
car.
You
can
query
all
of
the
cars,
you
can
change
the
car
owner
and
you
can
see
we
have
this
similar
thing
where
it's
contact
stub
get
state
and
then
for
something
that
is
Oh.
Actually
we
can
look
right
here.
We
have
a
get
state
here
and
then
later
on,
when
we
want
to
actually
write
something,
we
do
stub
dot.
What
state,
just
to
kind
of
give
you
an
idea
again
because
of
time.
A
I'm
not
gonna,
go
too
deeply
in
this,
but
these
resources
are
online.
For
you-
and
we
will
have
a
link
at
the
end
of
that
at
the
end,
to
show
you
that
so
with
that
the
first
thing
I
want
to
do
is
I
want
to
populate
the
ledger
with
some
information
because
I
don't
have
it
so
we're
inside
here.
This
is
my
CLI
container
that
it
has
all
the
credentials
that
I
want
first
thing
just
to
show
you
there's
nothing
inside
of
it.
A
A
And
you
can
see
what
I
get
returned
is
that
moves
it
up
a
little
bit?
It's
all
empty
right
there,
okay,
the
next
thing
I
want
to
do
is
let's
populate
that
with
in
some
information.
I'm
gonna
do
an
invoke
here.
So
now
the
difference
between
query
and
invoke
the
peer
doesn't
really
know
the
difference
between
that.
This
is
a
client
facing
thing.
The
client
knows
the
difference
between
the
two
and,
if
we're
doing
a
invoke,
basically,
what
we're
saying
is
the
client
needs
to
go
and
collect
all
the
endorsements
right
versus
a
query.
A
So
that's
invoke
I'm
gonna
do
this,
but
I'm
going
to
actually
you
in
it
ledger,
run
that
through
its
successful
and
just
to
show,
let's
see
what
the
data
is.
Now
we
have
a
bunch
of
cars
in
there
now.
Typically,
though,
we
want
to
use
something
a
little
more
user-friendly
than
the
CLI
to
interact
with
you
know
the
fabric
network,
so
I'm
gonna,
exit
out
of
the
container
here
and
I'm
gonna
show
you
some
of
our
SDK,
so
I'm
going
to
be
using
the
node
SDK.
All
of
these
are
using
features
of
fabric.
A
One,
for
this
is
a
new
chain
code
lifecycle.
It's
exciting,
it's
kind
of
there
to
kind
of
make
things
smart
contract
development
easier,
as
well
as
application
development,
a
lot
easier
so
going
into
fab
car.
The
first
thing
I'm
going
to
do
is
so
I'm
going
to
show
you
guys.
What's
in
the
wallet,
nothing
is
in
the
wallet.
So
in
a
typical
scenario,
you
would
need
an
admin
to
be
able
to
create
new
credentials.
So
the
first
thing
I'm
going
to
do
is
enroll
as
the
admin
and
just
show
you
guys
what
is
happening.
A
We're
using
the
fabricc,
a
client
here
and
then
we're
using
the
wallet
coming
for
the
fabric
network
modules.
We
connect
to
that
see
a
dot
example.
I
showed
you
guys.
There
was
a
fabric,
see
a
container
before
and
then
from.
There
is
just
doing
a
check
to
see
if
admin
has
already
been
created.
If
not,
it's
gonna
go
enroll,
enroll
ourselves,
those
admin.
So
if
I
show
you
guys
now,
there's
an
admin
directory
and
then
I
can
go
even
more
and
we
have
public
and
private
keys.
A
A
Let's
see
that
works
I,
don't
think
that
one
runs.
Ok,
so
I'm
going
to
show
you
guys
user
one,
even
though
cuz
I
haven't
changed
all
of
them.
That's
a
new
set
of
public
and
private
key,
and
the
reason
is
because
I've
already
done
this
demo
once
and
the
user
1
ID
in
the
fabricc,
hey
has
already
been
used.
So
it's
like
hey
somebody
already
registered
on
this
name.
You
can't
use
it
now.
A
Next
thing
is:
let's
go
into
query
similar
kind
of
structure
in
terms
of
code,
but
we
no
longer
need
the
fabric
CA.
We
just
need
the
wallet
and
we
need
a
gateway.
The
Gateway
is
how
we
connect
into
the
fabric
network.
So
it's
looking
for
the
your
wallet.
What
we're
going
to
do
is
we're
going
to
check
for
user
2
we're
going
to
connect
to
user
2
and
we're
just
going
to
query
all
the
cars.
A
There
you
go
a
long
winded
way
to
say
this.
Data
is
the
same
kind
of
data
that
we
had
earlier
on
now
because
of
time,
I'm
not
going
to
go
there
too
much
more,
but
we
do
have
it
in
VOC,
very
similar
kind
of
code
here
from
previous
and
the
only
real
difference
here
is
here:
we
use,
submit
transaction
and
then
my
and
then
the
other
code
we
have
is.
A
Query
so
on
the
right
here
that
I'm
scrolling
through
is
the
query
code,
and
this
is
on
the
invoke
and
kind
of
you'll
see
that
the
code
looks
very
similar
to
each
other,
and
then
this
is
really
the
key
difference
here
here,
I'm
evaluating
and
then
here
I'm
submitting
and
again.
This
is
a
way
to
tell
the
SDK
I
want
to
submit
this
transaction,
get
all
the
endorsements,
and
things
like
that.
A
So
with
that
I'm
going
to
quickly
get
back
to
our
slides,
don't
have
too
much
left
and
we
will
be
taking
questions
in
just
a
minute.
So
the
first
thing
is
just
our
roadmap.
We
went
100
almost
two
years
ago,
channel
selected.
This
is
very
different
from
the
old
version
of
fabric,
and
now
we
are
working
towards
the
girl
goal
of
getting
2.0
out,
which
should
be
coming
out.
Hopefully
soon,
1/4
is
an
important
release.
A
First,
that
was
our
first
long-term
support
release
with
that
we
have
a
change
in
the
chain
code
lifecycle,
some
of
the
stuff
that
I
was
showing
today.
The
Boro
EVM
is
now
something
you
can
kind
of
plug
into
the
fabric
network
so
because
I
work
on
that
I'm
going
to
mention
that
one
for
one
that
what's
cool
about
that
is
we
added
raft
as
an
option?
So,
if
you're
interested
in
that
also
come
find
me
and
I
can
introduce
you
to
some
people
and
then
the
cool
thing
with
2.0
is:
there
are
different
changes.
A
One
of
them
is
the
fab
token,
which
will
be
using
aut
EXO
model,
so
it'll
be
a
little
bit
different,
but
that
will
be
there.
Raf
will
become
a
default
and
hopefully
there
will
be
a
migration
path
from
Kaka
to
raft
yeah.
So
those
are
kind
of
quick
thing,
I
mention
if
you're
getting
started
with
fabric.
There
are
quite
a
few
tutorials
on
the
hyper
ledger
docks
this
last
one
fab
car
is
the
one
that
we
just
did,
or
the
one
I
just
showed.
A
A
Some
resources,
the
hyper
ledger,
Docs
and
tutorials,
are
the
first
link
as
part
of
IBM.
We
do
create
a
lot
of
code
patterns
and
lectures,
and
these
are
all
kind
of
free
for
you
guys
to
access
and
use.
We
have
them
there
for
you
guys
to
learn
about
a
lot
of
open
source
technologies,
not
just
blocked
in
so
go
ahead,
check
that
out,
and
then
we
have
some
links
to
get.
You
guys
started
on
the
IBM
blockchain
platform.
A
If
interested,
if
you're
interested
in
contributing
to
hyper
ledger,
we
always
are
welcoming
new
contributors,
new
ideas,
we'd
love,
that
there
is
a
China
working
group
for
those
of
you
who
are
based
in
this
part
of
the
country
and
to
my
knowledge,
very
active
working
group.
So
take
a
look
at
that
come
to
one
of
our
events
and
thank
you
and
I
think
we
have
time
for
no
questions.
But
if
you
find
us
afterward,
we
will
answer
them.
Thank
you.