►
From YouTube: Ask the Expert: Technologies for Meeting Privacy Requirements in... - Peter Broadhurst & Jim Zhang
Description
Ask the Expert: Technologies for Meeting Privacy Requirements in Enterprise Blockchain Networks - Peter Broadhurst & Jim Zhang, Kaleido
Privacy is among the top priorities of an enterprise blockchain network. Yet blockchain as a technology built on a shared ledger as its corner store, does not naturally offer privacy. Join this session to learn about the five technologies/techniques to build a blockchain based solution supporting various types of privacy requirements. They are: data isolation (channels), private transactions, and approaches involving off-chain compute technologies including zero knowledge proofs (ZKP), trusted execution environments (TEE) and secure multi-party computes (MPC). The session will cover how each of them works, how they are utilized in a blockchain based solution and what use cases they are best suited for.
Session Details & Slides (if available)- https://sched.co/j3eR
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
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 #HyperledgerGlobalForum2021 #Blockchain
A
Sounds
like
we're
get
started
hello,
everybody.
This
is
jim
and
peter
from
collido,
really
great,
be
back
on
the
global
forum.
This
exciting
annual
event
of
everybody
from
all
the
world
that
care
about
blockchain,
especially
its
adoption
in
enterprise
use
cases.
So
today,
we'd
like
to
talk
about
privacy
in
particular,
so.
A
We
okay,
so
the
agenda
is
two
parts
we'd
like
to
first
spend
a
few
minutes
just
to
recap
on
the
current
techniques
today
and
each
addressing
this
different
aspect
of
privacy
and
then
the
second
part
we'd
like
to
take
a
look
at
the
evolving
multi-party
systems
and
see,
if
there's
a
framework
that
can
tie
them
together
and
through
plugins,
to
bring
all
these
different
techniques
together
into
a
coherent
system.
So
when
you
build
your
solutions,
you
might
use
different
pieces
depending
on
your
specific
requirements.
A
So
you
don't
have
to
hunt
down
individual
technologies
yourself,
so
starting
with
sort
of
the
lay
of
the
land
in
terms
of
privacy
techniques
that
are
being
used
when
you
are
building
a
multi-party
system
from
with
the
foundation
on
the
blockchain.
Obviously
you
can
create
separate
instances
of
blockchain,
so
data
and
identity
is
completely
isolated.
A
If
you're
not
part
of
this
chain,
then
you
don't
know.
What's
going
on,
you
can
use
techniques
that
mask
your
submitters
transaction
submitters
identity,
either
using
true
random
or
pseudo-random
keys
to
sign
the
transaction.
So
they
look
like
they
come
from
completely
random
parties,
but
you
can
hold
the
the
master
key
to
all
of
them
so
that
your
trading
pattern
would
not
be
leaked
and
then
you
can
have
off
chain
communication,
so
your
sensitive
data
or
kind
of
business
data-
that's
very
key
to
your
business.
A
Competitive
edge,
are
transferred
to
your
parties
of
the
chain.
So
it's
not
a
broadcast
to
everybody
and
you
keep
your
private
data
private
and
then
in
these
green
boxes.
We
we
see
emerging
technologies
that
are
utilizing
more
advanced
cryptography
in
terms
of
produce,
producing
zero
knowledge
proofs
using
a
trusted
compute
on
the
special
hardware
or
using
multi-party
compute
to
make
the
output
collaborative,
but
no
one
has
the
whole
secret.
A
A
It's
worth
mentioning
that
technologies,
like
hyperledger
fabric,
makes
this
much
easier
with
their
channel
technology
so
that,
on
the
same
network,
with
the
same
set
of
identities,
you
can
create
multiple,
essentially
multiple
instances
of
blockchains
called
channels
with
its
own
governance
model,
its
own
permissioning
configurations
and
if
you're,
not
part
of
a
channel.
You
have
no
idea
what's
going
on
inside
that
channel.
A
So
everybody
on
the
chain
is
paying
the
duty
of
protecting
that
transactions.
Data
commitment
on
the
chain,
but
the
actual
data
is
only
communicated
among
the
parties
involved
in
the
transaction
and
and
so
that's
about
protecting
the
payload
of
the
transaction.
So
what
about
protecting
the
the
identity
of
the
transaction?
Submitter
in
certain
use
cases?
You
don't
want
your
sort
of
trading
pattern
to
be
analyzed
by
your
competitors
on
the
same
chain,
so
you
want
to
protect
your
submission.
Your
submissions,
identity,
signing
identity
in
certain
chains.
A
The
idea
is
I
can
you
just
go
ahead
and
use
complete
random
transaction
signing
keys,
but
then
you
have
to
keep
track
of
each
of
them.
So
that's
a
pretty
big
headache
and
overhead
or
you
can
use
this
technique
using
key
derivation
so
that
a
single
master
secret
can
be
used
to
generate
billions
of
derived
keys
that
you
know
to
the
outside
world
looks
completely
random,
even
though
they
are
all
generated
from
same
key.
A
Then
we
talk
about
two
off-chain
communication
technologies.
You
sometimes
you
just
want
to
send
some
structured
data
or
smaller
piece
of
json
from
one
party
to
another,
app
to
app
messaging.
It's
a
pretty
popular
technique,
even
though
there
are
different
implementations
by
different
vendors,
it's
usually
backed
by
a
enterprise
grade
queue
so
that
data
can
trans
transfer
from
one
party
to
another
without
getting
lost,
even
if
the
receiver
at
that
time
is
not
online,
so
using
kafka
or
other
queuing
technologies
and
then
utilize
encryption.
A
A
Now
we're
talking
about.
So.
If,
when
you
put
all
of
your
processing
logic
on
chain,
it's
pretty
difficult
to
protect
it
from
from
leakage
because
number
one,
everybody
will
see
that
if
it's,
if
it's
stored
on
the
chain
and
data,
because
because
the
processing
logic
is
on
chain,
the
data
itself
itself
must
be
unchanged
as
well.
A
So
what
if
we
take
both
the
processing
and
data
off
the
chain
and
make
it
happen
somewhere
else,
but
now
you
have
the
burden
of
proving
to
all
the
parties
on
the
chain
that
you
haven't
cheated
right.
If
you
are
spending
a
hundred
dollars,
then
your
transaction
is
deducting
a
hundred
dollars
from
your
account.
You
didn't
cheat
by
deducting
only
fifty
dollars
and
claim
you
have
deducted
a
hundred.
So
how
do
you?
How
do
you
prove
to
everybody
that
you've
done
this
transaction
honestly?
A
So
there
are
two
techniques:
one
is
using
a
cryptography
of
generating
a
proof
that
I've
done
this
particular
computation,
and
this
is
the
proof
that
I've
carried
out
that
computation
according
to
the
to
the
claim
the
other
technique
is
you
can
sort
of
lock
all
this
logic
and
data
into
a
secure
place.
So
no
one
can
see
it,
not
even
the
administrator
of
that
chip
can
see
it,
but
you
can
ask
the
chip.
A
So,
with
all
these
techniques,
it's
pretty
exciting
that
you
are
able
to
use
these,
for
you
know,
depending
on
your
specific
requirements,
but
you're
using
each
of
them
is
is
hard
enough.
You
know
think
about
generating
the
zero
knowledge
proofs
think
about
creating
the
off-chain
channels
that
are
reliable,
that
are
utilizing
end-to-end
encryption
doing
all
of
that
is
is
like
doing
any.
Some
of
that
is
necessary
to
create
a
real
world
enterprise
blockchain-based
solution.
A
So
now
it
gets
us
thinking
what
if
we
have
a
framework
that
makes
all
of
this
easier.
What
if
we
have
a
framework
that
has
all
box
support
for
some
of
this
and
then
have
plugging
systems
to
to
support
future
technologies?
That
may
be
developed,
so
we
don't
have
to
understand
them
individually.
We
just
stay
within
the
network
and
they
all
get
plugged
into
it
in
the
future.
A
So
now
we're
I'm
very
excited
to
talk
to
introduce
to
you
guys,
firefly,
and
this
is
really
a
multi-year
evolution
within
the
collido
team
and
now
it's
part
of
hyperledger
labs.
In
fact,
seven
individual
code
repositories,
encompassing,
I
think,
tens
of
thousands
of
lines
of
code
just
landed
today
in
the
hyperledger
labs
repository
and
we're
very
excited
to
share
this
with
you,
the
previous
generation,
that's
also
in
production
with
many
of
our
customers,
were
written
by
our
awesome
engineer.
A
Gabriel
indic
and
the
new
generations
have
have
taken
all
the
lessons
we've
learned
from
deployment
from
building
the
solutions
for
our
customers
and
we
have
a
a
more
efficient,
a
better
architected
framework.
That's
now
contributed
to
high
pledger.
So
now
I'm
going
to
introduce
you
guys
to
peter
broadhurst,
our
head
of
engineering
and
the
creator
of
firefly.
B
Thank
you,
jim
yeah,
so
I
guess
75
000
lines
of
code.
I
think
drops
dropped
as
the
seed
contribution
for
for
this
and
it's
I,
I
think,
a
significant
gap
that
that's
being
addressed
in
in
what
we
really
are
striving
to
be
a
vibrant,
open
community
here
to
solve
the
real
problem,
the
elephant
in
the
room
for
blockchain.
B
B
It's
an
enterprise
use
case
because
it
integrates
with
the
100
plus
years
of
innovation
on
the
business
side.
That's
happening
between
these
large
organizations
coming
together
to
form
a
business
ecosystem
and
we've
seen
over
and
over
again
the
same
journey
being
taken
by
by
business
networks,
the
the
the
the
start
of
the
journey.
It's
the
same
feeling
right.
B
What
you're
actually
building
is
trying
to
build
a
multi-party
system
where
that
little
kernel
of
on-chain
logic
fits
it's.
It's
not
the
whole
problem,
it's
just
a
piece
of
the
puzzle
and
actually
the
time
the
effort,
the
energy,
the
resource,
the
collaboration
over
many
years.
We
see
if
you
start
from
scratch,
goes
into
the
plumbing
goes
into
the
integration
with
your
core
systems
goes
into
reconciling
data
formats
and
the
differences
between
all
of
the
hundreds
of
years
of
business
evolution.
B
That's
happened
separately
across
these
organizations
and
combining
it
together
and
actually
the
number
of
projects
that
can
get
through
that
show
business
value
quickly
enough
quickly
enough
to
really
keep
the
interest
the
motivation,
the
projects
alive.
It's
it's
not
easy
to
do.
Nowadays,
it's
it's
a
the
getting
stuck
in
the
plumbing
just
seems
to
be
so
common
and
we
we're
lucky
right.
B
Now
we
don't
think
that
that
is
enough
for
multi-party
systems,
so
blockchain
and
all
of
the
other
technologies
that
are
about
allowing
systems
to
collaborate
in
a
different
way
to
how
they
have
done
in
the
past.
We
don't
think
it's
enough
to
just
have
a
company.
That's
there
trying
to
help
individual
companies.
B
B
B
Level,
but
you
know
a
layer
above
the
sort
of
second
layer
of
technology,
huge
amounts
of
strong,
open
source
projects
that
focus
on
that
area,
but
actually
that
that
sort
of
10
percent
of
the
overall
job
for
for
a
business
network.
That's
trying
to
actually
build
a
solution
here
and
this
center
in
the
middle.
B
That's
all
about
that
private
data,
all
about
the
plumbing
all
about
the
integration
that
happens
off
chain
as
much
as
it
happens
on
chain
that
piece
in
the
middle,
that's
sort
of
between
the
innovation,
that's
business
specific
at
the
top
and
the
core
blockchain
technology
at
the
bottom.
There's
just
nothing!
Nothing!
There!
That's
comprehensive!
B
So
we're
we're
really
excited
to
be
part
of
the
formation
of
this
gym.
If
you
just
move
on
to
the
next
slide,
so
it's
it's
firefly!
It's
it's
there!
It's
it's
in
the
open!
It's
a
a
really
big
engineering
commitment
to
get
it
started,
but
we're
at
the
beginning
of
that
journey
on
the
community
side,
which
means
that
everybody
has
the
opportunity
to
really
be
start
at
the
start
of
the
transformation
that
this
can
can
cause,
and
what
firefly
is
is
about
accepting
the
reality.
B
The
reality
that
building
a
multi-party
system
between
large
enterprises
is
about
more
than
blockchain
it's
about
more
than
blockchain
and
actually
more
than
anything
about
else.
It's
about
allowing
the
developers
web
traditional
enterprise,
api,
microservice
developers,
the
developers
and
the
integration
teams
of
these
organizations
that
are
trying
to
get
together
to
build
the
build.
B
Let's
make
the
technology
serve
the
business
use
case
and
the
developers,
let's
have
a
great
rest
api.
Let's
have
events
that
you
don't
need
to
like
be
some
specialist
to
decode
and
understand
the
hashes
to
use.
Let's
have
it
so
that
the
programming
model
is
easy
to
understand
and
easy
to
describe
so
that
you
just
get
on
with
building
your
use
case,
and
let's
embrace
the
fact
that
body
party
systems
are
never
going
to
be
just
one
technology.
B
It's
never
going
to
be
just
choose
your
blockchain
like
I've
chosen
fabric
or
I've
chosen,
the
hyperledger
besu
like
it's.
It's
never
going
to
be
that,
and
I'm
done
it's
actually
going
to
be
well.
Okay!
Well,
that's
the
blockchain
piece
of
it
solves,
but
what
about
the
off-chain
messaging?
Am
I
using
kafka?
Am
I
using
rabbitmq?
Am
I
using
active
enqueue?
What
what
am
I
doing
there
do?
I
need
end-to-end
encryption
of
that
off
chain
messaging.
B
What
about
the
the
shared
storage?
That's
too
big
to
actually
go
on
the
blockchain
things
like
ipfs
or
swarm?
Where
do
they?
They
they
plug
in?
What
about
the
fact
that
you
actually
need
your
own
private
copy
of
your
own
private
data
and
your
application
needs
this
fast
cache
where
it
can
query
the
stuff
and
find
the
stuff?
What's
the
history,
how
do
they
get
to
this
state
of
the
world?
B
B
You
know
so
many
years
of
experience
in
the
in
in
sort
of
across
multiple
projects,
be
that
having
contributed
to
all
the
top
three
of
the
of
the
blockchain
ones,
but
also
avalon,
and
these
other
projects
to
actually
say
well
just
a
minute.
All
of
this
innovation
that's
happening
the
lines
that
are
blurring
between.
What's
a
zkp
solution
versus
a
blockchain
solution?
Where
does
off-chain
compute
fit
in
all
of
that?
B
Can
integrate
into
this
ecosystem
as
as
well
and
to
do
it
with
enterprise-grade
engineering,
a
truly
open
approach
and
actually
bring
all
of
this
sort
of
production
experience
that
we've
got
because
we've
brought
you
know
these
years
of
of
code
along
along
with
it?
Well
well,
also,
a
lot
of
it
is
being
being
intentionally
started
again
in
order
to
make
it
open
and
pluggable
and
to
bring
the
community
in.
B
B
But
we
put
a
lot
of
effort
into
the
extensibility,
getting
the
foundations
there
to
allow
lots
of
parts
of
the
hyperledger
community
to
come
together
and
plug
into
this,
but
also
allowing
lots
of
innovation
of
of
other
projects
that
aren't
necessarily,
quite
so
blockchain.
So,
for
example,
we're
great
friends
with
projects
like
node
red,
for
example,
for
for
low
code,
low
code,
development
of
business
logic,
but
they're
a
place
where
they
can
come
together.
B
So
we
sort
of
talk
about
a
periodic
table
of
elements
as
the
way
that
you
can
sort
of
plug
into
the
system,
and
the
firefly
node
is
a
micro
services
architecture,
which
means
that
it
can
take
java
codes.
So
if
you've
got
the
corner,
plugins
is
all
java,
because
that's
the
only
way
to
do
it
in
quarter
like
well
that
can
fit,
even
though
that
core
brain
is
is
go
now
that
that's
been
built
in.
If
you
move.
A
B
Forwards
again,
jim,
and
if
you
when
you,
when
you
think
about
it,
this
makes
it
a
very,
very
different,
shaped
project.
What
one
of
the
the
things
that's
unique
about
firefly
is
that
it's
not
linked
to
an
individual
one
of
the
you
know
what
I
guess
in
some
places
have
become
a
little
bit:
siloed
pieces,
sort
of
spaces
of
innovation
in
the
enterprise
blockchain
and
space.
B
We've
actually
got
projects
that
started
on
one
of
the
big
three
and
moved
to
another
one,
I'm
not
going
to
say
which
direction
they
went
in,
but
between
ethereum
and
quarter.
We've
actually
proved
that
it's
actually
genuinely
possible
to
have
applications
that
are
one
layer
detached
from
the
blockchain
in
cases
it
makes
sense,
and-
and
that's
when
you're,
using
reusable
constructs
that
are
universal,
like
sequencing
like
for
me.
B
It's
it's
amazing
that
blockchain
solved
from
the
hardest
problems
in
moddy
party
systems
that
existed
the
whole
of
my
career,
of
allowing
multiple
organizations
to
sequence,
things
in
the
same
way
like
that
magic
problem,
absolutely
magic
problem.
Everyone
can
have
that
software
to
build
a
smart
contract
for
it.
It
can
come
with
the
technology
same
to
nfts,
right,
nfts,
really
well
understood.
We
know
how
to
do
them
as
a
developer.
You
shouldn't
need
to
like
think
well
just
a
minute.
B
Where
do
I
go
and
get
the
source
of
of
an
arc
721
from,
and
is
that
really
the
standard?
I
want
wait.
Well,
you
don't
have
to
do
about
databases.
You
just
have
to
go
well,
where's,
my
sql
query,
I'll
just
I'll.
Just
just
call
it
so
moving
away
from
a
world
of
everything
is
like
a
stored
procedure,
build
it
from
scratch
to
reusable
patterns
and
then
the
ability
to
drill
down
and
use
the
unique
features
of
each
of
these
technologies.
B
Where
you
want
to
right,
you've
got
some
specialist
logic,
that's
only
available
someone's
built
it
just
for
fabric
great
fantastic.
You
need
the
channels
of
fabric,
absolutely
brilliant.
You
you
really
like
the
community
around
tokens
and
the
tried
by
far
erc
20
standard
of
ethereum,
brilliant,
just
just
just
go
and
use
that
you
can
drill
down
and
use
the
best
features
of
these,
and
it
extends
more
than
just
the
the
hyperledger
family.
B
B
The
first
and
I
think
the
most
important
is
non-blockchain
developers.
I
just
want
to
use
you
like
a
user
database.
I
don't
care
how
the
internal
transaction
replay
system
of
the
database
works.
I
just
use
sql
and
it
works
or
just
use
nosql,
and
it
works
if
you're
even
more
modern
developer,
give
that
kind
of
great
experience
to
developers,
and
that
means
they
expect
tooling
that's
going
to
allow
them
to
see
when
things
have
gone
wrong.
So
we've
started
with
a
cli
comes
with
this
out
of
out
of
the
box.
B
There's
a
whole
cli
project
get
started
in
30
seconds.
Do
it
yourselves
come
along
on
friday,
enjoy
enjoy
joy,
actually
getting
started
with
the
tech,
make
it
really
easy,
a
user
experience
that
actually
lets
you
see
what's
going
on
as
you're
as
you're
doing
it
and
see
all
the
coordinations,
the
ping
pong,
we
call
it
between
yon
chain
stuff
and
the
off
chain
stuff
and
how
everything
works
together.
So
a
user
experience
with
it.
So
a
big
focus
on
that
on
that
developer
and
then
the
second.
The
second
focus
is
on
the
operational
side.
B
So
a
lot
of
efforts
got
in
to
make
it
pluggably
opera.
Up
from
an
operational
perspective,
think
about
things
like
active
active
which
get
forgotten
in
a
lot
of
projects
after
until
a
long
period,
in
think
about
things
like
well
just
a
minute.
How
does
this
integrate
with
my
database?
How
does
this
integrate
with
the
on-chain
stuff?
How
does
it
all
fit
together?
And
how
do
I
view
what's
going
on?
B
So
that's
another
big
persona
for
us,
so
that's
that's
the
second
one
and
then
the
third
one,
and
this
really
isn't
the
you
know
this
is
the
best
for
last.
I
guess,
which
is
the
community,
that
this
is
the
sort
of
project
we
want
to
unify
things
a
little
bit
like
the
nascent
percent
potential
of
a
docker
had
right
at
the
the
beginning,
this
fantastic
transformative
technology.
B
It
wasn't
actually
achieved
for
enterprise
until
kubernetes
came
along
and
kubernetes
allowed
it
to
be
consumable
and
work
from
a
from
the
perspective
of
all
of
those
operational
and
non-functional
requirements
that
are
needed
and
to
make
it
really
easy,
and
that
happens
because
of
collaboration.
That
happens
because
cuba
and
kubernetes
is
not
like
a
one
technology
thing.
B
So
if
you,
if
you
move
forwards,
one-
and
I
know
we're
just
a
a
time
here-
this
is
a
teaser
today
and
I
I
think
it
will
be
fantastic
for
everybody
here
and
tell
your
friends
and
share
about
it.
If
you
think
that
there's
a
problem
to
get
to
to
solve
here
come
along
on
friday,
and
let's
talk
about
it,
let's
see
where
we've
got
to
with
this
seas:
let's
try
it
on
our
laptops,
let's,
let's
poke
at
it.
B
Let's
see
the
you
know,
the
the
the
potential
value
that's
here
on
whether
this
particular
direction
is
something
that's
really
going
to
create
the
transformation
that
we
all
need
in
the
blockchain
space
and
let's
get
things
going
so
we've
we've
put
in
put
together
a
full
full
half
day
of
activities
on
on
friday,
with
hands-on
labs
lots
of
chance
to
talk
to
all
of
the
developers.
I
mean
collido
and
to
talk
about
how
we
take
this
thing
forwards,
deep
dive
into
the
architecture
the
dive
into
like,
where
does
blockchain
fit
in?
B
Where
does
the
off
chain
fit
in?
How
do
they
collaborate
together?
So
I
really
hope
to
see
you
all
there
on
friday
and
also
please
do
share
it
around,
because
oh
our
feeling
is
that
this
is
a
problem
that
really
does
need
solving
in
the
space
and
that
we
can
get
together
and
we
can
solve
it
in
a
really
meaningful
way,
and
thank
you
so
much
for
the
time
today.