►
From YouTube: Hyperledger FireFly 1.1 is Here!
Description
A virtual meetup hosted by Hyperledger Raleigh on Oct 19, 2022. At Hyperledger Global Forum, the Hyperledger FireFly community was pleased to announce the release of version 1.1. This release makes it possible for Hyperledger FireFly users to deploy multiple blockchain applications connecting to multiple chains, including leading public blockchains like Ethereum, Polygon, Avalanche, Optimism, BNB Chain, Arbitrum, Moonbeam, Fantom and more.
In this webinar, Nicko Guyer, Hyperledger FireFly maintainer and Community Lead, will take you through the new functionality in 1.1, including:
* Web3 Gateway Mode: Use Web3 Gateway Mode to connect to public blockchains including Ethereum, Polygon, Avalanche, Optimism, BNB Chain, Arbitrum, Moonbeam, and Fantom.
* Public Blockchain Support: Leverage new tools to simplify public use cases, including FireFly Transaction Manager, FireFly Signer, and Enhanced Gateway Support.
* Consortium Mode: Use Consortium Mode to build multi-party business networks where data needs to be agreed to and shared among the group.
* Multi-tenant Support: Use new namespace isolation to segregate and configure API security, identity broadcasting, on-chain data indexing, and data sharing.
* Multiple Instances of Plugins: Use several instances of each type of plugin in a single FireFly node.
* Pluggable API Security: Enable API Security at several levels and on any service or namespace.
Learn more about FireFly at: https://github.com/hyperledger/firefly
And join the conversation on the FireFly channels on Hyperledger's Discord server at: https://wiki.hyperledger.org/display/HYP/Our+chat+service
----
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
All
right
welcome
everyone.
Thank
you
for
coming
out
to
today's
webinar
on
Firefly
1.1
and
today
we're
going
to
talk
about
a
lot
of
exciting
new
features
in
this
feature:
release
of
Firefly.
Hopefully
you
are
familiar
with
hyperledger
firefly,
at
least
to
some
degree.
I
will
spend
just
a
couple
minutes
talking
about
what
it
is,
but
not
more
than
that,
because
I
really
want
to
dive
into
what
are
the
new
things
in
Firefly,
so
at
hyperledger
global
forum
last
month
we
announced
Firefly
1.1,
and
we
did.
We
had
one
slide
on
here's.
A
What's
new
in
1.1,
we
did
demo
some
of
the
things
that
are
new,
but
I
really
wanted
to
spend
some
time
to
dive
a
little
bit
deeper
and
really
just
kind
of
unpack
the
new
features
and
actually
go
Hands-On
and
show
the
community
how
to
actually
use
these
new
features,
how
to
configure
things
and
how
to
kind
of
go
a
couple
layers
deeper
than
what
we've
demoed
in
the
past.
So
that's
that's.
What
we're
going
to
look
at
today,
I'm
going
to
share
my
screen
and
we're
going
to
go
through
some
slides.
A
The
first
part
of
this
presentation
will
be
going
through
these
slides
and
the
second
part
will
be
a
Hands-On
kind
of
demo,
walkthrough
of
using
and
configuring
some
of
the
new
features.
So
let's
go
ahead
and
jump
right
in
so,
like
I
said,
hopefully
you're
familiar
with
hyperledger
firefly,
at
least
to
some
degree.
If
you're
not
familiar
with
it,
we
describe
Firefly
as
a
web.
3
super
node
for
building
Enterprise
blockchain
applications.
So
what
does
that
mean?
It
is
a
platform.
So
Firefly
itself
is
not
a
blockchain.
A
It
is
a
platform
that
allows
developers
to
build
apps
that
are
powered
by
blockchain
and
it
provides
an
API
and
very
developer
friendly
features
and
patterns
that
developers
are
familiar
with
to
help
speed
up
building
blockchain
apps.
So
Firefly
is
middleware
that
sits
between
the
actual
DLT,
the
blockchain
at
the
lower
layer
and
your
application,
your
business
logic
at
the
top
layer.
It
coordinates
a
whole
bunch
of
different
type
of
things.
A
Data
flows,
whether
it's
on-chain
data
or
off-chain
data,
get
handled
token
contracts,
indexing
transactions
on
the
Chain,
keeping
track
of
balances,
performing
transfers
and
a
bunch
of
other
stuff
like
this.
So
it
provides
a
bunch
of
building
blocks
for
building
blockchain
applications
really
quickly,
and
if
it's
an
open
source
platform,
it
is
a
standardized
way
of
building
blockchain
apps,
it's
also
very
pluggable.
So
so
one
of
the
things
that
we're
going
to
dive
deep
into
is
what
are
the
new
plugins
and
how
do
I
configure
them
in
1.1.
A
So,
as
you
notice
as
we
go
just
about
everything
in
Firefly
is
a
plug-in
and
or
a
microservice.
So
there
are
a
lot
of
different
pieces
of
the
architecture
and
we're
going
to
dive
a
little
bit
deeper
into
what
some
of
those
are
today.
So
that's
just
that's
Firefly
in
a
one
or
two
minute.
Nutshell
here
so
with
no
further
Ado,
let's
dive
into
what's
new
in
1.1.
A
A
We're
going
to
be
talking
about
public
blockchain
support,
specifically
evm
support,
we're
going
to
be
talking
a
lot
about
namespaces
and
how
to
have
multiple
namespaces
and
what
some
of
the
use
cases
around
those
might
be,
and
we're
going
to
be
talking
about
the
connector
toolkit
and
we're
going
to
be
talking
about
plugable,
API
security
and
fireflies
token
capabilities
as
well.
So
this
is
kind
of
the
the
high
level
of
here's.
A
What's
new,
and
now
the
next
few
slides
are
going
to
unpack
each
one
of
these
little
boxes
here
on
this
slide,
so
I
I
want
to
start
with
the
most
exciting
thing
and
kind
of
the
high
level
thing,
and
this
is
not
just
one
feature.
This
is
like
a
bunch
of
new
things
that
are
in
firefly.1.1
all
roll
up
to
enable
public
blockchain
support.
A
A
So
when
Firefly
1.0
launched,
we
had
eth
connect
and
we
had
Fab
connect
as
the
two
blockchain
connectors
for
Firefly
1.1
brings
a
new
connector
for
ethereum
based
chains
called
evm
connect,
it's
you
could
think
of
it
as
a
a
new
version
or
a
completely
Rewritten
ethnect.
It's
it
doesn't
like
eth
connect,
isn't
necessarily
going
away,
but
it
is
Backward
Compatible
with
ethnect,
so
we
still
have
production
use
cases
using
youth
connect.
So
we
plan
to
continue
to
maintain
it,
but
evm
connect.
A
A
So
so
the
idea
is
that
Firefly
can
be
my
company's
access
point
to
the
entire
web
3
world,
whether
that
is
a
public
chain,
whether
it
is
you
know,
a
bunch
of
different
D5
apps
on
different
chains
or
whether
it's
a
private
chain
in
a
blockchain,
Consortium
Network,
or
something
like
that.
Firefly
can
now
do
all
of
these
use
cases.
A
At
the
same
time,
within
the
same
Firefly
node,
it
was
not
so
when
Firefly
launched
it
was
possible
to
connect
to
either
an
ethereum
chain
or
a
fabric
chain,
but
the
same
Firefly
node
was
not
capable
in
the
original
version
of
connecting
to
both
of
them
same
time.
Now
it
can.
So
that's
that's
a
huge
new
thing
and
the
way
this
works
is
through
different
namespaces
within
Firefly
and
I'm,
going
to
unpack
how
we
use
namespaces,
how
we
configure
them
in
just
a
little
bit
as
well.
A
A
No
other
organizations
necessarily
involved
in
those
transactions
directly.
They
don't
need
to
be.
Nobody
else
needs
to
be
running
Firefly
for
me
to
run
Firefly
in
Gateway
mode.
So
you
know
over
here
on
this,
this
very
high
level,
sketch
sort
of
have
this
idea
of
one
Firefly
node
that
it
has
two
different
namespaces
configured.
So
my
Firefly
node
could
both
be
in
a
Consortium
namespace
talking
to
a
private
blockchain
and
other
organizations
could
have
their
Firefly
nodes
talking
to
the
same
chain
Meanwhile.
A
My
Firefly
node
could
also
be
configured
in
another
namespace
to
talk
to
a
public
chain
and
I
could
perform
token
transfers
or
you
know,
exchange
value
on
on
public
blockchains.
That
way
as
well.
So
a
really
great
new
Gateway
enhanced
support
here
and
really
this.
This
is
sort
of
the
the
picture
that
we've
we've
had
in
our
minds
for
what
Firefly
needs
to
become
for
a
while,
and
this
this
really
rounds
out
the
picture.
So
you
know
over
here
on
the
left
we
have.
You
know
this
is
you
can
think
of
this.
A
As
my
my
Enterprise,
and
this
dotted
line
is
like
the
boundary
between
this
is
what
my
company
runs
and
manages,
and
you
know
this
is
the
rest
of
the
world
out
here,
and
so
you
know
prior
to
Firefly
and
having
a
common
platform
to
build
blockchain
apps
on
you
know.
Most
of
the
solutions
over
here
were
custom,
one-off
Solutions,
and
there
was
no.
There
was
no
common
framework,
no
open
source
framework
that
that
fit
this.
A
This
middleware
that
sits
between
the
blockchain
and
my
my
web3
apps
that
I
need
to
build
and
also
integrates
well
with
existing
systems
and
Firefly
solves
this
need.
A
firefly
can
can
act
as
a
web
3
Gateway
now
for
many
different
use.
Cases
like
we
said
whether
that's
a
Consortium,
whether
that's
a
layer,
one
or
a
layer,
two
chain,
whether
it's
a
yeah,
you
know
some
sort
of
exchange
or
or
defy
app
Firefly
can
can
be
the
One-Stop
shop
for
connecting
to
all
these
different
types
of
web
3
platforms.
A
A
So
we'll
actually
go
look
at
a
config
file
here
and
I'm
going
to
walk
you
through
it
and
I'm
going
to
I'm,
actually
gonna
edit
it
and
create
some
new
plugins
and
new
namespaces
here
in
a
little
bit.
But
essentially,
you
can
think
of
I
can
define
an
entire
list
of
plugins
that
I
want
Firefly
to
set
up
and
initialize
and
connect
to
whatever
service
it
needs
to
connect
to
and
then
separately
I
can
define
a
whole
list
of
namespaces
and
then
I
can
pick
which
of
those
plugins
each
namespace
uses.
A
So
a
namespace
can
have
a
blockchain
connector,
a
shared
storage,
connector,
a
data
exchange
component,
etc,
etc.
Those
plugins
could
be
shared
by
multiple
namespaces
or
they
could
be
separate
per
namespace
within
one
namespace.
You
cannot
have
multiple
blockchain
connectors
within
one
namespace.
You
cannot
have
multiple
databases,
it's
you
pick
one
for
each,
but
you
can
have
many
namespaces
within
the
node.
So
that's
just
kind
of
the
mapping
between
all
those
things
so
over
here
we
just
have
a
little
high
level.
Sketch
of
you
know.
A
Well
oftentimes,
it's
helpful
to
I
think
think
of
the
question
like
what
what
use
case
does
this
enable?
So
one
of
the
really
pragmatic
ones
which
I'm
actually
going
to
walk
through
in
a
little
bit
is,
if
you
have
multiple
teams
that
want
to
use
a
single
Firefly,
node
I
could
set
up
a
namespace
for
each
team.
Now
those
teams
could
be
sharing
some
components
such
as
the
blockchain
connector
or
the
the
chain
itself
they
may
have.
A
We
may
want
to
completely
separate
the
data
between
them,
so
they
could
be
using
different
databases
or
they
could
be
using
the
same
one.
They
could
also
be
using
different
authorization
which
we're
going
to
get.
That's
that's
another
new
feature
that
we're
going
to
get
into
in
a
little
bit
and
they
could
be
using
different
signing
keys,
for
instance,
and
so
you
know
being
able
to
create
a
separate
namespace
for
each
team
kind
of
helps,
keep
things
organized.
It
also
helps.
A
If
you
want
to,
you
know,
run
different
applications
or
just
completely
different
use
cases
all
on
the
same
Firefly
node.
That's
that's
completely
a
thing
you
could
do
now,
so
lots
lots
of
different
use
cases.
There
are
unlocked
by
just
having
a
lot
of
flexibility
in
the
mapping
of
plugins
to
name
spaces.
A
All
right
one
so
so
now
now
we're
getting
really
technical.
We're
not
going
to
quite
go
look
at
code
yet,
but
we're
we're
talking
about
code
here.
So
one
of
the
the
really
cool
new
things
in
Firefly
1.1
is
the
blockchain
connector
toolkit.
And
so
so,
if
you
go
look
in
GitHub,
there's
a
repo
called
Firefly
transaction
manager
and
that's
that's
what
it
began
life
as
it
may
be.
A
Maybe
maybe
it's
not
the
best
name
for
it
anymore,
but
but
it's
stuck
so
far
because
we
haven't
thought
of
a
better
name
for
it.
Yet,
but
essentially
what
it
is
is
a
reusable
code.
Library
it's
written
in
go,
and
it
has
all
of
the
logic
that
a
blockchain
connector
needs
minus
the
protocol
specific
code
to
talk
to
a
specific
blockchain.
So
you
could
think
of
it
as
it's.
A
This
reusable
piece
of
code
that
has
a
bunch
of
the
really
hard
problems
of
building
a
blockchain
connector
things
like
you
know:
gas,
cost
estimation
managing
nonsense,
handling
event
streams,
knowing
where
it's
at
reading
a
chain
and
if
it
needs
to
catch
up.
If,
if
the
chain
has
moved
ahead
of
where
it's
at
and
it
needs
to
catch
up
or
if
you
create,
if
you
want
to
listen
to
a
certain
type
of
event
from
a
certain
block
number,
knowing
how
far
behind
is
that
particular
event
listener?
A
And
you
know
what
what
do
I
need
to
do
to
get
this
particular
event
stream
caught
up
with
the
head
of
the
chain?
All
this
stuff
is
written
in
Firefly
transaction
manager,
and
it
it
can
be
used
as
a
library.
So
so,
if
somebody
wants
to
create
one
of
the
goals
here
was
to
make
it
really
easy
for
the
community
to
create
additional
blockchain,
connectors
and
so
evm
connect
is
sort
of
the
the
first
blockchain
connector
that
uses
the
Firefly
transaction
manager
or
blockchain
connector
toolkit
to
build
out
sorry.
A
A
So
you
know
if
someone
wants
to
sit
down
and
create
a
new
blockchain
connector
to
connect
Firefly
to
a
completely
different
type
of
chain,
not
ethereum
based
the
goal
is
that
the
connector
toolkit
has
at
least
80
percent
of
the
code
already
there
and
and
then
it's
just
up
to
the
developer,
to
figure
out.
Okay,
what
you
know
the
the
toolkit
provides
this
interface,
that
I
need
to
implement
and
I
just
need
to
write
the
bit
of
code.
That
tells
that
is,
you
know
the
Syntax
for
my
particular
change.
A
How
do
I
query
a
range
of
blocks
or
for
my
particular
chain?
How
do
I
submit
a
transaction
and
encode
it
in
the
right
format
that
my
blockchain
node
is?
Is
going
to
accept
that
sort
of
thing?
So
here's
a
here's
another
look
at
sort
of
a
diagram
of
how
all
of
this
fits
together.
So
at
the
top
we
have
Firefly
core
Firefly
core
works
with
smart
contract
interfaces
and
token
standards.
If
we
go
one
layer
below
that,
the
thing
that's
running
both
of
those
is
a
blockchain
connector
API
and
then
so.
A
The
thing
that
is
backing
the
blockchain
connector
API
is
oh
sorry,
I'll
I'll
unpack
that
for
just
a
second,
so
one
of
the
things
you
could
do
in
the
API,
the
API
provides
functions
for
submitting
transactions,
getting
updates
on
transactions
querying
them
or
or
or
subscribing
to
updates.
When
transactions
have
new
status,
you
can
listen
to
events
and
it
provides
event
delivery
via
a
websocket
as
well.
So
that's
that's
sort
of
the
API
and
the
thing
that
that
actually
implements
this
API
and
is
backing
it
most
of
it.
A
If
we're
looking
at
evm
as
an
exam,
evm
connector
as
an
example,
most
of
it
is
the
blockchain
connector
toolkit
like
we
said,
that's,
you
know
roughly
eighty
percent
of
the
code,
and
so
it
has
everything
from
you
know:
transaction
manager,
nonce
management,
keeping
track
of
confirmations
for
a
particular
Trend
transaction
and
event
stream
management.
All
all
bundled
up
in
this
Library
Firefly
is
a
plugable
framework
at
every
level,
including
the
the
connector
toolkit.
A
So
there
are
plug
points
for
things
that
you
might
want
to
customize,
and
so
you
know
for
your
particular
Enterprise
use
case
or
for
your
particular
chain.
You
may
want
to
you.
You
may
have
a
a
particular
way
that
you
want
to
calculate
the
price
of
gas
or
you
may
have
a
particular
way
that
you
a
particular
strategy
around
how
to
handle
transaction
resubmission,
but
my
transaction
failed.
A
Was
there
a
problem
with
the
way
I
packed
the
transaction
itself,
or
was
it
a
temporary
Network
failure
or
you
know
so,
all
of
these
things
and
the
the
policy
around?
What
to
do
and
certain
failures
is,
is
pluggable,
so
you
could
write
a
custom
policy
and
if
you
need
customization
over
that,
there's
a
very
basic
policy
that
comes
out
of
the
box
with
the
connector
toolkit
and
it
basically
just
will
continue
to
retry
to
resubmit
a
transaction
so,
for
instance,
I
in
in
setting
up
various
demos
and
things
oftentimes.
A
When
I'm
working
with
the
public
chain,
I
will
forget
to
to
actually
fund
a
certain
account
and
I'll
submit
a
transaction,
and
it
will
fail.
You
know,
oh,
why
did
it
fail?
Oh
okay,
I
forgot
to
I
forgot
to
fund
it.
Well,
meanwhile,
the
transaction
manager
is
sitting
there
going.
Okay,
well,
I'll
just
keep
retrying
this.
It's
it's
a
like
you
know,
conditions
may
change
at
some
point.
Someday
I
may
have
enough
money
to
do
this
transaction
and
sure
enough
as
soon
as
I
find
the
account
the
transaction
goes
through.
A
So
that's
that's
the
basics
policy,
that's
out
of
the
box,
but
if
you
need
customization
and
control
of
that,
it's
a
plugable
thing.
That
is
totally
something
that
can
be
customized
and
then
so.
You
know
over
here
off
to
the
right
like
this.
This
tiny
box
in
the
corner
is
really
like.
That's
evm
connect
and
it's
it's
basically
just
the
implementation
of
all
of
this
Orange
Box
here
in
the
middle
and
with
the
the
syntax
of
like
well.
A
A
So
there's
lots
of
stuff
going
on
all
the
time
around,
but
okay,
so
that's
that's
enough
on
the
blockchain
connector
toolkit
we're
not
actually
going
to
it's.
It's
a
lot
of
code,
so
we're
not
going
to
dive
deeper
onto
into
that,
but
a
couple
other
things
I
wanted
to
touch
on
before
we
go
Hands-On
and
actually
use
Firefly,
plugable
API
security.
A
So
this
is
a
thing
this
is
I
would
say:
1.1
is
a
start
and
it's
a
solid
start
in
the
right
direction
for
API
security
within
the
Firefly
ecosystem,
and
so
so
up
until
1.1.
The
approach
has
been
yeah.
Obviously,
apis
need
to
be
secured
in
production,
but
probably
having
some
sort
of
appliance
that
sits
in
front
of
fireflies
API.
A
That's
handling
your
authorization
scheme
that
you
have,
whether
it's
oauth
or
or
some
other
some
other
authorization
scheme
having
some
sort
of
other
network
Appliance
handle
that
this
is
the
start
of
building
API
security
directly
into
Firefly
and
I,
say
it's
a
start,
because
we
know
there's
more
work.
That
needs
to
be
done.
It
needs
to
be,
it
needs
to
be
more
granular
and
that's
something
that's
sort
of
on
the
on
the
roadmap
for
future
enhancements.
A
But
like
everything
in
Firefly
API,
security
is
a
plug-in
and
API
security
can
be
enabled
at
several
different
layers.
So
you
can
enable
it
on
the
HTTP
listener
layer.
You
can
also
enable
it
in
any
other
any
other
microservices
within
the
Firefly
architecture
that
are
using
the
Firefly
common
HD
GP
listener,
which
is
several
of
them.
You
can
also
enable
it
there
as
well,
and
you
can
also
enable
it
in
a
specific
namespace
in
Firefly
core,
so
I
sort
of
talked
about
earlier.
A
You
could
have
two
different
teams
that
are
using
the
same
node
and
you
want
to
have
two
different
authorization
schemes.
So
that's
something
you
could
do
you
could
you
could
have
assign
a
namespace
to
each
team
and
allow
them
to
access
their
their
namespaces,
but
not
the
other
one
and
like
I
said
everything
in
Firefly
is
a
plug-in,
so
there's
a
basic
auth
plug-in
that
is
there.
Today
it
comes
out
of
the
box,
but
obviously
basic
auth
is
like
I
said
it's
just
a
start:
you're
probably
going
to
want.
A
You
may
want
something
else,
and
so
you
can.
You
can
write
additional
plugins
to
have
custom
authors
authorizers
within
Firefly,
so
that
is
it
in
terms
of
slides
and
then
we're
gonna
go
Hands-On
here
in
just
a
minute,
but
yeah
I
think
I.
Think
what
we'll
do
is
we'll
pause
for
just
a
few
minutes
and
I
will
ask
if
there
are
any
questions
on
anything
that
I
can
clarify
that
we've
talked
about
so
far,
I'll
open
it
up
to
General
Firefly
questions.
A
I'm
just
pulling
up
the
chat
here
to
see
I
I
hadn't
had
it
up
on
my
screen
here.
Let's
see
Shane
asked:
why
is
it
called
a
namespace?
It's
a
good
question.
It's
a
a
namespace
is
a
I
think,
a
fairly
common
term
in
the
industry.
To
just
you
know,
when
you
want
to
group
something
in
within
a
certain
within
a
certain
context,
we
just
decided
to
call
that
a
namespace
and
so
there's
there's
a
space,
and
it's
all
that
stuff.
That's
in
that
space
goes
together.
A
Our
namespace
is
strictly
designed
for
teams
nope,
you
can
so
you
could
have
one
team
that
uses
multiple
namespaces.
You
could
have.
You
know
namespace
per
team.
That
was
just
one
example
that
I
threw
out
there
of
how
that
can
be
used.
Other
use
cases
for
using
multiple
namespaces
might
be
if
you're,
building
an
app
that
needs
to
talk
to
multiple
blockchains.
A
You
would
you
need
a
namespace
to
talk
to
each
chain
because
you're
going
to
be
using
a
different,
blockchain,
connector
and
maybe
of
other
different
sets
of
plugins
as
well,
but
you
could
build
one
application
that
has
the
ability
to
talk
to
both
namespaces.
It's
it's
essentially
just
a
change
in
the
URI
of
the
API
calls
that
you're
making
and
you
could
build
one
app
that
talks
to
multiple
blockchains
using
multiple
namespaces.
A
A
Another
use
case
for
for
namespaces
is,
if
you
want
to
build
like
some
sort
of
monitoring
tool
that
actually
runs
transactions,
but
you
don't
want
to
pollute
the
the
data
set
of
the
real
live
application.
You
could
have
your
your
test.
Traffic
run
in
a
test
name
space,
and
it
makes
it
easy
to
just
like
completely
separate
that
data
from
the
data
of
the
actual
live
application.
A
Does
Firefly
support
permission
blockchain?
Absolutely
so
that's
you
know.
Firefly
started
the
very
first
use
case
that
we
tackled
in
the
Firefly
project
was
using
private
permission
chains
and
so
I
I'm
not
spending
a
ton
of
time
talking
about
that
today,
because
that
in
the
world
of
firefly,
that's
a
bit
of
old
news
now,
but
yes,
absolutely!
A
That's
that's
where
Firefly
started
was
with
private
permission
chains
in
consortiums
of
your
sort
of
blockchain
network
consortiums
of
organizations
and
public
permissionless
chains
is
something
that
is
brand
new,
which
is
why
that's?
Why
we're
talking
about
it
more
today
because
we're
just
sort
of
highlighting
the
the
new
features
in
1.1.
A
Does
the
namespace
part
of
the
data
out
of
the
public
ledger?
So
yes,
so
I
I,
think
I
understand
the
question
here
and
please
correct
me.
If
I'm
misunderstanding
it,
but
I
think
the
question
is
asking
does:
does
the
actual
data
that
I'm
sending
does
it
end
up
on
a
public
chain,
and
so,
if
you're
familiar
with
fireflies
concept
of
messaging
and
hashing
and
pinning
the
the
data
payload
does
not
actually
go
on
chain.
A
So
if
I,
so,
if
I
send
a
message-
or
you
know,
I'm
I
want
to
share
a
piece
of
data
with
with
some
other
party.
What
my
Firefly
node
does.
Is
it
hashes
that
piece
of
data
and
the
the
hash
of
the
data
goes
on
the
chain
and
then
the
actual
data
payload
itself,
which
could
be
very
large
I
mean
we
could
could
be
a
large
document,
could
be
a
video
file,
probably
not
suitable,
to
put
on
a
blockchain
that
that's
transferred
off
chain?
A
Okay,
great
so
we've
got
30
minutes
left
I
I
do
want
to
spend
some
time
actually
going,
Hands-On
and
walking
through,
like
how
do
I
set
this
stuff
up.
If
we
have
time
happy
to
to
come
back
to
q,
a
and
open
it
up
to
more
General
q,
a
at
the
end,
but
let's,
let's
do
some
some
Hands-On
stuff
now,
so
what
I
want
to
walk
you
through
is
I.
I
was
trying
to
think
of
a
something
that
I
could
do
that
basically
hits
all
the
new
features.
A
So
what
I'm
going
to
do
is
I'm
going
to
I've,
actually
done
a
little
bit
of
this
ahead
of
time
just
to
save
time.
So
you
don't
have
to
sit
here
watching
my
machine
spin
up
a
bunch
of
services
and
configure
a
bunch
of
things,
but
we're
going
to
start
a
firefly
stack
in
Gateway
mode,
we're
going
to
connect
it
to
a
public
test
net,
we're
going
to
configure
multiple
namespaces,
so
I'm
going
to
walk
you
through
this
use
case
this.
A
This
hypothetical
use
case
of
like
I,
have
multiple
teams
that
want
to
access
the
same
Firefly,
node
and
I
also
want
to
enable
basic
auth
on
each
of
those
namespaces
and
use
a
different
signing
key
on
each
namespace.
I
forgot
to
put
that
as
a
bullet
point
on
this
slide,
but
so
those
are
the
things
I'm
going
to
walk
you
through.
So
what
I've
done
over
here
is
I
have
gone
ahead
and
I've
set
up
a
firefly
stack
and
I'm
running
it
on
my
machine
here.
A
A
If,
if
you
are
unable
to
see
my
screen,
please
don't
hesitate
to
speak
up.
Okay,
great
I've
got
confirmations
in
the
chat
that
screen
sharing
looks
good.
Okay,
sorry
about
that.
So
what
I've
done
is
I,
basically,
just
I've
gone
through
one
of
the
new
tutorials
in
the
docs
site,
and
this
this
tutorial
is
is
is
up
on
the
on
the
doc
site.
Today
you
can
go,
take
a
look
at
it
and
I've
set
up
a
stack
to
connect
to
a
polygon
test
net.
A
A
This
will
tell
the
Firefly
command
line
interface
to
generate
the
appropriate
configuration
to
run
Firefly
in
Gateway
mode,
so
we're
not
creating
a
bunch
of
different
members
all
talking
to
the
same
chain
we're
just
we're
creating
one
Firefly
node
and
we're
going
to
connect
to
a
blockchain
and
we're
not
going
to
enable
all
the
we're
not
going
to
configure
the
default
namespace
to
to
use
multi-party
mode.
It's
an
ethereum
chain
I
want
to
use
evm
connect
because
I'm
talking
to
a
public
chain.
A
It
is
a
I'm
gonna,
in
this
case
I'm
going
to
connect
to
a
remote,
RPC,
node
and
then
I've
in
my
command.
That
I
ran
ahead
of
time.
I
put
in
a
remote
node
URL
here
for
a
a
blockchain
node,
that's
running
on
the
the
polygon
Mumbai
test
net
and
the
chain
ID
for
that
particular
chain
is
80,
000
won
and
then
I
I
have
a
an
evm
connect,
config
file
that
I
passed
in,
which
there's
some
instructions
on
how
to
create
that.
A
And
that
just
says
that
you
know
for
this
particular
chain.
I
want
four
confirmations
before
I.
Consider
a
transaction
to
P
final.
So,
on
a
private
permission
chain,
you
don't
have
to
worry
about
this,
necessarily
if
you're
using
proof
of
Authority
or
something
like
that
on
a
public
permissionless
chain,
though
just
because
one
particular
blockchain
node
says
that
yep
your
transaction
is
in
a
block,
doesn't
mean
that
all
of
the
other
nodes
in
the
network
are
going
to
agree.
In
fact,
several
minutes
later,
you
may
actually
get
a
new
block.
A
That
says
up
sorry,
actually,
that
block
that
we
told
you
about
earlier
didn't
happen.
The
rest
of
the
network
decided
that
this
is
actually
the
next
block,
and
so
you
know,
evm
connect
and
the
new
blockchain
connector
framework
handles
all
of
those
situations
for
you,
so
you
don't
have
to
worry
about
it.
Basically,
all
you
have
to
do
is
tell
it.
A
I
feel
confident
that
after
X
number
of
transactions
that
on
this
chain
with
the
way
the
consensus
algorithm
behaves
that
things
are
not
going
to
change
anymore,
so
I've
just
set
four
here,
that's
probably
not
an
appropriate
value
for
a
public
chain
that
you
may
be
using.
You
should
do
your
own
research
and
figure
out
what
the
right
value
for
for
your
chain
is
and
how
many
confirmations
you
want
to
wait
for
before.
A
You
feel
confident
that
your
transaction
is
final,
but
that's
what
we're
using
here-
okay,
so
I-
basically
just
went
through
this
tutorial.
I
have
some
some
accounts
set
up
and
I've
I've
funded
them
through
the
the
polygon
testnet
faucet
here
and
and
I
I,
basically
just
kind
of
set
up
Firefly
using
this
guide.
So
if
we
go
over
here,
we
can
see.
Firefly
is
running
so
what
I
want
to
do
now
is
I.
Have
my
default?
A
So
to
do
that,
I'm
going
to
do
a
couple
things
so,
first
of
all,
let's
go
create
the
the
other
signing
keys
and
sort
of
install
them
on
my
my
Firefly
signer.
So,
to
do
that
I
would
run,
FF
accounts
create
and
then
I
would
give
it
the
the
name
of
my
Firefly
stack,
and
this
would
be
I
called
it
webinar.
A
So
I
would
run
that
I've
already
run
this
a
couple
times
to
set
up
my
accounts,
so
I'm
actually
going
to
instead
of
FF
accounts,
create
I'm,
gonna
I'm
gonna
list
the
accounts
that
I
have,
and
it
should
give
me
three
okay,
so
here's
my
default
signing
key
here
is
my.
This
is
going
to
be
my
red
team
signing
key
and
my
blue
team
signing
key.
A
Please
don't
use
these
addresses,
as
I
have
now
just
leaked
their
private
keys
to
public
internet.
These
are
throwaway,
so
don't
do
anything
with
them.
That's
my
disclaimer!
Okay!
So
what
we're
gonna
do
is
we're
gonna,
there's
a
new
guide
in
the
docs.
Actually,
it's
it's
a
there's,
a
PR,
that's
open
for
it,
so
it's
not
quite
in
the
docs
yet,
but
here
it
is
I'm
going
to
walk
you
through
this.
So
this
is
how
to
enable
basic
auth
on
a
namespace.
A
If
you're
looking
for
general
information
on
just
you
know,
you
want
to
do
more
reading
on
on
namespaces
in
general,
there's
a
great
reference
guide
that
that
is
in
the
docs
here,
it's
under
reference
and
it's
under
namespaces,
and
this
just
walks.
You
through
you,
know
kind
of
starting
from
a
high
level
like
what
is
a
namespace,
the
difference
between
multi-party
and
Gateway
name
spaces,
how
to
configure
one
I.
We've
talked
through
a
lot
of
this
already
today
and
I'm
going
to
show
you
how
to
configure
it.
A
But
this
is
another
guide
that,
if
you
want
to
you,
know
kind
of
for
your
own
information.
If
you
want
to
read
up
on
it
afterward,
but
we're
going
to
go
through
a
couple
of
the
steps
here
in
this
basic
auth
guide
and
so
first
of
all,
we're
the
the
basic
auth
plug-in
for
Firefly
uses,
uses
bcrypt.
So
so,
basically
you
you
create
a
file
that
has
a
list
of
users
and
their
hash
passwords
in
it,
and
you
can
use
the
HT
password
utility
to
do
that.
A
So
I've
gone
ahead
and
done
that
and
I've
created
a
couple
of
those.
So
let
me
let
me
show
you
what
those
are
now
so
I've
got
now
we'll
just
use
this
terminal
here,
because
it
has
a
good
font
size,
see
I
could
just
cat
I've
created
one
called
test
users,
and
so
I
have
a
firefly
user
in
here,
and
this
is
the
hash
of
their
password
I
set
my
password
to
Firefly.
A
You
should
set
a
more
secure
password
than
that,
but
that's
what
it
is.
I
have
red
users
and
I
have
blue
users,
so
I
have
three
different
password
files,
one
for
just
general
test
users,
one
for
my
red
team
and
one
for
my
blue
team
and
they
each
have
one
username
in
them.
So
so
that's
what
I've
created
ahead
of
time
and
I
just
I
just
did
that
by
following
this
guide
here
and
using
the
HD
password
tool
to
create
that.
A
A
Okay,
cool
I
I
have
no
idea;
sometimes
it
doesn't
come
through
well
on
the
the
YouTube
stream.
So
hopefully
it
looks
good
on
YouTube.
You
know
just
I'll,
just
I'll
just
bump
it
up
one
just
to
be
sure.
Okay.
So
thanks
for
thanks
for
commenting
on
that
appreciate,
it
I
just
want
to
make
sure
that
people
can
follow
along
and
they're
not
having
to
squint
at
what
I'm
doing
here
all
right.
So
so
this
is
my
Firefly
core
config
file,
like
I,
said
we're.
A
Gonna
get
really
Hands-On
today,
so
I
have
one
namespace
configured
here.
It's
my
default
namespace.
It
has
a
default
signing
key,
that's
configured
and
it
has
a
list
of
plugins
they're
using
the
very
cleverly
named
database,
zero
blockchain,
zero
data
exchange,
zero,
shared
storage,
zero
and
a
token
connector
as
well.
If
I
go
further
down
here
in
the
yaml
file,
I
have
a
plugins
object
that
it
that
has
some
sections
in
it
has
a
section
for
each
of
the
different
types
of
plugins
that
Firefly
supports.
A
So
there's
a
blockchain
section,
a
data
exchange
object,
shared
storage
and
tokens
and
this
another
one,
a
new
one
auth
which
is
not
here
yet,
but
we're
going
to
add
that
so
so
each
of
these
is
so
so
my
disclaimer
is
I.
I
do
not
have
a
degree
in
yaml
editing
but
I'm
going
to
do
the
best
that
I
can
here
so
hopefully,
I
get
all
my
indentation
correctly
and
this
this
works,
but
yeah
yaml's
a
fun.
A
It's
it's
great
and
and
I
love
it
and
hate
it
all
the
same
time.
So
each
of
these
so
like
blockchain,
is
a
list.
So
we
have
one
item
in
the
list
and
it's
ethereum,
and
it
is
we've
said
it's
so
get
a
name
of
blockchain
zero
and
we've,
given
it
a
type
of
ethereum.
So
so
it's
a
list
of
objects
here,
and
so
you
could
continue.
You
could
configure
more
than
one
blockchain
connector
this
way,
all
right.
A
So
what
we're
going
to
do
so
that
I
I
get
my
yaml
correct,
I'm,
going
to
hop
back
over
to
my
guide
and
I'm
going
to
copy
this
section
here-
and
this
is
this-
is
our
configuration
for
our
off
plugin
and
I'm?
Gonna
go
paste
this
in
so
we're
defining.
This
is
a
new
type
of
plug-in,
so
so
in
the
op.
So
we're
setting
up
like
all
of
our
different
auth
plugins
here
so
here,
I'm
creating
one
and
I'm
calling
it
test
user
auth,
its
type
is
basic.
A
A
But
this
is
where
we're
going
to
put
it
right
now,
it's
just
in
my
home
directory
on
my
host
machine,
so
I
need
to
define
a
couple
other
ones
for
my
my
red
team
and
my
blue
team
as
well,
and
I'm
gonna
get
my
indentation
right
here
and
then
we're
gonna
say
we're
going
to
call
this
one
red
user
auth
and
we're
going
to
change
this
to
Red
users,
and
this
is
going
to
be
blue
user
auth,
and
this
will
be
blue
users
Okay.
So
we've
defined
our
three
plugins.
A
We
don't
have
any
namespace
using
those
plugins.
Yet
though,
so
what
we're
going
to
do
is
we're
going
to
scroll
up
here
to
our
existing
namespace
and
I'm,
going
to
I'm
going
to
create
some
more
namespaces
here
now
I
could
I
could
use
this
test
user
auth
on
the
default
namespace
if
I
wanted
to
I'm
actually
going
to
for
now.
A
A
And
make
sure
this
is
all
indented
correctly,
because
that
matters
in
yaml
Okay,
so
we've
got
three
different
namespaces
we're
gonna
call
this
one
red
its
name
is
gonna
be
red.
It's
just
this.
One's
description
is
blue
and
it's
name
is
blue
Okay,
so
we've
got
three
different
name
spaces
that
are
named
differently,
but
they're
all
using
the
same
plugins
right
now
and
they're
all
using
the
same
signing
key
right
now.
So
now
we're
going
to
customize
them
a
little
bit.
A
So
this
is
my
default
one
I'm
going
to
assign
this
one
to
my
red
team
and
this
one
to
my
blue
team,
all
right,
so
that
should
be
good
to
go
for
the
Firefly
config.
If
I
remembered
everything
correctly.
The
next
step
is,
we
need
to
actually
so
so
Firefly
when
you
run
Firefly
CLI
runs
all
the
different
components
in
Docker
containers
and
so
I
need
to
actually,
like
I
said
that
those
password
files
are
are
sitting
in
my
home
directory
on
my
host
machine
I
need
to
get
them
into
the
docker
container.
A
Somehow
so
the
way
to
do
that
is
by
adding
a
Docker
compose
override.
This
is,
in
my
opinion,
the
easiest
way
to
do
it,
there's
more
than
one
way
to
skin
a
cat,
but
so
what
I'm
going
to
do
is
I'm
going
to
edit
my
my
Docker
compose
override
file
for
my
stack
now
and
we're
just
going
to
open
that
up
here,
actually
I
think
I.
Have
it
I
think
I
actually
have
it
open
in
another
tab
yep
here
it
is
okay,
so
this
is
what
it
looks
like
by
default.
A
All
right
I
hit
save
okay,
so
that
should
be
good
to
go
now.
I
have
three
different
namespaces
I
am
I,
have
three
different
password
files,
I'm
I'm
mounting
the
the
appropriate
files
in
there
at
this
point,
if
you're,
following
along
in
the
guide,
what
you
would
need
to
do
is
actually
restart
your
Firefly
stack
to
pick
up
the
new
Docker
compose
overrides
and
read
the
new
config
file,
so
you
run
FF,
stop
ffstart
again
for
the
sake
of
time.
A
I've
gone
ahead
and
done
this
already,
and
so
now
what
we
should
be
able
to
do
is
we
should
be
able
to
make
some
requests
to
our
Firefly
node.
So,
first
of
all,
actually
we
should
be
able
to
come
here
and
see.
We
have
three
different
namespaces.
Now
we
got
the
default
One,
the
red
one
and
the
blue
one.
A
We
should
be
able
to
make
some
requests
to
the
various
namespaces,
and
so,
if
I
try
it,
for
instance,
if
I'm
a
red
user,
I've
added
a
username
and
password
here
to
my
curl
request,
I
try
to
access
the
blue
namespace
I
get
unauthorized.
Likewise,
if
I
try
to
access
my
own
namespace
I
can
I
can
query
the
API,
so
that's
good,
so
so
auth
is
working.
A
It
basically
just
lets.
You
set
an
integer
on
a
blockchain
and
query
it
back
and
that's
the
and
it
emits
an
event
as
well.
So
so
I
went
down
here
so
I.
We
can
go.
Look
at
this
again.
This
is
using
a
public
chain,
so
you
can
go.
Look
up
this
contract
that
I
deployed
earlier
I
deployed
that
from
my
default
signing
key
here
and
then
I
set
the
value
original.
A
This
I
set
the
value
in
this
transaction
with
my
default
signing
key
and
then
I
set
it
with
the
as
the
red
team
over
here
in
just
a
minute,
I'm
going
to
go
set
it
as
the
blue
team
and
we'll
see
what
that
looks
like
so.
I
should
be
able
to
actually
pop
into
these
and
see
if
I
can
see
what
I
actually
set
it
to
yeah.
A
A
So
what
I'm
gonna
do
is
I'm
gonna
pull
up
Postman,
because
that
will
let
me
set
off
very
conveniently
here.
Let's
do
actually
before
we
set
it.
I'm
gonna
I'm
gonna,
do
a
I'm
actually
going
to
weary,
get
I'm
just
gonna
double
check
my
value
and
then
I
want
to
do
this
as
the
the
blue
I'm
going
to
do
this
in
the
blue
name
space.
A
A
So
let's
set
it
to
three
so
basically,
where
you're
going
to
change
this,
to
invoke
if
you've
seen
Firefly
demos,
you're,
probably
familiar
with
how
Firefly
builds
these
rest
apis
for
for
smart
contracts,
already
I've
just
gone
ahead
and
set
up
all
of
that
ahead
of
time,
just
just
for
the
sake
of
time,
so
we're
going
to
invoke
set
and
the
see.
Actually
you
know
what
I
have
this
I
believe
I.
Have
this
query:
yeah?
A
Here's
here's
the
correct
payload
for
that
I'm
just
going
to
copy
this
over
here
and
I
will
set
our
new
value
to
three
and
make
sure
I'm
doing
it
in
the
blue,
namespace
and
I've
set
my
user
off
to
Blue
all
right.
So
let's
run
this
Okay,
so
we've
submitted
a
transaction.
It's
currently
pending
the
new
value
will
be
three,
and
so
you
know
the
the
ideally
here.
This
would
be
your
application
submitting
a
transaction,
not
a
human,
at
sitting
down
at
Postman
and
your
transaction
or
sorry.
A
Your
application
would
also
be
listening
on
Firefly's
websocket
for
receipts
from
you
know
when
the
transaction
was
is
actually
complete.
So
you
would
know
immediately
once
that
fourth
confirmation
has
come
in
I
I,
don't
have
a
websocket
listener
set
up
at
the
moment,
but
what
we
can
do
is
we
can
go
back
here
and
we
can
look
at
the
at
the
look
at
that.
There's
our
our
transaction
came
in
28
seconds
ago.
It
was
the
set
method
and
look
at
this.
A
It
was
from
the
other
from
a
new
signing
key
that
we
haven't
seen
here
before
and
I
bet.
If
we
go
back
to
our
Firefly
config
0x1ce
yep,
that
is
that's
our
blue
teams
signing
key,
so
blue
team
just
set
it
to.
Let's
take
a
look
at
the
transaction
itself
and
it
set
it
to
three.
So
there
we
go
so
this
is
this:
is
a
public
transaction?
You
know
anybody
can.
If,
if
you're
clever
at
copying
and
pasting
from
a
video
you
could
you
could
go
look
up.
A
My
transaction
on
my
polygonscan.com
and
you
can
see
those
transactions
coming
in
there
on
that
contract.
So
that
was
that's
it
that
I
had
for
the
the
Hands-On
section
of
this
kind
of
walking.
Through
all
these
new
features,
you
know
starting
up
Firefly
and
Gateway
mode,
connecting
it
to
a
public
test
net
configuring,
multiple
namespaces,
you
for
our
red
team
and
our
blue
team,
enabling
basic,
auth
and
and
Performing
transactions
with
different
signing
keys
for
each
on
those
different
name
spaces.
A
So
that's
it
for
the
for
the
demo
portion
just
one
more
slide
before
we
wrap
up
and
then
we'll
leave
a
couple
minutes
for
questions
here
at
the
end,
but
I
just
I
just
want.
First
of
all
wanted
to
thank
everyone
for
coming
out
today.
We've
had
a
great
turnout
here
and
super
excited
about
where
we're
at
in
the
project,
but
most
most
of
all,
I'm
excited
that
that
so
many
other
people
are
excited
about
the
project
and
that
you're
here
and
wanting
to
learn
about
it.
A
So
I
just
wanted
to
take
this
moment
to
encourage
you.
If,
if
you
haven't
already,
please
join
get
get
more
involved
in
the
community
join
in
Discord.
This
is
a
great
place.
If
you
have
you
know
after
today.
If
you
have
questions
for
me
or
for
the
rest
of
the
team
or
other
maintainers,
there's
a
firefly
channel
in
Discord
go
ahead
and
join
there,
and
we
would
love
to
chat
with
you
there.
A
A
A
A
Why
does
the
query
API
doesn't
trigger
the
blockchain
event,
good,
good
questions?
Okay,
so
I'll
try
to
hit
these
as
quickly
as
we
can
here.
So,
yes,
I
started
in
Gateway
mode,
the
Firefly
CLI
right
now,
so
the
Firefly
CLI
is
a
tool
to
create
a
local
development
environment
in
its
current
state.
It
has
the
ability
to
set
up
a
stack
and
configure
a
namespace
in
either
Gateway
mode
or
multi-party
mode.
Firefly
can
absolutely
operate
in
both
modes.
A
At
the
same
time,
the
tooling
automation
to
just
configure
that,
based
on
one
command
line,
This
is
not
there
at
the
moment
to
create
like
a
local
development
environment.
I
I
have
done
it
before
I've
demoed
it.
That
was
one
of
the
things
we
showed
it
at
hyperledger
global
forum
and
it
was
really
cool.
We
talked
to
both
a
fabric
chain
running
locally
on
my
computer
and
a
public
chain
testnet
as
well.
A
There's
there's
quite
a
bit
of
configuration
that
goes
into
that.
So
the
it's
you
know
it
is
absolutely
a
supported
use
case
and
definitely
something
that
you
could
use
in
production.
There's
just
not
a
tool
to
set
up
like
a
local
development
environment
that
has
many
namespaces
configured
in
in
very
different
ways.
A
Why
does
the
query
API
not
show
up
in
the
blockchain
Explorer?
That
was
a
great
question,
so
the
the
query
API
actually
does
not
perform
a
blockchain
transaction.
It's
using
a
different
it.
It
is
using
a
different
Json.
Rpc
call
at
the
sort
of
the
ethereum
protocol
layer,
and
so
it
doesn't
perform
a
transaction.
It
just
queries
the
current
state
of
the
chain,
so
it
actually
doesn't
need
gas
to
do
that
and
that's
something
you
could
do
for
free
that
that
doesn't
cost
a
transaction.
A
Would
it
be
right
to
call
Firefly
middleware
software,
yeah
I?
Think
that's
a
you
know
as
as
boring
as
the
word
middleware
sometimes
sounds
yes,
I
I
think
it
is,
if
you
think,
if
you
think
of
it
as
a
stack
that
sits
between
your
application
logic
at
the
top
and
a
blockchain
at
the
bottom,
it
it
fits
the
definition
of
middleware
absolutely.
A
A
How
can
we
apply
triggers
in
a
hyper
Ledger
I
apologize,
I'm,
not
I,
I'm
unclear
on
what
that
question
is
asking.
If
you
could
clarify
that
would
be
great
and
I
can
I
can
try
to
come
back
to
it
as
Firefly
part
of
Linux
Foundation?
Yes,
absolutely
so
Firefly
is
is
a
hyperledger
project.
The
hyperledger
foundation
is
a
part
of
the
Linux
Foundation,
specifically
focused
on
Enterprise
blockchain
software.
A
A
Yes,
absolutely
so
so
Firefly
looks
at
tokens
from
a
a
slightly
higher
level
perspective,
so
so
fireflies
tokens
apis
are
mint,
burn,
transfer
and
approve.
So
as
long
as
a
token
can
do
those
four
things,
Firefly
can
support
it.
No
problem,
the
the
thing
that's
necessary
to
add
would
be
if
you
have
a
token
that
has
a
different
contract
interface
than
any
or
C20
or
721
or
1155..
The
there
are
blockchain
connectors.
So
we
didn't.
A
We
didn't
look
at
the
big
Firefly
architecture
picture
today,
but
there's
a
a
small
piece
that
sits
in
between
Firefly
core
and
the
blockchain
connector,
and
we
call
it
a
token
connector
and
that
token
connector
is
usually
written
to
to
know
the
inner
workings
of
a
particular
token
contract,
and
so
it's
a
very
lightweight
small
microservice.
That
knows
how
to
talk
to
a
specific
token.
A
So
if
you
wanted
to
run
something
so
we
have
token
connectors
for
erc20,
erc721
and
1155
today,
so
those
are
the
three
that
are
supported
out
of
the
box.
Firefly
core
itself,
though,
could
talk
to
can
work
with
I
I'll
I'll,
say
any
theoretically
any
type
of
token,
as
long
as
there's
a
token
connector
for
that
type
of
token.
A
A
A
Okay,
well,
thank
you
all.
So
much
really
appreciate
everyone's
time
today
and
super
happy
to
to
kind
of
dive
a
little
deeper
into
Firefly,
1.1
and
yeah.
Just
thank
you
for
the
all
the
great
questions
and
and
the
great
participation
for
today
we're
gonna,
I
I,
see
one
or
two
more
questions
in
there,
but
we're
out
of
time
I
apologize,
we'd
love
to
take
those
questions
offline.