►
Description
A virtual meetup hosted by Hyperledger Budapest on April 29, 2021 featuring two presentations:
1. In search of the lost Hyperledger Fabric Composer - with Daml
Abstract: Hyperledger Fabric Composer was a promising, business-friendly idea, but ultimately got out of sync with the underlying Fabric platform and became a dead-end. So it was deprecated in 2019, two years after its start.
In my presentation I will show why the promise of Fabric Composer was (and still is) relevant, how the Daml smart contract platform (https://daml.com) fulfills a similar promise, and how it can be used with Fabric.
György Balázsi
Independent digital strategy consultant
2. Deepdive into Hyperledger Fabric certificates
One of the major challenge of Hyperledger Fabric is that the whole access control of the system is based on PKI infrasturcutre. During this presentation we will give an in-depth overview how this PKI infrastructure, including keys, certificates and access control lists are structured and how access control is implemented in Hyperledger Fabric
More about the event is at: https://www.meetup.com/Hyperledger-Budapest/events/277069241/
----
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
B
B
A
Okay,
super
thanks
a
lot
so
hi
everybody.
This
is
hyperledger
budapest.
This
is
a
meetup
from
linux
foundation,
focusing
actually
on
the
consortium.
Blockchain
technology-
and
you
know
I
mean
it's
basically,
a
free
knowledge
sharing
meetup,
so
everybody's
become
to
bring
any
topic.
I
mean
related
to
consortium,
blockchains
of
course,
especially
especially
products
of
the
hypoallergenic
umbrella
and
the
incubation.
We're
gonna
have
today
two
presentations.
A
The
first
is
from
eurek
balaji,
independent
digital
strategy
consultant
and
demo
expert
he's.
Gonna
have
actually
a
very
good
presentation
on
the
possibilities
of
of
having
demo
rapid
application
development
tool
instead
of
instead
of
fabric
composer,
and
the
second
presentation
will
be
will
be-
will
be
done
by
me.
It
will
be
something
a
little
bit
deep
drive,
I
mean
not
so
deep,
but
but
deeper
than
the
enhancing,
I
would
say
so
deep
dive
into
the
into
the
fabric,
keys
and
certificates
and
access
control
and
stuff
like
that.
A
C
Previous
person
needs
to
unshare,
first,
okay,
no,
it's
good
okay,
so
my
name
is
george
bonage
and
the
topic
will
be
the
fabric
composer.
What
its
its
design
principles
and
ambitions
was.
Why
was
it
relevant
and
why
is
it
still
relevant?
I'm
I'm
using
past
tense
because
it
has
been
deprecated
a
few
years
ago.
C
It
was
a
relatively
short
lived
project,
but
but
its
existence
proves
that
there
is
something
something
important
the
people
behind
this
project
tried
to
fulfill
and
I'm
comparing
the
promise
of
this
fabric
composer
platform
to
a
relatively
new
other
platform,
which
is
a
smart
contract
platform
called
demo
daml,
and
I
also
have
among
us,
a
community
manager
from
the
company
behind
demo,
anthony
luzadi.
He
promised
me
to
help
out
with
with
questions,
so
he
will
interrupt
me
when
he
sees
that
there
are
relevant
questions
in
the
chat.
C
C
B
C
C
The
company
behind
the
demo
is
no
stranger
to
the
hyperledger
project.
They
donated
actually
the
name
hyper
ledger
and
the
original
code
base
of
fabric
to
the
to
the
project
and
d.a
is
also
not
stranger
to
budapest.
They
have
an
office
here
among
other
locations
worldwide,
so
my
my
storyline
will
be.
B
C
Elaborate
on
a
bit
more
detail.
What
actually
the
fabric
composer
was
for
those
of
you
who
don't
know
that
platform
or
didn't
use
that
platform
or
don't
remember
so
so
well
what
it
was
and
how
it
was
used.
And
then
I
will
come
to
the
most
exciting
part
of
my
presentation,
at
least
for
me.
So
I
will
do
some
live
coding
and
I
will
demonstrate
one
key
feature
of
the
demo
smart
contract
platform.
This
is
the
proposed,
accept
pattern
and
I
will
show
you
how
we
can
create.
C
Real
real
contract,
like
objects
in
them
all
actually
signed
by
several
parties,
and
then
I
will
show
you
which
are
the
platforms
on
which
demo
can
be
used.
One
of
them
is
fabric,
but
there
are
several
other
platform
as
as
mentioned,
and
you
can
ask
questions
then
or
or
anthony
will
see
the
comments.
C
C
So
what
are
distributed
applications.
My
not
my
next
question.
So
if
you
think
about
it,
distributed
applications
are
older
than
computers
or
or
computer
networks
or
the
internet,
so
I
would
even
say
distributed.
Applications
are
as
old
as
as
mankind,
so
businesses
are
over
distributed.
So,
if
you
think
about
it,
when
you
sign
a
contract,
you
never
sign
a
contract
in
one
one
copy.
You
always
sign
several
copies
and.
C
On
the
left
hand,
side
of
this
of
this
slide,
I
have
put
an
interesting
picture.
This
is
a
mechanical
device
which
is
you
which
was
used
by
president
jefferson
and
it's
called
a
polygraph,
and
he
used
this
for
for
the
purpose
of
copying
every
outgoing
letter
so
that
he
can.
He
can
preserve
a
copy
of
the
letters
he
has
sent
and
this
this
virtual
shared
ledger,
which
consists
of
of
contract
copies,
is
supported
by
the
judicial
system.
So
it
doesn't
stand
in
in
itself.
C
C
C
B
B
C
That's
that's
true,
of
course
I'm.
So
I
I'm
not
I'm
not
stating
that
this
is.
This
is
always
always
true
that
the
transit
transaction
logic
is
implemented
client-side,
but
I
have
seen
several
examples
for
that
and
I
have
seen
several
applications
where,
where
the
fabric
platform
itself
was
was
only
used
for
for
like
a
a
notary
service,
so
I
I'm
not
not
stating
this
is.
This
is
always
the
case,
but
there's
a
tendency
for
that.
I
think.
B
C
C
So
this
this
diagram
was
taken
from
a
presentation
from
from
the
early
days
of
of
the
composer
platform,
and
it
shows
how
the
underlying
fabric
network
is
extended
by
this
by
this
upper
layer.
So
the
underlying
fabric
infrastructure
uses
concepts
like
key
value,
store,
chain
code,
peers
consensus
and
the
the
the
layer
built
on
top
of
the
of
that
consists
already
of
business.
C
C
C
We
are
speaking
about
these
kind
of
business
networks
and
the
so
I
I
find
important
the
abstractions
so
so
these
are
the
these
are
the
kind
of
business
related
or
business
friendly
abstractions
that
were
supported
by
the
fabric
composer
platform
and
are
also
supported
by
the
demo.
Smart
contract
platform.
C
So
there
there
is
actually
one
aspect
of
this
fabric,
composer
framework
which
was
not
so
much
convenient,
namely
that
you
had
to
create
several
files
with
several
syntaxes
in
order
to
implement
this
kind
of
business
network.
So
there
is
a
model
file
which
contains
the
assets,
the
participants,
the
transactions.
C
Who
can
do
what
so?
Who
among
these
participants,
can
do
what,
with
these
assets
listed
in
the
in
the
model
file?
And
there
was
no
very
convenient
way
of
checking
the
consistency
of
these
files,
and
in
this
respect
at
least
demo
seems
to
be
more
convenient
because,
as
I
will
show
you,
you
can
put
all
these
things
in
in
in
a
in
one
consistence
in
in
one
consistent
syntax.
And
you
can
you
have
a
consistency,
check
checks
in
terms
of
of
type
checking.
C
C
So
the
other
file
is
the
actual
javascript
code
which
implements
those
transactions
which
are
listed
in
the
in
the
model
file.
In
this
case,
there
are
two
transactions
offer
and
close
bidding
and
the
actual
functions
which
implement
these.
These
transactions
had
to
be
written
separately
in
a
in
this
javascript
file,
and
the
third
part
of
of
of
the
system
is
a
an
access
control
file,
which
is
a
another
different
syntax,
where
you
could
specify
these
access
control
rules
where
it
is
stated
which
participants
can
do
what
with
which
resources.
C
C
C
C
Development
platform,
and
now
I
will
go
to
some
some
live
coding,
so
I
have
to
say:
I've
never
done
this
before
and
I'm
I'm
very
exciting
to
do
this.
To
do
that,
I
did
a
few
rehearsals
and
I
hope
I
won't
do
many
mistakes,
so
the
focus
of
this
this
this
live
coding
session
will
be
that
I
will
show
you
how,
on
this
demo
platform,
you
can
implement
contracts
which
are
signed
by
several
parties,
and
before
doing
that,
I
I
want
to
mention
some
some
general
center
general
features
of
this.
C
This
smart
contract
mental
model
which
which
is
behind
the
demo
platform,
so
in
demo
the
basic
concepts
we
have
are
parties
like
in
fabric
composer
and
the
platform,
is
very
much
focusing
on
implementing
rights
and
obligations
and
its
ambition
is
to
implement
the
principles
of
contract
law
and
a
privacy
model
together
with
that
which,
which
is
which
is
the
need
to
know
basis,
so
that
information
is
only
disclosed
to
those
parties
who
actually
have
to
do
something.
With
that
information.
C
Other
details
of
of
the
of
the
demo
ledger
model
you
can
read
in
the
in
the
demo
ledger
model
section
of
the
of
the
demo
documentation,
and
now
I
actually
come
to
the
to
the
live
demo.
And
now
I
would
like
to
show
you
how
we
can
implement
an
agreement
contract
which
I
already
started
to
write
in
this
file,
and
so
this
is
how,
in
general,
a
a
demo
contract
template
looks
like
maybe.
C
A
missing
piece
of
information
that
in
demo,
we
have
a
different
terminology
from
let's
say
ethereum.
So
in
demo,
we
we
call
contract
the
actual
piece
of
of
ledger
items
which
are
created
based
on
demo
templates
and
the
the
demo
code
consists
of
these
contract
templates,
and
so
when,
when
writing
a
demo
code,
we
often
write
the
contract
templates
alongside
with
scripts,
which
actually
demonstrate
and
test
how
the
ledger
transactions
based
on
these
contract
templates
look
like,
and
what
what
the
result
of
these
ledger
transactions
will
be.
C
So,
in
the
background,
so
what
what
you
can
see
here
is
called
the
demo
studio.
This
is
a
vs
code
extension
and,
in
the
background
of
this,
a
ledger
sandbox
is
running
which
simulates
the
ledger,
transaction
validation
and
the
error
messages
signal.
The
fact
when
a
when
a
ledger
transaction
would
be
rejected
by
an
actual
demo
ledger,
and
what
we
can
see
here
is
that
I
started
to
write
an
agreement
template
a
very
for
a
very
simple
contract.
This
contract
only
says
that
we
have
two
parties.
We
have
party
a
and
party
b.
C
The
contract
should
be
signed
by
party
a
and
party
b
in
order
to
be
created,
and
it
only
says
it
only
has
an
agreement
text
text,
which
is
a
parametric
text
and
when
the
contract
is
created,
the
text
says
that
in
in
our
case,
alice
and
bob
are
good
friends.
So
this
is
a
very,
very
basic
contract
template.
But
we
have
a
problem
with
that.
C
B
C
So,
as
stated
we
are,
we
are
demonstrating
alongside
it.
Writing
the
the
contract
template
with
a
script,
and
we
have
allocated
the
parties
on
the
ledger
called
alicebab
and
carroll,
and
we
have
stated
that
we
call
alice
party
a
we
call
b,
both
party
b
and
carol
party
c,
and
this
is
the
line
which
says
that
alice
tries
to
create
this
agreement.
C
C
But
the
problem
is
that
this
is
not
the
contract.
We
want
to
save
c,
because
this
is
not
a
contract
signed
by
two
parties.
This
is
just
signed
by
by
one
party,
and
this
dilemma
seems
to
be
very
difficult
because
we
we
have.
We
have
the
challenge
of
signing
a
contract
by
two
different
parties
and
what
the
demo
platform
offers
as
a
solution
is.
C
I
I
put
back
here
so
point,
so
the
agreement
contract
should
be
also
signed
by
party
b,
and
now
we
have
a
proposal
template
and
an
agreement
template
and
in
the
script.
If
we
change
the
template
name
from
agreement
to
proposal,
then
we
can
see
that
alice
actually
can
create
this
proposal
contract,
and
this
can
be
seen
on
this
part
of
of
the
screen.
So
actually,
this
demo
studio
has
a
nice
feature
that
it
actually
shows
you
the
result
of
of
of
ledger
transaction
proposals
or
attempts.
C
The
name
of
the
choice
which
will
be
exercised
is
proposal
underscore
accept.
This
is
a
convention
which
indicates
that
we
are
defining
a
pro
and
a
choice
on
the
proposal
contract
which,
with
the
content
of
accepting
this
proposal-
and
we
also
have
to
specify
the
return
type
of
this
choice
and
the
return
type,
is
usually
a
contract
id.
C
So
this
is
the
the
the
choice
name
and
return
type
and
what
the
choice
actually
does
we
put
into
a
so-called
do
black,
and
in
this
case
the
the
result
of
exercising
this
choice
will
be
simply
creating
an
agreement
contract
with
the
parameters
which
are
already
specified.
So
we
want
to
be
created
this
agreement
contract
so
that
the
party,
a
parameter
of
the
agreement
contract,
shall
be
identical
with
the
party.
C
We
have
to
specify,
which
is
the
contract
on
which
we
exercise
the
choice,
and
that's
that
will
be
the
proposal
contract
we
have
just
created,
and
we
also
have
to
specify
the
choice
which
will
be
exercised
by
this
by
board,
and
this
is
the
proposal
accept
choice,
and
now
we
can
see
that
the
result
of
these
two
steps,
so
in
the
in
in
the
scripts.
These
are
two.
C
There
is
another
interesting
option
in
this
screen,
namely
we
can
specify
that
we
want
to
see
the
detailed
disclosure
of
these
contracts
and
the
disclosure
can
be
seen
in
this
part
of
this
of
these
tables,
and
this
shows
that
the
proposal
contract
was
signed
by
alice.
So
alice
was
a
signatory.
This
is
something
we
knew,
because
this
is
how
we
created
the
script
and
bob
was
an
observer
on
this
contract.
C
We
didn't
specify
this,
but
we
specified
that
bob
should
be
a
controller
of
a
choice
on
this
contract
and
this
is
why
the
demo
platform
make
makes
bob
automatically
observer
on
this
contract
and
I'm
going
to
show
you
another
interesting
part
of
this
disclosure
mechanism,
because
this
kind
of
observer
is
called
implicit
observer
on
the
demo
platform.
But
we
can
specify
observers
explicitly.
C
With
this
double
dot
shorthand,
we
already
made
sure
that
caro
will
be
substituted
in
the
place
of
party
c
at
the
creation
of
of
this
proposal
contract.
So
that's
why
we
can
see
here
carol
and
not
only
here,
but
in
the
proposal
contracts.
We
can
see
that
kerwell
was
also
an
observer
just
like
bob,
but
it
was
it.
It's
a
different
situation
because
carol
is
not
an
implicit
observer,
but
an
explicit
observer.
C
We
explicitly
told
in
the
contract
template
that
we
want
this
proposal
contract
this
close
to
carry
on,
but
there
is
an
interesting
consequence
of
this
observer
status
because
in
the
in
the
agreement
contract
tab
template,
we
didn't
say
anything
about
carroll.
We
didn't
say
in
the
agreement
contract
template
that
we
want
carroll
to
be
an
observer
of
of
of
the
contract
instance,
but
due
to
the
to
the
privacy
model
of
of
the
demo
platform,
carol
was
made
automatically
observer
of
this.
C
The
created
agreement
platform,
more
specifically,
not
an
observer,
but
a
witness-
and
this
is
called
witness,
because
because
it's
neither
an
implicit
observer
nor
an
explicit
observer
it
it's
the
witness
it
actually
so
she's.
Actually,
the
witness
of
the
creation
of
this
this
contract
and
that's
why
she
she
can
also
see
the
the
the
the
next
stage
of
the
evolution
of
this
of
this
contract
process,
and
I
don't
want
to
spend
more
time
or
with
this
with
this
live
demo.
C
But
the
next
question
would
be
if
we
wanted
to
spend
more
time
on
on
this
proposed
access
pattern
that
okay,
we
know
now
how
to
create
a
contract
which
is
signed
by
two
parties,
but
how
we
archive
a
contract
which
is
which
has
been
signed
by
two
parties,
because
I
I
will
show
that
to
you
that
the
naive
methods
won't
work.
So
we
cannot
archive
this
contract
in
a
simple
way.
C
C
An
error
message
which
state
that
this
transaction
would
be
rejected
by
a
demolisher,
because
bob
who
is
also
a
signatory
of
the
agreement
contract,
didn't
authorize
the
archival
of
this
contract.
So
I
think
I
spent
a
bit
too
much
time
so
far.
This
this
is
a
diagram
showing
this
two-step
process.
We
have
seen
in
detail
in
the
developer
environment,
so
this
shows
that
the
the
creation
of
this
agreement
process
happened
in
two
steps.
C
Uni
laterally,
okay,
so
this
was
this-
was
the
proposed
accept
pattern
of
the
demo
platform,
and
now
I
continue
with
with
information
about
which
underlying
ledgers
can
support
the
demo
smart
control
platform.
These
are
several
blockchain
platforms,
among
them
hyperledger
fabric
hyperages,
sawtooth,
hyperrager
basu,
which
is
which
is
the
enterprise
ethereum.
C
Client,
it's
also
supported
by
cortar
vmware
blockchain,
and
this
bsn
is
stands
for
the
chinese
nationwide
blockchain
platform,
which
has
been
created
last
year.
Maybe-
and
in
this
list
you
can
also
see
centralized
ledgers
or
or
simple
relational
databases,
so
you
can
use
the
demo
smart
contract
platform
with
amazon,
aurora
and
amazon.
C
Quantum
ledger
database
as
well
and
postgres
sql
is
not
listed
in
this
list,
but
it's
also
available,
and
there
is
a
cloud-based
ledger
as
a
service
developed
and
maintained
by
a
digital
asset
where
you
can
also
use
demo
based
applications,
and
so
the
beauty
of
this
portability
is
that
you
can
create
demo
models
without
actually
deciding
which
underlying
platform
you
want
to
use
eventually.
So
you
can,
you
can
start
with
a
with.
C
C
C
C
So
I
would
leave
you
with
a
few
hints
about
possible
next
steps.
If
you
found
this
topic
interesting,
I
would
recommend
to
check
out
the
wide
demo
section
of
the
of
the
demo
website.
It's
a
it's
an
excellent
summary
of
of
the
design
principles
and
the
application
potential
of
of
the
demo
platform.
So
I
I
would
recommend
this
as
a
first
read.
C
Definitely,
then
you
can
try
demo
online,
so
they
have
a
an
online
playground
where
you
can
play
around
basically
the
same
way
as
you
can
do
in
a
in
the
vs
code
demo
studio.
I
I
was
showing
to
you
next
step.
If
you
are
even
more
interested
download
demo
connect,
which
is
the
platform
the
demo
sdk,
you
can
learn
about
them
all
in
interactive
tutorials.
C
Driver
and
as
mentioned
them,
digital
asset,
is
also
already
maintaining
a
cloud-based
ledger
as
a
service
platform,
which
is
called
demo
hub,
and
this
is
also
a
potential
deployment
target,
and
the
interesting
part
of
this
demo
hub
is
that,
as
far
as
I
know,
this
is
the
only
platform
where
actually
the
demo
smart
contract
package
is
transparent
for
the
users.
So,
if
you
use
this
platform,
you
can
actually
see
with
your
own
eyes
what
is
the
underlying
camera
package
which
which
specifies
the
transactions
and
it
it's
an
excellent
opportunity
to
to
audit.
B
A
The
chat
at
the
moment,
but
actually
there's
not
much
going
on
so
if
no
more
question
then
I
would
propose,
I
would
just
switch
back
to
the
general
introduction
and
where
basically,
the
next
presentation
is
from
me,
it
was
planned
to
have
a
deep
dive
into
fabric
certificates,
but
I
would
say
so
I
mean
so
it's
a
big
topic
and
then,
due
to
time
limit,
it
will
be
just
a
brief
dive
into
demo
topic.
I
can
share
video
for
a
second,
but
I've
been
working
in
home
office
for
more
than
a
year.
A
So
if
we,
if
you
want
to
understand
hyperledger
fabric
and
typologist
certificates,
then
we
have
to
be
over
a
couple
of
things.
So
basically
fabric
is
something
which
is
called
an
enterprise
system.
Enterprise
system
is
something
that
is
capable
to
cover
many
different
scenarios,
which
means
it
can
be
set
up
with
many
different
enterprise
requirements.
A
It
is,
of
course,
an
advantage,
but
the
problem,
of
course,
is
always
that
then
it
it
gives
some
complexity
to
the
system.
So
it's
not
always
very
simple
to
set
up
even
in
simple
scenarios,
the
basic
idea
of
hyperledger
fabric
and
actually
for
all
for
most
of
the
blockchain
is,
is
the
digital
signature.
So
usually
there's
a
question:
hey
we
got,
we
got
blockchain
it.
It
has
a
lot
of
cryptography,
so
it's
it
makes
some
secrecy
as
well,
but
this
is
usually
a
misconception.
A
So
basically,
blockchains
do
not
really
provide.
Secrecy.
Do
not
really
provide
privacy.
There
are
some
ongoing
investigations
as
well,
but
basically
blockchains
do
have
a
lot
of
cryptography,
but
this
cryptography
is
usually
a
digital
signature
and
has
hash
functions.
Most
of
the
blockchains
do
not
have
built-in
privacy
concepts
as
cryptography
as
secrecy
as
as
encryption.
A
So
the
basic
ideas
is
digital
signature.
I
mean
digital
signature.
Looks
that
way
we
got
like
alice
and
bob
in
this
slide.
So
basically
alice
has
a
private
key.
She
can
sign
with
this
private
key
bob
having
basically
at
least
public
key
and
then,
if
elise,
signs
something
with
her
private
key
and
bob
having
the
public
key
from
alice,
then
he
can
verify
if
the
document
or
usually
transaction
or
communication
way
was
really
signed
by
alice.
So
that's
the
basic
idea
of
digital
signature.
A
B
A
So,
let's
just
take
a
look,
so
basically
we
got
like
two
big
arithmetic
systems
or
cryptography
systems.
One
is
basically
rsa.
Rsc
is
based
on
based
on
it's
like
you
know,
it's
a
clock,
clock
arithmetic.
So
this
is
like
12
o'clock.
This
is
like
six
o'clock
and
so
on.
So
the
basic
idea
is
something
similar
that
we
got
a
one-way
function
which
can
be
computed
very
easily
in
one
way,
but
it's
much
more
difficult
to
compute
in
another
way
so
like.
A
If
we
get
this
modulo
arithmetic,
then
I
mean
having
something
in
a
modular.
Modular
arithmetic
like
multiplication
is
something
which
can
be
very
easily
computed
in
one
direction,
but
based
on
like
a
multiplication,
implicating
back
to
the
original
numbers
is
difficult.
So
this
is
a
one-way
function,
easy
to
compute
in
one
way,
but
even
more
difficult
or
or
very
difficult
to
compute.
A
In
another
way,
it's
actually
not
a
not
not
an
mp
complete
problem,
but
it
is
supposed
to
be
very
difficult
to
compute
in
a
reverse
direction
and
we
get
another
one.
So
we
don't
have
rsa
in
hyperledger
fabric.
We
got
something
as
an
elliptic
curve.
Digital
signature
and
elliptic
curve,
cryptography,
so
elliptic
cryptography
has
something
similar
ideas.
A
A
We
get
something
as
multiplication
as
well.
Multiplication
is.
This
is
like.
If
this
is
key,
then
this
is
minus
two
key,
and
actually
this
is
two
key,
so
I'm
not
gonna
go
very
much
into
the
details.
The
idea
is
basically
the
same,
so
we
iterate
we
iterate
somehow
on
this
elliptic
curve
in
a
way
that
it
can
be
computed
very
easily
in
one
way
so
like
multiplicating,
something
several
times
is
easy.
A
B
A
A
A
A
So
we
still
have
time
in
this
sense,
but
you
know
I
mean
who
knows
perhaps
somewhere
in
secure
military,
complex,
there's,
there's
even
more
quantum
computing.
But
again
the
state
of
the
art
is
that
is
that
rsc
can
be
breaking
from
thousand
two
thousand
five
hundred
cubits
elliptic
curve
might
be,
or
requires,
perhaps
even
a
little
bit
more
and
then,
as
far
as
I
know,
the
state
of
the
art
is
something
like
a
hundred
cubits
at
the.
A
B
A
A
Cool
so
basically
fabric
based
on
elliptic
curve
and
elliptic
curve,
digital
signature
algorithm:
you
can,
you
can
choose
like
three
different
algorithm,
including
a
different
key
size
in
your
in
the
certificate
authorities,
but
all
threes
are
actually
elliptical
digital
signature,
so
there's
there's
no
exception,
so
that's
signing
and
then
one
more
stuff.
That
is
basically,
you
have
to
learn.
A
So
basically,
if
we
just
look
back
in
this
original
picture,
it
looks
that
way
that
I
mean
so
digital
signature
supposes
somehow
that
bob
has
the
public
key
of
alice
and
then
bob
should
actually
get
this
public
key
from
a
trusted
source.
Otherwise
the
whole
system
is
is
can
have
problems
and
many
individual
attacks.
So
this
public
key.
We
have
to
make
sure
that
this
public
key
comes
really
from
alice
in
the
standard
digital
signature,
algorithms.
A
A
Basically
x,
509
certificate
is
a
standard
standard
document
format
for
the
whole
public
key
infrastructure.
So
this
is
how
it
looks
like
we
got
something
as
so.
It's
it's
basically
a
public
key.
It
can
be
actually
a
private
key
as
well.
There
are
many
x
509
certificates,
but
in
our
example
it
is
usually
a
public
key
which
is
signed
by
a
certificate
authority.
A
So
this
is
how
looks
it
looks
like
we
get
a
lot
of
metadata
here,
but
basically
the
two
important
stuffs
are.
We
got
something
as
an
issuer
and
then
in
our
example,
issuer
is
actually
a
high
pressure
fabric
certificate
authority.
So
usually
you
get
your
certificates
from.
I
don't
know
good
at
your
or
some
some
other
sources,
but
this
is
important.
A
It
is
usually
if
you,
if
you
work
with
like
fabric
samples,
this
is
the
usual
setup,
for
instance,
for
the
for
your
whole
structure
and
for
the
for
the
certificate
authorities
for
your
certificate
already.
So
this
is
basically
the
issuer,
which
is
the
certificate
authority,
and
we
got
a
subject
and
then
subject
is:
is
somebody
having
basically
a
public
key
or
somebody's
publicly?
A
Basically,
so
at
this
example,
we
got
european,
so
we
got
a
peer
certificate,
basically,
which
is
the
pl0.org1.example.com,
and
then
it
is
again
something
which
is
usual
in
fabric
samples.
So
we
see
that
this
is
a
peer
certificate.
It
is
actually
a
peer
identity
certificate.
We
can
see
somewhere
that
this
is.
A
A
A
Okay,
so
basically,
this
is
the
content
of
a
hyperledger
fabric
certificate.
It
was
generated
actually
by
by
the
by
the
cryptogen,
so
it
wasn't
directly.
It
was
like
it's
like
a
simulated,
hyperledger
fabric
certificate
authority
certificate
and
we
got
here
the
information
like
the
issuer.
It's
again,
it's
a
certificate
authority
which
is
simulated
in
this
case,
but
usually
you
should
have
this
kind
of
certificate
or
probability
in
your
hyperledger
big
network,
yeah
daniel.
B
A
B
A
A
So
that's
the
reason
you
should
be
aware
of
this
whole
certificate
stuff
if
you
were
with
hyperledger
public
infrastructure
yeah.
So
so
you
see
the
issuer,
that's
the
issuer.
Here
you
see
actually
the
validity
it's
like.
Theoretically,
if
you
generate
these
certificates
with
cryptogen,
then
you
get
you
get
the
led
for
for
one
for
10
years,
which
is
which
is
not
very
practical
in
production
scenarios
and
then,
if
you
generate
for
cryptogram
it
can't
really
be
revoked,
for
instance,
but
anyway.
A
A
It
can
be
appear,
then
you
see
an
organization
unit,
that's
appear,
it
can
be
an
ordering
service.
Then
you
see
that's
an
ordering
service.
It
can
be
an
administrator
of
an
organization.
Then
you
see
here
admin
and
then
the
fourth
one
is,
if
I'm
not
mistaken,
that
client
client
is
somebody
wanting
to
send
transactions
on
the
network.
I
guess
that's
the
fourth
one
and
it's
reflected
in
the
organization
you
need,
and
it's
cn
you
see.
A
Basically,
so
that's
your
that's
your
period
here
basically,
so
this
is
a
peer
identity
certificate
for
the
spear,
and
then
I
mean
the
rest
is
not
fabric
specific.
You
find
something
like
I
guess
this
is
the.
This
is
the
algorithm
that
you
use.
You
got
one
elliptic
digital
signature
algorithm
and
then
you
get
to
have
hash
function
as
well.
So
basically
it
looks
that
way
that
you
get
like
a
public
key.
A
You
should
hash
it
together
and
sign
it
with
your
certificate
authority,
so
you
get
like
one
hash
function
and
sorry,
one
hash
function
and
one
elliptic
curve,
digital
signature
algorithm.
So
these
are
the
pairs
and
you
find
here
some
some
more
information
on
the
elliptic
curve
that
you're
exactly
using
one
of
the
most
important,
actually
the
key
usage.
A
So
you
can
see
here
if
this
key
is
used
for
digital
signature.
For
for
for
for
encryption,
I
mean
there's
no
encryption
in
fabric,
but
generally,
if
you
take
a
look
on
x,
509
certificate,
you
might
see
that
that's
used
actually
for
for
encryption.
You
find
here
tls
if
it's
used
for
tls
and
so
on,
and
then
I
guess
that's
your
signature,
somehow,
basically,
okay!
A
So
that's
how
an
x,
509
certificate
look
like
and
then
so,
based
on
public
keys,
x509
certificates,
we
got
something
as
a
public
key
infrastructure,
and
this
is
how
generally
public
key
infrastructure
look
like.
So
basically
what
we
have
we
have
somehow
I
mean
the
major.
The
basic
idea
is,
and
that's
that's
the
basic
idea
of
of
fabric
as
well,
so
I
generate
somehow
a
key
pair
I
generate
and
generate
the
public
key
and
the
private
key,
and
basically
what
I
want
to
do.
A
I
want
to
share
somehow
my
public
key
in
a
way
that
basically
everybody
knows
that
this
public
key
is
related
to
me.
So
it's
if
I
sign
something
with
my
private
key,
then
everybody
can
check
that
really
I
mean
this
was
signed
by
me,
but
for
that
it's
required
that
this
public
key
is
somehow
trusted.
So
if
this
public
key
is
not
trusted,
you
can
have
something
something
in
the
middle
which
should
be
avoided
so
what's
happening
here.
We
generate
a
key
pair.
Usually
that's
that's.
A
On
a
client,
for
instance,
I
mean
it
depends
on
the
infrastructure,
but
in
most
cases
that's
that's
on
your
client
and
we
get
something
as
a
certificate
signing
request.
So
we
send
this
public
key
to
the
certificate
authority
and
say
hey.
This
is
my
public
key.
Everybody
should
trust
me
so
sign
this
public
key
for
me
and
if
this
publicly
is
signed
basically
based
on
the
signed
public
key,
I
mean
the
sign
certificate.
A
Author
is
assigned
public
key,
we
generate
an
x
509
certificate
and
this
x
509
certificate
can
be
actually
distributed
to
anybody,
and
then
anybody
takes
a
look
on
the
text.
509
certificate
finds
my
public
key
inside
and
then
finds
the
signature
of
of
a
certificate
authority
and
knows
that
hey
this
guy
can
be
trusted.
I
mean,
if
I
see
basically
a
transaction
or
anything
which
was
signed
by
the
private
key.
Then
I
know
that
this
is
related
to
the
public
key,
and
I
know
that
this
public
key
is
related
to
that.
A
A
C
A
Not
exactly
so
so
one
of
the
different
between
so
so
you
get
you
get
digital
signature,
you
get
digital
signature
in
elliptical,
digital
signature
in
the
bitcoin
network.
That's
that's
correct,
but
you
don't
have
certificate
authorities.
So
the
point
I
mean
one
of
the
big
differences
between
between,
like
bitcoin,
public
networks
and
and
and
consortium
networks
like
like
hyperledger
fabry,
is
that
this
is
this
is
actually
a
certificate.
A
This
is
a
semi-trusted
networks,
so
we
have
something
which
is
which
certifies
my
public
key
in
bitcoin
I
can
generate
anytime
a
public
and
private
key
pair,
but
and
I
can
use
it
with
the
network,
but
this
is
a
fully
open,
permissionless
network
and
nobody
certifies
my
public
key.
So
I
can
generate
ssi
one,
but
there's
no,
something
it's
a
total
trustless
system.
So
there's
no,
like
trust
way
of
of
of
trusting
my
public
key.
The
point
is
behind
hyperledger
fabric
that
this
is
a
consortium
network
and
it's
it's
like.
A
You
can
build
up
like
semi-trusted
scenarios,
so
it
means
basically,
there
can
be
more
centralized
components
like
certificate
authorities
and
we
have
to
trust
in
the
public
keys
only
that
are
signed
in
the
signed
by
the
certificate
already.
So
this
is
like
a
consortium
and
permissions
network,
and
one
one
big
difference
between
like
bitcoin
and
and
and
hyperledger
fabric
in
terms
of
of
keys
keys
and
signatures
is
that
in
hyperledger
fabric,
these
signatures
must
be
trusted.
Somehow,
and
this
must
be
trusted
is
exactly
how
the
permission
blockchain
is
built
up.
A
Yeah
exactly
I
mean
you
get
absolutely
public
and
private
keys
keepers
and
they
work
pretty
much.
Similarly,
in
this
way
with
elliptic
digital
signature
algorithms
than
hearing
fabric
here,
the
big
difference
is
that
there
must
be
some
some
permission.
Permissions
built
in
the
system
and
the
permissions
are
built
in
most
with
the
way
of
of
having
like
certificate
authorities,
signing
your
public
keys
and
trusting
only
indesign
public
keys.
A
A
So
so
then,
the
next
slide
is
so
again
conceptually
what
we
got
here
if
we,
if
we
just
take
a
look
on,
let's
just
compare
like
bitcoin
and
and
hyperledger
fabric,
just
from
a
conceptual
point
of
view,
so
the
point
is
with
bitcoin
you
get
like
peace
running
your
blockchain
or
clients.
You
can
call
it
as
bitcoin
clients
and
basically
it
looks
that
way
everybody
can
can
run
appear.
So
basically,
if
I
download
bitcoin
core,
I
can
synchronize
my
network.
A
It's
gonna
take
a
while,
but
anyway
I
can
attach
to
the
network,
and
I
can
do
whatever
I
I
want
whatever
I
can.
So
this
is
an
open
permission.
Blockchain,
of
course
I
mean
there's
a
there's,
a
limited
resource
in
the
system.
That's
computation
at
the
moment
which
might
not
be
unlucky,
so
I
can
do
anything
in
the
network
up
to
my
computation
power.
Let
me
put
it
that
way,
but
this
is
like
an
open
permission
network.
The
major
idea
between
between
behind
hypo
ledger
fabric,
that
this
is
pretty
strongly
a
consortium
network.
A
So
it
means
you,
don't
have
the
peers,
the
clients,
just
I
mean
all
over
the
words
running
by
anybody,
but
you
get
here
something
as
as
institutes
institutes
that
basically
know
each
other.
They
don't
necessarily
trust
fully
in
each
other.
But
at
least
usually
we
say
that
hey.
These
are,
like
I
don't
know
like
financial
institutes
wanting
to
build
up
kind
of
a
network
and
we
get
like
these
five
financial
institutes.
A
This
is
just
four
but
anyway,
four
financial
institutes
in
the
network
and
they
wanting
to
cooperate
and
they
wanted
to
share
information
and
they
at
least
a
little
bit
trust
each
other,
not
fully
trust,
but
at
least
a
little
bit.
Trust
and
anybody
wanting
to
join
to
the
network
is
not
such
an
easy
process.
A
So
this
is
something
which
means
this
is
this
is
a
consortium
permission
network
and
then,
from
another
point
of
view,
that's
from
the
infrastructure
point
of
view.
If
you
take
a
look
on
the
client,
basically
in
bitcoin
it
looks
that
way.
Anybody
can
basically
generate
a
public
private
key
pairs
and
can
start
to
to
use
the
network.
So
there's
no
limit
on
that.
But
basically
it
doesn't
look
like
in
high
polisher
fabric.
Hyper
logic
is
a
is
the
primary
permission.
A
There's
more
trust
in
the
system
than
in
bitcoin,
because
because
you
know
I
mean
in
bitcoin,
you
don't
want
to
trust
anybody.
You
don't
want
to
know
anybody
in
a
consortium
network.
I
would
say,
there's
a
little
bit
more
trust
in
the
in
the
in
other
in
other
institutions
as
well,
because
because
the
point
is
basically
that
so
usually
there's
you
don't
expect
from
another
organization
to
to
attack
the
whole
network.
A
Okay,
so
basically
it
looks
that
way
in
bitcoin.
Nobody
knows
where's
your
where's,
your
where's,
your
client
where's,
your
where's,
your
node.
Basically,
if
you,
if
you
have
like
a
five
node
organization
in
a
consortium
network,
at
least
they
they
know
each
other,
so
they
are
not
animals.
So
if,
like
one
one
organization
try
to
attack
the
network,
then
the
others
will
recognize
it
we'll
know
exactly
who's
the
kind
behind
the
things
who's,
the
guy
behind
that
institution.
So
what
they
can
do,
they
can
have
something.
A
A
I
wouldn't
say,
because
I
mean
it
looks
that
way
that
you
find
you
find
a
coding
in
github.
So
of
course
you
have
to
trust
the
code,
but
this
is
a
totally
open
source
project.
So
what
you
can
do
you
can
download
the
code
and
then
you
can
review
it.
I
mean
by
to
buy
it
just
like,
as
seen
as
in
any
kind
of
a
public
blockchain
network.
So
you
don't
have
to
trust
the
linux
foundation.
A
B
B
A
So
sensor,
ship
resistance
depends
actually
a
little
bit.
It's
a
more
difficult
question.
I
would
say
it's
like
we
can
have
some
sense
or
she
presses
stance,
but
it
depends
on
your
on
your
on
your
algorithm
actually
like
on
your
wall,
margarine,
so
what
you
can
do,
for
instance,
if
you
have
like
I
mean
sensory
resistance
in
hyperledger
fabric
depends
on
the
ordering
service.
Basically,
so,
if,
if
you
have
your
full
ordering
service
running
in
with
one
con,
actually
let
me
just
think
it
over.
A
You
can
build
up
actually
pretty
centralized
systems
with
hyperledger
fabric,
but
let
me
just
imagine
if
both
your
both
your
endorsement
policy
and
your
ordering
service
are
fully
decentralized.
Then
it
means
that,
like
let
me
let
me
say,
we
vote
for
a
transaction
with
the
forum
of
this
of
these
five
organizations.
A
So
if
three
of
the
organizations
says
yes,
then
your
transaction
is
valid
in
very
simple
terms,
and
if
at
least
free
organization
blocks
your
transaction,
then
your
transaction
is
blocked.
Okay,
so
it
means
it
has
some
some
centralization,
but
this
some
and
some
decentralization
as
well.
So
it's
less
censorship
resistance
than
bitcoin,
but
it
does
not
necessarily
look
that
way
that
one
organization
decides
if
your
transaction
involved
or
valid
or
not.
A
Yeah,
that's
right,
that's
right!
So
that's
not
much.
Dx
is
policy,
but
you
get.
I
mean
you
get
actually
so
hyperledger
fabric
has
a
has
like
several
stage
consensus
mechanisms.
I
have
one
slides
slide
about
if
you,
if
you're
interested,
but
it's
basically
several
stage
consensus
mechanisms,
so
it
is,
it
is
totally
different
from
the
consensus
of
of
bitcoin
but
yeah.
One
part
is
the
is
the
ordering
service.
So
actually
consensus
is
how
much
your
consensus
is
decentralized,
based
on
two
things.
A
So
if
your
notes
are
hacked,
then
basically
that's
a
problem
in
kafka.
There
can
be
configured
something
as
byzantine
for
tolerant
consciousness
as
well
up
to
one
by
byzantium,
filler
error.
But
the
point
is
that
kafka
is
basically
difficult
to
configure.
But
let
me
say,
let
me
put
it
that
way
that
basically
the
so
the
attack
model
for
a
consortium
network
is
pretty
different
from
an
attack
model
of
of
bitcoin
so
like.
A
If
you
want
to
attack
at
the
bitcoin,
you
have
one
one
scarce
resource:
the
scarcity
source
is
the
computation.
So
if
you
want
to
attack
the
bitcoin
network,
you
need
a
lot
of
computation
in
consortium
network.
Your
scarcity
source
is
basically
the
identity,
so
these
these
institutes
have
actually
an
identity
behind
and
only
only
institutes
or
actors
with
identity
can
participate,
somehow
the
network.
A
So
if
you
want
to,
if
you
want
to
attack
a
consortium
network,
what
you
have
to
do
is
basically
steal
an
identity,
so
that
basically
means
that
you
have
to
break
in
into
one
or
two
such
organizations.
So
you
have
to
hack
the
organization
id
and
then
you
have
the
chance
of
of
somehow
attacking
the
network.
But
if
you
just
imagine
that
these
institutes
are
like,
like
I
don't
know,
banks
or
financial
institutes,
usually
it
is
not
so
simple
to
break
in
into
the
idea
of
of
such
an
institute.
B
A
A
That
is
again
again
access
control
and
you
can
have
something:
that's
basically
ros
of
your
user.
So
you
can
say
that
hey!
This
is
an
administrator
all,
so
it
can.
It
can
actually
communicate
with
your
with
your
network
as
an
administrator,
or
this
is
a
normal
user.
Basically
and
normal
user
can
communicate
with
your
network
as
a
normal
user,
and
then
the
I
mean
the
wide
idea
or
not
so
wide,
but
the
difficult
idea
is
that
all
of
the
hyperledger
fabric
access
control
is
built
up
with
public
public
key
infrastructure.
A
So
that's
the
reason
why
it's
so
so
complicated.
So
basically
it
looks
that
way
or
it
can
look
that
way.
One
way
of
doing
this
is
like
you
want
to.
You
want
to
be
sure
that
the
that
the
peer
communicates
with
the
order
and
then
basically
a
message
comes
from
your
peer
if
it
communicates
within
order,
so
one
way
of
doing
is
is
to
put
your
public
key
to
put
the
the
public
key
of
your
peer.
B
A
It's
basically
the
same:
if,
if
an
ordering
service
wants
to
communicate
with
the
peer,
we
store
somehow
the
public
key
of
the
ordering
service,
and
then
we
know
actually
that
the
ordering
service
communicates
with
us
and
basically
it's
the
same
for
user
as
well.
So
if
a
user
wants
to
communicate
with
us,
then
we
can
see-
or
we
can
say
that
hey
we
store
the
public
key
of
the
user,
so
anytime
a
user
signs,
a
transaction
or
or
or
or
signs
even
a
communication
signs.
Even
a
message,
then.
A
A
We
can
have
a
folder,
we
can
call
it
even
as
membership
service
provider
and
then
basically,
if
a
user
signs
anything,
then
we
know
hey.
This
is
an
administrator
user
and
we
can
define
some
exercise
for
for
our
administrator
okay.
So
this
is
the
easy
way
it
can
be
realized
in
a
more
complicated
way
as
well,
because
I
said
hey
if
we
want
to
know
that
this
is
our
user.
This
is
our
admin
admin
user.
A
We
can
store
the
public
key
of
our
user,
but
basically
it
can
be
built
up
in
a
more
complicated
way
as
well.
We
don't
have
to
store
the
public
key
of
our
user,
because
actually
the
user,
with
the
we
designing,
can
send
the
not
just
the
public
key
but
somehow
the
whole
whole
certificate
x,
509
certificate
as
well,
and
if
we
know
that
this
public
key
is
basically
is
in
an
is
in
a
certificate
that
was
signed
by
a
certificate
authority
that
we
trust
in
then
we
can
say
hey.
A
A
A
B
B
A
That
I
have
here
an
administrator
certificate
and
an
administrator
certificate
looks
that
way
that
I
get
an
issuer.
So
basically
I
I
need
to
have
an
issuer,
that's
the
basis
of
the
trust.
So
not
anybody
can
be
actually
an
administrator
in
my
network,
but
only
somebody
having
basically
an
x,
509
certificate
or
basically
a
key
pair
for
that.
The
public
key
is
actually
signed
by
the
certificate
authority
with
some
actually
meta
meta
attributes
as
well.
A
A
So
anybody
anybody
seeing
actually
this
signature
with
this
kind
of
a
certificate
knows
that
basically,
this
was
done
by
an
admin
and
then
this
is
actually
the
name
of
the
admin
and
we
can
have
some
more
information.
Like
actually
I
mean
the
organization
and
stuff
like
that.
But
this
is
the
major
idea
for
for
access
control.
A
So
if
we
want
to
have
a
role
of
users
or
the
role
of
of
of
of
of
any
kind
of
network
components
and
law
means
that
members
of
the
role
having
like
you
know,
I
mean
I
mean
different
different
rights
of
doing
things.
Then
everything
looks
that
way.
Then
there
should
be
actually
a
public
private
keypad
and
then
the
public
key
should
be
signed
by
a
trusted
certificate
authorities
and
the
trustee
certificate
authority
should
say
as
well
that
hey
this,
this
public
key
is
related
to
a
certain
role.
A
B
B
A
So
so,
based
on
this
stuff,
we
get
the
we
get
the
membership
service
provider.
I
mean,
if
you're,
if
you
heard
them
about
like
hyperledger
fabric
you,
you
probably
heard
that
so
membership
service
provider
is
this.
Is
this
lot
of
keys
are
collected
together,
having
access
to
the
components
to
each
other?
Okay?
So
if
you,
if
you
just
take
a
look
in
this
in
this
crypto
config
folder,
it
has
actually
a
lot
of
keys,
not
just
membership
service
providers.
B
B
A
So
if
you
just
take
a
look
on
your
crypto
cryptoconfig
folder
and
you
go
to
like
one
beer-
and
this
is
one
beer
under
one
beer-
this
is
like
one
component.
You
see
like
the
msp
folder,
an
msp
folder
is
actually
this
this,
this
bunch
of
keys
and
certificates
related
to
the
to
the
local
local.
You
know,
I
mean
who's
who,
in
the
network,
who's
who
and
what
rights
or
access
can
do
anything
on
the
local
peer
staffs.
A
So
basically,
you
have
here
like
administrator
search.
These
are
the
signs,
so
these
are
the
certificate
authority
sets
that
we
trust
in
this
is
the
this.
Is
the
identity
key
for
your
peer,
for
instance,
and
this
is
the
public
key
signed
by
your
certificate
authority
as
assigned
science,
science
certificates,
and
we
get
something
as
tls
we
can.
We
can
configure
like
tls
and
secure
connection
as
well,
and
it's
getting
even
more
complicated
okay,
but
the
point
is
basically
that
membership
service
provider
is
really
this.
A
A
It's
because
here
so
basically,
you
have
usually
in
the
different
test
networks.
If
you
use
with
like
fabric
samples,
you
get
basically
a
generate
script
and
generate
uses
one
built-in
tool,
that's
cryptogen
and
cryptogen
generates
for
you,
based
on
your
crypto
configura,
some
default
certificates
for
for
development
and
for
testing
reasons.
So
it's
just
you
know
much
easier
to
start
basically
or
your
network,
but
this
is
not
really
production
ready.
If
you
just
take
a
look
on
config,
it
looks
that
way
that
sorry,
this
is
the
wrong
conflict.
A
A
So
if
you're
not
very
much
familiar
with
higher
league,
it
was
probably
a
difficult
presentation.
This
is
like
hyperledger
fabric
here,
so
it's
like
you
know:
consortium
blockchain
networks.
You
get
different
components
on
your
network
like
peers,
ordering
services
certificate
authorities,
so
everything
which
is
one
client
one
node
with
bitcoin
that's
distributed
in
a
fully
microservice
architecture.
A
B
A
Stories,
if
you
good
yeah,
so
there's
one
question:
how
does
high
pleasure
topic?
Two
plus
version
supports
ubuntu
20,
it's
a
good
question.
It
should
actually
you
find
something
as
basically
as
an
installation
as
an
installation
guide
on
hyperledger
fabric.
It's
actually
one
script,
that
you
have
to
run
it
downloads,
all
of
your
components,
containers
and
then
installs
your
fabric,
samples,
where
you
kind
where
you
can
find
stuff
like
that
like
for
generated,
configs
and
and
other
stuffs,
but
it
might
be
actually
an
old
question.