►
From YouTube: FireFly Hands-on Workshop
Description
Peter Broadhurst, Co-Founder, Head of Engineering, Kaleido
Gabriel Indik, Software Engineer, Kaleido
Andrew Richardson, Software Engineer, Kaleido
Roll up your sleeves, pull FireFly down onto your laptop, and run your first transactions. See how simple building a decentralized application can be on a multi-party system.
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #HyperledgerGlobalForum2021 #Blockchain
A
So,
okay,
I'm
going
to
be
using
a
set
of
slides
way
to
get
started
with
firefly
is
using
its
command
line
interface,
one
can
spin
up
a
local
development
environment
in
seconds
and
immediately
start
building
an
application
against
it.
We'll
cover
the
command
line
interface
in
detail
during
the
workshop.
A
A
We
use
two
members
on
the
left.
We
have
member
zero
and
on
the
right
we
have
number
one
now,
since
we
are
going
to
be
doing
local
development,
we
are
going
to
have
remember
both
members
running
side
by
side.
On
the
same
laptop.
That
way
we
can
build
and
test
complete
end-to-end
floats
each
member
will
have
its
own
firefly
core
running,
and
also
each
of
these
firefly
cores
will
have
its
own
database.
A
A
A
A
When
running
firefly
locally,
the
command
line
interface
will
spin
up
a
number
of
docker
containers.
These
containers
will
have
each
of
these
items
that
we
just
listed
now,
specifically
for
the
case
of
the
blockchain.
What
we're
going
to
get
is
travel
ganache
for
the
blockchain
interface.
We
are
going
to
have
ifconnect.
A
A
C
D
Great
great
to
meet
everybody,
I
hope
everyone
can
see
my
screen.
Okay,
please
tell
me
if
it's
doing
anything
funny.
My
name
is
nick.
Okay,
super
thanks,
sophia
yeah!
My
name
is
nick
gaske.
I
was
involved
very
heavily
with
the
hyperledger
fabric
project
many
years
ago
and
really
excited
to
you
know:
work
with
the
broader
community
on
all
things,
firefly,
so
I'll
be
one
of
your
main
points
of
contact.
D
So
this
this
is
the
hands-on
workshop,
we're
gonna,
you
know,
actually
install
this
stuff
on
our
machines.
We're
gonna
run
some
code,
we're
going
to
look
at
those
core
interfaces
that
gabriel
just
talked
about
our
ethereum
shim,
the
public
storage
ipfs,
the
tls
secured
private
data
exchanges,
the
firefly
core
and
all
of
this
functionality.
That's
you
know,
encapsulated
and
abstracted
behind
a
really
simple
rest.
D
Api
will
show
you
some
some
running
user
interfaces
and
applications
and
you'll
get
a
sense
of
you
know
how
easy
this
is
to
use
and
how
extensible
and
how
powerful
it
is.
So
the
the
first
thing
I
want
to
draw
your
attention
to,
and
I
posted
this
in
the
chat,
but
I'm
going
to
post
it
one
more
time,
just
just
so
that
everybody
has
this
is.
D
Is
this
getting
started
on
firefly
cheat
sheet
that
we
have
right
here,
so
I'm
gonna
go
back
to
the
chat
and
just
make
sure
everyone
has
this
link
so
again,
I'd
like
everyone
to
please
visit
this
and
and
start
taking
a
look
at.
You
know
all
of
the
different
dependencies
that
we
need,
as
gabriel
mentioned,
the
the
first
thing
kind
of
the
the
beating
heart.
That's
going
to
make
your
life
easy
using
firefly-
and
you
know
interacting
with
with
these
different
interfaces,
is-
is
the
command
line
interface.
D
It's
a
powerful,
powerful
stack
of
functionality,
and
it
just
takes.
You
know
a
couple
commands
to
stand
up
a
full
firefly
stack
and
then
to
actually
you
know,
start
start
exercising
some
of
the
available
methods
and
commands
inside
of
firefly.
So
this
is
the
first
thing
that
we're
going
to
need.
Everyone
to
do
is
is
actually
follow
along
with
with
this
section
right
here,
the
the
references
and
dependencies
and
the
overall
firefly
cli
section.
D
D
The
other
thing
that
you
need,
which
I'd
have
to
imagine
you
know
99
of
folks,
have
is
docker
and
all
of
you
probably
have
go
as
well.
So
I'm
going
to
sort
of
drag
my
feet
for
for
a
couple
of
minutes,
and
you
know
let
let
any
folks
that
don't
have
this
installed
go
ahead
and
sort
of
start
doing
that
in
the
background
and
I'll
also
mention
you
know
as
as
we're
doing
this.
This
is
meant
to
be
as
interactive
as
possible,
so
you
know
often
times
you
know
things
go
wrong.
D
We're
trying
to
you,
know,
compile
and
build
stuff
locally.
There
may
be,
you
know,
just
ambiguity
in
your
own
point
of
view.
So
this
is
the
greatest
session
for
you
to
you
know,
raise
your
hand
speak
out
loud,
throw
any
questions
in
the
chat
if
you're
completely
lost
and
completely
broken,
or
you
know
you
really
would
rather
have
a
business
conversation
or
something.
Let
us
know
in
the
chat.
We
have
a
lot
of
folks
here
inside
of
the
room
and
that
are
you
know,
hands
on
deck.
D
You
know
with
collido
and
with
firefly
and
we're
more
than
happy
to
talk
to
you
and
sort
of
one-off
or
private
settings
or
to
answer
your
questions
inside
of
the
chat,
so
just
want
everyone
to
feel
as
as
comfortable
as
possible.
There
are
no
such
things
as
bad
questions
and
nascent
open
source
projects
or
in
technology
in
general.
So
don't
be
shy.
We're
friendly
we're
here
to
help
and-
and
we
really
would
love
to
get
to
know
everyone
and
interact
with
you
as
well.
D
So
as
as
you've,
you
know
sort
of
got
and
go
and
gotten
docker,
you
know
which
again
I
imagine
everyone
has
you're
gonna
either
you
know
call
one
of
these
go
commands
on
your
machine.
Go
grab
the
latest
cli
or
you
know.
If
you
don't
want
to
update
your
go,
you
can
go
grab
one
of
the
tagged
images,
one
of
the
pre
images
right
there.
D
Okay,
so
I'm
going
to
start
showing
you
guys
how
this
is
going
to
work
sort
of
in
in
real
time.
The
things
that
you're
going
to
be
able
to
do.
The
first
thing
we'll
do
is
is
we'll
actually
check
right,
we're
going
to
we're
going
to
check
and
make
sure
that
that
we
have
firefly
installed
this
this
command
right
here
the
go,
install
or
the
go
get.
This
should
have
only
taken
about
a
minute
on
your
machine
right
there.
D
So
I'm
assuming
that
you
know
all
the
folks
that
had
go
and
all
the
folks
that
had
docker
have
already,
you
know,
go
gone
ahead
and
you
know
issued
this
command.
And
hopefully
you
know
you
have
an
executable.
You
know
ff
command.
That's
available
on
your
machine.
If
you
have
that
you're
going
to
see
something
like
this
okay,
so
this
is
going
to
show
you
the
available
available
commands
and
the
available
flags
right
here.
D
What
we
really
care
about
is
is
just
kind
of
three
core
commands
in
inside
of
firefly.
We
care
about
this
init,
which
is
going
to
be
kind
of
a
high-level
wrapper
about
the
configuration
of
our
stack,
namely
we're
going
to
give
it
a
name
and
we're
going
to
give
it
the
number
of
members
that
we
want
inside
of
our
firefly
ecosystem.
D
D
So
what
we're
going
to
do
is
we're
going
to
stand
up
a
firefly
stack
with
three
members,
we'll
look
at
broadcast
transactions
where
everyone
gets
the
data
and
then
we'll
look
at
some
of
those
private
transactions
right
we're
instead
of
using
ipfs
we're
using
that
you
know,
tls
sort
of
peer-to-peer
protocol
right
there
to
you
know
directly,
send
messages
to
individually
enumerated
participants,
so
so
init
is
essentially
just
just.
The
config
of
your
stack
right
there
start
is,
is
kind
of
the
more
exciting
command.
D
B
D
It'll
also
start
up
those
corresponding
containers
as
well
and
provide
you
with
some
localhost
endpoints,
where
you
can
see.
You
know
a
user
interface
for
convenient
interaction
and
inspection,
as
well
as
an
embedded
swagger
api.
So
you
can
sort
of
you
know,
take
a
step
backwards
and
get
closer
to
how
you're
really
going
to
interact
with
firefly,
which
of
course
is
programmatically,
and
then
the
last
one
that
we
see
here
is
stop.
D
So
this
will
just
stop
the
containers
and
if
you
want
to
start
from
scratch,
you
can
use
firefly
remove
so
so
those
are.
Those
are
kind
of
gonna,
be
your
babies
right
here
for
for
step,
one
that
you
know,
you'll
get
you'll
get
very
familiar
with
in
the
shorthand,
so
I'm
gonna
pause
there.
I'm
just
gonna
check
the
chat
intermittently
and
make
sure
there's
you
know
not
not
too
many
questions
going
on
here.
D
I
see
nico's
doing
a
great
job,
helping
folks
with
you
know,
sort
of
if
you're
running
on
windows
or
you
need
to
stand
up
a
vm
or
you're
running
on
linux.
So
thanks
for
that
nico,
and
then
you
know
you
you
have
peter
and
andrew
and
all
of
our
subject
matter.
Expertise,
expert
expertise,
so
it
looks
like
chat
is,
is
the
greatest
way
to
put
your
questions
in
okay,
so
without
further
ado,
let's
go
ahead
and
stand
some
of
this
stuff
up
so
feel
free
to
participate.
D
D
D
D
Okay,
yeah-
I'm
apologies
to
folks
if
this
is
still
small,
throw
it
in
the
chat
and
peter
or
someone
will
yell
at
me
and
we'll
make
it
even
bigger
okay.
So
I'm
again,
this
is
just
the
wrapper
for,
for
my
firefly
stack,
this
is
the
config.
I
gave
it
a
name
of
data
transfer
and
we're
going
to
do
three
members
right
here.
So
cool
we're
happy.
D
We
can
see
the
the
compose
file
right
there
telling
me
where
it
is,
and
now
it's
telling
me
that
if
I
want
to
start
this
stack,
I
just
say:
ffstart
data
transfer.
So
again,
I'm
going
to
steal
some
more
room,
I'm
going
to
say
ffstart
data
transfer
now
remember
this.
This
is
going
to
take
some
time.
This
is
going
to
go
ahead
and
download
those
docker
images.
This
is
going
to
stand
up
your
local
ganache
interface.
This
is
going
to
instantiate
a
smart
contract.
D
It's
going
to
do
a
lot
of
things,
but
what
it's
doing
is
it's
giving
you
that
core
component
architecture,
it's
giving
you
all
the
goodies
that
are
inside
of
a
firefly
stack
and
inside
of
a
firefly
node,
so
we'll
be
able
to
see
you
know
approximately
how
long
this
takes
on
my
machine.
If
I
have
to
give
you
my
best
educated
guess,
I'd
say
about
a
minute
right
here,
but
this
cli,
which
was
written
by
nico
who's
on
the
chat.
D
D
And
again
I'll
reiterate
it
probably
10
or
20
times,
but
you
know
just
please,
please,
please,
please
don't
hesitate
to
you
know,
throw
any
questions.
Inside
of
this
chat,
you
can
feel
free
to
use
our
rocket
chat,
we're
just
at
firefly
dash
labs
on
rocket
chat,
we're
doing
a
better
job
of
it
as
a
team
of
of
getting.
You
know
very
interactive
on
that
and
putting
all
of
the
discourse
about
the
firefly
project,
about
any
errors
that
we
see
internally,
any
developmental
progress.
All
of
that's
going
to
reside.
D
You
know
fully
transparently
inside
of
the
rocket
chat
inside
of
firefly
labs,
so
love
for
you
know
anyone
and
everyone
to
to.
Please
join
that
and
you
know
interact
with
us
through
that
medium.
It's
it's
a
it's
a
little
bit
of
a
blast
class
from
the
past.
For
me,
I
spent
a
ton
of
time
on
there
using
interacting
with
with
sort
of
the
the
fabric
folks.
So,
oh
maybe
I
need
to
close.
D
So
what
we
should
see
if,
if
this
comes
up
properly,
is
it
should
expose
us?
You
know
all
of
the
localhost
endpoints
where,
where
we
can
get
to
that
user
interface
and
and
again
you
know
this,
we
we
would
love
for
this
to
be
perfect.
This
is
a
live
demo.
I'm
shameless
about
doing
live
demos,
and
you
know,
as
every
developer
knows,
you
know
there.
It
probably
makes
you
better
to
see
an
error
or
two
as
as
you're
doing
a
live
demo.
D
So
you
know
this
maybe
not
go
100,
but
you
know
we
will
do
this
in
real
time
with
you,
and
this
will
be
sort
of
a
sort
of
a
symbiotic
relationship
as
we're
looking
at.
You
know
all
of
the
different
permutations
and
all
the
different
edge
cases
that
could
occur.
So
we
see
you
know
a
little
bit
of
sort
of
possibility
for
an
error
if
you,
if
you
do
see
that
as
as
you're
starting
up
a
stack,
you
can
always
just
do
ff
stop.
D
You
know
stack
name
ffstart
or
you
can
take
the
approach
that
I
just
did
just
just
say,
ffstart
again
with
your
stack
name.
If
you
have
those
images,
if
you
have
those
containers-
and
you
know
all
of
them-
are
running
you're
going
to
get
success,
it
may
be
the
case
that
perhaps
you
know
maybe
one
container
started
and
it
exited
right
and
that's
not
going
to
serve
you
know.
All
of
these
end
points.
E
Right
before
I
think,
nick
as
you
hit
the
house,
I
think
you
actually
hit
an
issue
which
was
fixed
a
retry
loop
that
got
popped
in
this
morning.
So
hopefully
the
latest
release
won't
won't
hit
that
issue
just
for
the
background
to
chat
while
people
are
are
all
typing
on
their
machines
here.
What's
sort
of
happening
under
the
covers
here
is
we've
we've
embedded
docker
compose
inside
of
a
command
line
and
then
in
the
cli
nico
led
the
development
of
this
who's.
E
E
That's
that's
backing
the
private
data
exchange
of
a
simple
example,
but
kind
of
like
that
foundational
piece
that
needs
to
be
to
be
installed
so
that
all
happened
and
on
next
environment
and
it
all
stood
back
up
again
and
then
it
has
to
restart
the
the
the
firefighter
runtimes
so
that
they'll
register
their
event
streams
using
youth
connect.
That
will
then
listen
all
this
happens
under
the
covers
who
are
reliably
for
for
events
and
then
the
final
stage
is
the
network
map.
The
each
of
those
nodes
has
come
up.
E
It
hasn't
really
joined
the
network,
yet
it
actually
needs
to
advertise
itself
to
the
rest
of
the
network,
and
actually
the
area
you
saw
on
the
screen
was
that
the
cli
was
trying
to
do
that.
While
one
of
the
one
of
the
fireflies
was
still
coming
up
and
then
it
got
a
oh,
this
firefly
isn't
actually
running
when
you're
trying
to
do
it.
E
D
No,
no
no
problem
and
I'm
gonna
actually
restart
it
so
that
we
can
ensure
that
all
three
members
are
successfully
joined
to
the
network
in
the
member
map.
So
what
we
want
to
see
inside
of
the
ui
is
we
actually
want
to
see
three
network
members
inside
of
here,
so
I'm
going
to
go
ahead
and
restart
this
stack
right
here
and
hopefully
we'll
get
we'll
get
a.
F
E
I
think
just
ff
we're
moving
or,
as
as
andrew
said,
you
could
just
go
to
the
if
you
just
go
to
the
the
swagger.
Let's,
let's
do
this
next,
let's
keep
people
entertained
with
a
little
bit
of
a
dance
here.
So
if
you
go
to
5001
slash
api-
and
this
is
the
oh-
if
I
found
oh
you've
just
stopped-
I
stopped
it.
E
And
this
is
good.
This
is
the
sort
of
you
know,
the
the
the
the
the
command
line's
there
to
give
you
an
environment
that
you
can.
You
can
kick
the
tires
with,
so
this
is
nice
to
like
do
a
little
bit
of
thai
kicking
life,
so
the
unless
I
mean
I'll,
probably
waffle
on
a
little
bit
about
the
api.
Well
yeah.
E
E
You
don't
need
to
actually
perform
all
of
those,
but
the
ui
is
able
to
show
you
transactions
events,
data
operations,
all
of
the
all
of
the
model,
so
if
you've
got
5001
api
up
next,
if
you
scroll
down
to
network
the
slash
network
prefix
down
in
name
spaces
mode,
there
we
go
network
right
at
the
bottom
there.
So
so
you've
got
underneath
network.
There
are
nodes
and
there
are
organizations
and
you're
running
a
node
and
and
nodes
are
owned
by
organizations
which
is
just
a
fundamental
identity
in
the
system.
E
So,
in
order
to
kind
of
exist
to
everybody
else,
you
have
to
advertise
yourself
to
everybody
else.
Well,
what's
an
advertisement?
Well,
it's
just
a
broadcast.
So
the
the
system
eats
its
own,
eats
its
own
dog
food
here
and
uses
the
broadcast
mechanism
in
order
to
distribute
the
the
the
the
information
to
everybody.
E
So
if
you
click
on
well
on
the
second
node
that
failed,
if
you
click
on
register,
slash
node,
slash
organization,
the
the
post
next
and
you
click,
try
it
on
there
and
you
click
send
what
this
is
a
convenience
to
say:
look,
you
know
who
you
are
just
broadcast
yourself
to
the
network
and
that
payload
there
that's
a
message.
It's
the
same,
payload
that
you
get
back
if
you
were
to
send
a
message
that
was
like
an
application
level
message.
E
We
we
thought
it
was
really
important
to
think
about
multi-tenancy
from
day
day
zero,
because
most
of
these
business
networks
are
thinking
about
like
an
app
store
of
lots
of
different
applications,
so
being
able
to
have
lots
of
different
applications
on
the
system
from
day.
One
was
important:
it's
a
firefly
system,
name
space.
So
this
particular
message
is
a
broadcast
message
that
happened
on
the
firefly
system.
E
Message
to
say
system
name,
says
to
say:
hey,
look,
there's
an
organization
and,
and
then,
if
you
go
to
a
query
on
organizations
you
do
the
get
there
neck
on
slash
network
organizations
just
do
try
it
send
scroll
past
all
of
the
filtering
options.
You'd
expect
on
the
nice
rest
api,
and
we
should
see
that
oh
there
we
go,
there
must
have
been
something
else.
That's
that's
wide
in
your
organization,
but
this
is
the
this
is.
This
is
where
you'd
see
an
organization
that's
propagated
through
the
networks.
E
If
you
look
on
your
environments,
where
the
cli
run
all
the
way
through
completion,
it
looks
like
it
may
not
have
configured
some
of
the
the
connectivity
here,
the
the
you
should
see
an
organization
for
each
member
and
if
you
were
to
click
into
the
ui
and
change
the
name
space
in
the
top
right
hand,
column
to
firefly
system
and
then
click
on
messages
and
click
on
the
timeline.
You'd
see
the
publishing
of
all
of
those
all
of
those
those
organizations
going
through
the
system
as
broadcast.
D
All
right,
I'm
going
to
start
over
one
more
time
we
tried.
I
tried
this
before
we
got
in
the
workshop,
so
I
know
it
works,
so
I'm
just
going
to
start
from
scratch.
I
imagine
there's
other
people
out
there
still
trying
to
perform
a
download
if
I
fail
in
this
session,
we'll
we'll
just
turn
it
over
to
andrew
or
nico
for
for
the
last
20
minutes.
D
But
again,
we've
we've
seen
this
we've
seen
this
working
successfully
and
maybe
that
I
I
fat,
fingered,
something
or
or
you
know,
had
a
had
a
you
know,
predated
image
or
or
release.
So
we'll
try
this
one
more
time
on
my
machine.
If
I
have
bad
luck
today,
we'll
just
use
one
of
the
other
collido
and
firefly
engineers
to
take
you
guys,
sort
of
to
the
finish
line
here,
so
I'll
go
ahead
and
remove
that
stack.
D
Yes,
I
do
want
to
remove
it
and
we'll
go
ahead
and
start
from
scratch
where
everyone
else
likely
is
so,
let's
say,
ff
init,
we'll
call
it
knit
test
this
time
for
good
luck
so
and
we'll
say
3
for
the
number
of
members.
This
is
also
a
shorthand.
You
can
do
rather
than
you
know,
using
the
interactive
terminal
right
there
so
and
then
we'll.
E
Share
my
screen
here,
so
this
was
one
where
I
just
ran.
It
was
a
two-member
environment,
but
I
ran
just
immediately
before
we
started
this
morning
and
I've
got
the
little
sample
running.
But
what
I
was
talking
about
there
is,
if
the
top
right
hand
corner
here,
you
you
change
from
the
defaults
namespace
and
you
can
create
namespaces
yourself
as
as
well,
and
you
just
changed
to
the
firefly
system
namespace-
and
this
is
my
favorite
view
in
the
ui
here.
E
This
is
a
view
of
messages
in
a
timeline
and
the
thing
on
the
left.
This
is
your
organization.
This
is
stuff
that
you've
published
to
the
network
with
the
organization
of
the
node
that
you're
that
you're
in
and
then
this
is
stuff
in
this
is
all
in
in
reverse
timeline
order.
The
newest
at
the
top.
That's
come
in
from
other
people
in
the
network,
so
I'm
there
as
port
5000,
that's
as
node
the
first
node.
E
I
can
see
that
I
broadcast
the
definition
of
a
an
organization
to
the
to
the
network.
It
had
a
blockchain
identity,
it
gets
allocated
a
uuid
within
the
firefly
system
and
it
has
a
short
name
which
is
required
to
be
unique.
But
there's
a
few
few
cases
where
we
found
it
really
is
important
for
these
networks
to
do
some
things
and
choose
to
have
some
things
and
having
it.
Just
a
unique
name
for
orgs
is
something
that's
been
really
really
popular
in
the
in
the
networks
that
we've
seen
evolving.
E
E
This
is
the
api
where
you
can
ask
me
who
I
am
and
get
data
from
me
that
you
can
broadcast
to
everyone
else
in
the
network
so
that
they
can
connect
so
on
this
node
one.
When
the
firefly
core
asked
on
the
data
exchange,
the
the
the
the
mutual
tls
data
exchange
came
back
and
said,
based
on
the
certificates,
I've
looked
inside
of
them.
The
organization
name
inside
of
my
certificate
is
member
zero.
E
My
certificates,
because
we're
just
using
a
completely
peer-to-peer
system
here,
there's
actually
lots
of
options
inside
of
the
the
mutual
tls
data
exchange,
but
at
the
moment
we're
just
using
deliberately
self-signed,
because
it's
a
great
map
for
the
way
you
know
a
decentralized
network
would
be
managed
with
identity.
That.
E
E
And-
and
this
gives
this
little
piece
of
data
firefly
core-
knows
nothing
about
this
scheme
so
like
if
you,
if
you
wanted
to
build
the
nqp
one
like
this,
could
be
a
whole
bunch
of
mqp
endpoints
addresses
that
this
is
completely
pluggable.
What
this
broadcast
information
is,
but
the
way
that
the
broadcast
works
is
really
important,
because
this
is
being
broadcast
to
the
system
via
ipfs
and
it's
being
broadcast
with
the
blockchain
signature
identity
of
the
owner.
E
All
of
that
stuff
is
is,
is
you
know,
baked
into
the
firefly
core
stack,
but
with
the
plugability
that
actually
that
blockchain
can
be
any
blockchain?
You
like
the
mapping,
and
this
is
a
really
important
one-
the
mapping
between
an
on-chain
identity
and
something
like
a
did.
That's
a
pluggable
interface.
E
The
only
plug-in
implementation
of
that
one
right
now.
Is
there
the
same,
so
the
identity
that
you
see
in
the
message
is
the
blockchain
ethereum
address
in
this
particular
case.
But
that's
a
you
know,
that's
a
really
important
thing
in
these
enterprise
systems
of
how
do
I
know
that
the
signature
on
chain
maps
to
a
real
identity
off-chain,
because
because
identity
is
not
a
like,
I
I
identity
is
not
an
address.
Identity
is,
is
a
you
know.
Something
bigger
like
me,
as
an
identity
is
different
to
my
name
peter
right.
That's
that's!
E
While
I
was
doing
private
messaging-
and
I
can
see
the
I
can
see
the
the
events
as
they
they
came
in
on
on
on
on
this
note,
with
the
with
the
difference
of
which
ones
were
private
and
which
ones
were
were
public,
and
I
can
see
that
same
that
same
data-
that's
that's,
that's
that's
described
that
was
published
by
the
other
endpoint
now
I
do
want
to
just
talk
really
briefly.
Some
of
you
might
have
noticed
something
which
I'll
talk
to
alex
about
offline.
E
So
that's
the
reason
why
you
saw
that
it
wasn't
that
the
system
didn't
manage
to
do
the
ordering.
That's
like
a
core
construct
of
the
of
the
system.
It's
just
simply
that
the
the
order
that
the
ui
is
suspending
them
is
not
the
deterministic
order
that
they're
delivered
to
your
applications,
I'll
pause
there
in
case
there
were
some
questions.
I
wanted
to
go
back
to
nick.
D
That's
that's
how
it
works,
but
in
in
any
event
you
know
it's
it's
you
know.
If
you
do
see,
you
know
little
little
periods
of
you
know
the
failure
for
all
of
the
orgs
to
register
you
know
take
down,
take
down
the
stack,
you
know,
restart
the
stack
and
and
you'll
be
good
right
there.
So
I've
I've
successfully
restarted
it
all
of
my
orgs
have
joined,
and
now
what
we
want
to
look
at
is
we
want
to
look
at
some
of
the
accompanying
program,
specifically
sort
of
a
you
know.
D
It's
kind
of
a
turnkey
just
one-click
cli
program
that'll,
do
a
public
broadcast
to
everyone
and
then
a
very
nice,
powerful,
react-based
user
interface,
which
will
let
you
experiment
with
private
messaging
right.
If
you
have
more
than
two
members
inside
of
the
system,
you
can
enumerate
which
members
you
want
to
send
those
messages
to
so
just
just
for
posterity,
let's
go
and
make
sure
that
all
of
these
are
looking
as
they
should.
So
we
originally
were
seeing
one
network
member,
because
you
know
it
failed
to
broadcast
and
failed
to
do
that
registry.
D
But
now
across
my
three
members,
we
see
that
there's.
You
know
everyone
has
that
that
peer-to-peer
communication
and
I
even
sent
a
test
transaction
in
the
background.
So
what
we're
going
to
do
now
is
we're
going
to
transition,
assuming
that
the
cli
is
built
for
hopefully
the
majority
of
the
audience.
That's
you
know
interactively
following
along.
D
It
has
the
private
data
transfer
cli,
which,
like
I
said
this
is
just
going
to
do
a
broadcast,
and
then
it
has
the
private
data
transfer
ui,
which
will
allow
you
inside
of
a
gui
to
actually
you
know
pick
the
organizations
pick.
The
members
that
you
want
to
you
know
privately,
send
you
know
sensitive
or
you
know,
concealed
data
to
inside
of
the
system.
D
So
the
first
thing
we'll
do
is
we'll
just
do
the
cli
and
we'll
send
a
basic
hello
world
message
and
when
we're,
while
we're
doing
that
I'll
show
you
one
interesting
thing
we
can.
We
can
actually
look
at.
You
know
some
of
the
lower
level
logs.
We
can
see
the
true
existence
of
these
ethereum
transactions
hitting
our
ganache,
and
you
know
we
can
see
some
of
those
json
rpc
methods
that
everyone's
familiar
with
and
we'll
be
able
to
see.
You
know
transaction
hashes
and
time
stamps
and
all
that
good
stuff
from
ethereum
transactions.
D
So
if
we
look
at
our
running
docker
containers,
what
we'll
notice
is
that
we
have
an
etherconnect
container
for
every
member
has
their
own
unique
connect
container.
So
when
I
kick
off
this,
you
know
this.
This
end-to-end
cli
program.
It's
it's
going
to
be
org
number
one
member,
a
this
container
right
here.
D
The
first
organization
inside
of
my
stack
they're,
going
to
be
broadcasting
that
mess
that
message
so
will
be
interesting
to
sort
of
you
know
see
the
logs
for
this
container
right
here,
see
the
broadcast
of
that
transaction
and
then
see
the
subsequent.
You
know
commit
of
that
transaction
into
their.
You
know,
ganache
ledger,
so
I'll
go
ahead
and
copy
this
container
right
here
we
can
open
up
the
logs
and
then
over
here
on
the
right
side.
We'll
just
kick
off
this
program,
and-
and
these
are
you
know
very,
very
lightweight,
very
again
lightweight.
D
I
don't
mean
that
you
know
sort
of
in
a
negative,
connotation
they're,
just
very
simple:
you
do
a
quick,
npm
install
and
then
the
programs
will
run
so
it
makes
your
life
really
easy.
So
we'll
take
a
look
at
the
logs
for
this
container
right
here
and
then
we'll
go
ahead
and
start
sending
some
transactions
into
the
network.
D
So
here's
the
logs
nothing
overly
exciting
right
now,
when
we
start
to
kick
off
this
program
right
here,
I'm
just
going
to
do
an
npm
run
start
from
the
root
of
this
private
data
transfer,
cli,
folder
and
we'll
see
the
broadcast
of
you
know
a
hello
world
message
inside
of
the
system,
and
we
start
seeing
you
know
all
of
those
familiar
ethereum
things
right.
We
start
seeing
you
know
the
the
you
know.
The
json
rpc
calls
right
estimating
gas
sending
the
transaction.
D
D
You
know
to
our
trust,
anchor
to
our
ledger-
that's
kind
of
sitting
in
the
beating
heart
as
a
connector
inside
of
the
firefly
core
right
there.
So
just
wanted
to
point
that
out
for
for
folks
to
to
see.
So
that's
that's
just
kind
of
the
out
of
the
box,
you
know
click
npm,
start
and
boom.
It's
going
to
send
some
transactions
into
your
network.
You
can
go
into
your
user
interface
and
you
can
see
those
transactions.
D
You
can
do
what
peter
did
right
there.
You
know
you
can
click
on.
You
know,
sort
of
the
messages
you
can
open
up
the
broadcast.
We
can
see
the
strings
that
came
through
because
this
was
public.
It
was
available
for
node
number
two
right
here.
We
can
see
the
data
hash
essentially
and
any
any
piece
of
metadata
or
any
piece
of
detail
that
that
makes
sense
for
your
business
process.
This
is
going
to
be
exposed
if
you're
privy
to
that
transaction.
D
D
A
inside
of
this
system
feel
free
to
use
your
own
nomenclature,
but
what
we
have
is
three
members,
each
of
whom
has
that
application
that
we
looked
at
over
here,
5000
5001
5002,
and
we
can
toggle
context
right
here
so
that
we
can,
you
know,
do
invocations
to
to
the
blockchain
right.
We
can
do
message
broadcast
to
the
system.
We
can
do
private
messages
inside
of
the
system.
So,
let's
just
look
at
you
know
a
broadcast
where
everyone's
going
to
get
this
message
right.
D
Welcome
to
the
firefly
workshop
right,
we'll
go
ahead
and
broadcast
this
into
the
system,
and
this
is
going
to
go
out
to
everyone
right,
we're
going
to
see
that
it
was
sent
from
myself
if
we
go
and
toggle
the
different
components
right
here,
the
different
members
we're
going
to
see
that
they
received
it.
They
received
it
from
my
address
right
there,
this
guy's
going
to
have
the
exact
same
string,
and
this
is
you
know,
a
very,
very
easy
public
message,
and
I
even
see
that
I
sent
this
to
the
rest
of
the
network.
D
Let's
drill
down
another
layer
now
and
talk
about,
what's
really
important,
though,
and
that's
privacy
in
the
scope
of
this
broader
ecosystem,
so
rather
than
broadcasting
to
the
whole
network
and
again
there
are
clean
apis
that
will
make
your
life.
Do
this
a
common,
simple
rest
api
that
you
know
is
not
reliant
on
a
user
interface.
This
is
emblematic
and
represent
representative
of
how
easy
it
is
to
program
against
the
firefly
apis
and
and
build
out
a
nice
powerful
ui
like
this,
that
that
andrew
and
team
you
know
worked
on
really
really
quickly
too.
D
I
shouldn't
you
know,
sort
of
toss
that
aside,
the
the
development
on
on
firefly,
you
know
is,
is
really
accelerated.
There's
there's
easy
interfaces,
easy
rest,
apis
and
easy
components
to
wrap
your
head
around
so
rather
than
broadcast
to
the
whole
network.
I'm
just
going
to
go
ahead
and
choose
you
know
a
single
recipient,
so
I'm
grayed
out
right
here,
because
I'm
the
sender,
I
don't
want
to
send
anything
to
myself.
I
already
know
that
information,
but
maybe
let's
send
it
to
org
number
one
and
their
address
right
here:
okay,
really
private
data.
D
Okay,
we'll
do
that
we
can
go
and
submit
this
to
the
system.
We
get
that
immediate,
asynchronous
response
right,
that
the
message
has
been
sent
that
it's
into
the
system
and-
and
we
see
that
we-
we
have
this
right
here
right-
we
can
see
that
it
was
it
was
submitted.
So
let's
go
ahead
and
now
switch
to
org
number
two
right
here
and
we
see
that
they've
received
that
message
right.
They
have.
They
have
line
of
sight
into
this,
really
private
data.
D
We
could
go
into
their
user
interface
over
here
and
we
see
that
as
well
that
it
was
a
private
transaction
but
it,
but
it
is
available
for
this
organization
right
they
were
privy
to
this.
Just
like
you
know
you
can
you
can
make
this
analogous
to
you
know
something
in
using
tessera
inside
of
inside
of
ethereum
right
using
that
private
for
parameter
and
just
enumerating
the
the
public
tester
address
of
who
you
want
to
get
that
private
transaction
and
who's
going
to
be
able
to
execute
it
or
make
sense
of
it
in
the
system.
D
And
if
we
go
back
here,
it
should
go
without
saying
that
if
we
go
to
org
number
three
member
c,
who
I
did
not
make
privy
to
this
transaction,
they
don't
have
any
line
of
sight
into
the
inputs
right,
they're
they're
not
going
to
be
able
to
make
sense
of
of
that
private
payload
they're.
Just
going
to
be
able
to
see
that
you
know.
Maybe
something
came
out
into
the
system.
D
So
so
that's
that's
the
ui
and
the
cli
that
you
get
out
of
the
box
in
the
fabric
samples
repository
as
you
stand
up
your
firefly
cli.
You
get
these
wonderful.
You
know
user
interface
dashboards.
You
know
that
that
peter
did
a
much
nicer
job
than
I'm
doing
walking
you
through.
But
this
is
your
core
navigation
over
here.
On
the
left,
this
is
gonna.
You
know
give
you
all
of
that
macro
or
granular
information
that
you
need.
You
can
toggle
between
list
and
timeline
right
here.
You
can
go.
D
One
one
final
thing
that
that
I'll
point
out
here
as
well
and
and
I'll
I'll
say
five
or
ten
minutes
for
our
engineers
to
you
know
maybe
maybe
take
some
some
other
some
other
questions
or
show
pieces
that
I've
forgotten
to
to
show.
But
if
you
just
remove
the
ui
and
you
do
slash
api
which
we
did
show
earlier,
I
just
want
everyone
to.
You
know
just
know
at
your
core
that
this
is
there
and
ultimately
you're
going
to
want
the
apis.
D
Obviously,
this
this
will
give
you
the
interactive
swagger
interface,
and
this
will
get
you
again.
You
know
much
closer
to
how
you're
going
to
program.
You
know,
ultimately,
your
server
side
app
and
do
your
integrations
with
your
core
back
office
systems
as
well,
so
slash
ui
api.
These
are
both
served
after
you
successfully
stand
up
a
stack
once
you
do
an
init
and
a
start
using
the
the
ffcli
and
again
you
do
a
docker
ps.
You
can
see
all
those
containers
if
you're
into
you
know
the
actual
blockchain
transactions.
D
We
recommend
that
you
look
at
one
of
the
the
blockchain
connector
containers
such
as
ethconnect
for
ethereum,
okay,
ten
minutes
left
I'll
I'll
pause
for
a
second
and
just
ask
a
question
to
peter
and
folks.
There's
there's
another
repository
that
we
have
it's
the
it's.
The
data
exchange,
one
built
with
visual
studio
and
also
also
has
sort
of
a
a
nice
flow
and
some
exposed
api.
So
I
wonder
if
it's
worth
going
through
that
or
if
we
want
to
focus
a
bit
more
on
any
of
these
pieces
inside
of
the
cli.
F
Yeah,
I
just
wanted
to
add
a
comment.
I
know
there
have
been
a
lot
of
people
that
have
been
trying
to
get
this
running
in
the
background
here
and
running
into
a
whole
variety
of
issues.
There's
like
40
people
on
this
call,
which
is
probably
10x
the
number
of
people
that
have
tried
running
the
cli
before
today.
This
is
bleeding
edge,
and
so
we
just
appreciate
you
bearing
with
us
as
we
are
launching
firefly,
we're
really
excited
for
this
to
be
collaborative.
F
So
if
you
are
running
into
issues,
we
definitely
want
to
help
out.
I
will
drop
a
link
to
our
rocket
chat
in
the
chat.
If
you
want
to
join
and
chat
directly
with
us,
we
would
love
to
help
you
get
around
these
things
and
also
thank
you
for
reporting
stuff
that
you're
finding
there's,
as
you
saw
from
gabriel's
diagram,
there
are
a
lot
of
moving
parts
to
this
system,
and
so
there's
there's
just
a
lot
of
things
that
may
be
unpredictable
in
different
developer
setups.
We
want
this.
D
F
D
D
E
D
Yeah
and
this
one
as
you're
pulling
it
up
I'll,
just
speak
to
it
since
I've
used
it
a
few
times
this
one's
uberly,
convenient
gabriel,
has
abstracted
a
lot
of
the
heavy
lifting
for
you
and
it'll
automatically
generate
a
couple:
nested
folders
and
some
pki
artifacts
that
you
need
for
authentication,
and
then
it
gives
you.
You
know
a
unique
swagger
interface
for
each
of
the
members,
so
highly
encourage
everyone
to
to
use
this.
A
D
A
So
basically
it
relies
on
this
component
through
a
plugin
interface
and
it
basically
delegates
the
responsibility
of
sending
that
message
across
securely
to
the
other
member.
So
for
this
to
work,
the
cli,
what
it
did
when
everything
was
being
provisioned,
is
that
it
generated
a
number
of
certificates.
This
is
private
keys
and
public
certificates,
and
so
it
uses
those
in
each
of
the
members
so
that
the
members
can
basically
identify
themselves
and
each
other.
A
So
when
data
is
being
sent
from
one
member
to
another,
we
use
those
certificates
and
those
keys
to
encrypt
information
and
make
sure
that
it
securely
makes
it
to
the
other
side.
And
then
we
can
know
for
a
fact
who
the
information
is
coming
from
and
then
the
firefly
core
will
process
that
information
added
to
the
internal
database
and
then
continue
with
the
coordination
of
the
other
remnants.
C
F
E
E
These
communities,
you
know
not
least
besu
and
fabric
who've,
already
been
really
involved.
Over
the
past
few
weeks,
we've
been
discussing
this
within
within
the
the
hyperledger
community,
but
but
also
you
know,
we've
been
talking
lots
to
avalon
and
we've
been
talking
a
lot
on
the
identity
side
as
as
well
so
it's
gonna
be
really
exciting,
seeing
how
we
can
bring
this
all
together.
D
No,
we
just
yeah.
I
have
a
few
thoughts.
I
guess
we
really
really
appreciate
you
know
the
the
broad
attendance
and
for
folks
you
know
sticking
around
even
if
things
get
get
a
bit
bumpy.
That's
that's
how
nascent
projects
tend
to
work,
but
you
know
we're
here
to
get
this
mature
and
get
this
hardened.
Hopefully,
with
your
help.
I'll
just
reiterate,
we
really
really
do
want
to
hear
from
you.
You
know
in
in
our
meetups
on
rocket
chat.
D
If,
if
you
have
requests
for
updated
documentation
or
if
you're,
you
know
a
good
samaritan,
and
maybe
you
even
want
to
write
some
documentation,
we're
all
for
that
and-
and
we
really
just
sort
of
you
know-
want
to
be
sort
of
co-stewards
of
this
project
with
the
community
and
and
with
everyone.
So
we're
here
to
help
we're
here
to
build
together
and
again,
you
know
we're
we're
as
accessible
as
as
could
be.
So
please
don't
ever
be
shy
if
you
need
to
get
in
touch
with
us.