►
From YouTube: FireFly Technical Overview
Description
Peter Broadhurst, Co-Founder & Head of Engineering, Kaleido
Gabriel Indik, Software Engineer, Kaleido
The leading technical minds behind FireFly will walk you through a deep dive. You'll walk away understanding how the system works today, and what the road ahead is for FireFly.
----
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
You
know
accelerating
problems
for
our
customers
that
we've
been
working
with
directly
to
being
an
open
community
that
really
really
works
for,
but
but
actually
what
you're,
what
you're
running
on
when
you,
when
you
actually
try
firefly,
is
codes
that
is
based
on
what's
in
production
for
real
world
customers,
it
it
it's
it
it's
kind
of
us
trying
to
take
everything,
we've
learned
and
distill
it
in
a
way
that
it's
not
it
it
it's
it's
able
to
be
used
by
by
everybody.
So
that's
really
exciting.
A
For
us
as
engineers,
you
know
we're
so
passionate
about
open
source.
We
use
it
every
day.
So
it's
really
exciting
to
be
talking
to
you
all
today
about
the
architecture
of
what
we
really
hope
is
going
to
be
a
project
that
that
can
help
multiparty
systems
go
many
times
faster
than
they
have
across
many
more
industries
across
many
more
projects
than
than
if
everybody
continues
to
do
everything
sort
of
from
the
plumbing
coming
up.
A
So
with
no
no
more
do
let
me
let
me
start
to
drill
drill
down
a
little
bit
to
do
that.
I
am
going
to
start
by
by
zooming
back
out
to
a
couple
of
the
things
and
recapping
just
for
a
couple
of
minutes
on
a
couple
of
the
points
that
were
made
made
earlier
by
steve
and
and
by
severe
actually,
because
I'm
going
to
start,
I'm
going
to
start
talking
about
from
a
technical
person's
perspective.
A
This
this
slide
really
resonates
with
me
from
what
we've
seen
in
the
industry
this.
This
feeling
that
when
you
come
to
a
blockchain
project,
the
thing
that
matters
most-
and
it
is
the
kernel-
it's
the
beating
heart,
it's
the
thing
that
makes
your
project
different
to
all
of
those
other
enterprise
projects
that
have
come
before
it.
It's
that
smart
contract
code
right
that
critically
important
piece
of
of
code
that
you're
probably
going
to
be
reusing
and
building
upon
something
that
came
from
others.
There's
this
feeling
when
you
start
a
project,
but
it's
about
that.
A
That's
because
it's
the
most
important
piece
of
the
puzzle,
it's
the
linchpin,
the
project
as
a
whole
is
going
to
be
about
it,
and
once
we
get
that
right,
we're
golden
right.
Once
we've
we've
built
that
smart
contract
we've
got
it
audited,
we've
deployed
it
we're
sorted.
You
know
it's!
It's
there
in
chain
code
in
fabric
or
it's
there
in
solidity
in
in
in
ethereum,
or
it's
there
inside
of
a
cord
out
right,
we're
good,
but
but
actually
this
middle
column.
It
is
so
true
what
we're
doing
in
these
multi-party
systems.
A
What
anybody
who's
lived.
This
knows
is
you're
trying
to
bridge
sophisticated
decades-old
it
organizations
together,
you're,
trying
to
bridge
together
core
systems
that
perform
the
most
important
transaction
processing
inside
of
a
large
enterprise.
That's
been
around
for
a
hundred
years
and
you're
trying
to
do
that
in
a
an
atmosphere
of
competition
right.
A
The
reason
why
these
projects
are
so
valuable
building
these
ecosystems
is
so
valuable
is
because
you're
building
ecosystems,
not
just
with
your
supply
chain
or
not
just
with
your,
your
customers
and
partners,
you're,
actually
building
these
as
an
industry
with
your
competitors
as
well.
So
so
things
get
complicated.
A
Data
right
data
is
in
an
enterprise
context.
By
default,
private
sensitive
regulated
probably
comes
under
things
like
right
to
to
forget
and
right
to
get
to
be
deleted
legal
legislation.
That
means
you
need
to
be
able
to
prove
who
you
sent
it
to,
and
everybody
involved
in
that
training
needs
to
be
able
to
prove
that
they
can
delete
it.
Some
of
the
data
you
may
only
be
able
to
keep
for
a
short
period
of
time.
Some
of
the
data
may
be
extremely
sensitive.
B
A
Same
thing
that
you
do
in
a
in
in
an
enterprise
consortium,
so
so
actually
what
you
end
up
doing
is
worrying
about.
Well,
how
do
I
integrate
with
my
core
systems?
What's
this
data
gonna
look
like
what
is
the
tiny
nugget
that
can
go
on
chain?
Where
can
we
use
the
blockchain
to
the
greatest
effect?
Is
it?
Is
it
having
a
complete
unique
instance
of
something
like
a
like
a
legal
contract
or
a
document,
or
something
at
the
nft
space?
Is
it?
A
A
We've
been
part
of
trying
to
help
projects
that
have
got
a
few
years
in
and
struggles,
and
we've
got
all
of
this
experience
that
we
just
this
community
is
about
sharing
that
coming
together
with
the
practitioners
that
are
in
blockchain
the
practitioners
that
aren't
in
blockchain
and
have
to
use
this
thing,
the
integrators,
the
app
developers,
the
mobile
and
ui
beautiful
experience
builders
coming
together
to
get
to
where
the
job
ought
to
be.
Let's
decide
what
the
business
problem
is
we're
trying
to
solve.
A
Let's
work
out
what
our
canonical
data
formats
are:
let's
work
out
how
we're
going
to
share
data.
Let's
work
out
the
sequence
of
events
that
we
agree
has
to
be
true
and
in
an
enterprise
context.
Let's
work
out
where
everybody
can
do
things
differently,
because
in
reality,
there's
going
to
be
non-deterministic
human
processing.
A
A
B
A
This
this
technology
and
what
makes
it
different
to
a
blockchain.
How
does
it
work
with
blockchain?
Has
it
worked
with
other
multi-body
system
technologies
like
compute
like
cqpps
and
trusted
compute
et
cetera?
What
is
what
is
it
at
it's,
at
its
core
and
and
in
in
the
previous
session
we
we
we
talked
about
that.
A
firefly
node
is
like
a
microservices
architecture
in
its
own
right.
It's
a
plugable
system
where
you
run
for
your
organization,
a
mixture
of
technologies.
A
You
run
a
blockchain
node,
obviously,
but
you
also
you've
got
a
private
database.
That's
pre-integrated
with
this
indexed
fast
gives
you
your
view
of
the
network,
which
is,
by
definition
in
any
enterprise
context,
can
be
different
to
anyone
else's
view
in
the
network,
and
that's
not
some
strange
database
technology
that
you
can't
use.
That's
pluggable,
that's
your
core
sql
database
right!
That's
just
integrated
with
your
enterprise
context.
A
You
then
got
messaging
events.
Those
off-chain
transfer
technologies
that
we
all
know
as
a
plugable
service
and
today
you'll
be
using
one
gabrielle's
going
to
talk
you
through
the
technologies
you're
going
to
be
using
today
in
the
lab
and
you'll,
be
using
a
very
straightforward
one,
but
that
again
is
pluggable
so
that
you
can
plug
in
your
mqp
based
system,
if
that's
active,
mq
artemis.
If,
if
that's
you
know
your
core
enterprise
system,
your
your
typical
ibm
messaging
bus,
whatever
it
is
right.
A
That's
that
plug
point
is
there
in
the
system
to
be
able
to
to
to
integrate
that
between
the
members,
because
these
are
these
ecosystems
are
just
as
much
about
sharing
private
data
as
they
are
about
sharing
the
the
the
on-chain
transactions
as
part
of
the
system.
So
how
does
an
architecture
from
a
technical
level
support
that?
Well
in
the
modern
world?
It
does
it
through
modern
dockerized,
microservices
architecture,
and
that
is
something
that
takes
really
deliberate.
A
So,
starting
from
this
picture,
let's
talk
about
what
a
node
is
right.
It
has
some.
It
has
a
core
okay,
the
core
is
written
in
golang
for
the
latest
generation.
We
actually
had
a
previous
core.
That's
been
being
used
in
a
lot
of
a
lot
of
projects
which
we've
open
sourced.
It's
there
in
the
in
the
repository,
and
that
was
typescript
previously,
and
we
made
the
deliberate
decision
as
part
of
seediness
that
we
thought
a
go.
A
Pluggable
architecture
was
what
was
needed
for
the
kind
of
the
kind
of
problems
that
are
being
solved
with
this
with
this
technology.
So
this
this
core
is
responsible
for
orchestration
right.
It's
it's
responsible
for
plugging
things
together,
so
it
has
an
orchestration
tier.
It
has
an
api
that
it
services
surfaces
externally,
which
is
what
your
applications
connect
to,
and
then
it
has
the
core.
The
core
components
inside
of
there
that
orchestrate
the
big
things
that
are
done
in
multi-party
systems
expect
to
see
these
get
added
to
over
time.
A
Conversation
but
jim
zhang,
who
can't
be
here
today
but
is
a
critical
member
of
our
of
our
community
here,
is
leading
the
is
leading
the
drive
of
getting
the
wide
architecture
together
for
plugging
tokens,
both
nfts
and
value
transfer,
into
this
things
like
delivery
versus
payment
right.
So
that's
a
a
core
responsibility.
A
It's
sort
of
one
of
the
patterns
that
at
the
front
of
this
you
get
an
api,
but
there's
a
developer.
You
can
use
in
those
10
lines
of
code
that
andrew
showed
you
right.
You're
there
you're
working
you've
got
that
pattern
working
for
you,
those
are
exposed
externally
and
then
the
the
legs
of
the
swan
swimming
underneath
are
the
connectors,
which
are
micro,
service,
runtimes
that
connect
to
the
back
end
core
infrastructure,
and
we
made
a
very
deliberate
decision,
I'm
going
to
draw
down
a
layer.
A
They
they
conform
to
an
interface
in
go
which
allows
them
to
be
initialized
with
the
configuration
that's
standardized
as
part
of
the
core
to
be
able
to
advertise
what
capabilities
they
do
or
they
don't
provide
within
the
bucket
that
they're
in.
If
there
were
public
storage
plug-in
like
ipfs
or
they
were
blocking
a
blockchain
plug-in
like
like,
like
besu
or
or
fabric,
or
or
corder
or
they're,
a
database
plug-in
like
postgres
or
or
my
sql
implementation
like
couch
or
or
mongodb.
A
That
then
there's
bi-directional
track
of
you
know
data
that
can
go
in
either
direction.
Right
actions
can
happen
through
that
and
events
can
come
back
and
this
plug-in
interface
allows
any
transport
to
be
used
into,
and
out
of
and
out
of
this,
this
golang
shin
and
then
the
connectors
themselves
can
be
written
in
any
language
they
run
separately.
They
can
have
a
different
model
to
the
core
firefly
model,
which
is
what
you'd
expect
active
active
database
backed
highly
resilient,
modern
minimum
three
deployment
architecture
for
the
core.
A
A
Really
important,
they
could
also
be
written
in
completely
different
language,
so
today,
you're
actually
going
to
be
using
connectors
that
are
that
involve
a
typescript
node.js
connector
is
going
to
be
one
of
the
connectors
you're
using
for
the
private
data
exchange
and
that's
embraced,
and
it's
actually
necessary
when
you
look
at
the
different
communities.
So
cordo,
for
example,
is
a
java
centric
community.
A
The
native
rpc
interface
recorder,
is
java
serialization
of
objects
right.
It
only
makes
sense
to
do
that
in
java,
but
that
can
plug
in
does
plug
in
is
actually
already
one
of
the
things.
That's
quite
advanced,
it's
being
finalized
to
move
over
from
generation,
one
to
generation
two,
but
that's
been
proven
that
that
can
be
can
be
done
and
you
can
have
the
brain
working
in
a
different
fundamental
language.
So
this
means
it
can
actually
scale
like
projects
like
docker
were
able
to
do
with
their
their
plug-in.
A
A
You
know
you're,
making
it
just
just
this
sort
of
thin
thing
that
you're
you're
undervaluing
it.
Well,
we
value
it
so
highly
inside
of
the
the
firefly
community
of
engineering,
and
I
hope,
at
the
end
of
this
sort
of
next
section,
you'll
see
why
why,
even
for
the
simple
cases,
we
need
this
kind
of
framework
that
firefly
is
and
how
it
does
extend
to
a
cases
where
you've
got
super
advanced,
sophisticated
on-chain
logic
that
is
actually
part
of
the
the
system
as
well.
A
A
You
come
to
blockchain
and
you
want
to
do
something
meaningful
inside
of
this
diagram,
we're
showing
not
actually
just
what
would
need
to
be
done
inside
a
firefly,
but
actually
what
would
need
to
be
done
if
you're
building
this
from
scratch
three
stages,
we're
showing
I've
got
a
a
digital
asset,
a
piece
of
data-
maybe
maybe
this
is
the
scan
of
a
diamond
that
is
part
of
digital
twinning.
It's
to
an
nft.
A
A
I
want
to
say
that
it
exists
to
the
whole
community
and-
and
I
want
to
broadcast
that
out
and
and
maybe
some
of
that
data
can
go
directly
onto
the
blockchain,
but
in
most
enterprise
scenarios
we
find
that.
That's
not
always
true,
that
there's
at
least
some
data
that
can't
go
onto
the
blockchain
directly.
A
So
really
simply
right.
I
want
to
write
this
document
to
the
dot.
The
blockchain
that's
we've
had
that
said
to
us
so
many
times.
We
know
that's
how
it
feels
right.
I
just
want
to
put
this
document
in
the
in
the
blockchain.
How
do
I
do
it?
Well
that
that
sort
of
step
step
one
and
we'll
talk
through
kind
of
what
that
really
actually
means
for
a
poor
developer
today,
like
just
starting
from
their
principles,
I
want
to
like
push
that
out
to
everybody
that
broadcast
button
that
andrew
did
earlier.
A
The
next
stage
we're
going
to
look
at
is
well.
I
I've
seen
that
that
thing
over
there
that
organization,
I
know
who
they
are.
I've
got
their
identity,
they've
proven
that
they
have.
This
thing,
they've
published
enough
data
to
me
through
a
hash
or
real
data
or
whatever
it
is
that
I
know
I
want
this.
A
I
need
to
ask
for
it.
I
need
to
go
to
them
and
I
need
to
say
well.
You
know
that
that
scan
of
that
diamond.
You
know
that
matches
up
with
my
record.
I
know
I've
got
that
diamond.
I
I
want
to
ask
you
for
this
proof
that
you've
got
the
this
super
detailed
100
megabyte
ultra
fine
scanner
there
right,
I
want
a
copy
of.
I
want
a
copy
of
that,
send
it
to
me
now.
A
I
don't
want
to
put
all
of
that
somewhere
that
everyone
else
can
see
it
and
that
that
that
means
I
probably
want
to
send
this
to
you
as
a
sort
of
private
exchange,
but
you
still
probably
want
to
know
it's
from
me.
So
surely
what
I
just
need
to
do
is
I
need
to
send
you
a
private
message
through
the
blockchain.
A
Well,
okay,
that's
that's
great.
How
do
you
send
a
private
message
through
the
blockchain
and
with
all
of
the
data
right
that
needs
to
be
aggregated
together?
Maybe
five
different
bits
of
data
need
to
go
with
that
message
so
that
it
comes
across
and
then
that
first
organization
that
advertised
that
they
have
that
that
data
to
hand
they're
going
to
look
at
what
came
across
for
them.
For
this
other
organization,
they've
got
to
inspect
it,
they
it
may
be
deterministic.
A
A
There's
human
decision
making
involved
in
this
need
to
authorize
it
and
then
they're
gonna
send
the
data
back
again
to
the
other
side
and
in
this
example
that
doesn't
need
to
be
pinned
to
the
blockchain.
You
just
need
to
do
that
with
really
fast
efficiency,
because
blockchains,
regardless
of
whether
you're
using
a
private,
blockchain
or
you're,
using
a
public
blockchain
and
an
architecturally,
although
the
focus
in
enterprise
which
is
kind
of
why
we're
focused
there,
but
the
focus
of
the
enterprise.
At
the
moment.
A
The
real
world
production
adoption
is
in
in
the
permission
chains,
but
there's
a
great
evolution
happening
on
the
interlock,
with
public
chains
right,
but
even
in
a
permission
chain,
you're
not
talking
about
the
same
the
same.
You
super
super
fast
throughput
because
you've
got
to
get
agreement
on
that
transaction
from
a
set
of
parties.
Even
if
it's
a
fabric
channel
and
you've
reduced
the
number
of
parties
to
a
smaller
number.
A
It's
still
going
to
be
something
slightly
more
sophisticated
than
just
pushing
that
data
to
somebody.
So
there
are
going
to
be
cases
where
you
want
to
do
exchange
where
you
don't
even
want
to
use
the
blockchain
at
all.
I
know
I
know
in
a
blockchain
context
in
the
body
party
system.
That's
a
little
bit
hard
to
hear
like
why?
Wouldn't
I
pin
everything
we're
pragmatists!
A
A
It's
not
something
that
certainly
in
this
project
that
we
that
we
think
should
be
said
like
like
that's
that's
wrong,
you're
you're
wrong,
because
you
want
to
do
that.
No,
you
understand
your
business
process.
You
understand
how
it
fits
together,
yeah
that
can
that's
perfectly
acceptable.
Okay.
So
really
we
just
talked
about
three
super
simple
steps.
I'm
gonna
send
you
I'm
gonna
broadcast
the
network,
some
something
you're,
you're
gonna,
see
because
you're
part
of
the
network
that
it
exists.
You're
going
to
send
me
a
request.
A
That's
going
to
be
audited
that
you
sent
me
the
request
and
I'm
going
to
send
you
back
some
data.
Let's
look
at
what
would
be
needed
to
do
that
from
base
principles
from
base
principles.
Well,
I
want
to
pin
it
to
the
blockchain,
then
what
what
I?
What
I
need
to
do
is
I
need
an
api
inside
of
my
application
right.
I
need
my
app
is
not
blockchain
the
app
itself,
the
user
experience,
the
mobile,
the
core
integration
with
my
back-end
systems.
That's
unique
to
me!
Not
everybody
else
in
the
network!
A
That
thing
needs
to
be
able
to
upload
the
data.
That's
going
to
be
pinned
to
the
blockchain.
It
needs
to
be
able
to
say
do
it.
That
means
it
needs
an
api
and
almost
certainly
we
found
it's
almost
universally
true.
The
amount
of
transformation.
That's
needed
of
that
data
to
get
it
sort
of
into
the
system
means
you
want
it
to
be
stored
in
your
own
private
storage,
so
you're
going
to
have
a
database
that
isn't
your
application
core
database.
It's
not
the
database
of
your
erp
system
that
you
built
30
years
ago.
A
This
is
a
separate
database.
That's
for
the
blockchain
right,
it's
for
this!
It's
for
this
body
party
system,
you're,
building
and
you're,
going
to
have
to
transform.
You
know
code,
the
data
to
get
it,
so
you
can
have
a
database
inside
of
this.
This
thing
and
then
you're
going
to
say.
Look
I
want
to
broadcast
this,
but
because
it
can't
all
go
to
the
blockchain.
You've
got
to
actually
take
two
separate
actions.
A
You've
got
to
upload
that
that
data
to
somewhere
that
is
suitable
for
the
type
of
data
you're
uploading,
it's
100
megabyte
payload.
Where
am
I
going
to
stick
that?
And
and
and
that
means
you
need
something
like
the
proprietary
file
system
that
can
be
shared
between
everybody-
that
isn't
the
blockchain,
which
is
a
place
to
put
that
data?
That's
not
doesn't
just
just
doesn't
fit
the
blockchain
model,
you're
going
to
have
a
blockchain,
node
and
you're
going
to
work
out.
A
A
How
do
I
aggregate
signatures
from
a
whole
bunch
of
people
assemble
them
together
and
work
out
the
right
thing
to
do
to
be
able
to
submit
the
transaction
if
you're
you're
in
fabric
right,
so
you
could
build
that
thousand
lines
of
code
yourself
or
or
for
just
for
your
project,
or
you
could
use
something
robust
off
the
shelf
and
then
the
other
side.
It
gets
even
harder.
That
was
the
easy
bet
that
was
the
easy
bit,
because
you've
now
got
two
things
that
arrived
separately.
A
You've
got
to
aggregate
them
together
to
aggregate
them
together,
and
this
is
actually
one
of
the
most
important
roles
that
we
think
in
terms
of
real
engineering.
That
needs
to
be
in
a
coordination
system,
an
orchestrator.
This
is
actually
one
of
the
most
important
roles
of
the
project
like
firefly
can
take
on.
You
need
to
take
things
that
arrive
in
different
orders
and
assemble
them
together.
In
this
particular
case,
it's
actually
reasonably
straightforward
with
with
ipfs,
because
it's
going
to
come
across
the
blockchain
interface
you're,
going
to
detect
it
through
events
for
the
blockchain.
A
Oh
just
a
minute:
blockchains,
don't
have
a
nice
interface
for
for
event.
Listening
in
most
most
cases,
that's
like
super
easy
for
your
web
application,
rather
than
typescript.
So
you're
probably
going
to
need
a
blockchain
interface
here
as
well,
so
again
firefly's
trying
to
import
those,
and
we
have
the
production
production
ready,
one
fair
for
for
for
ethereum
and
working
on
the
other
two
there
as
well
so
you're
going
to
detect
that
it
happened
on
the
blockchain
and
then
you
can
go
and
fish
for
that
data.
Inside
of
ipfs,
you
can
aggregate
those
together.
A
A
It
isn't
all
of
your
logic,
that's
off-chain,
but
you
wouldn't
have
an
application.
If
there
wasn't
logic
off-chain
right,
even
even
cryptokitties
has
off-chain
capabilities.
It's
it's
just
the
truth.
There
is
off-chain
applications
and
this
thing
has
to
have
a
great
user
experience.
It's
got
an
update.
It's
going
to
be
suitable
for
business
users,
it's
going
to
do
integration
and
a
business
api
layer
with
a
with
you
know
a
message:
bus,
that's
integrating!
A
You
know
as
an
asb
to
your
core,
your
core
insurance
system,
your
core
health
care
system,
right
that
this
off-chain
stuff
is
not
trivial.
It's
really
important,
so
you
need
to
have
the
right.
The
right
triggers
coming
out
of
the
system
into
you,
so
you
can
do
something
you
can
do
something
and
in
in
this
case,
what
we're
doing
is
we're
just
saying
in
our
application.
What
okay?
A
A
Well,
that's
a
private
exchange
with
just
one
organization
to
another
organization,
but
if
I
want
it
to
be
audited
that
I
did
it
at
a
certain
period
of
time,
maybe
there's
a
race,
maybe
there's
a
waste,
and
I
have
to
do
it
before
somebody
else.
Maybe
only
one
person
in
the
system
can
do
this.
Lots
of
data
matching
scenarios
have
that
kind
of
waste
involved.
A
I
need
it
to
be
pinned
to
the
blockchain.
So
there's
no
ambiguity
over
the
fact
it
came
from
me.
It
happened
in
a
certain
order,
there's
a
global
order
with
everybody
in
the
system,
even
though
the
only
people
who
have
any
ability
and
in
future
sessions
we'll
talk
about
all
of
the
stuff.
We've
done
to
mean
that,
like
the
blockchain
transactions,
are
completely
obfuscated,
there's
not
even
a
link
between
like
transaction
one,
two
and
three
on
the
same
topic:
don't
even
have
a
a
link
between
them.
A
So
there's
some
great
stuff
that
would
love
to
talk
in
detail
there,
but
wait
fundamentally.
This
is
private
exchange.
You're
pinning
it
to
the
blockchain,
whatever
happens
on
the
blockchain,
even
if
it's
more
sophisticated
logic
like
there's
some
kind
of
coordinated
transfer
of
an
asset,
that's
happening
inside
of
that
generation,
one
we
have
that
built
in
that's
evolving
for
generation,
two
you're
coordinating
those
together,
you
don't
want
it
to
be
visible
while
you're
doing
it,
you
may
not
be
willing
to
vote
to
be
visible
who's
involved,
and
you
need
to
send
the
data
somehow.
A
A
Multi-Party
systems
will
will
know
for
sure
that
this
thing
exists
right
it
just
it
just
is
there
it's
in
in
almost
all
of
them
that
there's
some
way
to
transfer
data
peer-to-peer
between
the
organizations
so
that
that's
then
more
challenging
on
the
data
aggregation
side
because
it
comes
into
whatever
that
technology
is.
That's
your
you
know
your
active
mqr,
artemis
or
or
whatever
it
is
that
you're
that
you're
you're
using
rabbit
or
whatever
and
probably
you've
got
a
layer
of
end-to-end
encryption.
That's
happening
on
side
of
that.
A
That's
certainly
what
in
collido
we
did.
Kafka
is
the
technology
that
we
chose
to
use
inside
the
collider
for
enterprise
projects,
which
is
which
is
just
we
love
it
as
a
technology.
So,
but,
but
you
know,
you've
got
this.
This
run
time
right,
you're,
gonna,
you're
gonna
be
be
working
with
that,
whether
it's
centralized
or
decentralized
whatever
it
is
you've
built
it
you've
got
that
there
and
you're
also
gonna
have
your
blockchain
node,
but
these
work
in
very
different
ways.
A
Messages
are
going
to
be
batched
and
transmitted
and
arrived
in
completely
different
order
to
the
blockchain
node.
You
just
cannot
rely
on
those
things
happening
in
the
same
order
and
still
have
global
ordering
in
the
system.
So
one
has
to
be
king
and
here's
the
magic.
That's.
What
blockchain
can
do
that?
No
technology
in
the
whole
of
my
career
in
messaging
and
integration
has
ever
been
able
to
do
it's
gold
dust.
The
blockchain
can
do
this,
there's
one
sequence:
I
guess
it's
in
the
name
block
chain
right.
It's
a
chain
of
events.
A
It
sounds
trivial,
but
it's
magical,
absolutely
magical.
We
can
all
agree
on
one
order
of
events,
but
because
that
order
of
events
isn't
the
same
order
that
the
data
are
arrived,
you
need
aggregations,
you're
going
to
work
out.
Well,
how
do
I
aggregate
these
together?
It's
something-
and
this
is
the
really
hard
bit
that
we've
put
a.
A
A
B
A
I
didn't
receive
that
data.
Well,
actually,
the
way
a
system
should
work
the
way
systems
work
outside
of
the
body
party
system.
Blockchain
space
is
you
have
like
an
ordering
context,
a
topic,
and
things
on
that
topic
are
blocked,
but
things
on
other
topics
aren't
blocked
now
doing
that,
while
preserving
privacy
and
not
leaking
the
same
identifier
into
all
the
transactions
that
are
on
the
same
topic
we're
doing
batching,
because
batching
is
an
inevitability
with
these
technologies
you
have
to
batch.
Otherwise
you
can't
get
throughput.
A
You
need,
that's
suddenly
a
really
hard
problem,
we've
seen
it
implemented,
we've
implemented
it
many
times
over,
and
it's
just
not
valuable
for
for
the
world
of
of
these
systems
to
be
implementing
such
heavy
lifting
complex
stuff
over
and
over
and
over
again.
So
we
hope
firefly
is
going
to
be
a
place.
We
can
come
together
and
get
that
right
and
take
it
away
from
the
poor
developers
who
are
trying
to
meet
project
deadlines
and
solve
like
I
just
want
to
exchange
data,
so
then
we're
now
going
to
look
at
them.
A
A
I
just
want
to
send
the
the
data,
but
here's
the
thing
I
probably
want
to
send
multiple
pieces
together,
I'm
multiple
steps
into
my
business
process.
I've
got
10
documents
that
have
been
signed
along
the
way
as
part
of
this
proposal
by
different
people.
Some
of
them
came
from
me.
Some
of
them
came
from
other
people
in
the
system.
Some
of
them
were
broadcast.
Some
of
them
were
private.
I
need
to
assemble
them
together.
A
I
want
to
send
not
one
packet
of
data.
I
want
to
send
a
package
from
me
to
you
and
that
package
is
not
just
going
to
involve
tiny
bits
of
data.
It's
going
to
involve
documents
so,
and
this
isn't
unique
to
blockchain
for
sure,
but
you've
got
this
problem
in
this
multi-party
system,
where
you
don't
just
want
to
send
one
thing:
you
want
to
send
multiple
things,
and
some
of
them
are
big
and
some
of
them
are
small.
Some
of
them
are
blobs.
Some
of
them
are
structured
data
with
schema.
A
Some
of
them
are
agreed
canonical
data
formats.
Surely
that
should
be
simple,
as
a
developer
well
turns
out.
Do
it
from
base
principles?
It's
not
simple.
At
all,
you've
got
completely
different
transfer
technologies
that
work
in
completely
different
ways.
They
arrive
in
completely
different
orders
like
if
you've
got
a
rabbit,
enqueue
message
on
its
own.
That's
going
to
arrive
straight
away
like
that.
A
A
A
The
fact
that
you
won't
find
in
firefly
super
complicated,
smart
contracts
is
not
a
sign
that
those
aren't
incredibly
important.
They
don't
fit
the
model.
It's
just
that.
That's
the
innovation
that
we're
embracing
happening
all
over
the
place
in
the
blockchain
technology,
but
those
communities
that
are
building
you
know
erc20,
my
goodness,
the
years
that
it's
taken
the
trial
by
five
and
it's
taken
to
get
that
right,
fantastic.
A
It
fits
the
model,
bring
it
on
board.
We're
not
trying
to
reinvent
that
wheel.
Firefly
isn't
trying
to
reinvent
that
wheel,
but
it
is
trying
to
say
as
a
developer,
writing
a
web
application
full
stack
with
a
back
end
in
typescript
with
no
js.
I've
spent
my
whole
of
my
10k
career,
getting
fantastic
at
building
enterprise
software.
I've
been
through
the
microservices
revolution.
I've
been
through
java
spring
boot,
and
I'm
here
I
want
to
use
blockchain.
I
know
how
to
use
the
database.
A
Surely,
in
a
day
I
can
do
what
I
need
to
in
blockchain.
That
needs
to
be
true.
That
needs
to
be
true,
and
we
really
hope
and
through
the
lab
today,
you'll
sort
of
feel
it
a
little
bit
that
fireflies
there
to
make
that
true
for
you
and
the
architectural
heavy
lifting
that
we're
doing,
which
is
in
the
coordination
layer.
A
The
orchestration
layer
between
the
on
chain
and
the
off
chain
embraces
non-deterministic
logic
embraces
manual
business
processes
embraces
how
hard
it
is
to
agree
data
formats
and
schemas
between
a
whole
bunch
of
people
that
the
hours
of
meetings
we've
been
in
like
just
talking
about.
Are
we
going
to
ask?
Are
we
going
to
spell
address
in
our
canonical
format,
with
address
line,
one
two
and
three
or
with
address
as
one
line
and
everyone's
gonna
like
that
stuff?
That's
important.
We
need
to
spend
the
time
there.
A
A
A
A
Mqtt
based
technologies
can
plug
in
and
also
like
core
enterprise
messaging
mqp-based
technologies
can
can
plug
in
this
is
I've
got
10
different
ways
to
write
logic,
zero
knowledge
proof
logic
can
plug
in
here
off
chain
secured
provable
compute
with
trusted
compute
frameworks
like
sgx
et
cetera
they
can,
they
can
plug
in
here
and
great
communities.
We're
really
good
close
links
with
a
community
called
node-red
which
is
about
how
do
you
build
fast,
really
really
prove
our
event-driven
programming
models
with
an
event-driven
graphical
interface,
low
code
building
of
code
right?
A
That
kind
of
approach
can
now
plug
into
blockchain.
Almost
every
other
industry
is
talking
about
or
technology
sensors.
Talking
about
you
know,
process,
automation,
automated
process,
information
and
flow
right
and
simple
flow,
and
somehow,
as
of
yet
in
the
multiparty
system,
blockchain
space,
we've
not
made
it
easy
enough
for
flow
engines
to
just
be
able
to
plug
in
on
top
of
something.
B
A
A
Is
this
a
community
that
I
sort
of
agree
with?
Is
this
a
community
that,
like
matches,
how
I
feel
about
how
things
should
be
fitted
together
and
and
that
evolves
that
culture
evolves
with
the
community?
But
it's
important,
I
think,
if
anyone
is
seeding,
a
community
to
share
like
what's
their
mindset
when
they're
coming
they're
coming
in,
as
we
start
this
community
building
process.
So
I
want
to
talk
a
little
bit
about
about
this,
so
we
care
passionately
passionately
about
blockchain
and
other
multi-party
system
tech.
A
We
care
passionately
about
it.
We
don't
dismiss
it.
It's
not
just
a
timestamping
service.
We
care
passionately
about
it
and-
and
we
agree
that
in
any
real
world
system
that
making
the
ability
to
consume
that
logic,
easy
for
none
blockchain
engineers
through
rest,
apis
built-in
patterns
built-in
operations
for
common
enterprise
patterns.
A
That's
the
way
that
you
get
success
is
not
by
not
caring
about
the
inside
of
the
engine
block
that
you
care
so
passionately
about,
but
by
understanding
that
not
everybody
when
they
consume
this
thing
is
going
to
open
up
the
engine
block.
I
don't
open
up
postgres
when
I
use
it,
I
use
postgres
all
the
time.
I
don't
open.
A
A
That's
core
dna
process
orchestration
we
really
trying
in
this
project,
because
we've
done
it
with
real
world
projects
that
we're
working
with
directly
in
seeding.
This
we're
saying:
yes,
there's
a
lot
of
traction
in
just
you
know:
sdo
projects
in
blockchain
and
other
core
projects,
whether
where
there's
really
proven
on-chain
logic,
that
even
in
those
projects
in
an
enterprise
contract
context
and
in
all
the.
A
A
We
need
to
bridge
these
worlds
together,
so
you
it
really
matters
having
an
event-driven
of
an
event-driven
programming
model
that
works
for
these
other
scenarios,
but
not
at
the
cost
of
losing
things
like
digital
assets,
tokens
and
nfts
building
into
the
model,
and
actually
one
of
the
reasons
why
that
isn't
right
there
today
in
generation
two,
even
though
there
was
a
version
of
it
in
generation,
one
is
we,
we
feel
it's
really
important
to
get
this
one
right,
and
that
means
more
discussion.
So
there's
there's
a
there's
a
jump
into
this
community.
A
Like
I
said
jim
zhang's,
leading
it,
we
we
care
really
deeply
about
this
one
coming
right.
The
fact
is
not
there
today
is
not
reflection
that
we
don't
care
about.
It's
actually
how
much
we
care
about
that
one
and
then
the
last
pillar
is
to
say,
identity
really
matters,
but
here's
a
really
interesting
thing
about
the
enterprise
use
case.
B
A
That
matter,
in
any
enterprise
use
case,
there's
the
identity,
that's
visible
in
transactions
between
organizations
that
organizational
identity.
This
organization
signed
off
on
this.
This
organization
approves
this
because
this
other
organization
signed
off
on
that
it's
one
type
of
identity,
there's
also
another
type
of
identity
that
is
here
is
inside
of
my
organization.
My
three
hundred
thousand
employees-
they
come,
they
go,
they
onboard
they
off-board.
We've
built
the
processes
for
those
we've
built
the
identity
and
access
management
systems,
the
active
directory
or
whatever,
we've
we've
built
that
it's
not
changing.
A
Just
because
we're
doing
a
blockchain
project,
the
mapping
of
human
beings
in
an
enterprise
context
down
to
one
chain.
Identity
is
not
a
one-to-one
thing,
so
that's
something
that
we
care
about
in
in
the
project
and
you'll
see
the
start
of
a
plug-in
for
that
and
some
great
stuff
in
the
in
the
sort
of
the
architecture
side.
That's
starting
to
think
about
it
and
that's
something
where
we've
already
started.
Some
great
engagement.
B
A
With
with
the
community,
that's
that's
forming
here
to
try
and
work
out
what
identity
means
in
this
in
this.
In
this
context,
so
two
more
things
in
the
last
couple
of
minutes
here
I
want
to
say-
and
I
promise
then
you're
stopping
to
listen
to
me
and
you'll
get
your
hands
on
some
tech,
as
gabe
was
going
to
take
you
through.
I
wanted
just
to
cover
two
more
things.
Really
briefly.
The
one
is
where
the
heck
do.
I
find
the
code
right
brilliant.
A
You
showed
me
where
the
samples
are
where's,
the
actual
code.
Well,
it's
in
hyperledger.
Currently,
the
stage
we're
in
the
process
is
labs
and
there
are
a
set
of
repositories:
they're
all
prefixed
with
firefly.
So
if
you
start
at
hyperledger,
labs,
firefly
you'll
find
the
first,
and
if
you
have
a
look
at
it,
you'll
find
a
little
bit
of
an
introduction
to
what
it
is,
what
it
cares
about
why
it's
around,
and
this
is
actually
the
container
of
the
core
code
about
35
000
lines
ago.
That's
that's
in
this
core
repository.
A
A
The
command
line
interface
that
is
so
important,
you'll,
be
using
it
later.
That
means
that
anybody
blockchain
or
not,
can
start
programming
against
firefly.
In
a
couple
of
minutes,
the
ui
explorer,
which
you
know
we
put
a
lot
of
effort
into
hats
off
to
to
alex
and
brian
and
the
team
who've,
been
seeding
this
to
to
really
make
it
so
that
on
day,
one
humans
can
use
this
thing.
A
Human
developers
who
haven't
been
in
blockchain
the
whole
time,
don't
think
in
hashes
can
can
use
this
thing
and
a
bootstrap
for
for
operational
stuff
as
well.
A
data
exchange
out
of
the
box,
which
gabrielle
led
the
engineering
on
which
performs
mutual
tls
based
transfer,
which
is
where
most
projects
have
have
started.
It's
where
tesla,
for
example,
are
used
for
off-chain
coordination.
A
But
this
is
all
very
much
about
plugability
as
well,
and
you
know,
we've
proven
the
model
with,
as
I
said,
with
kafka
and
end-to-end
encryption
messaging
in
the
past
and
then
connectors
for
the
blockchains.
That's
an
evolving
space.
Ifconnect
is
another
piece
of
really
tried
by
fire
engineering
that
we
contributed
from
the
collider
side
to
sieve
the
project,
as
that's
become
part
of
the
the
firefly
family
for
ethereum
corder.
A
There's
a
lot
of
work
that
we've
done.
That's
evolving
the
merge
the
moving
across
of
that
is
happening
at
the
moment.
So
if
you
go
to
the
repo
you'll
only
find
part
of
it
but
event
streaming,
encoder
is
something
that
we've
done
a
really
lot
of
work
about,
as
well
as
kind
of
building
building
a
an
ordered
stream
inside
of
quarter.
It's
not
it's
not
not
like
a
a
block
based
system
is,
is
like
core
that
you
get
out
of
the
boxing
encoder
with
the
utxo
model.
A
That
stuff
there
and
then
a
whole
load
of
detail
on
the
architecture,
including
the
sort
of
periodic
table
of
elements.
If
you
want
to
look
inside
of
the
code,
you'll
see
the
core
broken
down
a
little
bit
more
and
we've
assigned
all
of
them
a
two-letter
prefix.
It
gets
used
in
the
go
code
in
various
places
and
you'll
see
the
core
components.
The
network
map,
broadcast
manager,
the
private
messaging
manager,
the
data
manager,
the
event
manager
subscription
manager.
A
The
asset
manager
batch
manager
are
all
the
core
pieces
of
core,
but
then
the
really
important
stuff
right,
the
plugins,
the
blockchain
interface.
We
even
have
a
fake
blockchain
that
that's
implemented
inside
of
there
as
well,
but
ethereum
quarter.
Fabric
plugins
ipfs
is
the
first
plugin
for
the
public
storage
interface,
http
direct
mutual
tls
for
the
off
chain.
Interface,
identity.
Mapping
at
the
moment,
simple
mapping
of
whatever's
on
chain
identity
is
your
identity
identity.
A
You
know
the
etherium
address
or
the
quarter
certificate
name
or
the
fabric
certificate
name.
That
is
your
identity,
but
this
is
a
plug
point
for
great
things
like
dids,
etc.
This
one's
still
still
evolving,
but
external
authentication
oauth
integration.
For
that
part
of
the
authentication
which
is
mapping
two
keys,
the.
So
that's
like
the
stage
before
you
get
to
the
identity
interface,
a
database
plugin,
which
at
the
moment,
we've
done
sql
first.
Interestingly
enough,
the
last
generation
did
no
sql.
A
First,
we've
done
sql
first
talk
about
that
in
the
in
in
the
offline
and
then
the
eventing
interface,
where
we
started
with
websockets,
because
it's
so
great
for
developers
just
what
about
where
developers
live
nowadays.
So
we
started
there
there's
way
more
coming
coming
here
that
we've
already
got
in
the
works.
B
Peter
before
you
transition
that
there's
just
a
question
in
the
chat
here,
they
thought
maybe
there's
some
nuance
too.
So
I
wanted
to
to
raise
it
to
you.
Luis
said
you
showed
we
could
send
data
privately
off
chain
from
org
one
to
or
two
now
you
question:
doesn't
that
mix
with
fabric
multiple
channels
and
private
data.
A
Absolutely
great
question,
so
we
believe
from
experience
that
they're
complementary,
that
they're,
complementary
and
there's
actually
a
construct
inside
of
the
firefly
core
model
called
a
ledger
which
is
designed
and
intended
to
map
to
things
like.
What's
the
scope
of
who
validates
my
transactions,
that's
the
channel
model.
A
What
we've
seen
is
that
there
are
cases
where
you
have
data
that,
for
whatever
reason,
doesn't
actually
fit
a
blockchain
at
all.
Doesn't
matter
how
much
you
restrict
the
parties,
it
doesn't
fit
the
blockchain-
or
this
is
a
really
interesting
one.
There's
data
where
you
need
to
prove
and
have
proof
with
a.
B
A
Data,
so
the
channel
might
include
the
supplier
and
the
purchaser
and
an
auditor,
but
the
visibility
of
the
data
that
goes
between
the
supplier
and
the
purchaser
might
be
different
to
the
data
that
goes
between
the
supplier
and
the
auditor.
That
goes
between
the
auditor
and
the
purchaser,
but
they
might
all
want
to
see
the
same
events
in
the
same
order
on
the
same
channel
and-
and
you
just
got
a
practical
problem-
if
I
want
to
send
a
one
gigabyte
file,
am
I
going
to
send
that
through
a
channel
with
the
on
chain
data?
A
Probably
not
that's,
probably
going
to
be
an
off
chain
transfer?
Am
I
going
to
send
a
scan
of
somebody's
passport
on
a
blockchain?
Well,
maybe
I'm
going
to
be
thinking
the
benefit
of
blockchain.
Is
it's
immutable?
I'm
never
going
to
be
able
to
delete
this
thing.
Does
that
does
that
fit?
If
I
put
it
on
a
blockchain
where
I
have
to
delete
the
whole
blockchain?
If
I
want
to
delete
that
data,
maybe
it's
just
easier.
A
Maybe
it's
going
to
save
me
a
year
of
regulatory
pain,
to
not
put
it
on
the
blockchain
directly
and
into
connect
to
the
blockchain.
So
we
we
embrace
the
the
the
synergy
between
the
two,
the
sets
of
privacy
and
in
the
session
earlier
in
the
week.
Actually,
jim
went
through
the
different
versions
of
privacy
that
exists
and
it's
only
a
15-15
minute
segment,
and
then
we
do
an
intro
to
a
firefly
afterwards,
you
might
want
to
listen
back
to
that
because
they
fit
they
fit
together.
A
They're
great
lego,
bricks
that
you
can
use
to
build
your
enterprise
system
and
and
all
firefly's
trying
to
do
is
to
say
you
should
have
access
to
all
the
lego
bricks.
It's
not
trying
to
say
this
lego
works
better
than
that
regular
brick.
It's
just
saying,
there's
a
reason.
Why
there's
different
shaped
lego
bricks
and
when
you're
building
your
solution,
you
should
be
able
to
fit
them
together
in
the
way,
that's
actually
going
to
give
you
the
velocity
that
your
business
goals
need.
B
Yes,
and
actually,
while
you're
talking
peter,
that
we
had
a
second
question
come
in,
which
I
think
is
a
pretty
similar
vein
asking
about
support
for
tessera
and
other
potential
enterprise
layer.
Two
solutions
and
tessera,
of
course,
is
the
private
off
chain
mechanism
that
sort
of
comes
in
the
box
in
ethereum
and
quorum
and
besso.
A
Another
great
question
so
so
right
now
today,
generation
two
firefly
code
does
not
have
an
implementation
of
a
a
you
know:
a
core
integration
of
tesla.
However,
the
blockchain
plug-in
that
partners
with
it,
which
is
firefly
ethconnect,
has
direct
integration
with
with
the
tesla
and
eea
private
transaction
model
built.
B
A
A
Been
thinking
a
bit
about
and
I'm
looking
forward
to
that
conversation
in
one
of
the
upcoming
architecture
sessions
and
hopefully
that's
a
great
area
where
we
can
have
a
contribution,
because
that
that
is
a
you
know
in
the
in
the
framework.
I
actually
think
that's
a
pretty
easy
one
to
solve
pretty
easy
one
to
solve,
so
that
would
be
a
great
area
to
to
start
bridging.