►
From YouTube: FireFly Opening Keynote
Description
Brian Behlendorf, Executive Director, Hyperledger
Steve Cerveny, Founder & CEO, Kaleido
Sophia Lopez, Founder & COO, Kaleido
Come hear about an exciting new project - FireFly - a multi-party system. FireFly's provides the broader infrastructure for common off-chain data flows and contains multi-protocol support. Come hear how this is dramatically simplifying and accelerating leading enterprise blockchain initiatives.
----
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
A
All
right
we're
going
to
get
started
thanks.
Everyone
for
joining
us
we're
very
excited
to
the
launch
event.
I
know
you
joined
us
during
sessions.
During
the
week
we
were
presenting
with
various
clients
and
consortiums
in
different
industries
that
have
been
building
platforms
and
moving
to
production
in
this
technology.
Today,
we're
excited
to
do
a
much
deeper
dive
on
the
technology
itself.
A
We
did
bring
along
some
friends
and
collaborators
from
the
community
to
participate
throughout
the
day
as
well.
So
right
now
we're
gonna
start
with
the
opening
keynote
from
9
to
9
and
we'll
do
about
a
20
minute
demo
as
part
of
that
to
take
us
to
the
top
of
the
hour,
we'll
have
a
one
hour,
deeper,
dive,
technical
overview,
then
a
hands-on
workshop,
where
you
can
download
the
code
and
get
started.
I
meet
the
experts
panel
and
then
for
people
on
different
time
zones.
We'll
do
a
closing
keynote.
B
A
A
All
right,
let's
let's
get
started,
then
we
wanted
to
start
actually
brian
just
to
get
a
couple
of
your
thoughts.
I
know
we've
been
working
with
you
over
the
last
few
months
on
on
the
proposal
and
we're
really
excited
to
be
part
of
the
hyperledger
community.
Now
what
really
excites
you
or
sparks
interest
for
you
with
firefly.
B
Yeah
well
so
so,
first
off
thanks
for
for
hosting
this
event,
and
I'm
really
happy
to
be
here,
the
the
thing
that's
exciting
about
firefly
to
me
is
you
know
we
try
to
ground
everything
we
do
at
hyperledger
in
the
reality
of
how
people
are
building
these
applications
out
there.
We
are
idealists,
but
we're
also
pragmatic,
pragmatists.
B
How
to
manage
a
cluster
of
systems
that
that
that
sort
of
thing-
and
you
know
we
did
have
a
project
early
on
called
composer,
which
was
an
interesting
tool
to
help
people
understand
what
this
concept
of
decentralized
systems
amongst
enterprises.
You
know
how
to
design
for
them,
how
to
how
to
think
about
building
those
apps.
But
it
was
a
design
tool
that
people
wanted
to
use
in
production,
and
it
wasn't
really
designed
to
be
a
production
tool
designed
to
be
a
development
tool.
B
You
build
on
top
of
blockchain
networks,
so
when,
when
we
started
to
talk-
and
you
said,
you
had
some
code
that
that
was
built
off
of
the
backs
of
all
the
different
projects
that
that
that
you've
been
developing
and
could
help
also
answer
something-
that's
really
key
at
hyperledger,
which
is
how
do
we
start
to
build
systems
that
span
multiple
different
ledgers
right?
I've
always
talked
about
the
differences
between
fabric
and
bay,
zoo
and
sawtooth.
You
know
just
within
hyperledger,
but
then
even
corda
and
corm
on
the
outside.
B
It
wasn't
like
race
cars
on
a
racetrack.
It
was
much
more
like
different
databases
out
there
in
the
world.
Right,
mongodb
and
mysql
are
very
different
kinds
of
databases.
Yet
at
one
level
you
use
them
to
store
data
and
query
data
right,
but
as
developers
we
know
that
those
differences
matter
when,
depending
upon
the
use
cases
or
the
rest
of
the
architecture
up
above
and
so
firefly
helps,
you
know
talk
amongst
different
ledgers
right
support
for
corda
support.
B
I
don't
need
to
preempt
the
whole
the
rest
of
the
day,
but
support
for
multiple
ledgers
and
such
is
also
something
that's
been
core
at
hyperledger
since
our
inception
like
how
do
we
support
a
diversity
of
different
options
at
different
layers
and
firefly
really
speaks
to
that.
So
all
these
reasons
you
know
when
we
first
started
talking.
I
was
like
yes,
this
really
belongs
at
hyperledger
and
and
I
think
we
can
build
a
really
big
community
on
top
of
it,.
A
Part
of
the
past
life
that
we're
involved
with
so
I
think
you
partially
answered
this,
and
what's
great
about
really
great
about
hyper
ledger,
is
just
the
diversity
of
projects
you
have
sort
of.
You
know,
I
think
you
call
it
the
greenhouse
where
you
lay
them
all
out.
I
mean
I
think
when
you
touched
upon
it
briefly,
but
just
in
terms
of
firefly
now
coming
into
hyper
ledger,
how
do
you
see
the
relationship
between
these
other?
You
know
code
bases
and
communities
and
in
hyperledger.
B
B
Sometimes
it
can
be
a
little
bit
like
you
know,
we're
just
getting
started
here.
Who
are
all
these
people,
but
but
what
it's
intended
to
do
is
try
to
help
build
a
hole,
that's
much
better
bigger
than
the
sum
of
its
parts,
and
so
I
I
yeah-
that's
that's,
I
think,
just
just
yeah.
You
know
that.
That's
that's
where
I
I
I'm
just
excited
about
the
project
coming
in
and
and
hoping
that
we
get
this
started
in
a
in
in
really
the
right
way.
B
Well,
I
I
think
this
is
a
chance
for
people
to
dive
really
into
what
what
is
firefly.
What
are
these
different
components
to
understand
what
you
know
where
the
design
of
this
comes
from
from
the
the
work
that
you've
done
for
so
many
different
clients
and
and
and
just
start
climbing,
that
learning
curve,
so
that
I
not
only
can
people
start
using
this
as
quickly
as
possible,
but
but
also
find
a
path
to
becoming
a
contributor
of
some
sort?
B
A
Thanks
brian,
I
know
this
is
why
open
source
is
the
most
fun
part
of
the
job
of
a
modern
enterprise
developer,
so
really
appreciate
having
you
on
with
us
today
and
getting
some
of
your
thoughts
and
perspectives.
I
know
you'll
be
joining
us
again
on
the
meet
the
experts
panel
and
then
for
the
closing
keynote.
So
thanks
again
for
the
support
and
we've
had
a
great
week
so
far
so
looking
forward
to
the
rest
of
today,
thanks
again.
A
A
If
you
look
across
all
the
b2b
back
office
processes,
many
you
know
built
on
legacy
systems
are
never
digitized.
There's.
You
know
tremendous
pain
points,
especially
during
covid.
We've
seen
supply
chain
disruptions
and
many
other
issues
that
have
come
up
in
health
care,
delivery,
etc.
Where
there's
a
lack
of
transparency
and
a
lack
of
trust,
so
likely
not
new
news
for
anyone
here,
but
we
go
to
the
next
slide.
You
know:
we've
seen
various
analysts
polling
their
clients
and
we've
spoken
with
our
clients
directly
as
well.
A
A
Only
eight
percent
of
companies
believe
their
current
models
will
remain
as
this.
You
know
viable
business
models
if
they
don't
digitize
and
a
lot
of
people
are
talking
about
digital
ecosystems,
so
bringing
multiple
parties
together
around
a
shared
view
of
data,
shared
application
logic,
tackling
shared
industry
problems.
So
mckinsey
is
saying
that
these
new
digital
ecosystems
could
account
for
more
than
60
trillion
in
revenue
2025.
A
A
So
one
interesting
thing:
we've
seen
over
the
last
half
decade.
People
are
really
excited
about
the
promise
of
decentralized
technologies
and
blockchain,
but
there
have
been
a
lot
of
challenges,
and
this
has
meant
projects
could
take
three
four
five
years
to
try
to
get
into
production.
They've
spent
tens
of
million
dollars
written
hundreds
of
thousands
thousands
of
line
of
code,
and
why
is
that?
It's
that
the
cr,
when
you're
really
doing
things
between
companies,
you
know
not
just
in
the
one
company
in
their
own
data
center,
but
across
companies.
A
These
cross-party
flows
require
a
lot
of
sophistication.
There's.
You
know
enterprise
space,
a
lot
of
requirements
around
privacy,
security
compliance
enterprises
have
struggled
with
the
skills,
all
new
frameworks
involved.
You
know
different
paradigms,
digitizing
moving
to
the
cloud
and
these
peer-to-peer
network
frameworks
and
technologies
and
as
companies
were
trying
to
roll
their
own
solutions.
They
ran
into
these
issues,
meanwhile,
still
trying
to
comply
with
all
of
the
heavy
duty
enterprise
requirements.
So
it
was
just
you
know
much
too
difficult
to
build
an
enterprise
blockchain
use
case.
A
What
we,
what
we've
seen?
That's
a
very
familiar
pattern.
You
know
enterprises
think
the
job
is
in
building
their
first
use
case,
and
this
can
be
an
emerging
tech,
lab
or
innovation
team.
You
know
they
think
it's
writing
smart
contracts,
you
start
a
node,
you
build
the
web
app
and
you
deploy.
It
sounds
pretty
simple.
You
know
they
think
it's
about
three
to
five
components.
Maybe
you
know
we're
talking
in
the
months
or
maybe
half
year.
A
Well,
we've
seen
it
repeatedly
across
industries
across
you
know
blockchain
initiatives
and
projects,
whether
it's
just
one
company
or
we're
trying
to
get
to
you
know
pilot
with
multiple
parties
or
even
into
production.
You
know
they
have
to
decide
how
to
use
the
blockchain
as
part
of
the
overall
solution.
You
know
running
the
node,
we
you
know
we've
seen
across
the
industries
five
to
ten
percent
of
the
total
solution.
A
There's
different
levels
of
maturity
and
sophistication
there
in
terms
of
ease
of
use
or
lack
of
ease
of
use,
and
then
you
know
getting
to
the
realization
that
deployment
can
be
a
lot
further
off
than
what
they
promised
to
their
stakeholders,
investors
and
to
their
clients
and
end
users.
So,
and
typically,
we've
seen
up
to
40
components,
40s
pretty
typical
and
it
could
take
a
number
of
years.
Probably
you
know
looking
at
two
to
four
years
as
a
general
range.
So
what
should
the
job
be?
A
A
You
know
the
bar
there
really
flipping
it
so
you're
you're
able
to
move
quickly
through
those
phases,
use
the
reusable
assets,
the
infrastructure,
design
and
architecture
as
well,
and
then
a
lot
of
your
time
and
and
money
and
focus
can
be
on
delivering
business
value
and
getting
to
business
outcomes.
So
that's
the
most
exciting
part
of
this.
This
whole
initiative.
So
with
that
I'd
like
to
pass
it
over
to
steve.
C
C
A
C
A
C
All
software
could
all
of
a
sudden
fit
in
a
uniform
box.
How
powerful
that
was.
You
can
secure
it
the
same
way.
You
can
do
networking
the
same
way.
You
can
scale
it
the
same
way.
You
can
do
high
availability,
the
same
way
all
the
hard
problems
for
enterprises,
all
of
a
sudden
inverted
you've
inverted
the
the
the
investment
or
the
cost
profile
of
an
it
project.
C
Where
you
don't
spend
all
your
time
doing
that
stuff,
you
instead
build
the
application
and
make
it
better
and
drive
more
value
for
the
user,
and
that
was
great.
However,
there
was
a
problem.
The
problem
with
docker
was
it
worked
great
on
your
laptop,
but
for
an
enterprise
to
go
into
production,
docker
alone
was
not
enough.
A
larger
system
was
needed,
sort
of
around
docker.
Underneath,
however,
we
think
of
now
kubernetes
today
and
kubernetes
was
such
a
game
changer
when
it
came
along
it
sort
of
a
bigger
framework.
C
C
You
know
the
the
best
implementation
and,
of
course,
there's
this
core
control
plane,
so
you
can
manage
not
just
one
two,
three
hundreds,
you
know
thousands
that
I
think
kubernetes
talks
about
planetary
scale,
right
of
of
of
docker
and
all
of
a
sudden.
You
have
this
this
this
other
layer.
This
larger
system
around
docker,
which
I
think
is
interesting,
actually
delivers
on
the
initial
promise
of
docker
of
helping
us
to
put
all
of
our
software
inside
of
that
same
box.
C
If
that's
the
metaphor,
how
about
blockchain,
let's
think
about
blockchain
for
a
minute
and
what
a
big
breakthrough
that
was
2015
2016..
I
know
you
know
my
fellow
speakers
on
this
session.
Sophia
and
brian
were
all
you
were
there
day,
one
I
I
was
also
there.
You
know
as
it
came
along
and
we
all
looked
at
it
and
said
how
cool
is
this
thinking
about
how
broken
the
back
office?
You
know
how
siloed
it
is,
and
so
on
the
shared
ledger:
automating
our
business
logic,
smart
contracts
and
chain
codes,
etc.
C
C
You
know,
there's,
there's
lots
of
activity
and
really
interesting
projects,
but
they
tend
to
be
focused
more
down
into
the
data
layers
and
around
you
know
the
blockchain,
obviously
itself
and
and
around
there,
and
there
are
interesting
projects
up
up
in
the
middleware
space,
but
we
don't
see
a
comprehensive
project
and
that's
really
what
firefly
is
trying
to
solve
is
to
step
into.
You
know
this
larger
umbrella,
sort
of
a
platform
or
system
and.
A
C
You
know
what
we
think
of
as
as
a
multi-party
system,
but
before
I
get
into
firefly
one
more
picture
just
to
level
set
on
what
a
business
network
looks
like
a
consortium,
a
group
of
organizations
that
are
trying
to
build
a
decentralized
application
and
how
this
is
fundamentally
different
from
the
previous
applications
that
they've
built.
So
the
the
light
gray
shaded
area
is,
is
the
business
network
and
and
the
the
big
circles
are?
C
C
There
that's
providing
that
that
shared
common
source
of
truth,
but
there's
also
private
data
exchange,
and
we
talk
all
the
time
about
how
important
privacy
is.
But
it's
important
to
know
that
that
often
lots
of
use
cases
need
there's
different
categories
of
data.
So
some
some
private,
but
some
data
is
appropriately
broadcast
right
and
so
the
the
ability
to
broadcast
data
to
define
things
like
assets
to.
C
C
We
see
a
lot
of
companies
really
want
to
constrain
the
the
amount
of
data
flows
that
are
happening
on
the
blockchain
themselves
itself,
and
so
what
what
we
we've
seen
and
learned
is
off
chain
that
a
tremendous
amount
of
data
flows
are
happening
and,
and
so
the
question
then
becomes
well.
How
do
you
achieve
those
those
off-chain
data
flows
and
do
they
adhere
and
can
conform
to
the
same
security
models
and
and
the
same
network
policies
and
and
how
to?
How
do
you
blend
all
these
different
technologies
together
and
manage
that
along?
C
C
We
define
that
the
multi-party
system,
as
that
larger
set
of
technology
runtimes
that
are
that
are
working
together
to
give
the
application
developer
a
really
simple
api
to
do.
Things
like
like
share
data
move
data,
whether
it's
a
blob
or
whether
it's
a
structured
piece
of
data,
whether
it's
you
know
completely
private
off
chain
and
and
pinned
to
it,
to
a
blockchain,
whether
it's
not
pinned
to
to
a
blockchain.
C
C
Right
across
across
the
space
and
so
being
able
to
create
these
robust
data
flows
in
a
decentralized
way
right,
so
everyone's
still
writing
their
own
stack,
still
cross-connecting
very
event-driven.
That's
an
incredibly
important
part
of
the
design
principle
here
and
effect,
a
flexible
technology
framework
and
we'll
talk
a
little
bit
about
the
roadmap
as
the
day
goes
on,
but
I
mentioned
that
sort
of
the
term
and
umbrella
project,
but
being
able
to
plug
in
other
things
well
in
in
a
scenario
that
we'll
you
know
we'll
dive
into
where
an
organization
shares.
C
A
C
Well,
maybe
they
broadcast
the
fact
that
this
data
exists
you
bring
in
the
broadcast
capability.
Maybe
they
need
to
pay
for
that
the
data
as
they
receive
it,
so
you
bring
in
tokens.
Maybe
you
need
to
prove
that
you
have
the
data
without
disclosing
the
data
so
now
you're
getting
into
you
know
confidential
computing.
So
you
can
see
how
you
know
this
this
larger
system,
it's
really
important
for
firefly,
to
be
able
to
plug
in
more
and
more
technologies
as
as
it
evolves.
C
I
do
want
to
to
want
to
let
you
know
you
know
where
the
sea
contributions
come
from
brian,
as
mentioned,
you
know.
One
of
the
things
that's
interesting
from
a
hyperledger
perspective
is
that
you
know
this.
This
code
has
gone
through
generations,
but
it
was
actually
a
core
part
of
the
clydo
product
itself,
so
it
takes
hours
six
years
of
learnings
and
three
years
of
active
development
and
there's
about
80
000
lines
of
code
that
that
have
gone
in
to
this
contribution.
C
C
C
You
know,
transaction
pools
and-
and
you
know
all
that
all
the
goop
down
in
into
the
plumbing
we've
we've
abstracted
that
away,
and
we
give
you
configuration
down
in
these
different
layers
and
we've
brought
a
tremendous
amount
of
engineering
down
into
these
different
connector
layers
to
handle
the
coordination
and
the
complexity
of
interacting
with
these
systems,
so
that
that
again
means
to
you
as
a
developer.
You
have
a
really
nice,
simple
microservice
in
the
core
to
to
integrate
with
and
to
build
your
application
upon
so
down
in
the
connector
layer.
C
You
know
connectors,
there
are
heavyweight
connectors;
they
they
adhere
to
the
the
plug-in
architecture,
which
is
something
that
we'll
talk
about
throughout
the
day.
There
are
we
don't
force,
for
example,
any
particular
protocol
of
between
the
connectors
and
the
actual
runtimes.
We
built
flexibility
there
and
knowing
that
the
runtimes
themselves
are
built
on
different
technologies,
but
some
of
these
connectors
are
doing
quite
a
lot
of
lifting,
for
example,
the
blockchain
interface.
C
C
C
C
You
know
token
this
this.
This
is
an
area
of
active
design
now
and
active
work.
The
ability
to
to
use
tokens
really
simply
and
easily,
as
you
build
your
firefly
based
applications
and
then
and
then
a
network
map.
So
these
technologies,
you
know
each
require
their
own
organizational
identity
so
having
it
having
a
single
place
where
that's
accumulated,
distributed
across
the
network,
things
like
permissioning
and
so
on.
C
C
B
C
There
and-
and
we
really
anticipate
that
that's
the
direction
the
community
is
gonna,
go
with
to
ensure
full
support
for,
for
all
the
big
three
fireflies
ready
for
enterprise.
You
know,
that's
that's
why,
as
collido
when
we
look
to
see
this
contribution
to
really
build
this
community
hyperledger
was
a
no-brainer
for
us,
with
its
enterprise
focus
for
for
dlt
and
ledgers
and
all
the
related
decentralized
technologies.
C
A
C
100
designed
for
enterprise
use
so
starting
with
the
apache
2,
you
know,
enterprise
license
friendly
license,
we're
committed
to
to
the
open
governance
and
the
values
of
hyperledger
and
the
linux
foundation
and
building
this
community.
We
invite
everyone
to
get
involved
and
to
find
a
way
to
be
involved
and
we'll
talk
about
ways
to
do
that
throughout
the
day
enterprise
grade.
C
You
know
things
like
zero
knowledge,
proofs,
confidential
computing,
which
are
sort
of
on
coming
of
age
of
their
own
right
and
so
so,
making
it
really
pluggable
and
sensible
and
that
what
what
else
this
could
mean
is
this
plugability
is
hey,
maybe
you're
a
really
large
enterprise
or
you're
part
of
a
really
large
network.
Maybe
you
need
a
completely
custom
way
of
exchanging
data
that
just
makes
sense
for
you.
C
Some
pieces
around
around
the
core
blockchain
technology-
that's
running,
you
know
things
like
global
ordering
and
finality
are
really
important,
important
to
coordinate
across
organizations
and
that's
sort
of
the
the
bedrock
upon
which
we
build
things
like
the
the
immutability
of
data
you
know
and
being
able
to
to
agree
and
and
have
that
single
source
of
truth
of
what
the
data
is
and
what
order
the
data
is
arrived
in
and
the
then
building
upon
that
sequencing
and
triggering,
but
also
the
larger
conservation
of
value
and
thinking
about.
You
know
that.
C
Tokens
that
that
is
really
powerful
programming
model,
as
well
for
for
developers
firefly
is,
is
bringing
all
that
to
bear,
but
we
are
extending
it
with
simple
apis
with
you
know:
off-chain
mechanisms
for
for
data
delivery,
thinking
about
efficiency,
so
we're
going
to
talk
about
how
batching
happens
and
how
grouping
happens
in
in
some
of
the
other
techniques
that
we've
seen
or
are
really
necessary
to
achieve.
You
know,
enterprise
levels
of
scale,
so
that's
all
easy
and
solved
and
sort
of
in
the
box.
C
C
Thinking
you
know
going
a
little
bit
beyond
you
know,
events
happening
and
thinking
about
going
from
triggering
to
streaming
right
and
thinking
about
how
we
can
really
up
the
level
of
process
orchestration
and
make
it
that
much
simpler
to
build
upon
and
then
and
then
also
unifying
or
simplifying
the
identity
problem
of
the
fact
that
these
different
technologies
need
to
plug
in
identity
in
different
ways.
Thinking
about
you
know,
I
mentioned
emerging
technologies
as
well.
C
Well,
we've
we've
given
thought
to
how
decentralized
identity
self-sovereign
identity
could
plug
into
the
system,
and
so
that's
that's
going
to
be
an
area
ahead.
You
know
on
the
exploration
front,
we
see
lots
of
opportunities
with
different
hyperledger
projects
and
other
technologies
out
there
in
the
broader
open
source
world
and
those
explorations
will
go
on
today.
We
we're
launching
firefly,
we're
we
are
formally
establishing
and
starting
to
build
the
community
if
we
will
be
pointing
you
and
you
can
check
out
the
booth
as
well.
C
If
you
want
more
specific
conversations
around
this,
but
we'll
be
kicking
off
bi-weekly
open
meetings
that
anyone
can
join,
I
encourage
folks
to
go
go
over
to
the
hyperledger
website
and
to
to
find
us
there
on
the
hyper
on
the
firefly
channel
and
to
get
plugged
in
firefly
channel
on
rocketchat,
but
just
a
really
quick
snapshot
of
high
priority
items
that
there's
active
investigation
going
on
you
know.
Full
fabric
support
we've
heard
loud
and
clear
from
folks
is,
is
is
going
to
be.
C
You
know
targeting
the
end
of
the
year
where,
where
firefly
itself's
hardened
and
we
really
use
the
glide
path
of
hyperledger
and
think
about
things
like
security
and
audit
verification,
and
so
on,
that
you
really
value
from
from
the
hyperledger
community
and
get
that
1.0
release
out
there
and
so
we'll
be
on
a
sprint
as
a
community
to
to
get
there.
I
think
it's
going
to
be
a
lot
of
fun
to
get
there
and
with
with
those
thoughts,
it
sort
of
concludes
the
overview
or
the
the
opening
keynote.