►
From YouTube: FireFly Developer Workshop | Getting started building apps on FireFly & contributing to Open Source
Description
The workshop will guide developers in setting up FireFly on their machine as well as a complete dev environment to be able to contribute code back to the FireFly project.
By the end of this workshop you will have:
A working developer environment capable of:
Building apps that run on FireFly
Making changes and contributions to the FireFly core itself
Sample apps running on your local machine
A working understanding of the components that make up a FireFly stack
Note: Please make sure to make sure you complete the steps in the Prerequisites section of the workshop guide. This will save time during the workshop and will help us make the best use of the time. Thanks!
Workshop Guide: https://gist.github.com/nguyer/62cedff84e5fa5a5e313d060690e5bba
----
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 #HyperledgerMeetup #Blockchain
A
A
If
you
have
not
had
a
chance
to
look
at
the
gist
that
I
sent
out
ahead
of
time
with
the
prerequisites
I'll
post
that
link
I'm
not
I'll
post.
That
link
in
the
chat.
Please
look
at
that
right
now
and
make
sure
that
you
have
the
the
prerequisites
installed
on
your
machine
like
golang,
docker
and
some
sort
of
ide
you'll
need
that
stuff
set
up
in
order
to
actually
go
through
the
workshop.
A
Would
so
this
is
going
to
be
very
hands-on,
very
interactive
if
you
have
questions
as
we
go
or
if
you
get
stuck
please
interrupt
me
unmute.
Ask
your
questions
we'll
try
to
try
to
make
this
as
like
as
possible.
So
I'll
walk
you
through
the
guide,
but
this
is
really
this.
This
workshop
is
for
you
all
to
help
you
guys
get
your
machines
set
up
and
so
that
you
are
prepared
to
either
a
build
applications
on
yeah.
So
look
at
the
the
workshop
goals
here.
A
A
All
right,
so
I'm
going
to
skip
over
the
prerequisites
section
hopefully
had
time
to
do
that
ahead
of
time
in
preparation
for
the
session.
If
you,
if
you're
kind
of
skimming
through
it
real,
quick
and
checking
the
the
two
things
to
really
check
for
to
make
sure
that
that
you
have
everything
on
here
are
the
make
sure
you
have
go
installed,
so
I
can
run
go
version.
I've
got
go
116,
so
I'm
good
there.
A
You
also
will
want
to
make
sure
your
go
path
is
on
your
path.
So
I
can,
let's
see
alt
echo,
go
path,
and
then,
if
I
check
my
my
actual
path,
I'll
see
that
this
go
bin
directory
is
on
the
path
as
well.
If
it's
not
the
quick
thing
to
do
is
edit
either
so
on
mac
os,
it's
a
zsh
rc
now
or
your
bash
rc
and
add
a
few
lines
to
it
at
the
bottom
of
it
to
put
that
on
there.
So
this
will.
A
This
is
important
because
we're
going
to
install
some
binaries
and
you
want
those
on
your
path
so
that
you
can
actually
run
them.
So
hopefully
everybody
has
that
set
up
and
you
have
at
least
a
working
go
environment.
The
other
important
thing
is
docker
and
docker
compose
as
well.
Those
are
usually
fairly
straightforward
to
set
up,
so
we
will
skip
ahead
here
to
actually
setting
up
firefly,
so
firefly
cli
is
a
if
you've
attended
any
of
our
other
sessions.
You've
probably
seen
it
in
action.
A
Maybe
you've
had
a
chance
to
play
with
it
yourself.
It
is
if
you
haven't
it's
a
dev
tool
designed
to
set
up
firefly
and
all
of
its
dependencies
in
a
working
environment
on
your
machine
and
it's
it's
designed
to
take
all
the
hard
devops
orchestration
work
out
of
the
equation
for
setting
all
that
stuff
up.
A
So
firefly
is
a
it's
a
distributed
system,
it's
a
microservices
architecture,
so
there
are
a
lot
of
small
pieces
to
it
in
lots
of
different
software
components,
and
it's
very
modular,
so
you
can
swap
components
in
and
out
so
the
firefly
cli
is
designed
to
help
you
manage
all
of
that
stuff.
So
it's
pretty
easy
to
install.
If
you
have
go
set
up
on
your
machine,
you
should
just
be
able
to
copy
this
line,
we'll
run
that,
and
it
should
go,
install
that
the
even
if
you
have
it
installed
if
you've
installed
it
previously.
A
A
A
B
A
A
My
intention
was
the
target
audience
here
with
somebody
already
interested
in
firefly,
but
needs
to
know
how
to
set
it
up,
but
yeah
to
just
to
just
back
up
for
a
quick
second.
So
firefly
is
a
a
multi-party
system
designed
for
enterprise
data
flows,
powered
by
blockchain
sort
of
how
we
describe
it.
So
what
does
all
that
mean?
A
It
is
it's
it's
a
it's
a
piece
of
software,
it's
many
pieces
of
software
that
help
multi
say
multiple
businesses
want
to
do
business
transactions
and
they
want
to
use
blockchain
as
a
ledger
for
those
transactions,
and
they
want
to
do
it
in
a
secure
way
and
they
want
to
do
it
in
you
know.
Maybe
some
pieces
of
data
need
to
be
shared
with
all
members
of
the
network,
they're
doing
it
in
a
private
blockchain.
So
it's
it's
not
on
you
know,
ethereum
mainnet
or
on
on
some
public
chain.
A
A
It's
it's
a
way
that
it's
a
system
that
orchestrates
all
of
those
communications
in
a
in
a
secure
private
manner
and
lets
developers
focus
on.
What's
the
business
logic
of
the
particular
business
problem
that
I'm
trying
to
solve
and
I'll
leave.
All
of
the
you
know.
I
need
to
get
this
piece
of
data
from
my
organization
to
another
organization
securely
I'll,
leave
that
to
firefly.
A
Oh,
I
need
to
put
this
piece
of
data
on
the
blockchain,
but
I
need
to
leave
this
piece
of
data
off
the
blockchain
leave
that
to
firefly
it
handles
all
of
those,
the
complexity
of
those
things
for
you.
So
it
takes
it's.
It's
really
about
accelerating
the
growth
and
the
adoption
of
enterprise
blockchain
and
giving
a
platform
that
is
just
an
api.
That's
really
easy
to
build
on
and
taking
away
a
lot
of
the
the
complex
or
or
even
not
complex,
but
just
tedious
to
implement.
A
A
Okay,
so,
hopefully
you've
been
able
to
install
the
cli.
We
will
keep
going
here,
so
the
cli.
We
we
talk
about
a
stack
and
I
kind
of
borrowed
this
name.
You
know
if
you're
familiar
with
cloud
formation
on
aws,
you
have
a
cloud
formation
stack,
it's
just
a
set
of
resources,
that's
designed
defined
by
some
document.
So
in
firefly
a
stack
is
it's
an
entire
firefly
network,
so
we'll
create
one
of
those.
A
So
we
can
see
when
we
ran
firefly
when
we
ran
ff
the
firefly
cli
that
printed
out
a
list
of
things
that
you
can
do
with
it,
and
the
very
first
thing
we're
going
to
do
is:
do
an
init,
so,
let's
ff
init
there
are
actually
before
I
do
that
there
are
lots
of
options
on
the
init
command.
If
you
want
to
customize
the
stack
and
not
all
of
these
are
fully
implemented.
A
A
You
can.
You
can
specify
a
different
database
implementation.
Sql
lite3
is
the
default,
but
there's
also
support
for
postgres.
So
if
you
choose
postgres
here,
it
will
spin
up
another
container
for
your
database,
so
so
there's
lots
of
different
customization
options.
When
you
are
editing
a
new
stack
so
just
wanted
to
point
that
out.
But
if
you
just
go
with
the
defaults
and
we
ff
init,
it
will
ask
you
a
couple
questions.
A
If
you
want
to
script
this,
there
are
ways
to
set
all
of
these
things
ahead
of
time
too,
so
it
doesn't
go
into
interactive
mode.
We'll
call
this
stack
name,
we'll
just
call
it
oops.
I
already
have
one
called
workshop,
so
I'm
just
kind
of
I
was
testing
that
last
night
to
make
sure
that
this
would
go
smoothly,
and
I
forgot
to
clean
that
up.
So
I'm
going
to
ff
init,
we'll
call
it
workshop.
You
can
feel
free
to
name
yours
whatever
you
would
like.
A
I'm
gonna
make
a
network
of
two
members
and
there
it
creates
it.
So,
as
you
may
have
guessed
reading
through
the
guide,
firefly
cli
uses
docker
and
docker
compose
to
orchestrate
all
of
the
infrastructure.
Here
so
it
will
actually
tell
you,
hey
your
docker
compose
that
I
just
generated
for
you
is
right
here.
So
if
we
want
to
take
a
quick
peek
at
that,
we
can
do
that
and
there's
a
lot
in
here,
like
I
said,
there's
there's
quite
a
few
moving
parts
to
this
whole
system.
So
that's!
That's!
A
That's
why
we
have
the
cli
is
to
automate
the
generation
of
all
this
stuff,
so
you
don't
have
to
do
it
by
hand
because
it's
there's
quite
a
bit.
So
we
have
our
data
exchange
nodes.
Here
we
have
our
blockchain
connectors,
which
in
this
case
is
going
to
be
ethconnect
and
as
you'll
see
for
each
of
these
there's
one
for
each
member
in
the
network.
A
So
we're
going
to
try
to
simulate
things
as
as
close
to
production,
as
we
can
here
within
reason
and
we'll
see
two
firefly
core
nodes
you
can
see
there
are.
There
are
a
lot
of
ports
that
are
exposed
by
all
these
things
as
well.
So
that's
something
to
watch
out
for
is
just
making
sure
that
those
ports
are
available.
Usually
we
don't
run
into
problems
there,
but
and
the
cli
will
help
you
check
for
those
things
when
we
start
it
up.
A
Here's
our
blockchain,
node
and
ipfs
nodes
here
for
file
storage
and
then
our
token
connectors
as
well-
and
these
are
new
we're
not
going
to
get
into
tokens
today.
Tokens
is
still
under
development
right
now.
It's
it's
new
it
it's
there
in
the
stack,
but
it's
it's
not
quite
done
yet
and
then
there's
some
named
volumes
that
are
exposed
at
the
end.
So
that's
kind
of
that's
just
a
quick
peek
under
the
hood
of
all
the
things
that
docker
compose
is
going
to
do
for
us.
A
So
now
we've
got
so
basically
when
we
run
ff
init
that
just
writes
a
bunch
of
configuration
files
to
the
disk.
It
doesn't
actually
start
anything,
it
doesn't
run
anything
and
when
we
run
ffstart
we'll
say
workshop.
I
think
I
in
the
guide,
I
called
my
stack
name
simple.
You
can
name
it
whatever
you
want,
so
I'm
gonna
start
my
workshop
stack
here-
and
this
is
gonna-
do
a
whole
bunch
of
things.
So
a
it's
going
to
so
right
now
we're
seeing
it
initializing
the
blockchain
node
so
for
ethereum.
A
It's
writing
the
genesis,
json
and
putting
all
of
the
identities
on
chain.
It
will
also
pull
the
latest
versions
of
all
of
the
firefly
components
to
make
sure
everything
is
staying
up
to
date.
For
you,
it
only
does
that
the
first
time
that
the
stack
launches
so
once
you
launch
a
stack,
it
will
stick
with
that
version.
Unless
you
run
the
upgrade
command
it
will
so
so
after
it
starts
everything
up,
it
will
deploy
a
smart
contract
for
you
and
it
will
register
the
identities
of
all
the
members
on
the
network.
A
So
it's
it's
doing
a
whole
bunch
of
things.
In
addition
to
just
starting
up
processes,
you
know
if
you
could
just
go
run
docker
compose
up
on
that
stack,
but
then
you
would
have
a
whole
bunch
of
other
manual
steps
that
you'd
need
to
do
after
that
to
actually
get
it
to
a
usable
state.
So
the
that
the
cli
is
designed
to
automate
a
lot
of
these
steps.
Usually
it
doesn't
take
this
long
to
pull
the
latest
versions,
so
I'm
gonna
actually
there's
a
way
to
skip
pulling
the
latest.
A
A
B
A
B
A
Okay,
great
thank
you
and,
if
you,
if
for
some
reason,
you
can't
run
ff
reset
on
it,
you
could
also
rm
rf
and
it's
going
to
be
in
your
home
directory
in
a
directory
called
dot,
firefly
stacks
and
then
the
the
name
of
your
stack.
So
you
could
just
if
you
need
to
manually,
delete
that
directory
for
some
reason.
That's
where
it's
at.
A
Sure
yeah
good
good
call
out
there
yeah.
I
forgot
to
mention
that
sorry,
so
docker
definitely
needs
to
be
running.
The
cli
does
not
automatically
start
docker
on
your
machine,
so
you'll
need
to
make
sure
that's
running
before
you
start
running
ffstart
or
any
of
the
other
commands
ff
init
just
writes
config
to
the
disk,
so
it
does
not
need
docker
running,
but
I
think
all
of
just
about
all
the
other
ones
do
something
with
docker.
So
all
right,
so
we've
got
a
working
stack
on
my
machine.
A
Hopefully
you
have
a
working
stack
on
your
machine
too
or
you're
very
close
I'll.
Try
to
try
to
keep
going
slow
here,
so
people
can
keep
up,
but
we
should
be
able
to
click
on
these
links
and
see
the
dashboard
now,
and
indeed
we
can
so
we
haven't
run
any
transactions
here,
but
we
we
have
a
working
stack,
so
you'll
see
the
the
default
url
so
that
we
clicked
here-
and
this
is
slash
ui-
so
you
can,
you
can
go
here
and
you
can
see
it
kind
of
we'll
see.
There's
two
sorry.
A
This
is
kind
of
it's
cutting
everything
off
here,
but
so
there's
two
network
members.
There
have
been
no
messages
and
once
we
start
sending
some
stuff,
we
can
go
to
the
messages,
the
data
or
the
transactions
tabs
and
inspect
those,
but
there's
nothing
in
here.
Yet
if
we
want
to
see
the
api
documentation,
the
swagger
definition
for
everything
we
can
just
change
this
from
ui,
we
can
go
to
slash
api
and
that
will
load
this
page.
A
So
here
we
can
poke
around
and
see
all
the
different
endpoints
that
we
can
hit.
The
kind
of
these
are
some
of
the
important
ones
that
we'll
be
focusing
on
today.
You
know
broadcasting
a
message
and
also
sending
private
messages,
and
so
these
are
the
end
points
here.
You
can
see
examples
and
all
the
different
fields
that
are
on
there.
A
Hopefully,
you
should
be
able
to
pull
this
up
on
your
machine
as
well,
if,
if
you're
just
curious
to
to
explore
the
api-
and
you
don't
want
to
go
through
all
the
hassle
of
starting
up
a
stack
this,
this
swagger
document
is
published
as
well.
You
can
find
it
at
labs.hyperledger.org
firefly
and
you
can
go
to
api
spec,
and
this.
A
I
have
linked
to
this
swagger
dock
down
here
as
well.
There's
also,
while
we're
down
here,
there's
also
a
postman
collection
that
you
can
download.
If
you
use
postman,
I'm
going
to
use
it
in
a
little
bit
to
actually
run
some
transactions,
you
could
download
this
collection
and
it
will
kind
of
pre-populate
postman
with
a
bunch
of
different
requests
that
you
can
use
to.
Try
out
your
firefly
stack
that
you
just
installed,
and
I
think
there's
a
note
of
that
in
the
guide
here
yep.
A
A
The
sample
apps
are
in
which
well
postman
is
coming
up
here
to
take
a
look
at
well
we'll
look
at
the
sample
apps
in
just
a
minute,
all
right,
okay.
So
this
is,
if
you
open
up
postband
and
you
import
that
collection,
we'll
see,
I
called
mine,
firefly
demo.
I
think
you
could
name
it
when
you
import
it.
Let's
just
run
a
broadcast,
simple
message,
so
we've
got
two
firefly
nodes
running
on
our
machine
right
now.
One
of
them
is
listening
on
port
5000
and
the
other
is
on
5001..
A
A
There
you
go
okay,
so
this
is
going
to
be
sent
to
the
first
member
and
this
will
be
brought
because
this
is
a
message
broadcast.
This
will
be
sent
to
every
member
of
the
network.
So
if
there
was
more
than
one
other
member,
everybody
would
get
this
so
we'll
hit
send
and
then
we
should
be
able
to
go.
Look
at.
A
Let's
go
back
to
the
ui,
and
here
we
can
see
that
there
was
a
message
that
was
sent:
let's
open
up
the
second
member's
network
or
explorer
as
well,
and
they
have
the
message
as
well.
So
now
there's
a
message
in
here:
we
can
go
to
the
data,
tab
and
click
on
this
row
and
we
can
see
there
there's
the
contents
of
the
thing
that
we
sent
foo
bar
and
then
we
can
see
it
postman.
That's
the
value
of
what
we
sent
here.
A
So
when
you're
sending
a
message
in
firefly,
there's
a
it's:
it's
wrapped
at
a
so
you're
you're
sending
you're
not
just
sending
a
piece
of
data
you're,
sending
a
firefly
message
that
contains
one
or
more
pieces
of
data
and
some
information
on
how
to
send
it.
Who
to
send
it
to
and
that
sort
of
thing
so
there's
there
are
in
the
docs,
there's
lots
of
different
lots
of
different
ways
to
send
messages,
we're
not
going
to
get
into
all
of
them
today.
A
So
I
will
show
one
more
though
we'll
send
a
so
now,
so
that
was
a
broadcast
to
everybody
in
the
network.
We'll
send
a
private
message
now,
and
so
this
one's
gonna
be
a
little
different.
So
here,
first
of
all,
it's
going
to
a
different
endpoint.
So
this
is
the
messages
private
endpoint
and
we
still
have
a
data
array
with
one
element
here
in
this
case,
I'm
just
sending
the
string
secret
message.
A
Last
time
I
was
sending,
I
was
actually
sending
a
json
object,
so
this
value
can
be
any
arbitrary
json
object
for
now,
I'm
just
making
it
a
string,
and
then
we
also
have
a
group
with
a
list
of
members
to
send
it
to.
In
this
case,
I'm
sending
it
from
the
first
node
in
the
network,
which
is
org0
on
port
5000
and
I'm
going
to
send
it
to
org
one.
A
A
A
A
So
yes
they're
their
firefly
has
its
own
smart
contract
that
it's
that
it's
executing
right.
Now,
if
the
question
is
about,
can
you
write
your
own
custom,
smart
contract
and
use
firefly
to
run
that
the
answer
is
coming
very
soon?
That's
one
of
the
next
major
things
in
the
firefly
project
that
we'll
be
working
on
in
yesterday's
community
call.
We
demonstrated
so
one
of
the
goals
of
firefly
is
to
be
very
modular,
very
pluggable
and
and
open.
A
All
right
I'll
pause
here,
any
other
questions
on.
Hopefully,
hopefully,
you've
been
able
to
get
a
stack
up
on
your
machine
and
you've
been
able
to
send
a
couple
messages.
Please
you
know,
raise
your
hand
or
or
unmute
if
you
are
stuck
or
have
questions
we'll
pause
here
for
just
a
minute
to
make
sure
that
everybody
is
kind
of
keeping
up.
A
Yep
it
it
is
it's
possible
to
do
some
of
this
on
windows
and-
and
I
think,
if
you're
running
wsl2,
it
is
it's.
I
think
it's
possible
to
do
all
of
it.
I,
unfortunately
that
is
like
the
most
complicated
setup
possible
for
this,
and
we
don't
have
time
today
to
walk
through
getting
wsl
2
set
up
on
windows.
B
A
Yep
there
was
a
question
about
the
recording
for
fabric.
Yes
later
today
it
will
be
up
on
the
the
hyperledger
wiki
in
the
the
firefly
lab
page.
We
we
have
a
page
for
for
every
community
call
and
the
recording
will
be
up
there.
I
haven't
had
a
chance
to
post
yesterday's
recording
yet,
but
I'll
do
that
later.
Today,.
A
A
A
We
can
do
a
get
on
network
organizations
and
where's
the
try
it
out,
but
there
it
is
at
the
top
execute
and
you
can
do
this
from
postman
to
I
don't
have
it
in
the
collection,
though
so
here's
so
this.
Basically,
I
just
asked
my
local
firefly
node,
hey,
get
me
the
list
of
everybody,
that's
in
the
network,
all
the
organizations
and
there's
there's
separate
endpoints
for
all
of
the
the
node
or
the
member.
A
Sorry,
all
the
nodes
that
are
in
those
organizations,
but
we
can
see
there's
there's
two
orgs
here:
org0
and
org
one.
So
this
is
me
I'm
I'm
or
from
the
oh.
Actually,
sorry
I
did
this
request
from
5001..
So
so
this
would
be
me
org
one
here,
and
this
is
org0
who's,
the
the
other
member
of
the
network.
A
So
in
the
real
world
this
would
be
probably
one
company,
and
this
would
be
some
other
company
that
have
entered
into
some
sort
of
consortium
and
that
want
to
do
business
transactions
with
each
other,
but
want
to
use
blockchain
want
to
keep
some
some
pieces
of
data
private
or
some
public,
and
but
but
they
want
to
do
transactions
with
each
other.
Does
that
make
sense.
B
A
A
If
we
go
look
at
let's,
let's
take
a
minute
to
to
look
at
what's
running
on
my
machine,
because
this
is
something
I
wanted
to
show
everybody
as
well,
so
I'll
just
open
up
my
docker
dashboard
here
and
we
can
see
in
the
workshop
stack
there.
I
have
a
a
go
ethereum
or
geth
node
running
on
my
machine
and
this
this
machine
is
this.
This
ethereum
node
is
set
up
in
a
private
chain.
So
when
the
firefly
cli
started
up,
it
created
its
own
blockchain.
A
It
created
its
own
genesis
block
and
then
gave
it
to
this
node
and
said:
hey
start
a
completely
new
chain
and
in
that
chain
gas
is
free
and
so
anytime
you're
running
transactions
in
the
private
network.
It's
free,
there's
no
cost
to
run
a
transaction.
It's
it.
It
just
works
fundamentally
differently,
because
the
the
economy,
if
you
will,
is
different
in
a
private
privileged
network
than
it
is
on
a
public
blockchain.
A
A
B
A
Okay,
sure
yeah,
so
this
is
so
the
firefly
explorer.
Is
it's
just
a
way
to
look
at
the
system
and
see
what
what's
going
on
inside
firefly?
It's
not
a.
This
is
not
a
a
you.
Probably
won't
use
this
in
production,
but
it's
it's.
This
is
a
tool
for
when
you're
building
your
app
to
see
hey.
What
did
I?
I
made
a
post
request.
What
happened?
Who
got
the
data?
What
does
it
look
like
on
the
other
side,
so
the
def-
this
is
the
default.
Dashboard
is
just
sort
of
a
summary.
A
A
If
lots
of
messages
are
going
through
the
system
all
at
once,
they
could
be
firefly
will
batch
things
for
better
throughput,
and
so
those
could
all
get
rolled
up
into
one
transaction.
That
firefly
will
it's
sort
of
it.
It
buffers
things
and
it
will
hash
and
write
things
to
the
blockchain
all
at
once
in
a
batch,
and
so
so
that,
if
you're
sending
requests
fast
enough
into
the
system,
you'll
see
you
actually
have
fewer
transactions
than
you
have
messages
sent
through
the
system
and
you
may
have
depending
on.
A
If,
if
each
of
those
messages
had
more
than
one
data
element,
you
could
have
more
pieces
of
data
than
you
do
messages.
So
hopefully
that
makes
sense
and
kind
of
the
difference
in
all
three
of
those,
and
this
is
just
a
way
to
to
view
each
of
the
three
messages,
data
or
transactions
and
the
dashboard
shows
the
overview.
A
All
right
we'll
do
a
couple
more
questions
here
and
then
I
do
want
to
let's
see.
Yeah
we've
got
about
a
little
less
than
20
minutes
left.
So
I
want
to
kind
of
get
back
on
track
here
in
just
a
minute
for
fabric.
I'm
setting
private
messages
between
different
orgs
will
firefly
create
separate
channels
for
each
pair
of
orgs
private
data
collections
yeah.
So
it's
a
great
question
so
that
that
topic
actually
came
up
on
the
community
call
yesterday.
A
The
short
answer
is:
there's
more
work
to
be
done
to
support
multiple
channels
right
now,
so
fabric
support
is,
is
not
fully
released
yet,
but
it's
we
showed
it
working
yesterday.
So
as
of
today,
there's
one
channel
that
it
uses.
But
that's
that's
not
the
the
end
game.
There
there's
there's
more
work
to
be
done
in
firefly
to
support
multiple
channels,
but
the
short
answer
is:
it
will
be
flexible
and
it
will
be
up
to
you
in
whatever.
A
A
A
This
is
meant
to
be
just
an
approachable
like
very
simple,
like
hey
here's,
how
you
write
some
code
that
sends
a
transaction
to
firefly,
so
it's
gonna
be
doing
basically
the
same
thing
we
just
did
in
postman
manually
but
with
some
code,
so
we'll
go
into
that
directory,
we'll
run
actually
so
in
here.
We've
got
a
cli
example
and
a
ui
example.
So
we'll
run
the
cli
one
first,
so
we'll
go
into
the
directory
oops
and
we'll
just
npm
install
that.
A
So
that's
going
to
go,
get
dependencies
and
set
that
up.
Okay.
Now
we
should
just
be
able
to
npm
start
and,
like
I
said
this
is
super
simple.
So
all
this
is
going
to
do
is
going
to
start
up
it's
going
to
broadcast
to
a
message
with
two
data
elements,
hello
and
world,
and
then
it's
going
to
make
sure
that
it
receives
them
on
the
other
end
and
it
sure
did
so.
A
It
would
send
it
from
what
it
calls
firefly
1.,
that's
on
port
5000
and
it
sent
it
to
firefly
2,
and
this
guy
got
it
so
here
this
sample
actually
demonstrates
listening
on
a
websocket
as
well.
We'll
just
go
peek
at
the
at
the
dashboard
again,
so
we
can
look
at.
Let's
look
at
the
data,
okay,
so
here's
yeah,
so
here's
hello
and
here's
world.
So
these
two
data
items
were
sent
in
this
message
right
here
and
we
can
see
yeah
so
there
this
one
had
two
pieces
of
data
in
it.
A
A
A
So
so
there's
this
is
basically
just
the
kind
of
the
flow
through
the
thing
here
we
define
the
data
and
then
we
we
broadcast
it
and
then
in
firefly
ts.
So
this
is
this
is
a
typescript
application.
We
define
some
basically
just
the
data
types
and
we
define
a
so.
This
is
if
you
wanted
a
simple
example
of
a
websocket
listener.
This
is
a
good
place
to
look
actually
if
you're
interested
in
doing
it
in
typescript
or
javascript
on
node.
So
so
this
is
going
to.
A
So
if
we
go
into
that
one,
what's
it
called
private
data
transfer
ui,
I
I'm
not
gonna
go
through
this.
I
think
this
one
uses
react
and
it
might
take
a
little
longer
to
install
I'm
not
going
to
go
through
and
run
all
of
this
one
right
now,
but
I'll
just
give
you
a
quick,
quick
tour
of
what
that
one
looks
like,
so
this
one
will
send
this.
One
has
a
couple
drop
down
menus.
A
It
will
send
either
private
messages
or
broadcasts
that
the
name
is
actually
we
should
rename
it
it's
a
little
bit
of
a
misnomer
right
now,
so
it
it
has
a
it's
a
very
simple
like
front
end
and
back
end.
So
here's
some
some
routes
that
it
defines
for
the
the
web
page
interface
to
hit
and
then
that
that
back
end
will
take
care
of
making
the
requests
to
firefly.
A
So
that's
what
we've
got
in
here:
here's
our
our
app
tsx.
So
this
is
this
is
the
front
end
yeah
it's
gonna
complain
because
I
don't
have
all
the
dependencies
installed,
and
this
is
if,
if
you're
familiar
with
react
development,
this
should
look
fairly
straightforward.
If
you're
not.
This
is
probably
super
confusing,
but
that's
this.
This
is
an
example
of
a
front
end
and
a
back
end
that
you
can
use
if
you're
curious
on
how
to
put
one
of
those
together.
A
So
at
this
point,
let's
see
I
want
to
make
sure
we
get
through
the
good
stuff
in
the
amount
of
time
we
have
left
here
so
kind
of
looking
at
our
goals.
What
have
we
accomplished
so
far?
We
have
a.
We
have
a
dev
environment
that
is
capable
of
building
apps
on
firefly.
We
just
showed
downloading
and
building
and
running
an
app
on
firefly
we've
made
some
manual
postman
requests
to
it,
but
we
haven't.
A
We've
we've
run
sample
apps
on
the
machine
and
hopefully
you're
getting
a
working
understanding
of
the
components
it
will.
This
that
that
may
be.
That
may
be
a
stretch,
because
there's
a
lot
going
on
here,
but
making
making
changes
to
firefly
itself
is
the
the
major
thing
that
I
want
to
get
into
now.
So
we
we're
super
excited
that
lots
of
people
are
interested
in
firefly
and
we
would
love
to
have
more
contributions
to
it.
We
would
also
love
if
people
are
really
passionate
about
it
and
really
want
to
get
involved.
A
We'd
also
love
more
maintainers
on
on
the
projects
as
well.
There
are
a
lot
of
different
repos
in
firefly
I've
linked
to
all
of
the
different
repos
here
at
the
bottom,
a
variety
of
languages
that
are
used
in
them,
so
you
don't
necessarily
need
golang
expertise
to
to
be
a
contributor
or
even
a
maintainer,
on
some
of
these.
So
if
you're,
if
you're
really
interested,
definitely
check
them
out,
please
reach
out
to
us
we
we
would
really
like
to
get
more
contributors.
So
this
is
that's
the
goal
of
today's
session.
A
Okay,
so
so
far,
we've
run
firefly,
but
we
haven't
actually
downloaded
the
source
code
for
any
of
the
firefly
repos
itself.
So
we're
going
to
do
that
now.
So
this
is
we're
really
shifting
gears
here.
Now
I'm
going
to
go
back
up
to
my
just
sample
directory
here
that
I
made
we're
going
to
go,
grab
the
source
for
firefly
core
and
we're
going
to
download
that
so
firefly
core
is
it's
it's
an
orchestration
engine.
A
So
it's
it's
sort
of
it's
it's
the
orchestrator,
but
all
of
the
hard
work
all
of
the
the
the
real
the
valuable
work
is
done
by
everything
around
around
it.
Well,
that's
not
to
say
that
what
firefly
does
is
valuable,
but,
for
instance,
the
blockchain
work
itself
is
is
actually
done
by
by
the
blockchain
node.
It's
and
firefly
is
really
orchestrating
all
of
those
things
together,
all
right,
so
we've
downloaded
the
code
for
it.
Let's
go
in
and
we've
gone
into
that
directory
now
so.
A
A
It's
it's
hard
to
debug
when
the
thing
that
you're
running
is
built
in
a
docker
image,
that's
published
somewhere
else,
and
it's
it's
just
just
complicated.
So
to
me,
it's
a
lot
more
straightforward.
If
I
can
just
debug
a
process,
that's
running
on
my
host
machine
and-
and
I
can
just
go
with
that-
so
what
we're
going
to
do
is
we're
going
to
create
a
different
stack
now,
and
this
stack
is
going
to
have
all
of
the
components
that
we
had
before.
A
A
A
A
Okay,
maybe
we
can
come
back
to
that
all
right,
so
it
has
built.
If
I
look
here,
I
have
a
firefly
binary
that
has
been
built
now
and
so.
Okay,
so
we've
stopped
the
stack
just
keep
going
through
the
guide
here.
So
now,
I'm
gonna
we're
gonna
create
that
new.
That
new
stack
that
I
was
talking
about.
That's
that's
missing
one.
A
A
I'm
going
to
call
this
one
we'll
call
it
dev
2,
because
I
think
I
already
have
a
dev
stack,
I'm
going
to
say
it
has
two
members
and
it's
going
to
generate
all
the
config.
For
me,
I'm
going
to
ff
start
dev
underscore
two
and
I'm
gonna
run
that,
and
so
what
will
happen
here
is
it'll,
go
through
all
the
same
initialization
steps
and
then
it
will
pause.
A
A
A
I'm
going
to
just
paste
that
command
over
in
this
terminal,
I'm
going
to
run
it
and
then
mac
os
will
ask
me
if
I
really
want
to
allow
it
to
listen
on
a
port.
So
we'll
see
firefly
core
come
up
over
here
and
then
basically,
this
the
cli
sits
there
and
it
waits
for
something
to
be
listening
on
that
port.
As
soon
as
it
sees
that
that
port
is
available,
it
will
continue
its
setup.
A
A
I'd,
I
will
look
at
that
in
a
little
while
here,
so
if
something
goes
wrong,
and
sometimes
it
does
especially
when
you're
doing
development,
the
cli
will
will
roll
all
of
the
changes
back.
So
it
will
try
to
get
everything
back
to
a
clean
slate
so
that
you
can
run
this
again
and
hopefully
it'll
work.
The
second
time,
I'm
not
actually
sure
what
was
wrong
here.
It
looks
like
it
might
have
been
something
with
with
tokens
or
or
one
of
the
newer
things
in
here
so
I'll
I'll.
Look
at
this
offline.
A
I
I
do
want
to
point
out,
though,
and
I
realized
we
were
running
out
of
time
so
there's
I.
I
really
want
to
show
you
how
to
connect
a
debugger
to
it.
So
we'll
we'll
just
talk
through
that
real
quick.
So
I'm
going
to
open
up
visual
studio
code
in
the
in
the
firefly
repo,
and
there
is
a
so
to
you-
don't
have
to
use
visual
studio
code.
You
could
use
your
own
ide
if
you
want.
A
A
I
called
mine
dev2,
but
if
you
called
it
dev,
I
could
literally
just
come
in
here
and
hit
f5
and
run
it.
And
then,
if
the
rest
of
the
stack
was
running,
it
would
connect
to
it
and
then
it
would
be
it
would
work.
And
then
I
could
go
into
any
of
the
any
of
the
source
code
files
here
say
in
in
batch
pin
and
you
know
any
time
any
time
I'm
submitting
a
append
batch.
I
could
put
a
breakpoint
in
here
and
I
could
inspect
this
code.
A
A
That's
that's
the
way
to
basically
let
the
cli
handle
all
the
hard
work
of
doing
everything
outside
of
firefly,
and
let
you
focus
on
hey.
I
just
I
just
want
to
focus
on
the
firefly
code
base
itself
and
build.
Maybe
it's
a
new
plugin,
maybe
it's,
maybe
maybe
it's
an
enhancement
or
bug
fix
or
anything
like
that.
A
A
So
if
you
want
to
go,
read
up
more
on
this
or
walk
through
it
on
your
own,
you
can
either
follow
this
guide
or
read
through
the
documentation
pages
there
and
I've
linked
to
all
the
rest
of
the
firefly
repos
here
and
again,
cli
setting
up
all
these
for
you.
But
if
you
want
to
go
poke
around
into
what
all
it's
setting
up,
you
can
go
into
each
one
of
those
there.
So
I
think
we
are
about
at
time,
but
that
is
the
the
end
of
the
material
that
I
had
to
go
through
today.
A
B
A
A
Yeah,
so
so
I
I
see
there
was
a
clarification
on
there.
So
firefly
is
is
firefly
is
designed
as
an
enterprise
grade
production
system.
The
cli
itself
is
a
is
a
development
tool,
so
so,
hopefully
that
helps
clarify
it.
So,
if
you're
going
to,
if
you
want
to
use
firefly
in
production,
you
don't
want
to
use
the
cli
to
set
it
up.
A
You'll
want
to
there's
there's
a
lot
more
things
that
you'll
need
to
consider
there
in
terms
of
network
access,
security
and
you'll,
you
will
there's
yeah
you'll
want
to
have
control
over
all
the
things
that
the
cli
is
doing
for
you.
It's,
the
cli
is
basically
going
okay
or
I'm
going
to
pick
reasonable
defaults
for
a
local
development
environment
so
but
but
firefly
itself.
It
is
designed
to
be
used
in
production.