►
From YouTube: FireFly Closing Keynote (Repeat)
Description
Brian Behlendorf, Executive Director, Hyperledger
Steve Cerveny, Founder & CEO, Kaleido
Sophia Lopez, Founder & COO, Kaleido
Catch a recap of the intro to FireFly - both what it does, how it came into being, and why it solves some of the biggest pain points in building and deploying enterprise blockchain applications.
----
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
B
C
A
Great
well,
let's
jump
in
we
wanted
to
start.
I
guess
with
couple
thoughts
with
brian.
You
know,
steve
was
saying:
we've
been
living
this
space
for
about
almost
four
years
now
as
collido,
and
you
know
felt
really
motivated
and
passionate
to
open
this
up
to
grow
a
real
community,
although
we'd
open
source
for
portions
of
this
before-
and
I
had
had
some
people
on
our
previous
panel
who
who
had
been
touching
the
tech-
I
guess
so
so
we're
really
excited
about
growing
the
community.
A
B
Yeah,
well,
you
know,
I
think
firefly
addresses
have
been
a
long-standing
challenge,
which
feels
very
much
like
the
the
early
days
of
like
the
linux
operating
system
when
to
compile
your
own
kernel
when
the
user
interface
was
a
very,
very
basic,
x-window
stuff
that
had
been
ported
over
from
solaris
or
whatever.
I
I
and
it
very
much
felt
like
a
hacker,
only
kind
of
environment
right
and
over
time
you
know.
B
Obviously
you
had
gnome
and
you
had
other
parts
of
the
of
the
stack
emerge
and
finally,
a
usable
operating
system
that
you
know
you
could
put
on
the
chromebooks.
You
could
put
it
in
anything
else,
and
and-
and
you
know,
we
had
a
couple
of
early
projects
that
try
to
build
the
bridge
between
the
low-level
plumbing
and
the
developer
friendly
kind
of
environment.
B
Things
like
composer,
which
I
know
you're
all
familiar
with
and
composer,
really
was
best
as
like
a
design
tool
to
design
the
thinking
tool,
but
people
wanted
to
use
it
to
build
and
manage
their
production
systems.
So
that
was
always
a
challenge,
and
that
was
one
reason.
I
think
that
the
composer
team
themselves
decided
to
to
pull
back
on
that
project,
and
was
you
know
that
was
there?
B
Wasn't
the
right
approach
to
a
high-level
tool
to
be
able
to
build
and
and
manage
apps
that
balance
this
on
chain
off
chain
kind
of
thing,
so
the
prospect
of
now
having
a
tool
again
that
makes
it
easy
to
build.
I
and
one
that
has
the
benefit
of
being
able
to
work
across
multiple
ledgers,
which
matches
very
neatly
our
our
objective
since
the
beginning
of
hyperledger,
which
was
to
say
there's
fabric,
and
it's
really
market
leading
and
has
all
this
power
and
complexity.
B
It's
like
a
gigantic
chainsaw
right,
but
there's
other
ledger
platforms
in
hyperledger,
including
bay
zoo,
which
is,
you
know,
obviously
inherits
the
ethereum
stack.
So
the
multi-ledger
nature
of
firefly
is
super
important
to
us
and
I'm
really
happy
to
see
now
this
this
backbone.
This
kind
of
you
know
forming
that.
A
A
B
I
also
would
be
interesting
to
see
if
there
were
cryptographic
primitives
that
were
recurring
in
in
the
design
of
firefly-based
apps.
That
meant
pulling
in
versa,
which
is
a
library
of
cryptographic.
Primitives
would
be
really
useful,
too,
so
actually
think
there's
potential
to
collaborate
with
probably
all
of
the
different
projects
in
hyperledger
and
have
them
fit
into
this
kind
of
framing,
because
I
I
think
very
few
of
them
were
designed
primarily
with
like
making.
A
A
B
That's
a
good
question:
well,
definitely
having
a
responsive
core
maintainer
community
involved
participating
in
chat
on
the
mailing
list,
helping
make
sure
that
the
developer
experience
is
smooth
being
having
that
activity
will
build
confidence
on
in
the
part
of
other
people
and
they'll
jump
in
as
well.
I
think
that's
a
faster
way
to
build
community
than
something
that
kind
of
you
know
launches
and
then
looks
a
little
almost
like
a
ghost
town
right.
So
maintaining
that
momentum
is
pretty
cool.
B
B
You
know
the
linux
foundation
produces
over
100
different
conferences
a
year
and
and
like
the
upcoming
open
source
summit
in
september
in
seattle,
which
will
be
a
hybrid
virtual,
real,
real
one
but
all
over
the
world,
and
once
we
reopen
again
most
of
those
will
go
back
to
being
face-to-face
so
presenting
at
those
getting
out
there
writing
posts
for
medium
or
for
for
other
sorts
of
like
channels
tweeting
about
updates.
You
know.
A
Thanks,
brian
and
yeah,
we
have
our
eyes
on
ozcon,
so
we're
going
to
submit
some
sessions
for
that
and
I've
been
in
talks
with
ryan,
david
and
others
about
that.
But
that's
great
advice.
Well,
thanks
again,
brian
for
your
support.
Getting
you
know
ahead
of
this
week
and
and
here
with
us
today,
to
launch
sort
of
an
invitation
to
the
community
to
join.
A
A
One
thing
we've
been
talking,
some
of
the
panels
and
other
activities
today
you
know
if
you
look
at
enterprise
blockchain
and
the
sort
of
the
promise
of
enterprise
blockchain
people
look
at
solving
your
deep
problems
around
transparency
and
trust
that
go
all
the
way
back
into
this.
You
know
core
systems
of
record
companies,
and
until
now
we
didn't
have
a
technology
that
could
really
provide
that
shared
view
of
the
data
and
that
shared
application
logic.
A
And
then,
as
we
went
through
copit
over
the
last
year
and
a
half,
you
know,
we
saw
implications
to
supply
chain.
You
know
the
inefficiencies,
you
know
a
lot,
a
lot
of
issues
where
we,
just
as
a
society
things
started
breaking
down.
So
I
think
there's
a
big
spotlight
on
how
can
we
do
a
better
job
as
people
are
digitally,
transforming
and
moving
to
the
cloud
to
solve
some
of
these
economic
inefficiencies
and
social
problems
that
result
through
some
of
the
misfunction
of
these
systems?
A
We've
seen
that
during
covet,
you
know
some
industries,
such
as
insurance
industry,
has
told
us
in
north
america,
their
digital
transformation
roadmaps
have
accelerated
by
a
decade
across
all
industries.
Various
analysts
have
done
research
on
this
and
they're
saying
there's
about
a
seven
to
eight
year.
Acceleration
of
that.
So
we
have
the
industry,
drivers
and
business
drivers,
but
behind
some
of
these
changes,
mckenzie
did
some
recent
research
and
saw
that,
oh,
you
know
eight.
A
Only
eight
percent
of
companies
believe
that
their
current
business
models
will
remain
viable
if
they
don't
digitize
so
they're,
seeing
this
digital
transformation
of
the
back
office
as
a
real
imperative
and
they
and
digital
ecosystems
are
estimated
to
account
for
30
of
global
corporate
revenues.
Just
in
the
next
you
know
four
or
five
years
alone.
A
So
what
it?
Basically,
they
think
the
job
initially
is
writing
some
smart
contracts,
starting
a
blockchain
note.
You
know,
building
a
web
app
and
then
just
deploying
so
a
couple
of
components.
You
know
a
few
a
few
months
four
to
six
months,
maybe
to
do
that.
What
the
job
really
becomes
is
like
looking
at
sort
of
the
architecture
and
design,
and
how
do
you
actually
use
blockchain
and
then
getting
into
looking
at
the
architecture
and
design
of
all
the
different
off-chain
pieces
so
that
the
apps
can
talk
to
each
other
you're
exchanging.
A
You
know,
documents
private
documents
between
parties.
You
know
solving
problems
that
are
are
needed
for
the
solution,
but
it's
much
beyond
just
running
the
node
or
writing
a
smart
contract
and
then
struggling
to
code
to
the
blockchain
apis
and
the
different
protocols
or
different
levels
of
sophistication
and
lease
of
use
around
that
aspect.
So
it's
a
blocker
for
traditional
enterprise
developers
who
are
looking
for
restful
apis.
A
So
then
you
know
they
come
to
the
realization.
Deployment
can
be
pretty
far
off
and
it's
really
more
like
40
components,
and
it
could
be
two
to
four
years
to
get
into
production
with
some
of
these
ambitious
projects
that
get
announced
with
big
fanfare,
and
then
they
run
into
the
reality
of
what
it
really
looks
like
to
build
one
of
these
solutions.
A
B
A
You
know
in
the
past,
with
the
gen
1,
you
know,
maybe
half
of
what
you
were
doing
was
all
on
the
plumbing
layer,
things
like
architecture,
infrastructure,
design,
reusability,
you
know
where
smaller
pieces
and
then
the
business
value
use
case
ended
up
being
a
very
you
know,
very
thin
slice,
so
you
people
would
have
a
very
ambitious
goal
for
their
consortium
or
project
and
then
spend
so
much
time
on
the
money.
Time
and
money.
A
That
they
end
up
building
sort
of
a
simple
calculator
app
when
they
really
needed.
You
know
very
complex
or
financial
market
exchange
was
the
initial
vision.
Now,
with
these
this
gen
2,
a
way
of
working,
the
plumbing
you
know
is
greatly
simplified
and
you
see
the
demo
you'll
see
what
that
looks
like
in
terms
of
what
you
get
versus
lines
of
code.
C
All
right,
thanks
sophia
and-
and
I
I
think
you
know
firefly
setting
out
it's-
it's
an
ambitious
goal
for
a
project
to
to
really
take
a
half
step
back
and
look
at
that
graph
and
say:
okay
something's
off
here.
If
you,
if
you're,
really
spending
most
of
your
budget
on
a
project
on
plumbing
right,
which
we've.
C
You
know
how:
how
can
we
invert
that
you
know
plumbing
is
a
is
a
great
candidate
to
build
an
open
source
community
around
and
just
solve
it
as
an
ecosystem
as
a
community
and
sort
of
allow
that
budget
to
be
inverted,
and
so
what?
What
we're
introducing
today
is
is
firefly.
A
part
of
the
the
hyperledger
community
coming
in
at
the
labs
stage
and
looking
to
grow
and
advance
through
the
community
there
and
be
incubated
is
a
what
we're
calling
a
multi-party
system
and
we're
gonna.
C
But
before
I
get
into
that
detail,
I
want
to
start
with
an
analogy
because
we
found
this
is
really
helpful.
If
you
think
about
docker
and
and
the
first
time
that
you've
used
it
or
saw
it-
maybe
maybe
you're
younger
and
you
just
take
it
for
granted.
But
some
of
us,
some
of
us,
saw
the
world
before
docker,
where
software
was
all
over
the
place
and
and
in
those
days
your
budget,
your
I.t
budget
for
a
project,
was
dominated
by
not
your
business
application,
but
dealing
with
a
lot
of
plumbing,
essentially
type
of
operations.
C
C
It
was
just
not
possible
or
feasible,
and
so
the
market
sort
of
became
stuck
or
there
was
a
need
for
a
larger
system
and
along
came
kubernetes,
really
sort
of
standing
in
the
gap
there
and
giving
you
this
that
broader
control
plane
upon
which
to
build
and
orchestrate
and
manage
your.
You
know
how
many
ever
hundreds
of
dockers
and
it
was
designed
to
be
really
pluggable.
C
So
there's
there's
more
than
one
choice
for
networking
and
you
know
you
know
the
cloud
providers
have
come
in
and
plug-in
plugged
in
underneath,
and
you
know,
technology
providers
have
come
along
and
plugged
in
and
built
tools
around
this,
and
you
have
this
larger
system,
this
enterprise
system,
around
docker,
which
importantly
delivered
the
initial
promise
of
docker
itself
right
the
breakthrough
of
all
software
fitting
in
the
same
box.
It's
now
achievable
or
consumable
how
about
blockchain.
So,
if
you
think
about
blockchain
wow
when
it
came
along
there's
this
like
it
just.
C
In
the
the
enterprise
software
space,
if
you've
seen
the
back
office
of
companies
in
the
sprawling
estate
of
hundreds
of
systems,
if
you've
seen
the
size
of
business
networks,
hundreds
thousands
of
participants
in
a
supply
chain
or
in
a
financial
network
or
in
a
you
know,
a
value
chain
in
the
insurance
space
or
whatever.
It
is
right
and
just
the
the
lack,
the
total
amount
of
inefficiency,
the
lack
of
coordination.
It
just
makes
sense.
However,
you
know
I
think
it's
pretty
clear
to
say
that
enterprises
just
can't
get
into
production.
C
C
You
know
we
see
firefly
as
a
multi-party
system
being
a
larger
system
where
there's
a
blockchain
still
there
right,
but
we're
also
looking
at
all
the
other
layers
of
the
stack
and
all
the
plumbing
that
we
were
just
talking
about
a
minute
ago
that
can
dominate.
You
know
the
budget
for
for
an
enterprise,
blockchain
solution
right
all.
A
C
C
That's
that's
trying
to
really
drive
that
simplification,
all
the
way
up
to
the
application
layer
and
encapsulate
a
multiple
layers
into
a
pluggable
framework,
and-
and
you
know
it's-
it's
really
just
a
quick
review
on
what
data
flows
look
like
inside
of
a
decentralized
business
network.
You
know
where
each
member,
in
these
dotted
line
circles,
has
a
full
stack
of
its
own
technology
right
that
stack.
We
were
just
talking
about.
It
doesn't
exist
once
it
exists
in
every
organization's.
C
Across
the
business
network
right,
we
see
multiple
kinds
of
operations
here,
they're
happening,
of
course,
there's
the
ledger
of
the
blockchain
itself,
but
almost
always
almost
always
in
an
enterprise
project.
There's
private
data
exchange,
usually
the
more
private,
the
better
that's
that's
quite
commonly
is
coupled
with
some
form
of
broadcast
as
well.
So
it's
not
just
one
of
the
other.
We
often
see
both
and
then
having
that
shared
ledger,
building
digital
assets
and
using
tokens,
and
so
on.
You
know
it's
a
really
powerful
programming
construct
so.
C
Together
that
this
is
the
shape
of
the
problem
that
you
need
to
solve
just
to
build
and
deploy
one
blockchain
use
case
across
a
business
network.
This
is
all
that
all
these
lines
are
plumbing
right.
All
these
all
these
rectangles
and
the
stack
are,
are
plumbing
in
different
parts
of
the
solution.
So
with
that
I'd
like
to
introduce
firefly
a
multi-party
system
built
and
designed
for
cross-organization
data
flows,
that's
what
it's
about.
C
At
the
end
of
the
day,
you
know
understanding,
decentralized
architecture
and
the
fact
that
all
organizations
are
going
to
be
running
a
stack
and
and
because
there
are
so
many
lines
of
collaboration
and
places
for
data
to
flow.
You
know
having
a
very
event-driven
system
and
framework
to
really
you
know,
tie
together
and
coordinate
all
the
disparate
systems
that
that
exist.
Acro
within.
C
And
also
the
the
legacy
and
core
back
office
systems
that
exist
around
the
business
network
as
well.
So
all
that
coordination
is
is
really
you
know
a
business
process,
feat
of
engineering
and
so
trying
to
make
that
part
of
the
problem
orders
of
magnitude
simpler
for
for
it
for
a
poor,
old
developer
who's,
just
trying
to
get
a
piece
of
data
from
point
a
to
point
b,
often
right
and
really
importantly,
just
like
kubernetes
a
flexible
technology
framework.
C
You
know,
because,
because
a
there's
lots
of
different
technologies
b,
there's
different
implementations
of
how
to
do
messaging
or
data
exchange,
but
but
most
importantly
c,
there's
also
emerging
technologies.
You
know
confidential
computings,
your
knowledge
proofs
and
so
on.
That
really
ought
to
fit
into
this
larger
multi-party
system.
So,
as.
C
Can
evolve
with
technologies,
different
blockchains,
you
know
as
well
as
off-chain
technologies,
just
a
quick
word
on
the
seed
of
the
contribution
this.
This
is
coming
from
primarily
from
collido
the
initial
80
000
lines
of
code
that
that
are
firefly
within
hyperledger.
Now
this
this
is
our
six
years
of
learnings,
as
well
as
three
years
of
active
development.
So
we've
had
this
these
capabilities
in-house
as
clydo
products
and
but
we're
we're
convinced,
and
we
have
large,
very
large
customers.
Some
of
them
spoke
throughout
the
day
today.
C
To
to
invite
others
to
contribute
to
help
to
let
the
community
help
shape,
you
know
how
the
investments
go
into
this
code
going
forward
and
to
really
build
a
stronger
product.
We
were
just
talking
with
brian
a
few
minutes
ago
about
the
synergies
across
different
hyperledger
communities,
and
we
want
to
explore
those
going
forward
as
sort
of
like
an
umbrella
project
we
sometimes
have
referred
to
to
hyperledger
or
it's
a
firefly
state.
You
know.
A
C
Plugging
in
some
of
those
other
cross
pollinations
as
well
going
forward
so
just
zooming
in
for
a
second
on
the
firefly
node
itself,
there
will
be
recordings
up
soon.
If
you
want
to
really
dig
dig
into
the
technical
workshop.
There
also
are
pointers
available
in
the
booth,
if
you
want
to,
if
you
need
help
being
routed
into
to
the
community
through
the
larger
hyperledger
website,
but
just.
C
On
the
node
itself,
the
core
is
is
essentially
the
brain.
That's
there
that's
the
thing
that
you
you
interact
with
as
a
developer.
Building
your
application.
It's
there
to
give
you
really
simple
apis
in
web
hooks
to
say,
hey.
I
want
to
send
this
piece
of
data.
Hey
give
me
a
call
back
when
you've
received
it.
You
know
provide
give
me
the
proof
with
the
blockchain.
I
don't
want
to
go
into
the
low-level.
C
You
know
interface
that
they
conform
to
to
make
it
really
pluggable,
so
that
the
blockchain
interface,
which
is
definitely
doing
a
lot
of
heavy
lifting
you
know,
there's
one
there
for
ethereum
you'll,
see
in
in
the
firefly.
There's
also
you
know
ethconnect,
but
there's
also
quarter
connect
sitting
alongside
of
it.
C
There
are
discussions
today
about
fabric
connect
and
getting
that
launched
and
built,
and
there
may
be
even
another
community
out
there
that
wants
to
help
merge
some
code
in
to
make
that
possible,
but,
alongside
the
blockchain,
really
importantly,
bringing
sophia
said
five
to
ten
percent.
Well,
what
about
the
other?
Ninety
percent,
all
these
other
forms
of
plumbing,
that
until
today,
you've
had
to
do
to
build
a
blockchain
use
case.
Off-Chain,
you
know:
data
exchange,
whether
it's
structured
or
whether
there's
a
gigabyte
file.
You
know
large
blobs
being
passed
around.
C
You
know
whether
there's
broadcast
going
on
of
of
of
events
or
datas,
that's
being
synchronized
and
then
how's
that
all
connect
together.
So
if
I
send
something
to
you
privately,
let's
pin
that
to
the
blockchain,
let's
get
global
ordering
and
finality
and
keep
that
into
the
puzzle.
I
already
mentioned
multi-protocol,
that's
really
important
to
us
to
to
give
that
a
flexibility
and
choice,
but
also
to
tap
into
the
strength
of
unique
attributes.
C
So
some
of
these
underlying
protocols
so
they're
still
there
that
power
is
still
available,
while
while
there
are
easy
interfaces
into
them,
the
existing
interfaces
are
still
there.
You
still
write,
you
know
arbitrarily
complex
smart
contracts,
so
chain
codes.
If
that's,
if
that's
what
you
desire
to
do,
and
that's
there
for
that
five
percent
of
the
time,
but
for
the
rest
of
the
time
when
you're
using
you
know
what
we
now
recognize
are
pretty
common
patterns
fireflies
there
to
give
you
simple
apis
to
accomplish
that
almost
like.
C
You
crud
operations
are
great
most
of
the
time.
Occasionally
you
need
to
write
that
you
know
stored
procedure
with
with
a
bunch
of
of
data
wrangling
inside
of
it,
and
so
so
that
we
see
that
similarity
there.
Firefly
is
ready
for
enterprise,
it
is
an
active
code
base,
but
it
is
designed
for
enterprise
use.
I
you
know
that,
and
you
understand
that
with
the
hyperledger
community
and
the
licensing
that
it
implies,
as
well
as
the
open
governance
that
it
brings,
you
know,
firefly
brings
with
it.
C
C
Of
data
awesome
things
like
tokens
and
nfts
and
triggering,
but
we
take
that
a
level
up.
So
it's
not
just
triggering
it's
event
streaming.
It's
it's
not
just
getting
transactions
in
this
automatic
batching.
You
know
they're
a
simple
api
restful
api
so
that
it's
not
low
level
pro.
You
know
rpc
calls
and
so
on,
and
then
you
find
the
identities.
So
so
everything
has
an
identity.
C
As
as
identity
sort
of
a
system
as
the
blockchain
itself,
and
so
having
an
identity
registry
with
organizations
and
simple
member
management
and
onboarding,
putting
all
that
in
one
place
almost
like
an
address
book
is
another
really
important
piece
of
of
how
firefly
works.
So,
finally,
just
real
real
quickly
on
the
road
ahead
today
is
a
launch.
It's
it's
a
beginning,
fortunately
we're
not
starting
from
st
standing
still.
We
have
a
running
start
as,
as
I
mentioned,
the
three
years
of
active
development
and
six
years
in
the
blockchain
space
seating.
C
This
this
contribution
has
already
been
a
jolt
of
energy
from
different
parts
of
the
hyperledger
space
and
even
beyond
about
you
know,
wanting
to
get
involved.
We
encourage
everyone
to
get
involved.
The
community
building
process
is
now
officially
underway.
So
there
will
be.
You
know
all
the
things
you
would
expect
happening,
maintainer
selections.
C
You
know
open
meetings
happening
on
a
regular
basis,
there's
a
rocket
chat
channel
set
up
on
on
the
hyperledger
chat
tool,
so
you
can
get
plugged
in
there.
You
can
certainly
download
the
code
today,
but
looking
forward
at
the
roadmap,
there
are
definitely
some
high
priority
items
that
are
already
feedback
in
right
from
the
community
fabric.
I
talked
about
as
well
as
looking
at
some
some
specific
token
use
cases
which
are
quite
common
again.
C
Almost
like
the
crud
versus
stored
procedure
example,
I
was
using
a
minute
ago
there's
some
common
things
that
have
happened
with
tokens.
We
want
to
extend
firefly
to
make
to
make
those
a
whole
lot
easier
than
they
are
today.
One
simple
example:
delivery
versus
payment.
I
send
you
data
or
a
thing
an
asset.
I
want
tokens
back
value
tokens
back
in
exchange
right.
So
how?
How
do
you
make
that
happen?
Atomically
there
are.
There
are
common
ways
to
do
that,
so
those
sorts
of.