►
From YouTube: Getting Started with Hyperledger FireFly
Description
A virtual meetup hosted by Hyperledger Jalandhar on April 25, 2023. In this session, Nicko Guyer, Hyperledger FireFly Community Lead and Sr. Full Stack Engineer at Kaleido, will show you how to get started with Hyperledger FireFly and radically speed up your development time.
It’s no secret that building Web3 apps is hard. There are protocols to master, new constructs like tokens and smart contracts to understand, and then the challenge of integrating everything with existing systems, which may be the hardest part of all.
That’s why our community created Hyperledger FireFly, the first open-source Supernode: a complete stack for enterprises to build and scale secure Web3 applications. FireFly's next gen-gen platform simplifies development, making it easy to connect across multiple public and private chains while running many use cases simultaneously.
With live coding and easy-to-follow steps, you’ll have everything you need to build and run your own blockchain powered app.
More about Hyperledger FireFly can be found at: https://github.com/hyperledger/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
Discord: https://discord.gg/rVCn4j7UFd
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 #Blockchain
License
Creative Commons Attribution license (reuse allowed)
A
So
Nico
we
can
start
whenever
you
want
I'm
gonna
also
do
a
backup,
recording,
okay
and
when
you
want
to
start
we're
good
to
go,
we
are
live
streaming
on
YouTube.
The
YouTube
link
has
been
shared
in
chat
in
case.
Anybody
wants
to
share
it
with
a
colleague
and
I
will
post
the
links
that
I
shared
a
little
while
ago,
because
we
have
more
folks
joining
links
to
like
the
Firefly
Wiki
fireflies
GitHub
link
to
our
Discord.
A
B
C
C
B
Right,
thank
you
so
much
for
organizing
this
and
inviting
me
here
today.
I'm
excited
to
share
about
Firefly
and
give
a
little
introduction
to
it
and
then
kind
of
show
it
in
action
as
well.
So
with
that,
we
will
jump
right
in
my
name
is
Nico
Guyer
I'm,
a
senior
software
engineer
here
at
collido
and
I'm,
also
a
maintainer
of
hyperledger
firefly
and
the
open
source
Community
lead
as
well.
B
B
B
Then
I
want
to
look
at
hyperledger
Firefly
and
how
is
building
a
web3
app
better
with
it
and
then,
lastly,
we're
going
to
go
Hands-On
and
I'm
actually
going
to
show
you
an
app
that
I
wrote
and
we're
going
to
talk
through
what
it
does
and
show
you
how
easy
it
is
to
build
an
app
that
works
with
the
demo
that
we're
going
to
walk
through
uses
a
public
blockchain,
and
it's
going
to
do
transfers
of
both
fungible
and
non-fungible
tokens.
So
we'll
look
at
that
in
just
a
little
bit.
B
Okay.
So
let's
Jump
Right
In.
What
do
you
need
to
build
a
web3
app?
Let's
say,
for
example,
that
we
wanted
to
build
a
game,
and
this
is
just
a
hypothetical.
This
could
be
many
different
types
of
applications
could
be.
You
know
Enterprise
track
and
Trace
could
be.
You
know
a
variety
of
things
but
we'll
say
we'll,
say:
hypothetically
we're,
building
a
game.
The
game
needs
some
sort
of
economy
with
the
currency,
that's
backed
by
blockchain.
B
The
our
game
needs
to
have
a
decentralized
Marketplace
that
allows
end
users
to
buy
and
sell
items
that
are
in
the
game.
They
need
to
have
full
custody
of
their
assets,
so
they
can
take
those
those
in-game
assets,
things
that
they
earn
or
or
win
and
take
them
to
other
marketplaces
and
sell
them
as
there
as
well.
B
It
would
also
be
really
cool
to
have
the
ability
to
exchange
in-game
currency
for
for
Fiat
in
either
direction
so
that
you
could
actually,
you
could
actually
earn
money
by
playing
if,
if
you
play
the
game
a
lot
that
sort
of
thing,
so
these
are
just
some
some
hypothetical
requirements
of
of
a
web
3
app.
So
with
that
in
mind,
you
know
what
what
do
we
need
to
build
all
of
this?
B
Well,
let's
start
at
the
we're
going
to
build
a
stack
diagram
here
and,
let's
start
down
at
the
bottom
of
the
stack.
So
obviously
the
first
thing
that
comes
to
mind
is
we
need
some
sort
of
blockchain
node.
This
could
be
a
public
chain
could
be
a
private
chain,
there's
a
lot
of
different
decisions
into.
Where
does
the
chain
run?
Who
has
access
to
it?
Who
runs
it?
How
many
nodes
do
we
need
to
run?
Do
we
run
on
an
existing
chain,
or
do
we
create
our
own?
B
That's
there's
a
lot
of
decisions
that
need
to
be
made
there,
but
the
good
news
is
there
are
lots
of
Open
Source
projects
that
are
kind
of
down
here
at
this
at
this
bottom
layer
of
our
stack
diagram,
so
we
need
to
blockchain
node.
Well,
that's,
obviously
not
enough
in
and
of
itself
not
every
piece
of
data
needs
to
go
or
even
should
go
on
the
blockchain
Node
itself.
So,
for
instance,
if
you
have
an
in-game
asset,
say
it's
a
skin
or
a
3D
model,
or
something
like
that.
B
Those
things
are
probably
too
large
to
put
on
the
blockchain
itself
and
so
oftentimes.
What
we
do
is
we
create.
We.
We
talk
about
the
concept
of
pinning
something
to
the
hash
to
the
to
the
blockchain,
so
we
hash
the
data
and
then
we
put
the
hash
of
the
data
on
the
blockchain,
but
we
keep
the
actual
payload
the
actual
asset
off
of
the
blockchain.
So
we're
gonna
have
this
other
column
in
our
stack
diagram
here,
which
is
our
off
chain
side
of
the
diagram.
B
Immutable
has
a
lot
of
attributes
of
blockchain,
but
is
is
different
and
is
optimized
for
a
different
use
case
like
file
storage
and
distribution,
and
handling
much
larger
payloads,
okay,
so
down
here,
we
kind
of
got
the
bottom
of
our
stack
diagram
moving
on
yeah.
So
there's
there's
lots
of
great
open
source
projects
that
do
these
things.
Now
we're
going
to
start
writing
our
own
code.
We
probably
need
some
sort
of
token
smart
contract
this.
This
may
need
to
be
customized
to
to
our
particular
use
case.
B
We're
gonna
need
some
code
to
manage
transactions
to
that
smart
contract,
and
then
we
need
code.
That's
listening
for
events
that
are
emitted
by
it
as
well,
for
when
tokens
get
transferred
from
wallet
to
wallet
over
on
the
off
chain
side,
we're
going
to
need
some
code
to
actually
access
all
of
those
assets
and
know
how
to
get
them,
how
to
download
them
where
to
put
them
that
sort
of
thing
we're
going
to
need
some
code.
B
That's
going
to
manage
all
of
our
signing
keys,
we're
going
to
need
some
code
that
is
going
to
keep
track
of
the
balances
of
certain
wallets,
so
we're
getting
Events
off
of
the
chain
as
transfers
are
happening,
but
we
have
to
write
code,
that's
going
to
keep
track
of!
Who
owns
what
token
and
how
many
tokens
they
have
now,
there's
going
to
be
a
layer
that
sits
across
both
of
these
that's
going
to
correlate
all
of
the
data.
B
Now,
in
this
app
in
this
game
in
this
ecosystem,
a
lot
of
it
is
public
a
lot
of
it's
open,
but
there's
probably
going
to
be
some
amount
of
data.
That
is
private,
is
sensitive.
You
know
user-specific
data,
and
so
we
need
to
have
some
code
that
also
manages
what
things
should
be
shared
within
our
ecosystem
and
what
things
should
be
kept
private
or
only
selectively
or
optionally
shared.
B
Now
we
start
getting
to
the
good
stuff,
the
actual
business
logic,
if
you
will
or
the
the
back
end
API.
This
is
where
the
actual
logic
of
the
game
actually
sits.
It's
way
up
here
at
the
top
of
the
stack
diagram
and
then,
lastly,
we're
going
to
need
our
our
front
end,
whether
that's
a
web
UI
or
a
mobile,
app
or
or
a
native
app
of
some
sort.
That
actually
is
the
thing
that
the
users
log
into
and
get
to
experience
all
of
this
stuff.
B
And
so
that's
exactly
what
Firefly
does
Firefly
takes
care
of
the
entire
middle
of
this
stack
and
then
it
lets
you
focus
on
the
top
layers,
your
user
experience
and
your
business
logic,
which
are
the
things
that
really
Drive
value
for
your
business
and
Firefly
handles
the
rest
of
it,
and
so
so.
We've
seen
now
on
the
first
diagram.
B
We
had
open
source
at
the
very
bottom
and
the
rest
of
it
was
stuff
you
have
to
write
or
build
yourself,
and
now
we've
moved
the
amount
of
Open
Source
software
up
that
we're
using
to
most
of
the
stack,
which
is
really
great
now.
This
absolutely
does
not
prevent
you
from
coming
down
here
and
say,
say
this
token:
smart
contract,
like
hey
I,
have
my
own
contract
I,
don't
want
to
use
Firefly's
built-in
contracts,
that's
totally
fine!
You
can
absolutely
use
your
own
custom
contract.
B
In
fact,
that's
what
we're
going
to
demo
today,
there's
nothing
stopping
you
from
from
going
down
to
the
lower
levels
and
customizing
things
as
you
need,
or
using
your
own
contract
and
that
sort
of
stuff,
so
that's
kind
of
where
Firefly
sits.
This
really
to
me
as
a
developer,
captures
the
value
of
it.
That
shows
like.
B
So,
where
does
Firefly
sit
in
terms
of
the
you
know,
kind
of
my
my
organization
and
my
business,
not
not
just
looking
at
the
the
text.
I
text
stack
diagram
of
what
is
Firefly,
but
you
know
where
does
Firefly
fit
well
Firefly?
Is
we
often
describe
it
as
a
web?
3
Gateway,
it's
sort
of
designed
to
be
your
company's
One-Stop
shop
for
everything
blockchain,
so
you
can
install
Firefly
within
your
organization
over
here
and
it
it
can
be
sort
of
your
your
gateway
to
the
web.
B
3
world
we've
called
a
web
through
Gateway,
whether
that
is
a
private
blockchain
running
in
you
know,
a
Consortium
of
organizations
that
have
agreed
to
collaborate
in
a
Consortium
Network
and
perform
business
transactions,
whether
it's
transferring
value
or
data
or
both
within
a
private
network.
It
could
be
public
layer,
one
or
layer.
Two
chain
could
be
an
exchange
for
D5,
apps
or
whatever
it
is.
B
Firefly
has
a
lot
of
great
features.
A
lot
of
these
boil
down
to
giving
you
the
ability
to
write
apps
flows
and
build
digital
assets.
So
there
are
super
easy
to
use
apis,
and
the
idea
is
that
we
we
provide
technologies
that
web
2
developers
are
already
familiar
with,
such
as
Arrest
apis
and
web
sockets,
and
make
those
easy
to
use
and
basically
provide
ways
for
that
feel
very
familiar
to
developers
already
to
build
web
3
apps
using
Technologies
they're
already
familiar
with
web
tube.
B
So
a
lot
of
great
things
in
here
Firefly
core
is
kind
of
the
the
orchestration
engine
of
all
of
firefly,
so
Firefly,
it
is
a
microservice
architecture
and
there
are
many
different
services
that
run
within
it.
But
Firefly
core
is
the
the
thing
that
connects
all
of
them
together
and
orchestrates
transactions
across
both
the
blockchain,
both
shared
storage
or
private
data
exchange,
as
well
within
a
Consortium
network.
B
If,
if
that's
how
you're
running
Firefly,
there's
lots
of
great
Tools
around
Firefly
as
well
such
as
sdks
command
line
tool,
that
is,
makes
it
really
easy
to
get
up
and
running
on
your
machine,
which
is
what
kind
of
what
I've
used
to
bootstrap
the
demo
that
we'll
look
at
here
in
a
little
bit.
It
is
designed
as
a
cloud
native
application.
B
So
it's
designed
to
be
run
in
containers
in
kubernetes,
in
the
cloud
or
or
in
your
own
Data
Center
and
has
you
know,
is
ready
to
go
with
things
like
Prometheus,
metrics
and
a
bunch
of
stuff
that
make
operational
work
around
it
really
great.
So
lots
of
cool
features
in
there
I'm
not
going
to
dig
into
every
single
box
there.
I
want
to
talk
a
little
bit
more
about
how
Firefly
works.
B
So
a
firefly
can
operate
in
two
different
modes.
One
is
called
Gateway
mode
and
one
is
called
multi-party
mode
and
I'll.
Preface
this
by
saying.
I
think
you,
just
as
you
know,
talks
that
the
maintainers
have
been
having
recently
right
now,
there's
a
pretty
hard
divide
between
Gateway
mode
and
multi-party
mode,
and
it's
somewhat
arbitrary.
B
So
I
imagined
a
future
version
of
firefly
I,
don't
know
what
version
number
that
will
be,
but
we'll
sort
of
blur
the
line
between
these
two
and
you'll
be
able
to
kind
of
pick
and
choose
features
from
from
either
one.
So
with
that
said,
Gateway
mode
today
is
you
can
think
of
it.
Like
hey
I
I
want
to
you
know.
B
I
have
my
company
and
I
want
to
write
an
app
that
my
end,
users
are
going
to
use
and
I
need
to
connect
to
either
a
public
chain
or
a
private
chain
and
I
don't
really
care
about
anybody
else
that
may
or
may
not
be
running
Firefly.
It's
just
I
just
need
a
way
to
access
a
blockchain
somewhere,
that's
Gateway
mode.
B
So
as
a
business
you
could
think
of
this,
is
you
know,
Firefly
I
install
as
a
piece
of
software
in
my
network
and
it's
sort
of
the
the
API
Gateway.
If
you
will
to
the
web,
3
world
and
I
could
use
it
as
a
control
Point
within
my
organization
that
you
know
anything
that
needs
to
access.
The
blockchain
goes
through
Firefly.
Anything
that
comes
from
the
web
world
to
my
apps
goes
through
the
blockchain
as
well.
B
B
All
right,
let's
talk
a
little
bit
about
multi-party
mode,
so
multi-party
mode
was
the
default
and
it
was
the
only
mode
that
was
available
when
Firefly
first
launched
and
the
the
original
use
case
that
Firefly
tackled
was
the
ability
to
to
have
what
we
call
these
multi-party
networks.
And
so
as
an
example,
you
might
have
several
different
organizations
all
in
the
same
in
the
same
business
or
in
the
same
sorry,
in
the
same
say
like
they're,
all
insurance
companies,
or
something
like
that.
B
Now
these
insurance
companies
they
need
to
work
together,
because
you
know
if
it's
a
car
insurance
company,
for
instance,
for
example,
you
know
a
client
from
company
a
gets
into
a
wreck
with
a
client
from
Company
B.
Well,
they
need
to
exchange
data.
They
need
to
agree
on
the
facts
of
what
happened.
Who
was
at
fault?
A
B
B
So,
in
this
case,
each
organization
can
run
a
firefly
node
and
they
can
use
the
blockchain
to
to
exchange
data
to
exchange
value
and
perform
their
business
transactions,
and
so
some
of
the
cool
things
about
the
the
multi-party
features
is
there's
a
great
messaging
feature.
That's
built
in
that's
really
fundamental
to
Firefly
the
ability
to
share
either
both
public
broadcast
messages
that
are
as
data
that's
shared
with
all
the
members
of
the
the
Consortium,
but
you
can
also
share
data
privately
as
well.
B
So
you
know,
maybe
you
wouldn't,
for
example,
you
wouldn't
want
to
share,
like
your
the
the
personal
contact
information
for
your
client
with
everyone
in
the
network,
but
maybe
the
other
organization
that
you're
working
with
needs
to
know
it,
so
they
know
they
can
match.
Yes,
this
is
the
person
that
we're
talking
about
and
We've
we've
both
agree
that
we're
both
talking
about
the
same
person.
So
there's
some
great
great
features
there
around.
B
You
know
what's
public
within
the
network,
what's
private
within
the
network
and
that
sort
of
thing
so
kind
of
behind
the
scenes
in
these
things.
Firefly
is
using
again
it's
it's
all
pluggable,
so
Right
Now,
the
default
implementation
for
a
the
shared
storage
bus
is
ipfs.
So
when
you
publish
something
in
Firefly,
the
payload
of
that
thing
goes
to
ipfs
by
by
default
it's
probably
a
private
ipfs
cluster.
B
That's
that's
only
accessible
by
the
organizations
that
are
in
the
that
Consortium
there's
another
component,
which
is
a
a
private
data
bus
using
a
a
software
component.
We
call
data
exchange,
it's
a
one
of
the
microservices
within
the
Firefly
architecture
and
that
will
transfer
either
messages
or
files
directly
peer-to-peer
from
different
organizations.
And,
lastly,
the
blockchain
itself
is
used
as
sort
of
the
the
layer
that
notifies
all
the
different
organizations
of
when
data
is
shared
and
it's
available.
B
Things
that
fireply
can
do
whether
it's
in
Gateway
or
multi-party
mode
is.
It
can
turn
a
smart
contract
into
a
set
of
easy
to
use
apis
complete
with
a
Swagger,
UI
and
Rich
documentation
of
all
the
inputs
of
each
of
the
functions.
So
that's
something!
That's
really
cool
I'm,
probably
going
to
skip
over
that
piece
in
My
Demo
today,
because
that's
been
extensively
demoed
in
a
lot
of
our
other
sessions.
B
If
you're
interested
in
seeing
that
sort
of
thing,
there's
some
great
recordings
on
YouTube
that
cover
that
already
that
that's
one
of
the
cool
features
that
Firefly
could
do,
you
could
just
upload
your
smart
contract
and
say
you
know
generate
me
an
API
that
I
can
use
from
this,
and
it
gets
makes
getting
up
and
running
with
with
a
custom
Smart
contract.
Really
quick
and
easy.
B
The
the
orchestration
engine
of
firefly
is
is
really
a
key
part
of
the
architecture
and
it's
it's
sort
of
it.
It
is
sort
of
the
the
thing
that
connects
all
of
the
different
pieces
of
firefly,
whether
that's
ipfs
Firefly's
local
database,
the
data
exchange
component
or
the
the
blockchain
itself,
and
so
it's
it's.
The
piece
that
has
the
context
for
all
of
those
different
things
it
is
designed
to
be
stateless
and
to
be
horizontally
scalable.
B
B
B
A
as
well
I
would
love
to
keep
this
interactive
as
we
go
all
right,
I
I
think
we've
I
think
we've
kind
of
talked
about
most
of
the
things
it
on
this
slide
already
actually,
but
I'll
just
cover
some
a
couple
of
the
the
quick
bullet
points
here
that
we
haven't
talked
about.
Firefly
can
handle
both
structured
and
unstructured
data.
It
has
you,
can
Define
data
types
in
it
for
so
you
could
say
you
wanted
to
find
like.
B
This
is
what
a
customer
looks
like
in
our
you
know
in
our
Network,
and
it
has
these
fields
and
these
ones
are
mandatory
and
here's
all
the
type
information
and
Firefly
can
can
validate
that
when
somebody
publishes
data
that
it
matches
that
schema.
So
it's
got
some
some
great
stuff
there,
we'll
get
into
we'll
actually
see
fireflies
token
and
digital
Asset
Management
in
live
in
action.
B
This
is
the
screen
that
we'll
look
at
we'll
save
that,
for
the
demo,
Firefly
has
a
really
cool
Explorer,
which
we'll
also
look
at
in
the
demo
again.
This
is
just
kind
of
these.
Are
things
we've
already
talked
about
on
the
slides
here,
but
just
making
sure
we
hit
all
the
highlights.
There's
great
developer
tools,
great
devops
tools,
the
Explorer
is
really
useful
for
kind
of.
Like
you
know,
hey,
hey,
I
I
did
something
in
Firefly.
What
happened
to
it?
Did
my
transaction
work?
Oh,
if
it
didn't
what
went
wrong.
B
Yeah
so
I
think
the
question
there
is
getting
at
like
can:
can
we
use
Firefly
to
talk
to
multiple
chains
and-
and
the
answer
is
yes,
absolutely
so,
just
real,
quick
on
on
kind
of
blockchain
interop.
There
are
several
projects
within
the
hyperledger
foundation
that
are
kind
of
within
the
realm
of
blockchain
and
and
interop.
So
you
had
the
the
cactus
project
and
then
the
Weaver
project
and
I
believe
those
joined
and
became
cacti.
B
Please
correct
me
if
I'm
wrong
on
that,
but
I
think
that's
I
think
I
got
the
aiming
right
there
and
those
those
projects
are
focused
more
on
the
integration
and
interop
at
the
Smart
contract
and
at
the
chain
layer.
Firefly
is
you
know.
Interop
is
not
the
primary
goal
of
firefly,
but
it
is
one
of
the
things
that
it
can
accomplish
and
in
Firefly
the
the
interop
itself
is.
It
happens
at
the
app
layer.
So,
basically
you
set
up
Firefly
with
different
blockchain
connectors
that
can
connect
to
multiple
chains.
B
At
the
same
time
they
can
both
deliver
events
to
your
application.
They
can
both
your
application
can
submit
transactions
to
both
chains
through
Firefly
and
it's
up
to
your
application
to
then
Define
the
rules
of
like
what
does
it
look
like
for,
say,
say
you
wanted
to
build
a
bridge
as
an
example.
A
firefly
is
not
a
bridge
in
and
of
itself.
B
I
just
want
to
make
that
clear,
but
you
could,
in
theory,
build
a
bridge
with
firefly
to
to
bridge
assets
from
one
chain
to
another,
but
it's
up
to
you
to
decide
for
your
use
case.
What
are
the
rules
around
when
I
move
tokens
from
one
chain
to
the
other?
When
do
I
burn?
When
do
I
went
how
how
do
I
make
sure
that
I
don't
get
duplicates?
B
B
B
So
we
did
that
a
couple
times
and
then
and
then
we
said
hey,
we
should
build
a
framework
that
does
this,
and
so
we
had
an
internal
framework
that
we
started
and
that
was
really
like
generation
one
and
and
then
we
said
hey.
This
is
really
powerful
and
we
think
it
could
be
even
more
powerful
if
it
was
open
source
had
a
huge
Community
behind
it.
B
We
had
our
our
1.0
release
in
April
of
22,
so
it
was
a
little
less
than
a
year
later
went
from
like
first
line
of
code
to
1.0
and
back
in
February.
We
just
released
1.2
and
we're
up
to
about
704
000
lines
of
code
when
I
looked
yesterday
in
the
the
Linux
Foundation
insights,
so
that
the
project
is
growing,
the
the
number
of
contributors
continues
to
grow,
which
is
super
exciting
and
I.
B
I,
just
love
to
I
love
to
tell
people
about
the
project,
I
love
to
to
invite
people
to
get
involved
and
yep.
There's
some
some
great
links
that
that
Quran
just
posted
there
I
appreciate
that
if
you
want
to
get
involved
in
the
project
I,
the
the
best
next
step
is
to
hop
into
Discord
join
the
Discord
link.
That's
there
and
there's
a
channel
called
Firefly
in
there
I'm
in
there
every
day
and
all
the
maintainers
are
in
there.
B
It's
it's
open
source,
it's
part
of
the
hyperledger
foundation,
so
it's
an
Apache
2
license
it's
very
Enterprise
friendly
and
is
designed
as
such
from
the
get-go
we'll
just
take
a
quick
peek
at
this
slide.
We've
talked
about
a
lot
of
these
things,
but
I
think
a
picture
helps.
So
this
is
sort
of
the.
This
is
a
really
high
level
view
of
the
architecture
of
all
the
different
pieces
that
go
into
hyperledger
Firefly.
B
Each
of
these
big
boxes
is
a
runtime,
so
you
know
kind
of
at
the
heart
of
firefly.
We
have
Firefly
core
and
it
has
a
bunch
of
different
parts
within
it.
That's
sort
of
what
these
little
boxes
represent.
It
has
an
API.
It
has
a
UI
that
hosts
it
has
smart
contract
generation
and
down
here.
It
has
all
these
plugins
that
talk
to
various
services,
so
the
various
services
that
it
talks
to
would
be
either
a
metric
service
which
is
optional
but
highly
encouraged.
B
Sql
Library
should
work
as
well
so
down
here
we
have
a
token
connector,
we'll
we'll
talk
a
little
bit
about
the
the
token
connector,
because
we'll
be
using
one
in
the
demo,
but
essentially
it's
designed
as
an
abstraction
layer
between
Firefly
and
the
blockchain
connector.
That
has
some
details
about
how
your
specific
token
contract
works,
and
so
you
may
want
some
some
special
features
about
your
particular
contract.
B
You
may
have
things
that
should
work
a
certain
way
or
certain
rules
about
how
you
how
tokens
work
in
your
app,
and
so
some
of
those
things
can
be
implemented
there
in
the
token
connector
down.
Here
we
have
the
the
blockchain
connector.
This
is
a
super
important
part
of
the
the
ecosystem.
There
is
a
framework
for
building
blockchain
connectors,
especially
if
you
are
building
it
and
go.
B
There's
a
library,
that's
provided
it's
called
the
Firefly
connector
toolkit,
and
it
has
like
80
of
what
you
need
to
build
a
blockchain
connector
for
Firefly
already
implemented
for
you.
It
provides
an
interface
of
functions
that
you
need
to
implement
for
your
specific
chain.
You
can
think
of
it
like
how
do
I
for
my
particular
blockchain.
B
What's
the
Syntax
for
submitting
a
transaction
or
what's
the
Syntax
for
querying
a
block
or
creating
an
event
listener
those
sorts
of
things
and
then
the
the
the
library
takes
care
of
a
lot
of
the
really
hard
logic
of
like
you
know,
estimating
gas
how
do
I
resub
like
when
and
and
how
do,
I
resubmit
transactions
and
sort
of
all
of
this
stuff
around
the
stuff?
That's
not
fun
to
implement
is
is
all
handled
by
the
library
there.
B
So
you
got
your
blockchain
connector
down
here,
that's
talking
to
either
public
chains
or
private
chains,
either
Fabric
or
ethereum
based
blockchains
there.
Our
data
exchange
connector
over
here
is
talking
to
some
sort
of
data
bus,
whether
that's
you
know
peer-to-peer
directly
with
another
data
exchange
connector
or
with
some
other
some
other
bus
there,
and
over
here
we've
got
the
the
shared
storage
plug-in
which
talks
to
ipfs
today.
B
So
that's
just
a
quick
highlight
of
the
the
different
runtimes
that
are
involved
in
Firefly
and
kind
of
the
different
pieces
and
areas
that
plugins
can
help
and
then
I
I
didn't
talk
about
the
top
of
the
diagrams,
we'll
touch
on
that
real,
quick.
So
up
here
at
the
top.
Obviously
you
have
your
application.
Your
application
can
use
fireflies
API
to
submit
transactions
and
it
can
listen
to
websockets
or
receive
web
hook.
B
Just
real
quick
on
the
most
recent
update,
there
were
some
some
really
cool
things
in
there.
We
we
had
some
really
expanded
support
for
tokens
and
the
token
connectors
and
the
token
plug-in
in
Firefly
became
a
lot
more
flexible,
and
so
so
now
today,
you
can
go
to
the
open,
Zeppelin
wizard
and
create
a
a
your
own
smart
contract.
B
I
think
it
was
like
a
month
or
two
ago.
I
did
a
work,
a
couple
hour
workshop
on
how
to
do
this.
So
that's
on
YouTube
as
well.
If
you're
interested
in
that
like
how
to
launch
your
own
token
from
scratch
with
firefly,
you
can
just
go
click
through
the
wizard
and
have
it
generate
the
starting
point
of
your
contract
and
then
use
that
with
firefly
and
launch
that
on
a
public
chain,
a
lot
of
other
features
around.
B
Just
you
know:
quality
of
life
improvements
a
lot
of
things
for
for
operations,
better
traceability
through
the
system,
custom
header
pass
through
the
you're,
just
better,
better
feedback
on
the
API.
That
sort
of
thing,
the
other
big
thing
it
was
more
of
a
symbolic
thing
than
anything
was
evm.
Connect
is
Now.
The
default
connector
when
you
create
a
new
Firefly
stack
and
that's
just
sort
of
a
like
I,
said
a
symbolic
thing
of
us
sort
of
declaring
to
the
world
that
your
evm
connect
is
ready
for
prime
time
now.
B
It
is
the
the
newest
of
all
of
the
three
blockchain
connectors
that
Firefly
has
today.
There
are
two
for
ethereum
and
one
for
fabric
evm
connect
is
now
the
Preferred
Choice
and
should
do
everything
that
you
need
that
that
ethnic
could
do
but
better,
because
it's
it's
newer
and
we
learned
a
lot
along
the
way
with
each
connect,
which
is
actually
it's.
The
the
oldest
piece
of
the
Firefly
architecture
that
predates
Firefly
core
itself.
B
B
B
This
is
kind
of
a
great
transition
point,
I'll,
take
a
few
questions
and
then
and
then
we'll
hop
over
to
a
quick
demo.
So,
let's
see
somebody
asked,
can
I
use
Firefly
as
a
bridge
for
communicating
between
Fabric
and
a
basic
Network
sure
like
I
said
Firefly
is,
is
not
a
I.
I
have
to
be
careful
when
we
talk
about
bridges,
because
if
you
talk
about
bridges
and
you
don't
get
it
right,
the
trolls
come
out
from
underneath
the.
B
Not
our
Bridge
Works,
so
I
always
like
to
preface
this
by
saying:
Firefly
is
not
a
bridge
it
is.
It
does
give
you
the
pieces
that
you
probably
need
to
build
a
bridge,
though,
and
so
so,
like
I
said
it,
you
could
set
up
Firefly
to
connect
to
both
a
hyperledger
fabric,
Network
and
the
basic
Network
at
the
same
time,
and
then
you
could
have
one
app,
that's
that
is
at
that
point,
able
to
talk
to
both
chains
and
can
Define
the
rules
for
like
okay.
Well,
how
do
I?
B
B
What
can
you
recommend
in
order
to
run
Firefly
in
a
production?
Cloud
environment
such
as
self-hosted,
Cloud
I,
would
highly
recommend
kubernetes
it's.
What
Firefly
is
designed
to
run
with
it's?
What
we
at
collido
run
Firefly
with
there,
are
some
Helm
charts
in
the
open
source
repo
that
provide
you
kind
of
a
starting
point
for
getting
all
the
different
Services
up
and
running,
and
you
can
excuse
me,
you
can
customize
those
from
there.
B
B
B
B
There's
some
great
instructions
on
on
how
to
set
it
up
here.
So
if
you
want
to
go
try
this
out,
this
is
the
place
to
start
basically
I
got
it
installed
and
then
I
went
down
to
tutorials
connect
to
remote,
blockchains
and
I.
I
went
to
the
polygon
test
net
and
then
so
I
followed
this
guide
to
set
up
a
firefly
stack.
Here's
the
the
really
important
bits
here,
which
is
how
to
configure
Firefly
to
talk
to
polygon,
testnet,
and
so
so.
I
am
connected
to
the
test.
B
B
B
So
you
could
think
of
like
an
nft
can
represent
a
collectible
item
or
it
could
represent
a
it,
could
represent
some
sort
of
credential
or
or
something
that
you've
earned
or
something
like
that,
and
so
to
get
these
contracts.
What
I
did
is
I
went
to
the
the
token
connector
for
hyperledger
Firefly
I
went
into
the
solidity
samples
here
and
you
could
find
the
source
code
for
these
here,
they're
under
contracts
and
here's
here's
the
source
code
for
them.
B
So
here's
the
here's,
the
erc20
that
I
deployed
it
extends
the
the
open,
Zeppelin
erc20,
and
you
can
go
check
out
the
source
for
these.
If
you
want
to
here's
the
erc721,
which
is
the
non-fungible
token
contract,
and
so
so
I've
deployed
those
and
set
them
up.
So
the
reason
I'm
going
fast
through
this
is
there's.
There
have
been
lots
of
great
videos
already
on
YouTube
on
like
how
to
set
this
stuff
up.
B
The
thing
that
I
really
want
to
demonstrate
today
is
like
the
power
as
a
developer,
that
having
all
this
stuff
gives
you
to
like
how
easy
it
makes
it
to
build
an
app
with
all
this.
So
so
I'll
walk
you
through
a
little
bit
more
of
what
I
have
running
here.
So
I
just
ran
yep
I'll
make
this
a
little
bigger,
so
I
ran
FF
start
to
start
up.
My
Firefly
stack
said:
okay,
here's
your
URL
for
your
web
UI.
B
So
if
we
go
there
here
is
our
our
Firefly
Explorer
UI,
and
we
can
see
that
you
know
I've
been
doing
some
stuff
here.
This
was
me
last
night,
setting
all
this
up
and
testing
it
and
failing
a
couple
times
and
then
and
debugging
and
and
going
back
through
it,
but
this
is
the
dashboard.
So
if
we
go
down
here
to
the
Token
section,
we
see
there
are
two
token
pools
that
have
been
configured.
So
we
can
click
on
that.
Here's,
my
fungible
token
pool
and
my
non-fungible
token
pool.
B
B
This
is
my
my
metamask
wallet
and
I
also
have
I,
have
a
wallet
app
on
my
phone
that
I've
set
up
here,
which
I
will
show
you
in
just
a
second
we'll
get
that
we'll
get
that
screen
share
going
in
just
a
second
I'll
pull
it
up,
so
you
can
see
that
Wallet
app
okay,
so
so
I've
got
these
two
token
pools
and
I've
got
these
two.
Oh,
the
other
thing
I
wanted
to
show
you
was
was
where
they're
at
on
chain.
B
So
here's
here's
the
address
so
if
I
take
this
address
and
I
go
to
polygonscan.com,
make
sure
I
switch
it
to
test
net
and
I
can
paste
this
address
in
minus
the
quotation
marks
there
and
here's
my
contract,
okay
and
I
can
see
all
of
the
the
transfers
that
have
happened
on
that
contract
and
again.
This
is
just
me
testing.
It
here
so
so
that's
one
of
them.
Let's
go!
Look
at
the
just
so
I.
Have
these
tabs
open,
I'm
gonna
go
look
at
my
fungible
contract.
B
Sorry,
the
non-fungible,
the
nft
contract
open
a
new
tab
and
look
up
that
one
as
well
all
right
cool.
So
there's
been
one
one
transaction
here,
and
this
was
me
testing
it
last
night.
This
was
here
was
the
contract
as
it
was
created
in
this
transaction,
and
here
was
the
one.
The
one
test
run
that
I
did
nine
hours
and
36
minutes
ago.
Okay,
so
so
that's
kind
of
those
are
the
contracts
that
we
have
there.
B
The
app
that
I
wrote
is
say:
I
wanted
to
to
build
an
app
that
can
can
listen
for
receiving
some
funds
and
it's
going
to
receive
those
funds
as
as
a
fungible
token
and
and
then
what
happens
is
if
somebody
gives
you
enough
tokens,
then
you
mention
them
in
nft
and
send
it
back
to
them.
So
I
I
basically
built
a
a
small
exchange
that
can
can
it's
a
very
trivial
exchange,
but
it
does
it
exchanges
some
erc20
tokens
for
a
single
nft
token,
and
so
to
do
that.
B
I
just
wrote
a
little
bit
of
code
and
I'll
show
you
how
little
code
this
is
here.
It
is
40
lines
of
code,
and
a
lot
of
this
is
just
declaring
variables
walk
you
through
what
I
wrote
here.
This
is
going
to
be
a
very
code,
heavy
demo
and
then
in
a
second
we'll
push
go
but
I
wanna,
I
wanna
talk
you
through
the
code
to
show
you
everything
that's
going
on,
so
this
is
typescript.
B
You
can
use
JavaScript,
though
it's
and
you
don't
even
have
to
use
JavaScript.
You
could
use
whatever
language
you
want
to
access.
The
the
Firefly,
API
and
websocket
connections.
Typescript
and
JavaScript
are
easy
because
we
already
have
a
pre-packaged
SDK
ready
to
go,
that's
really
easy
to
use
and
it
comes
it's
it's
built
with
typescript.
So
it
comes
with
type
definitions.
B
It
also
has
a
websocket
listener,
a
websocket
client
built
into
the
library,
which
is
just
it's
super
easy
to
get
up
and
going
so
I'll
walk
you
through
what
we're
doing
here.
So,
first
of
all,
we're
gonna
we're
gonna
initialize,
the
SDK
and
I'm
running
everything
locally.
So
it's
going
to
be
on
localhost
Port,
5000.,
I
just
filled
in
a
couple
of
constants
here
with
the
IDS,
from
my
my
token,
pools,
which
I
got
by
going
to
the
Firefly
Explorer
and
going
to
the
my
token
pools
and
looking
these
up.
B
B
You
could
say
FF
accounts
list
and
then
the
name
of
the
stack
I'm
just
going
to
grab
by
the
address,
and
then
there
that's.
The
account
address
that
my
Firefly
node
is
using.
This
is
the
one
that
I
had
to
fund
with
somatic,
and
this
is
this
represents
me
and
my
Firefly
node,
okay
and
then
I
just
declared
a
variable
for
like
how
much
I
want
the
nft
to
cost
and
I
just
said
10..
So
you
send
me
10
erc20
tokens
on
my
my
fungible
pool
I'll.
B
Send
you
one
nft
back
on
the
non-fungible
pool.
Okay,
so
then
I'm
gonna
create
a
a
subscription
and
I'm
going
to
filter
that,
based
on
token
transfers,
so
Firefly
can
emit
lots
of
different
types
of
events.
The
thing
that
I'm
most
interested
in
here
are
token
transfers,
and
so
we're
going
to
filter
based
on
that
then
I
just
say:
Firefly,
listen
on
my
subscription
that
I've
set
up,
and
then
you
get
this.
Basically,
you
get
a
callback
function
here
that
you
put
in,
and
this
is
your
function
that
runs
anytime.
B
That
listener
has
an
event
or
that
subscription
has
an
event,
and
so
what
I'm
going
to
check
here
is
if
the
event
type
is
a
confirmation
on
the
token
transfer
and
we're
already
at
this
is
probably
redundant,
because
we're
already
filtering
by
that
we
could
probably
get
rid
of
that.
But
if
we
are,
if
the,
if
the
token
pool
is
the
fungible
pool-
and
it's
to
me,
is
basically
what
I'm
looking
here
so
this
this
event
listener
will
get
fired
for
every
token
transfer
that
happens
on
the
pools.
B
That
Firefly
is
watching
so
it'll
happen
for
when
I
send
a
token
or
when
somebody
else
sends
me
a
token.
So
we
just
have
to
make
sure
that
we're
looking
at
okay
is
it.
Is
it
fungible
tokens
that
we're
looking
at
and
are
they
to
me?
Otherwise
we're
going
to
ignore
it
and
then
then
we
look
at
is
the
the
quantity
yeah
well,
so
so
I
just
real
quick
on
why
we're
dividing
by
10
to
the
18th
here
quick
side,
tangent
and
I
realize
we're
running
out
on
time.
B
So
I'm
going
to
try
to
go
fast,
but
ethereum
virtual
machines
only
they
don't
do
decimal
math,
so
basically
to
do
fractionalized
tokens.
What
you
do
is
you
add
a
bunch
of
decimal
places
to
it.
So
behind
the
scenes
like
one
nft
may
have
or
sorry
one
fungible
token
may
have
18
zeros
behind
it,
that
that
number
is
defined
by
the
contract.
In
my
case,
it's
18.
B
so
I'm
dividing
by
10
to
the
18th
here
to
just
to
log
the
the
whole
number
rather
than
like,
with
all
the
decimals
behind
it.
Okay,
so
that's
what
that's
about
I
will
log
how
much
they
sent
us
and
if
the
quantity
is
greater
or
equal
to
the
cost
that
we
defined
up
here,
then
we
will
mint
an
nft
in
our
non-fungible
pool,
we'll
Mint
one
and
we
will
send
it
to
whatever
account
originally
sent
us
those
tokens.
Okay.
B
B
I'm
gonna,
so
so
my
my
fungible
tokens
are
called.
We
really
put
the
fun
and
fungible
here
so
they're
called
Fun
tokens
I'm
going
to
send
some
and
then
I
need
to
get
my
address
of
my
Firefly
node.
The
easiest
way
to
do
that
is
because
I
don't
like
typing
out
really
long.
Hex
numbers
is
to
go,
find
it
on
polygon
scan,
and
this
is
me
and
I'm
going
to
get
the
QR
code
for
it.
C
B
Gas
hit
confirm
it's
asking
me
for
my
fingerprint:
that's
why
the
screen
went
black
there.
Okay,
no
thanks
all
right!
So
the
transaction's
in
progress,
that's
great!
It's
pending
transaction!
Let's
go
back
here
and
watch
our
app,
so
we
received
well
clearly
I
did
my
math
wrong
there
in
the
logging,
but
but
we
received
some
and
it
was
greater
than
the
cost,
and
so
we
minted
an
nft,
that's
cool!
B
B
Yep,
so
there's
one
and
two
I
had
one
from
my
test
last
night
and
now
I
have
two
as
well
so
so
you
just
saw
in
real
time
there.
My
wallet
app
running
on
my
phone,
interacting
with
a
contract
on
a
public
chain
Firefly,
saw
those
events
emitted.
Those
events
to
my
application,
my
application
decided
yep.
You
have
earned
an
nft
and
invented
it
and
sent
it
back
to
my
wallet.
App
and
I
did
all
of
that
in
40
lines
of
code.
B
B
I
can
see
here
here
is
my
transfer
that
I
sent
from
my
my
phone
and
here's
the
transfer,
here's
the
mint,
the
my
app
did
to
send
back
to
my
phone
as
well.
You
can
see
all
the
details
there,
so
that's
it
for
the
demo.
Hopefully
this
was
a
good
use
case.
Hopefully
you're
able
to
follow
that
it
was.
This
is
a
little
bit
of
a
different
style
demo
than
we've
done
in
the
past.
B
B
That
I
can
focus
on
what
are
the
rules
around
how
I
want
this
exchange
of
value
to
work
and
Firefly
can
handle
all
of
the
the
really
challenging
nitty-gritty,
stuff
and
and
all
the
plumbing
that's
required
to
get
all
of
that
done.
So
that's
it
for
the
demo.
Today
we
have
a
few
minutes
left
and
I
would
be
happy
to
to
take
a
q
a
for
the
rest
of
the
time,
but
but
thank
you
so
much
for
for
watching
and
coming
out
to
today's
session.
I
really
appreciate
it.
C
B
Manage
the
using
Firefly
with
fabric
I
think
it
really
comes
down
to
what
are
the
the
needs
of
your
specific
use
case?
What
are
the
needs
of
your
organization
and
whether
Firefly
sorry
weather
fabric
is,
you
know,
meets
meets
those
needs,
whether
it's
you
know
so
fabric,
for
instance,
one
big
difference
is
the
the
use
of
channels
and
and
the
isolation
of
channels
between
different
members
and
and
how
chain
codes
are
specific
to
channels.
So
so
maybe
for
your
particular
application.
B
B
B
Can
you
please
elaborate
on
how
you
can
generate
the
rest,
API
Swagger
from
the
apps
you
created
in
Firefly,
yeah
there's.
Let
me
I'll
share
my
screen
here:
real
quick
again
and
there
there's
some
tutorials
on
this
in
the
docs.
But
if
you
go
to
the
docs
page,
the
docs
site
and
then,
if
you
go
under
tutorials
and
work
with
custom
Smart
contracts,
ethereum
is,
is
the
one
that
has
the
the
generator
from
you
can
go
from
an
ABI
all
the
way
to
a
a
working
API.
B
But
if
you
just
follow
this
guide,
it
will
show
you
all
here:
here's
a
just
a
really
trivial
sample.
Smart
contract
walks
you
through
how
to
deploy
it,
how
to
how
to
create
the
Firefly
interface
and
Define
that
and
then,
if
we
scroll
all
the
way
to
the
bottom
yep,
then
you
end
up
with
the
the
Swagger
UI
at
the
end,
and
you
could
view
that
right
in
your
browser,
you
could
click
through
and
actually
use
it
right
here
in
your
browser.
So
this
is
a
great
guide
to
that.
B
Do
people
use
Firefly
as
a
dashboard
for
a
fabric,
blockchain
I'm,
not
sure
it's
a
good
question
I
haven't
heard
of
anyone
doing
that,
specifically
the
the
Firefly
Explorer
is
not
necessarily
meant
to
be
a
an
all-purpose,
blockchain
Explorer.
It's
really
meant
to
be
looking
at
sort
of.
What's
what's
going
on
inside
my
Firefly
node
and
with
my
apps
that
I
have
running
on
it.
A
B
A
B
B
B
All
right,
we
are
at
time
but
I'm
happy
to
take
any
other
questions
that
folks
may
have
I
have
a
few
minutes
to
spare.
If,
if
folks
want
to
hang
out-
and
you
have
more
questions
otherwise,
if
I
would
love
to
to
two
requests,
if
you
thought
this
demo
was
cool,
if
you
could,
if
you
could
go
to
GitHub,
slash
hyperledger,
slash,
Firefly
and
come
here
and
push
the
star
button,
this
is
my
thank
you
for
watching
my
YouTube
video.
Please
like
And
subscribe.
B
It
just
helped
boost
the
project
a
little
bit
and
I
would
we'd
love
to
get
some
more
stars
on
it.
So
if
you
thought
this
is
great,
we
would
really
appreciate
that
and
if
you
want
to
keep
talking,
please
join
Discord
and
would
happy
be
happy
to
continue
the
conversation
there.
If
you
have
more
questions
or
want
to
get
plugged
into
the
project,
I
would
love
to
to
chat
with
you
all
there,
but
I
think
that
is
it.
Thank
you.
So
much
everyone
and
I
really
appreciate
you
coming
out
today.