►
From YouTube: Panel Discussion: All Things Cross-Chain - Jim Zhang & Sophia Lopez; V Ramakrishna; Takeuchi Takuma
Description
Panel Discussion: All Things Cross-Chain - Jim Zhang & Sophia Lopez; V Ramakrishna; Takeuchi Takuma
As enterprises and organizations increase their adoption and deployment of blockchain technology and networks, the overall complexity of systems are growing exponentially. A host of new requirements for cross-chain sharing of data and transaction management arise, which necessitates a clear strategy on multi-chain connectivity and cross-chain interoperability. In this panel, leaders from Hyperledger Cactus and Hyperledger FireFly projects, as well as other blockchain experts will share their thoughts on all things cross-chain. We’ll cover: -The necessity for cross-chain connectivity in a multi-chain world -Challenges with implementing cross-chain functionality -Emerging technologies for building cross-chain solutions -And more!
Sessions Details & Slides (if available): https://sched.co/14H6J
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
Discord: https://discord.gg/rVCn4j7UFd
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 #Blockchain
License
Creative Commons Attribution license (reuse allowed)
A
You'll
have
a
better
sense
of
what
you
might
want
to
ask
the
panelists
so
I
think
we
can.
Are
you
guys
going
to
sit
sure,
welcome,
welcome
to
stand
so
I
I
mean
I
was
reflecting
hyperledger
basically
was
born
in
December
of
2015,
although
it
didn't
have
the
name
hyperledger
at
the
time,
so
we're
about
like
almost
seven
years
in
and
I
think
in
the
early
days.
A
lot
of
it
was
just
about.
A
You
know
which
layer
one
are
you
using,
and
there
were
a
lot
of
debates
about
which
one's
better
and
I
think
now
the
industry's
come
to
realizing
it's
a
multi-chain
world
people
are
far
long
enough
that
they
use
different
protocols
and
they're
thinking
about
connecting
them.
They
have
applications
that
might
want
to
talk
to
different
apps.
A
We
actually
for
those
of
you
who
are
members
had
really
good
sessions
yesterday,
where
there
was
a
chance
of
members
to
say
what
they're
looking
for
going
forward
on
interop
and
hybrid,
so
I
encourage
anyone
next
year
to
to
come
to
that
and
if
you're,
not
a
member
to
can
consider
one.
That's
one
of
the
benefits
is
to
get
sort
of
the
inside
scoop
and
to
be
able
to
share.
A
D
I've
worked
on
hyperledger
fabric
performance
measurement
actually
is
not
limited
to
fabric,
but
fabric
was
our
main
focus
and
since
the
end
of
2018
I've
been
focused
on
the
interoperability
goal.
That
is
given
that
we
have
all
these
permission:
networks
that
are
out
there
and
so
many
varieties
of
dlts
they're,
not
all
going
away.
So
how
do
the
all
these
networks
coexist
because
we
are
not
going
to
have
one
network
to
rule
them
all?
We're
not
going
to
have
all
networks
coils
into
one.
So
how
do
you
make
them?
D
E
My
name
is
Jim
Zhang,
one
of
the
co-founders
of
collido
before
starting
Clio
I
was
a
committer
on
a
hyperledger
fabric.
Now
I'm
one
of
the
maintainers
on
Firefly.
Also
a
member
of
the
hyperledger
technical
steering
committee
I.
Think
today
we're
going
to
focus
on
interop,
which
is
one
of
the
things
that
Firefly
can
be
used
for,
but
Firefly
is
a
a
bigger
project
that
covers
a
lot
of
integration
concerns
and
connecting
to
blockchains
to
have
high
quality
developer
experience.
We
can
touch
on
those
as
we
go
along
yeah.
A
E
Doing
so,
yeah
yeah.
So
when
we
work
with
with
our
customers,
we
started
collido
as
a
platform.
We
started
with
the
blockchain
layer
to
make
sure
it's
very
easy
to
stand
up
blockchains
of
all
kinds
of
protocols,
but
then
very
quickly.
We
realized
that
our
customers,
when
they
build
the
full
Solution
on
blockchain
the
blockchain
itself,
is
just
10
the
rest
of
the
90.
They
have
to
have
a
cue
to
send
transactions
reliably.
E
They
have
to
have
a
event
listener
to
to
get
events
from
the
chain
reliably,
so
they
can
coordinate
the
off
chain
reactions
to
events
on
chain.
So
a
blockchain
is
not
going
to
be
a
component
that
stands
alone
from
the
rest
of
the
I.T
systems.
It
needs
to
have
ingestion
of
data
from
from
the
rest
I.T
systems
and
when
certain
events
happen
on
blockchain
there
needs
to
be
oftentimes.
There
needs
to
be
reactions
in
the
rest
of
the
I.T
systems,
so
between
blockchain
and
the
rest
of
the
core
I.T.
E
That
concern
is
mostly
categorized
as
integration,
so
blockchain
can
work
with
everything
else.
Around
them
interrupt
is
mostly
around
between
blockchains.
So
so
you
have
one
fabric.
Doing
doing,
let's
say
tracking
trace
for
your
supply
chain
when
it
moves
to
a
certain
stage.
You
want
to
do
payment
on
a
separate
Network,
maybe
up
running
on
ethereum,
using
tokens
to
do
payment,
so
those
two
transactions
need
to
happen
in
the
atomic
way
and
that's
about
interacting
interactions
between
two
chains.
So
that's
interrupt.
E
So
if
you
picture
in
your
head
a
two-layer
sort
of
picture
one
is
you
have
all
kinds
of
blockchains
and
you
have
errors
going
across
them.
That's
interrupt,
but
then
you
have
your
app
layer
that
talks
to
one
or
two
or
many
of
the
blockchains
and
from
between
the
app
and
the
blockchains
and
between
the
app
and
your
core.
I
t
that's
Firefly,
I'm
sure
the
others.
C
A
Emma
well
just
to
explain
to
the
audience
so
cactus
practitioner
from
Fujitsu
and
Accenture,
and
now
Rama
you
were
part
of
Weaver,
so
I
was
curious.
What
Weaver's
approach
was
to
interoperability
and
now
Weaver
and
Cactus
have
combined
and
it's
cacti.
So
maybe
you
could
comment
on
that
as
well.
So
one
is
interoperability
to
Weaver
and
then
what
does
it
mean
that
these
two
communities
are
coming
together
from
a
cross-train
perspective?.
D
A
D
So
I
see
it
as
there's
a
spectrum
of
solutions,
so
at
its
core
interoperability
to
me
means
the
ability
to
for
two
or
more
blockchain
systems
to
be
able
to
come
together
and
communicate
and
talk
to
each
other
in
a
way
that
can
solve
a
purpose
that
requires
all
the
system
to
work
together,
so
that
in
the
is
my
most
general
definition
of
interoperability.
Now
how
how
tight
you
want
those
blockchain
systems
to
get
or
how
Loosely
coupled
you
want
to
them
to
be.
D
That's
the
choice
you
can
make
so
I
think
the
Spectrum
Solutions
you
can
have
there
the
closer
they
get.
You
can
think
of
it
as
you're,
integrating
to
different
blockchain
systems,
the
more
Loosely
coupled
you
get.
You
can
think
of
it
as
a
somewhat
more
independent
kind
of
interoperability
between
systems,
so
the
Weaver
approach
tries
to
go
as
close
to
the
independent
end
or
Spectrum
as
possible,
so
our
Core
Design
principles
involve.
D
If
you
have
your
blockchain
network,
it's
built
on
a
particular
DLT
stack,
be
it
Fabric
or
bezoo,
or
any
technology
outside
of
hypology.
Like
Corda,
you
run
your
applications
as
you
would.
You
do
not
have
to
change
your
stack.
We
will
not
go
and
ask
fabric
to
change
its
code.
We
will
not
go
and
ask
order
to
change
this
code,
but
we
will
provide
the
enablers
that
allow
you
to
perform
transactions
that
require
some
kind
of
cross
chain
or
cross
Network
operation,
and
we
have
a
particular
taxonomy
of
such
operations.
D
We
categorize
them
into
the
ability
to
share
data
from
one
smart
contract
in
one
ledger,
to
a
different
smart
contact
in
a
different
Ledger,
there's
the
ability
to
exchange
assets
or
to
conduct
an
atomic
Swap,
and
then
there's
the
ability
to
transfer
an
asset
from
one
ledger
to
another.
That
is,
you
burn
an
asset
in
Ledger
and
recreate
it
in
another.
So
collectively
we,
our
observation,
was
that
this
sort
of
covers
almost
all
of
the
cases
you
want
in
a
real
production
rate,
Enterprise
application,
which
involves
more
than
one
blockchain.
D
A
D
We,
we
both
aim
for
the
design
principles
that
I
just
articulated,
and
there
are
some
differences
in
the
technical
approach,
but
they
broadly
fall
under
the
spectrum
that
I
talked
about.
So
the
goal
of
bringing
the
two
projects
together
was
one
we
aim
to
achieve
the
same
thing,
but
by
bringing
the
two
projects
together,
we
can
provide
a
spectrum
of
features
that
you,
as
Network
developers
or
administrators,
can
use.
D
A
E
Yeah,
absolutely
so
I'd
say
Firefly.
You
want
to
use
Firefly
for
every
project.
You
have
a
blockchain
component
in
because
it
just
makes
it
much
easier
to
to
interact
with
blockchain.
So,
but
it's
it's
not
fair,
because
we're
we
want
to
focus
on
the
interop
So
within.
If
interrupt,
is
your
concern.
Firefly
can
still
help
you,
because
a
single
Firefly
instance
can
be
connected
to
multiple
blockchains.
It's
very
easy,
in
fact,
I
think
it
was
announced
in
the
previous
sessions
that
we
just
released
1.1,
which
has
a
very
significant
enhancement
compared
to
1l.
E
Is
you
have
a
single
instance
that
can
be
connected
to
multiple
chains
on
the
per
namespace
basis,
which
means
what
you
can
do
within
your
application
layer
with
firefly?
Is
you
can
coordinate
among
multiple
blockchains,
so
you
can
listen
to
event
in
your
fabric
chain
with
the
dragon
Trace
using
that
example.
So
when
the
event
triggers
that
says
this,
this
batch
of
goods
has
arrived
at
its
destination,
then
you
can
do
the
corresponding
payment
on
the
other
chain,
so
with
Fireflight.
This
just
makes
it
very
simple
to
do.
E
Of
course,
if
you,
you
ask
the
interop
experts,
they
will
say,
this
is
one
mode
of
interop
which
is
going
through
a
trusted
third
party
or
a
trusted
off
chain
component,
which
you
know
is
depending
on
your
needs,
can
be
a
fair
option
for
you
to
choose,
and
Firefly
is
pretty
easy
to
to
build.
On
top
of
to
achieve
this
type
of
architecture
and
I'll,
let
the
others
comment
on
other
modes
of
interop
and
why
you
might
use
cacti.
A
C
C
A
D
I
mentioned
the
three
broad
interoperability
modes.
Really,
your
data
sharing
asset
exchanges,
asset
transfers,
so
one
use
case
I'll
talk
about
is
something
you
can.
You
can
read
about
it's
so
we
were
last
year
was
used
by
Bank
of
France
and
HSBC
in
a
in
a
set
of
use,
cases
which
involved
experimentation
on
Central,
Bank,
digital
currency.
D
So
what
the
scenario
involved
was
you
had
different
networks,
they
were,
one
of
them
was
built
on
fabric
and
it
was
built
in
Corda
and
we
were
doing
different
kinds
of
transactions
across
them.
So
there
was
one
network
which
maintained
Securities
another
which
maintained
cbdc
accounts
and
a
national
use
case.
There
was,
if
you're
paying
for.
If
you
want
to
sell
a
security
on
one
network
on
Securities
Network,
you
want
to
get
payment,
but
where
will
you
get
the
payment
on
the
digital
currency
Network?
D
So
you
need
the
ability
to
do
an
atomic
swap
across
the
two
networks.
So
you
can't
just
have
security
getting
transferred
in
one
network
and
without
any
guarantee
that
the
payment
will
happen
on
the
other.
So
engineering
across
Network
transaction
using
a
trustworthy
protocol
is
important
and
with
Weaver
we
have
such
an
asset
exchange
protocol
using
the
hdlc
mechanism,
which
many
of
you
may
have
heard
of.
D
If
not
I'll
be
talking
about
it
in
a
presentation
on
Vivo
tomorrow,
then
there
were
other
instances
where
you
had
to
these
networks
were
doing
coupon
redemptions,
for
which
they
needed
to
communicate,
legislate
or
some
records
in
one
ledger
to
a
different
ledger.
So
they
used
the
Weaver
in
a
what
you
call
the
data
sharing
mode,
which
is
where
you
one
from
one
Ledger.
D
You
can
make
a
request
to
another,
and
the
requesty
provides
not
just
the
data
but
also
authenticity,
proof
that
the
record
was
that
the
record
is
valid
and
was
committed
in
a
in
a
previous
transaction
and
the
receiving
Network
can
then
get
the
data
and
then
validate
that
the
proof
is
is
accurate.
So
these
were
several
cases
that
were
successfully
demonstrated
in
that
POC
last
year
and
yeah
I
think
I'll.
Maybe
we
can
touch
on
other
topics
later.
E
To
the
next
topic
use
cases
that
involve
cross
chain,
there
are
a
ton
of
them
and
we
continue
to
see
more
and
more
earlier.
In
my
session
talking
about
technology
adoptions
in
recent
years,
I
was
very
encouraged
to
see
that
a
whole
bunch
of
Advanced
Technologies
that
when
I
built
the
chart
for
I
thought
those
are
bleeding
edge.
But
when
I
ask
audience,
are
you
doing
these
everybody?
E
Well
for
every
one
of
them
there
was
a
bunch
of
hands
going
up,
so
it
was
very
encouraged
to
see
that
so,
specifically
for
hybrid
chains,
I
think
that's
one
of
the
more
popular
patterns
with
Enterprise
use
cases,
because
in
the
previous
years
the
Enterprise
space
has
been
focusing
on
permission,
change,
right,
solving
existing
pain
points
or
creating
a
token
economy
in
the
in
this
controlled
walled
Gardens
space,
but
then
pretty
quickly.
They
realized.
E
B
E
So
they've
a
lot
of
them
figure
out
that
if
I
allow
the
crypto
holders
to
inject
their
values
into
this
ecosystem
and
do
that
investment,
let
the
proceeds
grow,
and
so
at
some
point
they
can
cash
out
that'll
be
a
great
way
to
to
encourage
usage
of
the
ecosystem
they
built
so
and
then
we
will.
We
see
naturally
a
interop
scenario
right.
D
I'll
leave
with
each
of
those
topics
a
little
bit
so
security,
one
of
the
express
goals
that
we
had
when
we
were
creating
viewer
was
you
already
have
an
you,
you're,
building
a
rather
complex
network.
If
you
take
fabric,
you
have
your
build,
you
have
to
bring
together
several
set
of
nodes
running
under
different
organizations.
You
decide
which
of
them
are
endorsing
which
of
them
are
committing.
You
have
to
select
yet
another
set
of
order
nodes.
D
It's
a
rather
complex
structure
and
there
are
a
lot
of
hidden
pitfalls
when
it
comes
to.
When
that
security
expert
can
look
at
and
say,
okay,
you,
you
may
have
a
problem
here.
One
thing
explicitly
explicit
did
not
want
to
do
was
to
increase
the
burden
on
security
professional.
We
want
to
make
sure
that
we
did
not
increase
the
trust
footprint
that
you
would
require
if
you
use
viewer
as
a
solution
for
your
network
to
interpret
it
with
another.
So
what
we
did
was
we.
D
We
tried
to
Institute
mechanisms
that
you
can
use
as
augmentations
to
what
you
you
already
have
in
your
network.
You're
already
like
take
fabric
Network,
you're,
already
deploying
and
running
chain
code,
we
will
just
require
you
to
run
one
extra
piece
of
chain
code
that
will
provide
some
function,
that
you
need
you.
D
You
extend
your
client
applications
to
just
import
viewer
libraries
to
trigger
particular
calls,
and
you
add
one
more
component,
which
is
we
call
a
relay
but
which,
if
we,
if
you
have
time,
we
can
talk
about
standards
which
we
are
talking
with
other
people
about
standardizing
into
a
sort
of
common
Gateway
Appliance
for
networks.
But
when
you
add
a
relay
to
your
network
like
an
ordering
service,
it
it's
a
it's
an
extra
component.
We
we
want
to
make
sure
that
the
relay
is
completely
trustless.
D
That
is
you
don't
have
to
trust
it,
for,
as
you
don't
use
it
as
a
trusted
third
party,
so
security
issues
are
very
important.
I
mean
if,
if
my,
if
the
solution
that
we
are
providing
to
your
network
is
results
in
additional
security,
vulnerabilities
you're
likely
not
going
to
use
it.
So
we
wanted
to
eliminate-
or
at
least
minimize
any
security
issues.
So
we
have
some.
We
have
a
lot
of
documentation
on
that.
We
have
some
research,
so
there
may
be
still
a
lot
of
work
to
do
on
that.
D
We
have
to
make
sure
that
it's
validated
by
Security
Professionals
and
all
that
Prime
privacy
is
another
topic.
I
mean
privacy
is
hard
enough
within
Network
as
it
is
in
fabric.
We
have
different
solutions
for
like
channels
pdcs,
and
you
may
have
heard
the
talks
on
public
private
chain
code.
Cross-Chin
privacy
is
yet
another
dimension
of
heart,
so
I
don't
claim
to
have
solved
the
problem.
It's
an
active
research
question
so
with
solicit
all
your
thought
and
input
on
that
usability.
I
think
there's
a
lot.
We
can
learn
from
Firefly
in
this
respect.
D
What
we
do
want
to
make
sure
that
we
are
not
trading
of
usability.
I
mean
security
is
great.
We
don't
want
to
completely
give
up
usability
for
that,
so
at
least
in
in
Cactus
and
Weaver.
We
have
apis
that
make
it
rather
quite
easy
for
developers
to
handle
and
yeah.
We
will
be
looking
to
Firefly
to
actually
lead
the
way
on
that
and
we'll
be
borrowing
as
much
as
possible.
Okay,.
A
I
actually
was
thinking
we
have
about
10
minutes
left
I
wanted
to
ask
if
there's
any
questions
from
the
audience.
Since
we
we've
got
some
great
subject
matter
experts
on
the
stage
and
then
you
could
get
a
sense
for
what's
on
people's
mind
and
what
they're
looking
for
from
the
community,
so
I
think
I
could
bring
the
mic
over.
Is
there
anyone
who
has
any
questions?
A
G
G
So
it
has
other
ramifications
because
security
trading
happens
in
a
setup
where
there
is
credit
involved,
meaning
you
when
you
don't
settle
like
if
I
sell
you
a
security
and
you
don't
pay
me
right
away.
There
are
many
reasons
for
that.
You
know:
you're
you're,
a
bank
I'm
a
bank
or
you're
a
big
customer.
So
why
does
everybody
go
for
Atomic
swaps?
G
E
My
view
is
Tommy
swap
is
just
one
of
the
more
mature
cross-chain
technologies
that
there
is
definitely
a
need
for
may
not
make
sense
in
the
some
of
the
financial
Industries
scenarios,
but
definitely
makes
sense
in
some
other
scenarios,
and
it
absolutely
makes
sense
when
you
don't
have
trusted
parties
in
between
so
I.
Think,
that's
what
mostly
this
is
used
for,
that
the
two
parties
that
are
doing
swaps,
don't
trust
each
other,
each
other.
They
need
a
mechanism
to
make
sure
they
can
exit
without
the
other
party.
E
C
D
So
Nancy
can
be
different
depending
on
whether
you
put
on
a
technologist
hat
or
a
business
person's
hat.
So
as
a
technologist,
you
know
going
from
the
classical
database
world
where
you
have
system
you
have
protocols
like
two
phase
commit
right.
They
are
rather
elaborate
protocols
you
can.
You
can
allow
different
replicas
to
just
sync
on
their
own
time
without
regard
to
Atomic,
steer,
consistency
right,
but
two-phase
protocol
Commerce
protocols
serve
real
purpose.
D
So,
from
a
Technologies
perspective,
doing
an
atomic
swap
across
two
decentralized
chains
in
a
decentralized
manner
seems
like
the
right
solution.
So
now
putting
on
a
business
person's
hat
you're
right
I
mean
we
have
when
we.
What
you've
heard
from
clients
are
performance
matters
a
lot
and
Atomic
swaps.
If
they
do
not
deliver
adequate
level
performance
in
those
settings,
we
may
ultimately
end
up
using
solutions
that
involve
trusted
parties
which
do
not,
but
without
strict
atomicity
yeah.
So.
A
A
B
My
name
is
Flora
I'm
from
Pfizer
I
lead
the
blockchain
division
of
Pfizer.
My
question
is
like
we
have
cross
chain.
We
have
all
the
Technologies
great
Technologies
and
great
Community
working
behind
that,
but
from
the
Enterprise
sector.
What
we
face
is
like
the
use
case
of
all
these
Technologies
right.
So
is
there
any
place
where
I
can
go
and
find
out?
Firefly
is
there.
These
are
the
Enterprises
using
Firefly
for
their
use
case
or
Cactus
or
cacti
as
they
are
with
River.
E
It's
a
great
question:
I
think
that's
something
we're
continuing
to
work
on
the
we
have
many
customers
at
different
stages
of
adopting
for
the
technology.
Some
have
been
using
them
like
gen
one
of
firefly
in
production
for
many
years.
Some
are
just
reporting
to
from
gen
1
to
Gen
2,
which
is
what
we
have
on
hyperledger
Firefly.
Some
are
just
starting
to
build
on
Firefly
I
think
we
can.
E
We
definitely
can
go
back
and
and
do
some
inventory
I
do
agree
that
this
will
help
the
Potential
Prospect
adopters
to
see
okay.
This
is
used
here
that
makes
sense
that
use
there
that
makes
sense
and
I'm
pretty
close
to
that
kind
of
use
case.
So
maybe
I
should
try
that
too
yeah
I
appreciate
the
the
the.
C
D
Thanks
so
I
mentioned
one
use
case
that
Weaver
was
used
for
last
year
in
a
proof
concept.
There
are
several
others
like
with
the
fireflies
Jim
mentioned
in
different
stages
of
work
with
the
client
there's
some
that
being
actually
worked
on
somewhere,
we're
talking
to
them.
Unfortunately,
I'm
not
at
Liberty
to
share
details
of
that
right
now,
but
hopefully
very
soon,
and
even
with
cat
with
the
cacti,
that
is,
the
cactus
in
the
Weaver
team
have
been
having
periodic
meetings
with
several
organizations
to
understand
their
their
needs
and
yeah.
E
A
A
So
that
could
be
like
a
very
easy
way
to
make
more
visible
what
others
are
doing
in
the
industry,
so
that
people
can
look
at
the
use
cases
and
say:
oh,
this
is
something
people
are
really
using.
I
could
even
call
them
up
and
ask
them
what
their
experience
is
like
I
could
show
this
internally
to
my
management
to
just
show
there's
adoption
of
these
Technologies.
So
that
was
a
great
question.
Hopefully
we
we
can
Implement
that
right
away.
F
C
A
B
E
I
think
you
guys
are
already
doing
a
really
great
job,
because
when
we
opened
the
booth,
so
many
people
want
to
come
to
a
firefly
booth
and
and
learn
about
it,
but
I
guess
there
was
one
incidence
where
we
were
somewhat
surprised.
That
seems,
like
our
leadership
team
from
from
the
foundation
can
be
told
more
about
Firefly
in
general,
because
a
lot
of
them
don't
speak
about
Firefly
when
they,
when
they
give
talks.
So
I
think
that
I
don't
know.
E
D
Thanks
yeah
I'll
Echo,
what
said
I
think
hypology
is
already
doing
a
great
job
at
promoting
all
the
projects
under
hypology
of
the
main
ones
and
the
labs
we
have.
It's
super
easy
to
start
a
GitHub
repo
host
Discord
channels,
everything
so
if
and
if
you
want
to
contribute,
please
go
to
the
GitHub
repositories,
go
to
the
Discord
channels,
Etc,
maybe
the
one
thing
that
hyperledger
can
do
in
addition
is
like
projects
like
ours
which
are
inherently
enabling
other
different
blockchains
to
link
together.
D
Maybe
we
can
advertise
that
a
bit
more,
so
we
have
several
different
different
blockchains
and
other
kinds
like
Indie
Sawtooth,
iroha
fabric
Etc.
Maybe
it
can
be
advertised
up
front
on
on
the
hyperledger
Forum
from
the
main
website,
for
example,
that
the
way
to
link
these
systems
or
the
way
to
provide
a
common
view
across
different
chains.
Look
to
projects
like
Firefly
or
cacti,
so
that'd
be
great.
A
H
Yeah
Dixon,
so
the
the
eea,
the
Enterprise
ethereum
Alliance,
has
a
cross-chain
working
group.
The
eea
is
not
there
to
build
software
right.
The
hyperledger
managers
open
source
software
development
projects
and
we're
trying
to
essentially
write
specifications
so
that
multiple
software
projects
like
these
can
actually
interoperate
and
work
together.
So
the
question
is:
how
do
we,
how
do
we
tighten
that
collaboration
and
how
do
we
make
it
clear?
H
You
know
people
like
data
chain
who
produce
software
are
members
of
both
people,
like
consensus,
who
are
working
on
the
standards
that
eea
is
trying
to
develop.
How
do
we
tighten
that
conversation
and
make
sure
we're
actually
talking
to
you
guys,
as
implementers
of
you
know
what
amount
to
reference
implementations
and
therefore
core
drivers
of
what
should
the
specifications
say
and
how
it
should
work.
A
D
Yeah
I
think
we
had
a
good
chat
yesterday
about
this,
so
we,
when
we
are
designing
protocol
for
interoperability,
we
want
to
be
I
mean
it
would
be
great
because
we
are
in
the
business
of
mitigating
the
diversity
in
heterogeneity,
C
right.
So
standards
are
a
best
friend
here
and
I
mentioned.
There's
a
standards.
There's
a
group,
that's
working
towards
trying
to
standardize
internet
work,
communication
protocols
and
to
be
creative.
The
EA
could
join
that
and
contribute
to
that.
E
I
think
it's
always
a
challenge
for
EA
to
create
a
standard
not
too
early
to
sort
of
stifle
Innovation
or
you
know
nobody
look
at
it
right
if
you
can
publish
standards,
but
nobody
looks
at
it.
It's
not
very
useful,
yeah
exactly
so
so,
but
but
but
I
think
Stena
is
is
critical
for
the
cross
chain
space,
because
naturally
this
is
about
working
together,
which
standard
is
the
best
for
so
definitely
looking
forward
to
going
back
to
contribute
more
over
there.
Thank
you,
yeah.
A
I
could
I
guess
I
I
have
a
mic,
so
so
I
guess
would
close
out.
I
was
just
reflecting
with
the
evm
becoming
somewhat
of
an
industry
standard
evm
compatible
chains
even
across
different
layer
ones.
It's
interesting.
Some
of
those
mechanisms
emerge
so
wanted
to
thank
everyone
on
the
panel
for
participating
and
an
audience
for
some
great
questions.
I
do
believe,
there's
something
at
six
o'clock
so
like
a
meet
up
a
Dublin
Meetup,
that's
happening
in
the
solution
Center.
A
So
there
might
be
some
people
external
to
the
hyperledger
community,
but
blockchain
leaders
who
will
be
here
so
it
might
be
a
chance
to
meet
some
interesting
people
who
are
are
local
and
looking
to
learn
more
about
what
we
do
at
hyperledger
but
I.
Thank
you
all
and
probably
we'll
see
you
all
in
the
hallways
during
the
next
few
days
thanks
everyone.