►
From YouTube: Blockchain Interoperability: Challenges, Ongoing Efforts, and Potential Solutions - Vinayaka Pandit
Description
Blockchain Interoperability: Challenges, Ongoing Efforts, and Potential Solutions - Vinayaka Pandit, IBM Research - India
DLTs have seen signifiant innovation and a wide range of application, from streamlining cross-company business processes and tokenizing assets to supporting self-sovereign identity. But increasing protocol heterogeneity and network specialization is driving the emergence of data and value silos, impeding the vision of a decentralized Internet. Addressing this issue requires seamless interoperation between diverse DLT networks while preserving the properties of decentralization beyond the boundaries of a single network. In this talk, Vinayaka will analyze interoperability and its technical and governance challenges, survey prominent efforts and emerging patterns in this area, and present a point of view on the salient design aspects of blockchain interoperability stemming from his experience of enabling interoperability between networks built on multiple different blockchain protocols.
Session Details & Slides (if available)- https://sched.co/j3dr
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
Thanks
again,
this
topic
is
on
blockchain
interoperability.
My
name
is
vinayak
pandit.
I
blockchain
and
supply
chain
strategy
at
ibm.
Research
based-
and
this
point
of
view
really
is
a
joint
work
with
my
colleagues
from
ibm
research,
venkatraman,
ramakrishna
rama
in
short
and
ermias
abhibi,
who
was
part
of
ibm
research.
A
A
A
A
A
Okay,
so
I
was
for
blockchain
interoperability
right.
So
if
you
can
really
look
at
this
question
from
two
points
of
view,
one
is
looking
at
the
the
stage
in
the
technology
evolution
when
it
comes
to
blockchain
right
in
some
sense,
especially
in
the
enterprise
setting,
is
still
in
its
infancy
right
and
we
have
many
different
abstractions
of
the
concept
and
for
many
different
implementations
of
these
abstractions
right
and
these,
and
these
abstractions
right
are
actually
implemented
on
different
type
technical
stacks
right.
A
For
example,
we
have
certain
networks,
which
is
meant
only
for
certain
networks,
which
are
meant
only
for
certain
aspects
of
trade
finance,
whereas
we
might
have
very
general
networks
looking
at
all
aspects
of,
let's
say
trading,
so
that's
one
aspect,
technology,
the
heterogeneity
of
technical
stacks,
different
abstractions
and
implementations,
and
the
second
aspect
is
really
the
way
the
techno
adopts
in
the
enterprise
setting
right.
So
the
adoption
is
really
a
very
gradual
adoption
and
the
adoption
through
use
cases
right.
So
people
are
finding
meaningful
use
cases
that
give
immediate
benefit.
A
These
boundaries
are
fairly
narrowly
defined
and
the
use
cases
themselves.
Even
if
you
look
at
it
from
the
point
of
a
single
organization,
they
just
cover
a
slice
of
the
business
right.
For
example,
you
know
point
of
view
of
a
single
organization
right,
you
know
its
trade
logistics
related
aspect
might
be
covered
on
a
trade
logistics
network.
A
A
So
in
the
last
two
years,
on
the
left
hand
side,
I
have
pointed
out
some
of
the
pro
market
research
reports
that
have
come
out
right
and
you
can
see
familiar
names
like
idc
world
economic
forum,
eu
commission,
forest
turrets
right
and
then
some
of
the
major
vendors.
When
it
comes
to
blockchain
adoption
code,
ibm
accenture,
they
all
have
come
out
with
their
own
view
of
interoperability,
in
which
there
are
a
lot
of
commonalities
right,
so,
which
is
actually
a
good
sign
that
this
is
the
right
time
to
look
at
this
particular
topic.
A
So
what
are
the
object?
Interoperability
right.
So,
as
I
said
you
know,
we
have
networks
that
are
coming
up
in
isolation
and
in
some
sense
the
picture
on
the
left
hand
side.
You
know
depicts
that
right,
so
you
might
have
a
a
you
know:
a
logistics
network
which
is
really
not
talking
to
network
or
trade
finance
network
and
so
on
and
so
forth.
Right
and
what
we
really
want
them
to
be
able
to
do
is
to
kind
of
seem
and
give
an
up
user
as
if
that
user
is
seamlessly
working
across
a
complex
workflow.
A
By
connecting
all
these
different
networks
right,
so
remove
the
networking
data
silos
right.
So
that's
actually
one
important
thing
and
second
thing
is:
it
will
allow
individual
networks
to
focus
on
what
is
they
are
most
competent
right
like
for
payment
and
focus
exclusively
on
payments
and
logistics
network
and
exclusively
scaling
logistics,
network
etc,
and
it
will
create
very
new
and
novel
type
of
network
effects
right,
for
example,
certain
kind
of
business
interactions
that
today
do
not
take
place.
A
A
We
might
even
have
new
networks
that
come
up
and
overall
we
expect
that
this
will
blockchain
market
size
and
you
know,
increase
liquidity
of
assets
within
the
networks
and
actually
create
a
next
level
of
efficiency
right.
So
here
I'll
just
take
a
pause
and
just
go
back
to
the
chat
room,
to
see
that
to
make
sure
that
you
are
all
able
to
view
the
tran
slides
easily.
A
Simple
technical
matter
right
so,
as
as
technology
really
focus
on
levels
of
interoperability
right,
you
know
the
technical
layer
which
really
looks
at
wire
protocols.
What
kind
of
you
know
delivery
guarantees?
Are
there
etc
syntactic
layer
which
focuses
on
the
protocol
structures
and
how
the
payloads
are
formatted
and
so
on,
and
then
the
semantic
layer
right,
which
is
where
the
blockchain
aspect
really
starts
coming
into
in
the
form
of
different.
You
know
type
of
all
messages,
whether
they
are
a
data
transfer
asset
transfer.
A
What
are
really
important
are
existence
of
you
know:
domain
standards
in
application
areas
where
the
needs
to
work
in
the
case
of
supply
chain
and
logistics.
You
know
exist
of
standards
like
gs1,
etc,
which
will
allow
you
know
the
underlying
exchange
across
different
blockchain
networks
to
be
made
sense
of
at
the
application.
A
You
know,
changes
to
local
laws
and
regulations
to
actually
make
blockchain
based
business
flows
valid
right
and
to
call
out
here
that
when
we
say
when
we
talk
about
blockchain
in
the
context
of
multiple
networks,
one
can
actually
think
of
different
integration
patterns.
And
hence
we
want
to
call
out
the
pattern
that
we
are
most
concerned
with
right.
So
one
pattern
is
very
simple
right:
you
are
a
big
organization,
big
retailer
and
you
know,
and
you
are
participating
in
a
network.
You
are
participating
in
a
trade
logistics
network.
A
The
second
one
is
that
you
know
you
might
want
a
single
network
in
which
this
bring
up
the
peer
infrastructure
in
the
way
that
they
actually
feel
most
comfortable
with
right.
For
example,
you
know
you
might
have
peers
that
are
on
entrepreneur
that
are
on
different
cloud
services
and
so
on,
and
you
should
be
able
to
orchestrate
a
single
network
and
possible
today
right
and
the
third
pattern
which
you
know,
the
the
interaction
between
the
two
networks
actually
take
place
at
the
application
layer
through
api
part
is
exposing
those
apis.
A
This
is
also
possible
today,
but
the
problem
with
this
pattern
is
that
the
underlying
decentralization
tenets
that
are
associated
with
the
decentralized
test
actually
get
lost
right.
So
we
are
really
interested
is
in
this,
what
I
am
calling
out
as
the
pattern,
four
in
which
the
networks
are
interacting,
while
enabling
data
and
value
exchange
right
while
preserving
the
dlt
tenants
right.
So
this
is
really
the
most
important
aspect
that
we
you
know
we
want
to
kind,
and
this
is
the
pattern
that
we
are
really
focused
on
right.
A
A
A
It
should
be
able
to
reason
about
the
identities,
transaction
and
state
of
the
right
and
that's
really
hard,
because
while
we
want
to
give
the
full
independence
day,
you
want
to
allow
them
to
reason
about
each
other
and
and
while
preserving
decentralization
right
without
introducing
trusted
third
parties
and
really
the
big
challenge
right
and
the
really
the
spectrum
of
blockchain
interoperability
right.
I
just
wanted
to.
A
Interoperability
is
that
there
are
two
different
networks
that
are
built
on.
Let's
say
a
fabric:
one
is
a
supply
chain,
finance
network,
another
is
a
logistics
network
and
you
they
should
be
able
to
exchange
information
between
each
other
right,
another
level,
and
then
you
might
have
a
network
which
is
built
on
one
protocol
like
let's
say,
fabric
trade,
finance
network
and
your
payment
network,
which
is
on
let's
say
ethereum,
should
be
able
to
interact
with
each
other.
A
That's
the
third
level
of
interoperation
right
and
then,
as
I
said,
for
the
sake
of
completion,
you
might
also
the
application
layers
talking
with
each
other
and
you
all
the
systems
to
be
able
to
interrupt
with
non-dlt
system.
Although
for
the
purpose
of
this
talk,
we
will
be
focusing
exclusively
on
these
three
parts
right.
A
So
just
to
say
so,
the
unique
challenges
is
really.
You
know
the
fact
that
the
ownership
of
a
state
in
a
single
party
system
lies
with
just
one
party
and
if
that
party
says
something
about
its
state,
you
can
trust
it,
whereas
in
multi,
in
a
multi-party
system
like
in
a
blockchain
network,
the
state
is
really
owned
by
the
collective
and
that
is
defined
by
the
participants
and
the
consensus
protocol
of
that
and
a
party
which
is
really
trying
to
consume
right.
A
So
the
roles
that
proofs
and
verification
play
is
very
important
and
then,
finally,
you
know
in
the
traditional
context,
interoperability.
We
typically
talk
about
data
interoperability,
right
people
are
able
to
exchange
messages,
but
here
we
are
actually
also
talking
in
terms
of
assets,
which
is
great
aspect
right
that
you
know
we
are
interested
in
is
asset
exchange
right.
So
the
essentially
the
change
of
ownership
of
an
asset
in
a
source
network
and
a
corresponding
change
of
ownership
in
another
network
right
so,
for
example,
delivery
versus
payment
in
the
context
of
trading.
A
So
this
is
one
classic
example:
asset
transfer
right,
so
here
you
know
we,
the
movement
of
an
asset
from
one
stress,
ledger
to
a
consuming
ledger
right,
so
the
asset,
the
asset,
cannot
be
double
spent,
which
means
that
on
the
source
network,
as
it
should
be
locked
and
then
be
released
to
be
used
in
the
consuming
ledger.
Right
simple
example:
here
could
be
movement
of
money
from
a
wholesale
cbd
retail
cbdc.
A
The
third
pattern
that
we
are
talking
about
here,
which
is
not
covered,
that
much
in
the
literature,
is
what
we
call
as
data
sharing
right,
which
is
the
consuming
ledger,
is
able
to
query
and
obtain
state
ledger
with
a
proof
of
validity.
Right.
An
example
is
a
trade
finance
network
right
wants
to
make
sure
that
there
is
a
valid
bill
of
lading
in
a
trade
logistics
network
before
issuing
letter
of
credit
right.
So
this
is.
A
A
And
then
we
have,
you
know
interoperability
in
which
there
are
no
intermediaries
right
independently
and
simple
example.
Here
is,
you
know,
asset
text
using
a
protocol
like
hash
time,
lock
contract
and
then
we
have
which,
through
a
project
which
I
will
be
covering
in
some
detail,
is
you
know
there
is
a
consortium
of
network
cross
chain
validators
in
which
the
consortium
has
presence
of
cross
chain
validators
in
each
one
of
the
networks,
and
then
they
talk
amongst
themselves
to
create
federation
right.
A
A
Current
and
on
and
the
other
pattern
which
we
said
is
for
the
networks
to
operate
independently
and
then
basically
interact
with
each
other,
using
the
format
of
claims
and
proofs
right.
So
this
network
is
making
a
particular
claim
and
providing
a
proof
of
that
state
and
this
network
is
able
to
consume.
A
These
proofs
can
be
as
simple
as
digitally
signed
messages
in
permission
networks.
If
you
know
any,
is
like
sufficient
information
about
the
source
network
will
be
in
the
form
of
merkle
proofs
and
zero
knowledge
proofs
as
well
right
so
again,
a
very
quick
summary
right
and
the
permission
less
space
we
have
interoperability
like
ilp,
is
a
very
well
known
pattern:
polka,
dot
commerce,
like,
as
I
said,
networks
as
intermediaries
right
and
on.
In
the
permission
space
we
have
integration
frameworks
like
hyperledger
characters,
independent
networks
without
intermediaries,
hyperledger
right.
A
So
we
will
talk
a
little
bit
about
these
projects.
Right
factors
is
actually
a
hyperledger
incubation
project
right,
and
this
follows
this
pattern
in
which
there
is
a
consortium
of
what
we
call
as
cross
chain
validators,
and
the
consortium
has
some
of
its
verifiers.
There
called
participate
in
each
one
of
these
networks
right,
so
they
are
not
part
of
the
consensus.
A
You
know
building
the
consensus
in
this
networks,
but
they
participate
and
observe
all
the
state
changes
right
and
when
information
needs
to
be
fed
across
cross
chain,
validators
have
a
way
to
talk
amongst
each
other.
They
run
a
consensus
amongst
themselves
and
based
on
that
consensus,
allow
for
exchange
of
value
and
information
right.
So
more
details
can
be
found
in
the
links
I
have
given.
A
So
it's
a
plugin
architecture,
meaning
you
know
they
are
providing
maximum
flexibility
in
terms
of
different
ledgers,
to
which
you
know,
interoperability
can
be
enabled
by
building
specific
plugins
for
each
type
of
these
ledgers
and
they
do
not
make
any
managers
themselves
and
the
idea
is
security
by
default,
meaning
that
you
not
have
to
worry
about
the
security
of
the
framework
itself.
There
there's
a
very
interesting
concept:
they
have
called
toll
free,
which
is
that
users
should
be
not
charged,
for
you
know,
participate
use
just
to
create
interoperation
right.
A
So
I,
in
the
kind
of
quickly
cover
the
weaver
project,
which
is
a
project
that
we
are
currently
working
on
from
ibm
research
right.
This
is
a
you
know.
We
have
built
based
on
the
forum
principles
right,
so
we
inclusiveness.
We
want
to
avoid
approaches
that
are
specific
to
any
particular
dlt
implementation.
A
We
want
the
networks
to
retain
their
independence
and
reduce
the
trust
to
what
is
really
essential
right,
for
example,
just
the
id
network
right
and
privacy
by
design,
which
means
that
any
interaction
between
parties
across
networks
is
kept
private
and
confidential,
and
revealed
only
to
those
parties
that
are
right
and-
and
we
avoid
the
presence
of
trusted
third
parties
right
and
practical
considerations
very
similar
to
characters
right.
We
do
not
assume
any
that
we
do
not
permit
any
changes
to
underlying
platform.
A
A
A
Questions
so
there's
just
one
question
I'll,
probably
take
just
one
minute:
if
you
had
to
implement
improbability
this
year,
which
protocol
would
you
use,
you
know,
I
think,
unfortunately,
that
right,
I
think
it
depends
on
the
use
case
that
you
have
and
what
kind
of
trust
you
want
to
work
with.
As
I
said,
the
different
patterns
assume
different
trust
models,
so
I
do
not
want
to
really
pick
any
sites
here.