►
From YouTube: Hyperledger FireFly Overview: The SuperNode for Enterprise Web3 Apps - Steve Cerveny & Nicko Guyer
Description
Hyperledger FireFly Overview: The SuperNode for Enterprise Web3 Apps - Steve Cerveny & Nicko Guyer
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. In this session, Kaleido CEO Steve Cerveny will explain why SuperNodes are critical to enterprise web3 adoption and explain how Hyperledger FireFly helps enterprises: -Accelerate Development – build Web3 apps faster with a rich stack of native Web3, B2B, and integration services -Automate Deployment – deploy and manage many apps on the FireFly platform from a single console -Run at Scale – Connect to the multi-chain and multi-protocol Web3 world on a scalable, cloud-native platform built as microservices on Kubernetes Hyperledger FireFly community lead Nicko Guyer also shared a live demo showing how easy it is to get up and running on FireFly.
Sessions Details & Slides (if available): https://sched.co/14H6G
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
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
A
Can
you
raise
your
hand
if
you're
somewhat
familiar
with
what
Firefly
is
and
what
problem
it's
solving
and
how
it
could
help
okay,
awesome
you're
in
the
right
place,
let's
jump
in
then
my
name's
Steve
and
I'll
be
covering
the
first
half
I'll.
Take
you
through
some
slides
a
overview
of
Firefly
and
then
Nico
my
teammate
who's.
One
of
the
Firefly
maintainers
is
going
to
drive
a
live
demo
and
we'll
see
what
the
demo
gods
have
in
store
for
us
today.
A
Yeah
so
I
just
said
overview
demo.
Hopefully
we'll
have
some
q
a
time
and
if
not,
we'll,
hang
out
up
front
to
chat.
So
big
big
picture
right
over
here
on
the
right
is
the
the
Wild
Wonderful
World
of
web3
we've
kind
of
decomposed
it
into
some
different
bubbles.
That
probably
makes
sense
to
you
over
on
the
left.
A
Is
your
Enterprise
right,
the
company
that
that
you
work
with
and
you
have
a
set
of
existing
systems
and
you
want
to
build
a
web
3
application
and
what
this
has
looked
like
before
Firefly,
which
I'm
calling
the
Gen
1
era
of
of
web
3
of
Enterprise.
Blockchain
of
you
know
your
these
early
blockchain
applications
is
to
connect
out
to
web3
really
a
lot
of
the
Gen
1
is
focused
on
that
Consortium
bubble
up
there,
and
to
do
that,
you
may
have
stood
up
your
own
blockchain
nodes.
A
You
may
have
used
a
cloud
vendor
service
or
a
service
from
collido
or
a
company
like
us.
There
was
a
web
3
infrastructure
provider,
so
you
got
the
node
great,
but
actually
you're
only
five
percent
of
the
way
there
right,
because
your
application
the
little
bubble
the
web
three
applications
that
you
want
to
build,
still
need
a
whole
lot
of
software,
a
whole
lot
of
code
written
to
get
your
end-to-end
solution
up
and
that
code
is
pretty
web
3
specific
code.
You
need
to.
A
You
need
to
solve
a
lot
of
problems
and
I'll
I'll
get
into
that
in
a
second.
By
contrast,
Firefly
has
come
along
for
for
Gen
2.
and
in
Gen
2
building
your
web
3
applications
is
a
whole
lot
simpler.
Not
only
that,
but
Firefly
can
help
you
to
do
more
than
just
B2B
Consortium
style
blockchain.
It
can
help
you
connect
out
to
public
chains
and
and
do
lots
of
other
things
in
the
the
web
3
space.
This
is
a
lot
more
scalable
approach.
A
A
You
know
we
just
saw
that
there
was
an
opportunity
for
a
new
open
source
project
to
accelerate
and
drive
standardization
across
the
board
and
and
one
thing
that
we
noticed
that
if
you
look
first
on
the
right
hand
side
of
this
slide,
you
know
what
Firefly
is
not.
Is
it's
not
another
blockchain
protocol?
We
think
the
world
has
enough
of
those.
A
Custom
one-off,
almost
as
a
side
effect
of
trying
to
build
your
app,
you
had
to
build
the
whole
stack
and
it
was
just
really
inefficient,
and
so
you
know
the
clotto
actually
seated.
As
with
an
initial
contribution
into
hyperledger.
Now
many
organizations
are
involved.
It's
a
very
quick
growing
project,
moving
forward
to
give
you
an
example
of
some
of
the
some
of
the
complexity
around
building
your
application,
many
of
the
considerations
around
how
to
build
a
decentralized
architecture
into
your
application.
A
Idiosyncrasies
of
of
the
protocol
how
to
handle
privacy.
You
know
the
orchestration
of
transactions
on
these
event-driven
systems
doing
that
reliably,
seeing
a
transaction
through
end
to
end.
You
know
these
are
pretty
hard
problems
and
Firefly
handles
them
out
of
the
box,
and
so
you
now
have
the
wisdom
of
the
herd
of
lots
of
other
companies.
You
know
using
this
code
hardening
it
all
the
benefits
of
an
open
source
project.
Firefly
is
multi-protocol,
as
you
see
on
the
right,
so
you
know
we
sometimes
say
we're
not
trying
to
be
religious
here.
A
This
is
a
a
logical
architecture
for
Firefly.
You
can
see
at
the
middle
of.
It
is
the
core
that
orchestration
engine
again
blockchains
are
event
driven
systems,
and
so
just
the
complexity
of
getting
a
transaction,
maybe
into
a
pending
pool
mined
into
a
block
written
to
a
chain.
You
know
and
understanding
that
whole
process,
your
application
not
having
to
deal
with
that,
is
a
big
relief
to
the
developers
on
your
team
right.
So
the
orchestration
engine
at
the
core
of
that,
but
you
can
see,
there's
a
whole
framework
of
functionality.
That's
that's
built
around
that.
A
A
So
what
we
see
a
lot
of
times,
especially
in
Enterprise
applications,
is
not
just
on-chain
activity
but
off-chain
activities
as
well.
For
example,
data
exchange
going
from
B
to
B
and
there's
a
whole
set
of
apis
and
patterns
for
how
to
coordinate
off-chain
and
on-chain
activities.
Those
are
called
flows
and
then
finally,
digital
assets,
so
in
in
API
pillar
around
making
interacting
with
digital
assets
easy
and
simple.
A
So
I'm
going
to
step
through
a
couple
of
these
Concepts
and
in
just
a
little
more
detail
and
then
we'll
get
on
to
the
demo
on
that
first
pillar
of
apis.
The
building
your
apps.
So
one
of
the
things
that
Firefly
does
it's
pretty
cool
is
you
can
teach
Firefly
about
the
smart
contract
that
you've
written?
A
And
so,
when
you
feed
in
your
smart
contract
into
Firefly,
it
hands
you
back
a
set
of
rest
apis,
so
that
when
you
build
your
application,
you
can
just
code
to
rest
apis
and
that
allows
any
developer
on
your
team
to
build
web3
apps
and
the
web
3
specialty
then
is
constrained,
adjust
or
it's
isolated
just
to
the
developer.
Who's
writing
the
smart
contracts.
This
allows
your
team
to
scale
and
and
get
Solutions
out
more
quickly.
A
So
another
concept
here
is
acting
as
a
gateway,
so
once
you've
once
you're
coding
to
these
simple
apis,
you
can
rely
on
the
orchestration
engine.
That's
inside
of
firefly
to
do
all
the
heavy
lifting
for
you.
So
so
you
say:
hey
I
want
to
Mint
this
token
or
I.
I
want
to
put
this
transaction
onto
the
chain
and
then
the
100
000
lines
of
code
of
firefly
that
manage
these
sorts
of
things
kick
in,
and
you
know
this
again:
Firefly
can
connect
to
multiple
chains.
A
A
So
things
like
ipfs
for
a
shared
storage
layer
and
then
it
also
a
a
peer-to-peer
messaging
layer.
So
so
Firefly
can
connect
or
gate
org
b
in
a
private
Channel
off
chain
to
exchange
data
or
or
data
or
D,
in
a
private
channel
to
exchange
data
and
so
forth
and
Firefly
has
an
address
book
built
into
it
as
well.
So
all
the
different
identities,
public
private,
key
pairs.
All
of
that
is
made
simple
for
you
within
the
Firefly
engine.
A
A
A
So
I
was
mentioning
a
minute
ago.
Things
like
the
history
tracking
automatically
tracking
the
history
of
a
token.
So
if
you,
if
you
meant
a
token
through
the
the
API
it
automatically
gets
registered
in
the
the
database,
that's
part
of
the
Firefly
stack
and
that
token
history
is
tracked
for
you.
You
can
also
Point
Firefly,
for
example,
at
a
public
chain
and
a
token
that
already
exists
and
say:
hey,
pull
in
all
the
history
of
this
token
and
track
it
going
forward.
A
So
almost
like
an
audit,
Trail
or
or
the
the
lineage
in
the
history
of
a
token,
and
then
you
have
an
efficient
way
to
query
that
going
forward.
As
you
know,
blockchains
can
be
pretty
slow
when
you
ask
them
questions
they're,
not
really
optimized
or
designed
for
that,
and
so
having
all
that
state.
A
track
for
you
in
a
efficient
and
fast
query
way
can
be
pretty
handy
and
then
on
wallets.
If
you're
in
the
financial
services
space
wallets
are
a
pretty
big
deal
tend
to
call
the
space
custody,
you
know
who's.
A
Managing
the
keys
and
and
Firefly
comes
similar
to
many
areas
of
firefly.
It
comes
with
an
a
wallet
or
implementation
for
that,
but
it's
also
designed
to
be
pluggable,
so
the
community
is
looking
at
things
like
well,
you
know
what
what
about
what
are
some
popular
wallets
out
there
and
can
we
have
plug
points
or
Integrations
in
into
those
into
all
of
those
wallets?
It's
something
again.
That's
important
for
institutional
scale,
I
think
we're
going
to
do
a
questions
at
the
end,
just
due
to
the
time.
A
Okay,
I'm
gonna
skip
forward
just
a
bit
here
and
there
are
out
on
YouTube
longer
form
overviews
of
this,
but
I
did
want
to
touch
on
Firefly
1.1,
so
so
coming
out
this
week
is
Firefly
1.1
sort
of
time
to
the
event
they're
a
cute
cool
few
new
things
that
I
want
to
touch
on.
Just
for
a
second
to
give
you
an
idea
of
the
the
history
of
the
project,
it
was
launched
initially,
as
a
hyperledger
lab
mid
2021.
A
It
was
then
promoted
a
few
months
later
to
project
status
within
a
hyperledger
again
due
to
the
amount
of
interest
and
activity
and
and
engagement
through
the
community
Firefly.
At
this
this
it
was
seated
by
code
from
collido,
which
really
was
several
years
old
and
things
that
we've
was
already
in
production
code
that
we
used
for
for
a
number
of
our
clients
projects.
A
It
moved
to
1.0
status,
this
last
April,
essentially
reaching
ready
for
for
a
production,
use
or
or
acknowledged
for
production
use,
and
then
just
just
this
week,
Firefly
1.1
is
being
cut
as
it
stands
today.
There's
19
repos
and
about
a
quarter
million
lines
of
code
and
growing
over
a
thousand
new
commits
came
in
between
1.0
and
1.1,
so
a
very
active
and
growing
project.
B
A
Both
can
can
be
can
run
in
either
Consortium
mode
or
Gateway
mode.
The
idea
with
Gateway
mode
is
that
you
can
connect
out
to
many
different
chains
and
and
have
Firefly
act
as
a
Gateway
for
all
of
those,
in
conjunction
with
that,
Firefly
now
knows
how
to
connect
to
a
number
of
public
blockchains
through
a
a
new
connector
in
the
connector
framework
layer
called
evm
connect.
So
if
you're
familiar
with
the
ethereum
VM,
any
evm
based
chain
Firefly
now
knows
how
to
connect
with
and
the
additional
complexities
of
public
blockchains.
A
A
There
are
a
number
of
guides
in
the
docs
for
things
like
polygon
and
optimism
arbitrum,
you
know
ethereum
itself
and
more
name
spaces,
so
so
Firefly
now
can
run
multi-tenant.
So
what
we've
seen
in
large
organizations
is,
you
have
different
teams,
building
different
use
cases
and
you
want
to
keep
those
isolated
and
and
now
on
on
Firefly.
A
There's
a
degree
of
isolation,
that's
called
namespace,
which
you
know
for
if
you're
familiar
with
things
like
kubernetes,
that's
you
know
an
isolation
technique
on
on
a
lot
of
tools,
and
now
now
it's
there
on
Firefly
there's
a
new
connector
toolkit.
So
it's
really
easy
to
build
your
own
connector.
The
community
is
looking
at
self-service.
I
know
that
there
are
teams
out
there
looking
to
contribute
a
connector,
hey
we're
a
layer
one
chain.
It
would
be
great
if
Firefly
could
connect
to
us.
A
C
C
Is
this
Mike
on?
Can
you
guys
hear
me?
Okay
out
there?
Okay,
great
hello,
everyone?
My
name
is
Nico
Guyer
I'm,
a
maintainer
on
hyperledger
Firefly
and
the
open
source
Community
leader
I'm.
Also
a
software
engineer
at
collido
and
I'm
really
excited
to
talk
about
Firefly
1.1
and
some
of
the
really
exciting
new
features
in
it.
Today,
I
see
a
couple,
people
have
come
in,
there's,
there's
still
some
seats
if
you
guys
want
to
take
a
seat
you're
more
than
welcome
to
so
thank
you
Steve
for
the
the
great
overview
on
on
Firefly.
C
Jim
Zhang
gave
a
great
session
on
Fab
connect
a
little
bit
ago
and
how
it
makes
using
hyperledger
fabric
easier
and
providing
a
nice
API
layer
for
it.
It's
also
a
blockchain
connector
for
hyperledger
Firefly,
so
so
my
Firefly
core
talks
to
fabconnect,
which
talks
to
a
fabric
Network,
that's
also
running
on
my
laptop
I've,
set
this
network
up
like
a
Consortium.
So
there
are
actually
multiple
super
nodes
running
on
my
machine
that
represent
other
organizations.
So
you
have
many
different
organizations,
collaborating
with
this
same
fabric
Network,
and
we
can
exchange
data.
C
We
can
pin
data
to
the
blockchain.
We
can
privately
exchange
data
all
through
our
super
nodes,
and
so
this
is.
This
is
an
example
of
what
Firefly
has
done
since
launch,
which
is
allowing
you
to
build
a
Consortium
that
uses
blockchain
as
an
integration
point
or
a
multi-party
network,
as
you
may
have
heard
us
call
it
sometimes.
So
how
does
this
change
in
1.1?
Well,
Steve
mentioned
that
now
you
can
have
multiple
namespaces
simultaneously.
C
So
here's
the
rest
of
my
demo
I'm
going
to
be
using
the
same
database
I'm
using
the
same
Firefly
super
node,
but
I'm
actually
going
to
also
be
connecting
in
a
different
namespace
to
an
evm
connect.
Blockchain
connector,
which
Steve
also
mentioned,
is
the
new
evm
compatible
blockchain
connector
for
Firefly.
It
uses
a
new
open
source,
ethereum
signer
called
Firefly
signer,
it's
a
an
Apache
2,
very
Enterprise
friendly
license
and
it's
available
as
part
of
the
it
can
be
used
Standalone
or
it
can
be
used
as
part
of
firefly
as
well.
C
This
stack
is
actually
connected
to
the
polygon
Mumbai
test
net.
So
what
I'm
going
to
demonstrate
is
being
able
to
run
transactions
privately
in
my
fabric,
Consortium
Network,
and
also
interact
with
tokens
or
execute
other
smart
contract
functions
on
a
very
public
permissionless
polygon
testnet.
So
hopefully
that
makes
sense.
C
I
I,
think
things
make
more
sense
like
seeing.
Pictures
is
great
but
I
like
seeing
things
in
action
more.
So
let's
actually
do
it
all
right,
so
I'm
gonna,
I'm
gonna
slide
over
here
and
okay.
So
this
is
I've
got
two
different
colored
browsers
to
represent
two
different
Firefly
nodes:
two
different
organizations
in
my
network,
so
over
here
you
can
see
in
the
right
hand,
corner
I've
got
node
one,
and
over
here
I've
got
node
zero
and
they're,
just
color
coded,
so
you
just
visually.
So
you
can
see
the
difference.
C
If
you
look
closely
you'll
notice,
the
the
the
port
number
is
different,
so
I'm,
because
I'm
running
two
different
super
nodes
on
my
computer
to
simulate
an
entire
Consortium
running
here,
so
I
can
build
apps
and
use
the
Consortium.
So
if
you've
seen
a
firefly
demo
before
I'm,
just
going
to
very
briefly
touch
on
some
of
the
things
you
can
do
with
firefly,
the
Firefly
command
line
interface
has
set
all
this
up
for
me,
I'm
happy
to
chat
through
how
that
works
later,
but
it
takes
some
I
wanted
to
skip
all
that.
C
So
we
can
get
to
the
good
part,
so
everything's
already
set
up
and
running
the
Firefly
command
line.
Interface
also
sets
up
the
Firefly
sandbox
sandbox
is
a
great
tool
for
being
able
to
just
really
quickly
in
a
browser
use.
Firefly
I
can
click
a
couple
buttons
and
like
try
out
different
major
features
in
Firefly,
so
we
kind
of
talked
about
the
three
pillars
earlier
and
you
know
right
across
the
top.
We
have
tabs
for
messages,
tokens
and
contracts,
so
those
are
kind
of
the
the
three
main
sets
of
functionality.
C
C
I
have
a
hard
time
typing
and
talking
at
the
same
time.
I,
don't
know
if
you
guys
have
that
too
I
hope
it
works
all
right,
so
I'll
publish
that
this
will
run
a
batch
pin
transaction
on
my
fabric,
Network,
so
I
I
could
go
hop
over
and
look
at
my
my
fabric,
nodes
and
I
could
actually
see
that
that
got
mined
into
a
block
on
my
fabric,
channel
that
these
Firefly
nodes
are
configured
to
use.
C
I
could
go
to
my
Firefly
Explorer
and
I
can
see
that
you
know
I
just
submitted
a
transaction
here.
My
message
was
confirmed:
I
can
go
look
at
the
off
chain
data.
So
when
you
broadcast
data
in
Firefly,
the
the
payload
itself
remains
off
chain.
The
the
fact
that
something
was
broadcasted
is
what
goes
on
to
the
chain
and
triggers
an
event
which
triggers
other
Firefly
nodes.
Listening
for
that
event
to
know,
hey
I
have
a
message
from
somebody.
C
Let
me
go
retrieve
that
payload
from
ipfs
and
see
what
it
was
so
I
can
look
in
data
and
I
can
click
on
this
one
and
here's.
My
demo
hope
it
works.
Let's
go
check
out
the
other
Firefly
node
running
over
here.
So
we'll
look
at
the
green
one
or
node
one,
so
we
can
see
that
there
was
a
message
that
happened
here
as
well.
Let's
go
check
to
make
sure
we
also
got
the
data
payload.
We
can
look
under
off
chain
data
and
yeah.
This
is
my
demo.
C
I
hope
the
rest
of
it
works
too.
Okay,
so
you
know
that's.
This
is
nothing
new
from
from
Firefly
1.0,
but
just
wanted
to
I
just
wanted
to
demonstrate
that,
like
everything
that
was,
there
is
still
there,
but
here's
what's
new.
So
now
in
my
Explorer
I
also
have
this
drop
down
up
here
and
this.
This
lets
me
switch
between
different
name
spaces
that
I
have
in
my
Firefly
node.
So
so
my
Firefly
note
in
this
demo
is
the
red
one,
the
imaginary
other
organization
that
I'm
communicating
with
is
the
green
one.
C
C
If
I
hop
over
to
that
polygon
namespace,
we'll
notice,
the
the
my
node
diagram
looks
different
because
I'm
using
a
different
set
of
plugins,
we'll
notice
that
there's
some
different
pieces
of
data
in
here
also
before
this
demo
I
went
ahead
and
I
deployed
an
erc20
contract
to
the
polygon
testnet.
We
can
hop
over
here
and
we
can
take
a
look
at
that.
So
here's
here's
the
contact
address.
This
is
public.
You
can
go
to
this
URL
right
now
on
your
machine
and
you
can
see
my
contract.
You
can
see
that
I
deployed
it.
C
C
So
there
are
a
couple
sets
of
there's
a
set
of
endpoints
if
you're,
using
the
default
namespace
and
there's
a
set
of
endpoints,
where
you
can
fill
in
a
custom
name
space,
which
is
what
we
need
to
do
so.
I
just
came
down
here
and
I
did
a
a
post
to
yep
here
it
is
tokens
pools
and
that
set
up
a
token
pool.
Now
what
that
does
is
it
uses
fireflies
a
token
connector
to
go
index
the
chain
so
Steve
talked
about
earlier.
C
C
In
the
day,
what
happened
in
the
background
was
Firefly
set
up
a
job
through
the
blockchain
connector
through
evm
connect
that
went
and
it
started
at
the
first
block
and
I
said:
okay
I'm
going
to
go
query
the
blockchain
and
I'm
going
to
build
that
whole
history,
and
so
that's
already
happened.
So
if
we
go
look
in
our
dashboard,
we
can
see
under
tokens.
C
We
can
go
see
our
token
pool,
that's
here,
and
it
has
so
I've
deployed
this
thing.
I
I
called
it
FFC,
Firefly
coin.
If
you
will
and
there's
there's
a
hundred
of
them
I,
don't
know,
maybe
that
font
is
it.
Is
it
hard
to
read
in
the
back
of
the
room,
okay,
I'll
zoom
in
a
little
bit
here,
maybe
not
that
much
okay,
the
the
responsive
UI
was
kicking
in
there.
C
I
thought
I
was
on
a
phone
because
I
zoomed
in
so
much
so
yeah,
so
there's
a
hundred
of
them
here
we
can
see
that
there
was.
There
was
one
mint
action,
that's
taken
place
and
that's
it
so
to
demonstrate
that
this
really
is
a
public
chain,
and
then
this
all
really
works
and
I
can
actually
transfer
tokens
with
this
I
I
have
a
wallet
on
polygon
testnet
that
I'm
going
to
transfer
to
I
I
would
love
some
audience.
Participation,
though,
does
just
by
happenstance.
C
Does
anyone
have
an
ethereum
wallet
configured
on
a
polygon
test
net
and
I
can
give
you
some
some
FFC
right
now.
If
you
want
as
a
souvenir,
do
you
all
right,
never
mind
I'll
I'll,
send
it
to
my
metamask:
that's
fine!
It
was
a
long
shot,
but
okay,
so
over
on
this
other
desktop
over
here,
okay
I've
got
my
metamask
wallet.
C
I
have
some.
This
is
configured
to
use
polygon,
testnet,
I,
don't
really
own
200
Matic!
Well,
actually,
I
do
but
it's
in
a
different
wallet.
So
so
this
one
is
configured
to
use
polygon
test.
Now
you
can
see
I
own
I
have
zero
FFC,
though
so
I've
I've
told
metamask,
hey
here's
my
contract
address
on
a
polygon
test
net
and
what
I'm
going
to
do
is
I'm
going
to
copy
my
account
address
here
and
I'm,
going
to
go
over
to
my
Swagger
UI
and
I'm,
going
to
go
down
to
the
transfer.
C
C
Most
of
this
I
don't
need
so
I'm,
actually
just
going
to
type
out
what
I
do
need
I'm
going
to
transfer
it.
To
my
this
is
my
metamask
address
I'm
going
to
transfer
it
from
I'm
gonna.
Go
look
that
up
here,
my
yeah,
so
this
is
my.
This
is
the
address
that
I
use
to
deploy
the
contract.
It's
also
the
address
that
my
Firefly
node
is
configured
to
use,
so
I
I
have
the
private
key
for
this
address
on
my
Firefly
signer.
C
That's
that's
kind
of
how
that
works
behind
the
scenes,
so
I'm
going
to
copy
this
address
here.
So
this
is
the
address
that
owns
the
the
currently
only
existing
100
FFC
that
exists
on
this
chain
and
save
this
from
this
address
and
then
we're
going
to
say
the
amount
is
so
so
for
the
amount,
just
just
a
quick
background
information
here.
If
you
aren't
super
familiar
with
how
erc20
Works
there's
there's
a
configured
number
of
decimal
places,
so
the
ethereum
evm
only
works
in
integer
math.
C
C
Why
I'm
going
to
type
a
super
long
number
here,
one
two:
three:
four:
five:
six:
seven:
eight
nine
10
11
12
13,
14,
15,
16,
17,
18.,
okay,
so
that
should
transfer
10
tokens
and
then
we
will
hit
execute
okay,
we
got
a
202
back,
which
means
it
has
accepted
my
token
transfer,
and
it
will
happen
in
the
background.
So
what's
going
to
happen
now
is
that
will
get
submitted
to
my
remote
RPC
node
that
I've
configured
to
talk
to
the
polygon
test
net
I've
configured
my
evm
connector,
to
wait
for
four
confirmations.
C
C
What
that
means
is
I
I
want
to
wait
to
know
that
I
get
four
consecutive
blocks
mined
on
the
chain
that
all
have
my
transaction
in
them,
and
so
I
for
this
test.
Net
I've
determined
just
arbitrarily
that
that
four
is
sufficient,
but
for
a
network
or
that
may
be
more
unpredictable
or
maybe
you
want
even
more
guaranteed.
You
could
set
that
confirmation
number
much
higher.
C
It
means
it
will
take
much
more
much
more
time
before
we
consider
the
transaction
to
be
definite
or
that
it's
not
going
to
be
reverted
or
that
we're
not
going
to
get
conflicting
blocks
and
have
to
rewind
the
blockhead
there's.
So
there's
a
bunch
of
really
complex
stuff,
that's
happening
behind
the
scenes
in
the
blockchain
connector
right
now,
and
so
it's
probably
probably
finished.
We
could
go
hop
over
to
look
at
our
contract
here
and
we'll
refresh
this
page,
okay
yeah.
So
there
was
a
minute
ago.
C
There
was
another
transfer
here,
so
there
was
a
transfer
from
and
there's
there's
my
my
addresses
and
if
I
go
hop
over
to
my
Firefly
Explorer
I
get
this
refresh
button
now
and
I
can
see.
Now
there
is
a
new
account
that
has
a
balance
of
10
and
my
my
Firefly
nodes
balance
has
decreased
to
90.,
so
that
transfer
was
successful.
C
Now
it
says
we've
got
10.,
and
so,
if
I
wanted
to,
I
could
transfer
if
I
knew
someone
else
that
had
a
polygon
test,
net
wallet
I
could
transfer
some
of
these
10
tokens
there
and
because
my
Firefly
node
is
indexing
this
token,
that
transfer
would
show
up
there
as
well.
So
Firefly
is
now
aware
of
all
of
the
transactions
that
happen
on
this
public
chain.
C
So
that's
kind
of
what
I
wanted
to
highlight
for
for
the
demo.
This
this
hits
on
a
bunch
of
the
new
features
in
Firefly.
It
touches
on
multiple
namespaces.
It
touches
on
both
public
and
private
chain
interactions
at
the
same
time,
in
the
same
Firefly,
node,
multiple
namespaces
and
and
a
bunch
of
other,
really
cool
things
that
all
combine
together
to
make
a
really
powerful
platform
to
build
blockchain
apps
thanks
for
coming
out
today,
we've
got
about
five
minutes
and
we'll
take
some
questions
now
and
really
appreciate
you
coming.
Thank
you,
foreign.
D
My
question
is
primarily
center
around
identity
and
access
control
so
that
Swagger
UI
tab
you're
able
to
go
in
there
and
execute
that
transaction
without
Authentication.
Is
there
a
an
access
control
you
can
put
on
top
of
that?
That
says:
okay,
you
need
to
have
this,
and
if
so,
what
what
sort
of
controls
do
you
support
there
yeah.
C
Absolutely
great
question
so
for
context:
this
is
a
local
development
environment.
That's
running
on
my
laptop,
which
is
why
there's
no
https,
it's
all
localhost,
so
new
and
Firefly
1.1
is
plugable
API
security.
So
there
is
a
basic
auth
plug-in.
That's
built
in.
You
can
configure
it
at
the
HTTP
listener
layer.
So
you
can
say:
I
want
username
and
password
on.
You
know
everything
you
can
configure
it
on
the
namespace
layer,
so
you
might
have
one
team
in
your
organization
that
is
working
within
a
certain
namespace
and
you
give
them
one
set
of
credentials.
C
You
may
have
another
team,
that's
working
in
another
namespace,
so
you
can
separate
them
that
way,
because
it's
a
plug-in
anyone
can
write
a
an
authorizer
for
Firefly
and
plug
into
any
kind
of
user
authentication
system
they
want.
You
know.
Other
options
also
includes
some
sort
of
network
Appliance
in
front
of
firefly,
like
a
reverse
load.
Balancer
that
handles
the
off.
You
know
outside
of
the
process
as
well,
but
there's
there's
options
for
both.
We
we
like
to
try
to
be
generic.
C
D
D
Okay
and
then
I
see
this
fabric,
Consortium
Network
and
there's
a
connection
there
from
fab
connect.
So
then,
is
there
some
notion
of
identity
that
goes
beyond
the
fabric,
Network
that
sort
of
identifies
an
account
inside
of
firefly
across
both
of
the
the
evm
connect
and
the
fabric
Consortium
Network.
C
C
Network
Firefly
also
has
a
concept
of
an
organization
that
can
map
one
to
one
or
one
to
many
with
fabric
identities
as
well
within
this
public
chain,
namespace,
that's
less
relevant
because
I'm
I'm
using
this
in
what
we
call
Gateway
mode,
where
this
is
just
it's
just
a
an
appliance,
an
API
Gateway
that
I've
set
up
where
my
organization
can
talk
to
a
public
chain,
so
identity,
the
sorts
of
org
identities
and
node
identities
are
less
relevant
in
that.
In
that
space,
my.
D
C
D
C
B
C
C
C
Yes,
there
there
are
so
the
docs
are
a
great
resource.
If
you
go
to
I
believe
it's
it's
linked
in
our
it's
pinned
and
Discord.
If
you
go
to
it's
a
hyperledger.github.io
firefly,
these
are
the
main
docs
for
Firefly.
This
is
a
great
place
to
start
learning
full
disclosure.
We
have
a
lot
more
docs
that
we
should
write
they're
they're
coming
soon,
but
yeah.
This
is
a
great
place
to
start.
A
A
You
know,
Firefly
knows
how
to
connect
to
fabric
and
interact
with
it.
What
Firefly
does
is
it
accumulates
all
of
that
identity
information
into
an
address
book,
so
when
you're
in
Consortium
mode,
you
you,
your
Firefly
node
will
create
an
address
book
of
all
that
pki
information
for
all
the
different
organizations
that
you
connect
to
I.
Think.
B
E
C
Today,
there
is
a
plug-in
for
SQL
style
databases,
the
specific,
so
there's
a
plug-in
today
for
postgres
there's
a
plugin
today
for
SQL
Lite.
When
you
set
up
the
development
environment,
the
default
is
SQL
Lite,
just
to
not
have
an
yet
another
Docker
container
running
in
production.
You
probably
want
to
run
postgres,
but
it's
very
easy
to
add
a
plug-in
for
a
different
type
of
SQL
database.
C
Perhaps
a
nosql
database
will
come
down
the
road,
but
we,
it
doesn't
currently
support
nosql
databases
for
for
its
for
fireflies
internal
database,
which
is
is
really
sort
of
the
current
state
of
the
world.
That
being
said,
there's
also
a
shared.
A
separate
separate
from
the
database.
There's
also
shared
storage
is
what
we
call
it,
which
the
current
implementation
of
that
is
ipfs.
So
if
you
want
to
store
Blobs
of
Json
or
binaries
or
or
whatever
you
want,
those
those
are
good,
ipfs
good
question,
Cool.