►
Description
A virtual meetup hosted by Hyperledger Raleigh on January 18, 2023 featuring Andrew Richardson, a senior full-stack engineer at Kaleido. Andrew will talk about how to connect to public and private chains with Hyperledger FireFly.
For Enterprises looking to take advantage of web3, it’s critical that they have a gateway to connect to the multi-chain, multi-protocol web3 world.
Hyperledger FireFly provides exactly that, and in this meetup, Andrew Richardson, Senior Full Stack Engineer at Kaleido and Hyperledger FireFly maintainer, will show you how Hyperledger FireFly makes it possible to build apps that connect to both public and private chains.
You’ll learn how Hyperledger FireFly makes it easy to:
* Connect to popular public chains including Ethereum, Polygon, Avalanche, Optimism, Arbitrum, and more.
* Handle the complex concerns of public chains, including gas estimation and resubmission policies.
* Access both public and private chains simultaneously, while building in guardrails specific to the enterprise space that ensure new apps meet both user and compliance requirements.
With live coding and easy-to-follow steps, you’ll have everything you need to build and run your own blockchain-powered app.
This session is targeted to developers of intermediate skill level and above, with some prior amount of blockchain knowledge. New developers or those without any prior blockchain knowledge will still find it informative, as Hyperledger FireFly is very approachable. At the same time, it is also flexible and customizable to meet the needs of experienced blockchain developers.
And to find out more about FireFly, including how to join their regular calls and Discord channel, check out their wiki at:
https://wiki.hyperledger.org/display/FIR/Hyperledger+FireFly+Home
----
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)
B
Great
well
welcome
everyone
to
a
hyperledger
Meetup
focused
on
hyperledger
Firefly.
My
name
is
Andrew
Richardson
I'm,
one
of
the
maintainers
of
hyperledger
firefly
and
I
work
for
a
company
called
collido
that
provides
hosting
services
for
blockchain
nodes
and
and
blockchain
services
related
to
that
and,
of
course,
hosting
for
Firefly
itself,
so
always
love
to
talk
about
Firefly
and
the
capabilities
it
brings
and
the
the
really
easy
developer
experience
for
building
really
powerful
blockchain
applications.
So
the
topic
today
is
connecting
to
public
and
private
chains
with
hyperledger
firefly.
B
So
we're
going
to
talk
through
a
lot
of
that
today.
Just
a
kind
of
quick
overview
of
the
agenda
I
want
to
start
with
an
overview
of
firefly
and
the
Firefly
blockchain
connectors,
just
to
kind
of
set
the
stage
I
know
many
of
you
are
familiar
with
firefly,
but
I
want
to
make
sure
everyone
knows
kind
of
the
pieces
and
how
they
fit
together
and
then
I've
set
up
a
demo
environment
that
is
connected
to
both
a
public
and
private
chain.
B
So
we're
going
to
do
kind
of
an
interactive
tour
of
that
setup
and
see
how
the
pieces
fit
together
and
what
you
get
out
of
the
box
with
a
firefly
development
environment.
And
then
you
were
promised,
live
coding
in
the
description.
So
we're
going
to
do
some
live
application,
coding
kind
of
show
taking
how
do
those
pieces
fit
together
and
how
could
I
build?
You
know
an
actual
start
of
an
application
that
can
do
really
cool.
B
You
know,
coordinating
of
on
and
off
chain
and
coordinating
of
public
and
private
chain
events
to
kind
of
build,
an
actual
sort
of
starter
application
use
case.
So
that's
kind
of
the
agenda
today,
since
this
is
a
Meetup
I'm
happy
to
keep
it
interactive.
If
you
want
to
interject
with
questions
or
ask
for
more
details
on
anything,
I've
got
some
of
my
colleagues
and
co-workers
on
the
call,
as
well
that'll
kind
of
help
to
keep
an
eye
on
the
chat.
B
If
you
have
questions
about
anything
as
we
go
along
so
with
that
said,
I'm
kind
of
starting
at
the
most
zoomed
out
picture,
and
and
what
is
what
hyper
hyperledger
Firefly
is
and
what
it's
trying
to
provide
in
the
web.
3
landscape
web3
has
come
a
long
way
and
there
are
so
many
different
facets
to
it.
B
You
have
whole
ecosystems
and
defy
angles
to
it,
right
from
coins
to
Dows
to
all
these
different
constructs
that
are
being
built
on
top
of
web3,
and
it
can
be
kind
of
difficult
to
figure
out.
You
know
how
do
you
connect
to
any
one
of
these
different
things?
If
you
want
to
focus
on
one
particular
angle,
there's
usually
a
very
steep
learning
curve
for
each
one
of
them,
and
what
Firefly
is
aiming
to
be
is
to
not
be
any
one
of
these
particular
bubbles
right.
It's
not
specifically
for
consortiums.
B
It's
not
a
chain
itself,
it's
not
specifically
for
D5,
but
it's
aiming
to
be
the
glue
and
the
Gateway
that
connects
everything
else
together
right
it.
We
call
it
a
web
3
super
node.
So
it's
a
toolkit.
It's
a
set
of
services
that
allow
you
to
connect
whatever
web3
and
blockchain
Technologies
you
care
about
connect
them
together
and
build
real
applications
on
top
of
them
by
taking
advantage
of
a
lot
of
integration
code,
a
lot
of
orchestration
code
and
all
the
kind
of
really
difficult
problems
that
kind
of
come
out.
B
Many
of
you
might
have
seen
this
on
on
some
of
the
other
hyperledger
Firefly
calls,
but
hyperledger
Firefly
has
become
a
very
large
project
and
the
name
of
the
game
is
modularity.
Definitely
has
an
open
source
Community,
aiming
to
keep
this
as
modular
as
possible
and
continue
adding
different
tools
into
this
ecosystem,
with
as
wide
support
as
possible
for
for
different
blockchain
Technologies.
B
Some
of
the
big
pieces
in
the
Box
here
at
the
bottom
Firefly
cores
orchestration
engine
is
kind
of
the
brains
of
all
this,
and
it
knows
how
to
orchestrate
all
sorts
of
different
events
together
on
chain
off
chain.
Token
events,
public
chain
events,
private
chain
events
and
that's
one
of
the
big
value
ads
that
we're
going
to
talk
through
and
how
you
can
leverage
that
for
building
an
application,
but
a
lot
of
other
pieces
here
that
come
right
out
of
the
box.
B
When
you
start
a
Project
based
on
hyperledger
Firefly
right,
it
can
take
your
smart
contracts
and
it
can
give
you
apis
and
make
it
really
easy
to
build
sort
of
a
more
traditional
application
architecture.
That's
backed
by
a
smart
contract
by
converting
those
smart
contracts
into
HTTP
apis
and
giving
you
reliable
event
streaming
out
of
them.
You
can
do
very
complex,
complex
flows
between
multiple
parties.
B
You
can
have
a
very
strict
control
over
privacy
and
security,
and
you
can
have
very
strict
control
over
what
goes
on
chain
and
what
goes
off
chain
and
how
those
things
are
married
together,
and
you
can
use
these
streams
of
events
to
trigger
application
logic
based
on
both
on-chain
events
and
off-chain
events
and
we're
gonna.
We're
gonna
talk
through
some
of
that
and
show
some
examples
of
how
these
flows
can
can
progress
both
on
public
and
private
and,
of
course,
there's
a
whole
component
to
digital
assets.
B
Very
easy
to
use
token
apis
minting,
burning,
transferring
fungible
tokens,
non-fungible
tokens
and
tracking
wallets
and
there's
a
bit
of
that
in
the
demo,
as
well,
so
around.
All
that
just
a
lot
of
the
kind
of
tools
that
you'd
expect
from
a
robust
developer,
ecosystem
sdks,
a
CLI,
Tool
web
tools
and
explorers
metrics
lots
of
things
come
in
the
box,
so
just
kind
of
plugging
a
little
bit
of
what
Firefly
is
and
all
the
things
that
are
kind
of
part
of
the
ecosystem.
B
We're
only
going
to
touch
on
a
few
of
them
today,
but
we'd
definitely
love
to
see
people
get
involved
in
the
open
source
project
on
any
of
these
pieces.
That
interest
you,
you
know,
join
us
on
Discord
and
talk
to
hear
more
about
all
of
them,
zooming
down
a
little
bit
below.
If
you
look
kind
of
in
this
picture,
because
today
we're
talking
very
specifically
about
public
and
private
chains,
there's
actually
a
whole
piece
of
firefly
that
you
can't
see
in
this
zoomed
in
picture.
B
So
right
here
between
Firefly
and
the
blockchain
is
another
layer.
That's
very
interesting
and
I
think
particularly
of
interest
to
this
audience.
If
you're,
looking
at
various
public
and
private
chains
and
that's
the
Firefly
blockchain
connector
framework,
so
Firefly
again
is
not
a
blockchain
node
and
it
doesn't
connect
to
any
single
blockchain
node.
It
provides
a
set
of
layers
and
interfaces
for
connecting
agnostically
to
any
number
of
different
blockchain
nodes.
B
So
the
two
well-supported
connectors
that
come
as
part
of
the
open
source
project
are
one
called
evm
connect
for
connecting
to
evm-based
chains
like
ethereum
and
then
one
for
connecting
to
fabric
networks,
I'm
going
to
be
focusing
a
little
bit
more
on
the
evm
layer
today,
just
because,
in
terms
of
connecting
to
public
and
private
chains,
ethereum
ecosystem
lends
itself
very
well
to
that
and
there's
plenty
of
public
evm
based
chains.
So
we'll
use
some
of
that
as
a
foundation
today,
but
you
can
actually
mix
and
match.
B
You
can
have
a
firefly
that
talks
to
a
fabric
Network
and
an
evm
Network,
so
lots
of
capabilities
here
again
trying
to
keep
it
as
modular
as
possible.
So
Below
Firefly
itself.
We
have
a
layer
that
we're
going
to
mostly
be
using
evm
connector
today
and
there's
this
whole
API
that
it
leverages
that
can
be
used
for
building
your
own
blockchain
connectors
as
well,
so
we're
not
tied
into
just
the
ones
that
are
in
the
Box,
evm
connector.
B
Sorry,
evm
based
blockchains
could
easily
be
forked
off
of
evm
connect
and
other
blockchains
can
probably
share
a
lot
of
the
code
if
you
needed
to
build
custom
connectors
there.
One
thing
that's
really
interesting
in
connecting
to
public
chains
in
particular,
is
that
it's
been
designed.
The
connector
toolkit
itself
has
been
designed
with
a
lot
of
plugable
pieces,
so
not
only
the
whole
connector
can
be
plugged,
but
little
pieces
of
it
can
be
changed,
such
as
the
policy
engines.
A
B
So
I'm
gonna
pause
for
a
second
show
some
GitHub
links
that
might
help
some
people
that
are
really
interested
in
getting
involved
and
digging
in
then
try
to
come
back
and
answer
as
many
of
the
questions
as
I
can.
So,
of
course,
the
place
to
get
started
is
the
Firefly
GitHub
right.
This
is
the
core
run
time
that
was
in
that
big
box.
On
the
first
slide,
github.com
hyperledger
Firefly
you'll
find
links
to
the
Firefly
documents
and
links
to
some
of
the
other
important
bits.
B
B
Then
we
have
evm
connect,
which
I'm
talking
a
lot
about,
and
this
is
designed
to
be
the
connector
layer
that
sits
below
Firefly
and
can
connect
to
any
evm
based
blockchain.
So
we're
talking,
you
know,
ethereum
blockchains,
like
bezu
and
like
go
ethereum
nodes
and
also
l2s
like
polygon,
that
support
you
know
evm
and
Json
RPC.
So
this
is
kind
of
your
starting
point
for
any
evm
based
blockchain.
B
So
right
now
we
have
very
good
support
for
evm
and
if
any
blockchain
is
kind
of
a
slight
variation
on
evm,
this
would
be
the
starting
point
to
kind
of
build
that
the
other
piece
that
I
talked
about.
That's
a
big
part
of
the
blockchain
connector
framework
is
this
Firefly
transaction
manager,
which
is
leveraged
by
evm
connect
and
would
be
leveraged
by
any
blockchain
connector.
B
This
generalizes
some
of
the
flows
about
the
policy
when
I'm
showing
this
kind
of
policy
engine
over
here
it
has
plug
points
for
registering
your
own
policy
engine
and
handling
okay.
How
does
my
network
have
gas
right?
Most
blockchains
have
some
notion
of
gas,
whether
they
call
it
that
or
something
else.
But
how
does
my
network
handle
gas?
How
does
it
handle
estimating
gas
paying
for
gas
resubmitting
based
on
failures?
That
kind
of
thing,
so
that's
kind
of
the
tour
of
the
pieces
involved.
B
If
you
would
like
to
you
know,
get
involved
in
the
open
source
Community.
These
are
probably
the
three
that
are
of
interest
to
you.
There
was
a
question
about
exactly
what
is
supported
in
the
open
source
Community
right
now,
and
that
is
exactly
the
two
that
I
talked
about:
the
evm
connect,
blockchain
connector
and
the
Fab
connect
blockchain
right,
so
evm
evm
base
change
and
Fab
connect
for
fabric
based
chains.
A
Yeah
and
and
just
a
quick
housekeeping
note
if
you
are
not
speaking,
if
you
wouldn't
mind
putting
your
mic
on
mute,
that
would
be
great
if
you
have
a
question
that
you
you'd
like
to
raise,
feel
free
to
raise
your
hand
and
we'll
be
happy
to
answer
your
question,
but
just
to
keep
down
on
background
noise
be
great
if
folks
were
on
mute
yeah.
So
the
other
question
was
about
like
webassembly
based
chains.
A
There
I've
had
some
conversations.
I
had
some
conversations
with
Folks
at
hyperledger
global
forum
about
this,
and
there's
no
support
for
that
today.
Definitely
something
possible
in
the
future,
assuming
that
the
the
chain
has
a
few
kind
of
Core
Concepts
like
block
numbers
and
there's
yeah.
We
we
can
go
to
detail
about
like
what
are
the
minimum
requirements
of
a
chain
to
for
for
Firefly
to
support
it,
but
that's
that's
probably
a
a
deeper
technical.
C
A
A
A
B
And
I
know:
there's
been
some
talk
about,
you
know,
could
could
there
be
Synergy
between
Firefly
and
projects
like
cactine
Weaver?
For
you
know,
if
you
want
to
do
that,
interoperability
at
the
lower
level
and
then
orchestrate
it
up
and
that's
you
know
definitely
within
the
realm
of
of
things
that
could
be
supported
because,
like
you
said,
Firefly
is
all
about
kind
of
one
level
up.
It
can
talk
to
multiple
chains,
but
it's
not
directly
doing
on-chain
integration
between
them
and
I'm,
going
to
show
kind
of
an
example
of
this.
B
D
B
Does
Firefly
allow
processing,
configure
configuration
updates
as
part
of
fabric
yeah?
Firefly
is
definitely
sitting
on
top
of
fabric
at
more
of
a
sort
of
higher
level.
So
a
lot
of
the
core
fabric
constructs
remain
core
fabric
constructs
if
that's
kind
of
a
general
answer,
so
so
yeah
I
I,
don't
think
I,
I,
guess
I'm
not
familiar
enough
with
fabric
in
terms
of
processing
configuration
updates
what
that
entails.
So
you
probably
don't
have
a
full
answer
on
that
question.
B
B
B
You
know.
These
are
not
directly
on
chain
but
they're
applications
that
want
to
interact
with
events
that
are
coming
from
blockchain
right,
and
this
is
kind
of
the
common
use
case.
That's
emerging
in
a
lot
of
web
3
spaces
right,
I
have
existing
business
logic
or
I
have
new
applications
that
I
want
to
write,
but
I'm,
not
writing
the
entire
thing.
As
adapt
that's
going
to
live
on
the
blockchain.
B
So
the
problem
with
these
types
of
applications
and
the
problem
that
Firefly
is
aiming
to
solve,
because
you
know
we,
as
the
founders
and
maintainers
saw
this
kind
of
being
solved
over
and
over
and
over
again,
and
it's
a
typical
problem.
Every
time
you
solve
it
is
decentralized
event.
Processing,
so
I
mean
the
way
that
you
can
set
up
an
application
under
the
Firefly
architecture.
Is
you
can
run
many
different
applications
or
different
instances
of
the
same
application
in
completely
decentralized
places?
Right?
B
You
can
have
an
app
running
over
here
in
org
ones,
data
center
or
Cloud.
You
can
have
an
app
running
over
here
in
org2's
data
center
or
Cloud.
They
don't
need
Ingress
to
each
other.
They
don't
need
to
communicate
directly
all
they
need
to
communicate
reliably.
Is
these
two
kind
of
pipelines
at
the
bottom
right,
a
blockchain
node
with
some
amount
of
on-chain
smart
contracts
that
are
going
to
store?
Whatever?
Is
the
you
know,
sort
of
decentralized,
adapt,
blockchain
State
and
then
always
there's
always
this
other
rail
for
off-chain
data?
B
B
I
have
some
way
for
these
two
apps
to
directly
send
a
packet
of
data
to
each
other,
and
then
I
have
some
way
for
them
to
both
access,
a
common,
on-chain,
smart
contract
and
then
the
problem
is
to
keep
them
both
in
the
state
the
same
state
right.
So
this
notion
of
an
application.
State
machine
is
really
critical
and
I'm
gonna
as
part
of
the
live
coding
kind
of
show.
B
What
does
it
look
like
to
spin
up
a
very
basic
application,
State
machine
that
can
function
in
an
architecture
like
this,
so
Firefly
helps
to
sequence.
The
events
coming
from
both
of
these
sources
right
from
the
private
data
that's
sent
to
me,
and
only
me
directly
from
some
other
member,
and
also
the
events
that
are
happening
on
the
blockchain
and
how
do
I
kind
of
marry
those
things
together.
How
do
I
keep
private
data
private?
B
How
do
I
sequence
things
in
a
reliable
order,
so
my
app
State
machines,
even
though
they're
not
directly
syncing
State,
they
always
end
up
in
the
same
state
because
they
process
events
in
exactly
the
same
way.
So
that's
that's
one
of
the
difficult
problems
to
solve
and
what
I'll,
hopefully
kind
of
show.
As
part
of
this
demo
did
we
have
more
questions
popping
up.
B
Okay,
yeah
I
think
Nico
answered
it
in
chat.
There
was
a
question
about
Atomic
transactions
across
multiple
blockchains
and
no
Firefly
at
this
time
doesn't
have
a
cross
chain,
Atomic
guarantee.
So
again,
it's
definitely
something
that
could
be
plugged
in,
and
you
know,
love
having
those
continuing
discussions.
But
at
this
time
we're
focused
very
much
on
the
sort
of
application,
Level
integration.
B
Okay,
good
thanks
for
the
questions,
keep
them
coming,
so
the
architecture
for
the
demo
that
I'm
going
to
show
you
today
is
a
bit
like
this.
I
have
two
members:
these
members
are
in
a
private,
multi-party,
Network
or
Consortium
right.
This
is
one
of
the
use
cases
in
the
web,
3
landscape,
that
we
talked
about
these.
You
know
our
organizations
that
need
to
share
some
amount
of
private
data
with
each
other
and
they
want
to
use
a
blockchain
ledger
to
kind
of
verify
that
data.
B
On
the
other
hand,
Member
One
is
also
going
to
serve
a
role
where
they
need
to
help
communicate
with
a
public
chain,
so
they
are
going
to
have
two
namespaces.
This
is
a
construct
in
Firefly
for
kind
of
grouping
what
your
plugins
are
and
what
your
blockchains
are.
So
both
Member
One
and
member
two
are
members
of
a
default
Firefly
namespace,
that
is
a
private
multi-party,
Network
they're,
going
to
share
the
same
type
of
blockchain
connectors.
B
They
can
both
talk
to
a
private
ethereum
sidechain
over
here,
so
you
can
see
they're
they're
each
operating
an
ethereum
node
that
forms
a
private
side
chain
they're
both
going
to
have
token
connectors
so
that
they
could
create
tokens
and
share
them,
and
they
have
that
private
data
exchange
pipe.
That
I
talked
about
I'm
using
the
open
source,
Firefly
data
exchange,
which
is
based
on
Mutual
TLS,
and
they
have
ipfs
a
private
ipfs,
not
public
ipfs.
B
This
is
an
ipfs
runtime,
that's
shared
between
them,
so
that
they
can
post
data
that
needs
to
be
visible
to
anyone
on
the
network
right.
So
that's
my
one
namespace,
on
the
other
hand,
number
one
also
has
an
additional
namespace
for
connecting
to
polygon.
So
this
Firefly
node
is
not
only
talking
to
a
ethereum
node,
that's
part
of
a
private
Network.
It's
also
talking
to
an
ethereum
node
that
has
been
joined
to
the
or
it's
talking
to
a
polygon,
node.
That's
joined
to
the
public
polygon
Mumbai
test
net.
B
So
if
you
follow
the
getting
started,
guide,
it'll
walk
you
through
getting
the
Firefly,
CLI,
Tool
and
then
starting
an
environment
by
default.
You
get
a
stack,
that's
a
multi-party
system
that
kind
of
represents
a
system
similar
to
this
right
hand,
side
the
command
that
you
run,
for
that
is
this
FF
init
by
default,
you'll
get
a
two
or
three
member
stack.
However,
many
members
you
specify
and
you're
up
and
running
it's
going
to
start
a
bunch
of
Dockers
using
Docker
compose.
B
On
the
other
hand,
if
you
want
to
connect
to
public
chains,
there's
another
tutorial
that
might
be
interesting
to
you
for
this
connecting
for
remote
blockchains
like
connecting
to
polygon.
So
if
you
run
a
slightly
different
init
command
with
your
CLI,
you
can
create
a
network
that
connects
to
public
Mumbai
test
net
right
by
selecting
an
RPC
endpoint.
That's
joined
to
that
Network.
Now
getting
a
more
complex
setup
that
talks
to
both
is
kind
of
an
additional
exercise.
B
So
I
have
not
included
the
setup
as
part
of
the
demo,
because
it
would
just
kind
of
be
me
writing
yaml
for
30
minutes,
and
it
didn't
seem
very
interesting.
But
what
I've
done
is
kind
of
built
a
stack
on
top
of
what
you
get
by
adding
a
bunch
of
extra
Docker
containers
right.
So
it
spun
up
some
of
the
docker
containers
for
me
and
then
I've
kind
of
by
hand
edited
my
Docker
compose
override
to
add
a
handful
of
other
Docker
containers
that
allow
me
to
talk
to
polygons.
B
So,
as
you
become
a
little
more
advanced
with
firefly,
you
can
build
on
what
the
CLI
gives
you
by
building
custom,
Docker
environments.
So
I've
got
a
whole
bunch
of
Dockers
running
here,
and
this
is
kind
of
the
development
environment
that
I've
set
up
for
for
this
type
of
public
private
chain
use
case.
B
And
then,
of
course,
when
you
want
to
move
to
production,
Firefly
provides
starter,
Helm
charts.
So
you
can
kind
of
graduate
from
local,
Docker
and
Docker
compose
to
proper
deployed
kubernetes
infrastructure
and
just
kind
of
take
your
same
code
that
you're
able
to
develop
locally
and
and
put
it
right
out
into
production
on
a
proper
hosting
solution.
B
So
I'm,
starting
today
with
a
whole
bunch
of
Dockers
I'll,
show
you
kind
of
some
of
the
tools
that
come
in
the
box
with
firefly
as
well,
so
each
node
gets
a
UI,
so
Firefly
has
a
very
robust,
Explorer,
UI
again
I'm
sure
many
of
you
have
played
around
with
this
and
seen
it.
But
if
you
haven't
we'd
highly
recommend
downloading
the
tools
and
spinning
up
an
environment
and
taking
a
look
at
this,
you
can
see
this
is
node
one.
E
B
B
All
right,
the
use
case,
I'm
going
to
kind
of
walk
through
today,
is
kind
of
trying
to
Showcase
a
couple
of
the
main
things
that
Firefly
helps.
You
do
and
kind
of
put
them
into
a
pseudo
use
case
that
that
might
help
you
to
Envision
some
of
the
ways
the
Firefly
could
apply
to
you
or
your
company
or
industry.
B
So
the
first
thing
that
I'm,
showing
here
I'm
kind
of
doing
a
an
achievements
workflow
here
so
remember,
one
is
serving
as
an
org
that
kind
of
publishes
achievements
that
can
be
gained
and
then
other
orgs
in
this
private
Network
can
submit
members
that
have
gained
those
achievements
and
if
they
are
verified,
then
they
receive
an
nft
on
polygon,
Network.
So
there's
a
sort
of
private
data
exchange
over
here
and
then
a
public
Testament
to
that
achievement
that
goes
out
to
polygon.
B
So
it's
a
bit
of
a
made-up
use
case,
but
you
can
kind
of
Imagine
analogs
to
this.
In
gaming,
with
nfts
in
sort
of
internal
and
external
recognition,
programs
for
workers
in
education,
certifications
a
lot
lots
of
different
types
of
use
cases
you
can
imagine
where
there
might
be
some
element
of
a
private
Network
and
then
some
element
of
sort
of
publishing,
interesting
things
that
have
been
recognized
on
that
Network
out
to
polycon.
B
So
this
is
the
sort
of
use
case
we're
going
to
walk
through
and
show
all
the
different
things
that
Firefly
can
help.
You
do
I'm
going
to
leverage
some
of
the
Firefly
UI
tools,
including
the
Firefly,
sandbox
and
I'm,
also
going
to
write
a
little
bit
of
code
because
you
were
promised
some
live
coding.
I'll,
try
to
keep
it
to
about
100
lines
of
code
and
show
that
we
can
do
a
really
pretty
complex
and
robust
workflow
with
just
right
around
100
lines
of
code.
B
So
the
first
step
in
the
workflow
is
going
to
be
triggered
with
a
smart
contract.
So
I
have
a
smart
contract.
We're
going
to
talk
about
how
you
can
deploy
smart
contracts
to
an
ethereum
blockchain
and
interact
with
them
using
Firefly
I'm,
going
to
talk
about
private
messaging
and
how
Firefly
can
exchange
private
messages
that
have
an
on
and
off
chain
piece
to
them
and
then,
finally,
mint
and
nft
that
can
be
sent
to
a
metamask
all
it
on
public
one
by
testnet,
because
Firefly
has
a
lot
of
capabilities
around
tokens
anything
else.
B
B
I
forgot
a
network
name,
so
my
fireplace
stack
that
I've
set
up.
It's
called
Meetup.
So
now
the
Firefly
command
line
can't
be
used
for
deploying
every
contract
in
the
world,
but
it's
a
really
good
starter
and
again
something
that
just
comes
in
the
Box
for
deploying
ethereum
and
fabric
contracts.
All
right.
So
my
contract
has
now
been
deployed.
B
So
my
contract
is
now
deployed,
and
this
deployed
it
to
the
internal
private
blockchain,
just
to
be
clear,
we're
not
putting
this
out
onto
polygon
at
this
time.
This
is
part
of
the
sort
of
right
hand,
half
of
this
picture
in
the
side
chain,
where
these
nodes
are
operating
so
I
got
the
address
of
where
my
smart
contract
has
been
deployed.
B
The
next
thing
that
I
need
to
do
to
interact
with
this
contract
in
a
really
really
easy
way
is
to
tell
Firefly
about
it,
so
I'm
going
to
go
to
another
tool
that
comes
in
the
box
with
firefly
called
the
Firefly
sandbox
and
because
I'm
running
all
these
Dockers
locally
I'm
playing
the
part
of
every
member
in
this
network
right
I'm
I've
got
two
members,
so
I
have
two
sandboxes
right.
This
is
number
one
sandbox.
B
This
is
member
two's
sandbox,
the
sandbox
is
kind
of
part
demo
Tool
Part
code
bootstrapper,
and
it's
a
really
good
place
to
start
playing
around
and
learning
the
different
things
you
can
do
with
firefly,
but
it's
also
kind
of
a
good
tool
for
for
doing
setup
in
a
quick
way.
So
the
first
thing
I'm
going
to
do
is
tell
Firefly
about
my
smart
contract
that
I
deployed
and
Firefly
calls
this
a
contract
interface,
so
I'm
going
to
define
a
contract
interface.
B
The
two
formats
that
Firefly
understands
are
ffi
Firefly
interface
format,
which
is
kind
of
a
format
that
we
have
specified
as
part
of
the
Firefly
project.
That's
kind
of
blockchain
agnostic
defines
methods
and
events
in
a
generic
fashion.
We
also
want
to
support
you
know
any
blockchain
that
has
its
own
format
of
describing
a
smart
contract
interface
on
for
ethereum.
B
So
that's
the
ABI
I
can
just
go
right
into
the
sandbox
and
paste
that
whole
thing
in
here.
I
give
it
a
name
and
aversion,
and
you
can
see
here
the
sandbox
actually
helps
me
to
see
what
the
JavaScript
code
would
be
for
deploying
this
or
I
can
just
run
it
directly
in
the
browser.
I'm
gonna
go
ahead
and
run
it
now.
B
This
is
the
first
node,
the
the
one
that
I
just
deployed
the
con
or
created
the
contract
interface
from-
and
we
see
this
batch
pin
transaction
batch
pin
is
one
of
the
functions
that
is
built
into
Firefly
and
it's
basically
a
classic
on
and
off
chain
marrying
of
data.
But
it's
a
very
kind
of
complicated
piece,
the
more
you
drill
into
it
in
the
case
of
a
broadcast
we're
leveraging
the
the
private
ipfs
over
here.
So
something
like
a
contract
interface
is
something
we
want
to
be
visible
to
everyone.
B
B
So
the
blockchain
provides
the
ordering
and
the
authorship
of
the
data,
but
the
actual
like
heavy
data
payload
can
be
off
chain
in
this
case
in
ipfs,
so
Firefly
kind
of
does
this
all
for
you
coordinates
the
on
and
off
chain
message
and
we'll
see
a
few
more
instances
of
on
and
off
chain
throughout
the
rest
of
this
demo.
But
if
I
go
to
member
two,
they
get
the
same
message.
They
know
that
this
new
contract
interface
has
been
confirmed,
called
achievements.
B
Now,
that's
just
defining
the
shape
of
the
interface
not
where
to
find
it.
So
I
can
go
one
step
further
and
use
that
contract
interface
to
create
a
contract.
Api
I'm
going
to
call
this
achievements
as
well,
and
now
I
can
specify
a
contract
address.
So
this
is
the
address
on
my
side
chain
where
that
contract
was
deployed
and
we
can
see
kind
of
sample
code,
but
I'm
just
going
to
run
it
here
and
it's
going
to
do
the
same
thing.
B
It's
going
to
advertise
the
details
of
that
API
to
everyone
in
the
network
and
the
cool
thing
is
now:
Firefly
has
taken
this
contract
interface
and
the
location
of
it,
and
it's
generated
a
nice
little
open.
Api
document
and
I
can
actually
interact
directly
with
this
smart
contract
using
HTTP.
Instead
of
having
to
do
it,
you
know
over
web3,
Json,
RPC
type
of
calls,
so
I
can
invoke
my
methods
here
and
member
two
can
also
see
that
this
thing's
been
created
right.
B
So
within
a
multi-party
network,
you
have
this
ability
to
create
things
like
contract
interfaces
and
apis
and
have
them
implicitly
shared
with
everyone,
so
that
everyone
can
interact
with
them,
foreign
moving
on
to
kind
of
The,
Next
Step.
So
now
that
I've
got
a
contract
deployed,
the
other
construct
that
I'm
going
to
need
to
set
up
ahead
of
time
in
this
flow
is
a
place
to
put
tokens.
B
So
in
order
to
Mint
an
ft
or
to
do
anything
with
tokens
in
Firefly,
you
have
to
create
what
we
call
a
token
pool.
It's
kind
of
a
made-up
word.
It
could
be
a
single
contract
like
an
erc721.
It
could
be
an
1155
contract
might
have
multiple
pools
right,
some
flexible
token
standards
can
let
you
create
many
different
types
of
tokens
within
a
contract,
and
then
you
know
it's
blockchain
agnostics.
B
So
if
you
know
you
want
to
create
token
constructs
based
on
fabric,
you
can
Define,
you
know
what
does
a
token
pool
and
a
token
look
like
over
there
for
this
use
case,
I'm
going
to
keep
it
pretty
simple
and
use
an
ERC,
721,
non-fungible
token
and
I've
already
pre-deployed
a
contract
out
here
on
to
Mumbai,
since
sometimes
it
can
take
a
little
bit
to
get
those
out
there.
So
this
is
my
contract.
It's
a
pretty
straightforward,
ERC,
721
and
I'm,
going
to
tell
Firefly
about
a
token
pool.
B
E
B
Oh
and
it's
see,
I
got
an
error
because
it's
not
a
fungible
pool.
It's
a
non-fungible.
Let's
try
that
again!
Okay,
so
now
I
have
created
a
non-fungible
pool,
I'll,
see
probably
a
failure
in
here
and
then
that's
the
wrong
namespace,
all
right.
So
back
on
the
polygon
name,
space
right,
the
sort
of
left-hand
side
of
my
diagram
I
tried
once
to
create
the
token
pool
and
it
failed.
I
tried
it
again
with
the
actual
correct
parameters
and
it
confirmed
so
now
if
I
go
to
tokens
I'm
now
tracking
this
pool.
B
So
it's
now
indexed
at
721.
We
will
probably
see
in
a
moment
because
I
did
test
out
on
this
contract
and
mint
a
few
nfts
earlier.
So
as
it
catches
up
to
the
current
head
block,
it
should
actually
find
some
transfers
and
and
index
them
here,
because
it's
going
to
start
from
that
block
that
I
said,
and
it's
going
to
start
indexing
all
the
things
that
have
happened
on
that
contract
and
hopefully
it'll
catch
up
to
the
current
time.
B
By
the
time
we
get
there
all
right
so
I
think
that's
all
these
setup
and
kind
of
a
tour
of
some
cool
things
you
can
do
with
the
Firefly
sandbox,
so
I've
deployed
a
private
Custom
Contract
into
my
side
chain.
I've
deployed
a
sort
of
very
straightforward,
simple
erc721
onto
Mumbai
test
net
and
I've
set
them
both
up
so
that
Firefly
knows
about
them.
It
knows
about
this
API
that
it
can
use
in
the
default
namespace,
and
it
knows
about
this
token
contract
it
can
use
in
the
polygon
namespace.
B
So
this
is
the
part
where
I
start
doing
coding,
so
hopefully
everyone's
ready
for
it,
hopefully
I'm
ready
for
it.
I
said
the
first
step
here
is
going
to
be
invoking
the
contract
I'm
not
going
to
do
that.
First
Domino
we'll
save
that
for
last,
but
I'm
going
to
start
by
showing
you
know
what
does
it
look
like
if
I
was
going
to
write
this
application
State
machine
this
logic
over
on
member
two
to
trigger
Things,
based
on
an
on-chain
invocation
of
a
smart
contract
in
Firefly?
B
So
the
other
thing
I've
done
as
a
kind
of
a
starter
here,
is
to
zoom
bars
in
the
way,
okay
to
set
up
two
starter
projects.
Very
simple
typescript
projects.
I've
got
one
that's
kind
of
for
member
one
and
one
that's
for
member
two.
So
we're
going
to
start
here
and
remember
to
kind
of
give
you
a
quick
tour
of
you
know
what
does
the
code
look
like
when
I
want
to
write
an
application
on
top
of
Firefly,
so
I?
The
first
thing
I
want
to
do
is
listen
for
this
event.
B
B
So
when
you
want
to
do
this
event
driven
processing,
you
need
to
create
a
firefly
subscription.
Basically,
it's
a
checkpoint
for
you.
This
subscription
is
going
to
keep
track
of
what
are
all
the
events
that
Firefly
has
delivered
to
you
as
you
act,
those
events
it
moves
your
checkpoint
forward,
so
it
gives
you
that
reliable
delivery
from
Firefly
right.
So
all
you
need
for
a
subscription-
is
a
name.
B
B
I'll
tell
it
to
start
from
the
oldest
event.
So,
regardless
of
when
I
start
the
subscription,
it's
going
to
deliver
me
all
the
events
the
Firefly
knows
about
now
you
can
do
a
lot
more
with
the
subscription.
You
can
filter
types
of
events,
you
can
say
I
only
care
about
tokens
or
I,
only
care
about
messages
or
I
only
care
about
Custom
Contract
events
from
this
particular
contract
for
Simplicity
I'm.
Just
going
to
tell
Firefly
to
deliver
me
everything,
but
generally
you
would.
B
B
All
right,
so
this
I
just
provide
a
callback
I
tell
what
subscription
I
want
to
use
it's
going
to
connect
to
that
subscription
start
from
wherever
the
last
point
I
was
at,
and
it's
going
to
start
triggering
this
callback
for
every
event
that
comes
in
I'm,
going
to
I.
Think
in
the
interest
of
being
slightly
correct,
I'll
create
a
little
class
here
that
this
would
be
my
my
event
handler.
So
this
is
a
piece
of
logic
that
you
kind
of
are
going
to
have
to
implement
for
every
application.
B
And
you
can
see
with
the
the
typescript
developer,
experience
is
kind
of
tailored
to
be
very
nice
and
easy.
We've
got
a
fully
fleshed
out
SDK
with
types
and
everything
that
kind
of
helps
you
along,
oh
and
the
one
other
thing
I
do
need
to
set
up,
because
what
I'm
listening
for
is
a
custom
blockchain
event.
That's
coming
from
this
achievement.
B
Tracker
contract,
so
I
do
need
to
do
one
more
thing
in
the
sandbox
and
that
is
register
contract
listener,
because
Firefly
is
not
automatically
going
to
start
cataloging
events
from
every
contract
on
the
blockchain.
You
do
need
to
tell
it
what
contracts
you're
interested
in
and
then
it'll
suck
those
into
its
own
database.
So
I've
deployed
this
achievements:
contract
onto
my
side
chain,
I'm,
going
to
tell
Firefly
I'm
interested
in
this
achievement
available
event.
B
I,
give
it
a
unique
topic
and
I'll
tell
you,
so
this
is
just
going
to
do
a
one-time
setup
where
it's
now
created
a
contract
listener
so
anytime
that
contract
that
I
deployed
emits
this
achievement
available.
Event
Firefly
is
going
to
index
it
and
then,
by
extension,
if
I'm
listening
to
events
from
Firefly
Firefly
will
deliver
the
event
to
my
application.
E
B
I
can
bring
in
I
can
look
at
the
details
of
that
make
sure
it's
defined
we'll
go
fast
and
loose
here,
because
we're
live,
but
now
I
can
actually
inspect
the
event
to
see
what
came
from
the
blockchain
achievement
available
is
the
event
that
I'm
looking
for
and
I
said
that,
based
on
this
flow,
if
I
get
that
I
would
check
and
see.
You
know
which
of
my
members
are
eligible
to
claim
this
achievement
and
I'm
going
to
send
a
private
message
back
to
orgwan
for
all
of
those
members.
B
So
my
achievement
event
has
a
name
so
we'll
expect
a
name.
That's
called
Meetup
attendee
and
then
I
can
kind
of
trigger
this
logic.
I
can
say:
okay
when
I
receive
an
event
on
chain
I'm
going
to
now
send
a
private
message.
That
is
an
on-chain
off-chain,
coordinated
message
back
to
org,
one
to
say:
okay,
be
eligible.
B
B
B
So
if
I
now
run
this
listener,
see
if
this
works,
it's
going
to
catalog
a
bunch
of
events
that
happened
ahead
of
time,
but
now,
if
I
send
it
a
smart
contract
invocation
and
it
gets
the
event
it's
looking
for,
it
should
claim
the
achievement.
So
I'll
go
to
my
contract.
Api
I'll
show
I'm
going
to
advertise
by
doing
a
smart
contract
transaction.
B
B
B
So
we're
running
short
on
time
and
I
know
there's
a
lot
going
on
here,
but
basically
what
happened?
My
running
application?
My
state
machine
received
that
blockchain
event
based
on
Firefly
sequencing
and
delivering
the
event
to
that
application.
It
consumed
that
event.
It
replied
by
sending
a
private
message.
This
is
using
that
batch
pin
technique.
B
So
this
message,
the
the
body
of
the
message,
is
going
to
be
delivered
off
chain
in
the
private
data
exchange
pipe
from
Member
two
to
member
one.
But
a
hash
of
that
message
is
pinned
on
chain,
so
all
members
can
see
it
and
then
number
one
is
going
to
receive
that
message
and
now
we
could
trigger
the
last
part
of
the
flow
and
say
you
know
if
Member
One
receives
this
message,
go
ahead
and
mint
an
nft
I.
Actually
guess
I
should
probably
stop
and
ask.
B
B
B
That's
happened
on
that
Network,
whether
it's
you
know
all
the
transfers
that
Firefly
has
cataloged
or
all
the
blockchain
invocations
or
all
the
messages
you
can
replay
them
all.
If
you
want
to
join
and
just
say,
okay,
this
is
a
new
thing.
I
don't
expect
there
to
be
any
history,
you
can.
You
can
start
from
newest,
so
there's
two
levels
of
indexing
in
it
at
each
point
you
can
say
you
know,
do
I
want,
oldest
or
newest,
or
something
in
between
yeah.
A
So
four
and
I'll
just
chime
in
here
a
little
bit
to
add
on
to
that
for
an
existing
chain
that
may
have
lots
of
other
things
on
it
or
the
chain
might
be
quite
old.
The
best
practice
is
actually
to
specify
the
specific
block
number
that
you
want
to
start
listening
from,
because
that
will
produce
the
the
least
amount
of
wasted
work
by
the
system
to
go.
Look
at
blocks
that
we
know
will
never
have
an
event
in
it
that
matches
the
thing
that
we're
looking
for.
A
So
in
this
case,
you
know,
say
this:
this
network
that
Andrew
had
stood
up
had
been
going
for
a
year,
and
then
he
deployed
this
contract
as
a
new
thing.
The
network
is
now
doing.
You
would
want
to
pick
the
the
block
number
that
his
contract
was
first
deployed
in
as
the
point
in
time
to
start
indexing
from
that
point
forward.
A
E
B
B
I'm,
gonna
kind
of
real,
quick,
try
and
show
this.
This
second
arm
and
I'm
gonna
make
an
app
that
would
represent
okay.
What
is
Member,
One
doing
and
listening
for
a
message
and
then
minting
an
nft,
so
some
things
are
going
to
be
the
same
they're,
both
they're,
going
to
need
a
firefly,
but
they're
actually
going
to
need
two
fireflies,
because
they're
listening
to
two
different
namespaces,
so
they're
both
on
Port
5000.,
it's
the
same
Firefly,
but
it's
a
different
name
space.
B
B
B
B
B
B
D
B
B
Oh,
so
that's
a
little
demo,
so
there's
the
that
so
kind
of
Whirlwind
here
at
the
end,
but
showing
kind
of
hopefully
driving
home.
The
fact
that
Firefly
is
this
application.
Level
orchestration
right,
you
can
use
it
to
do
if
x,
happens
over
here
do
y
over
here
and
that's
actually
really
really
useful
for
a
lot
of
common
use
cases.
B
One
of
my
members
also
decided
to
take
action
on
a
public
network
and
all
done
in
just
about
100
lines
of
code,
so
a
lot
of
complicated
stuff
going
on,
but
kind
of
wanted
to
show
how
this
stuff
builds
up
and
how
it's
really
easy
to
trigger
a
lot
of
complicated
blockchain
application.
Logic
I
know
we're
over
time.
I
don't
know
if
we
can
go
and
take
a
few
more
questions
before
we
close
out.
A
B
So
I
copy
pasted
that
from
the
sandbox,
so
it
probably
scrolled
by
really
fast,
but
right
here
is
the
API
for
sending
a
private
message.
I
put
this
tag
on
it
right.
If
tag
is
okay,
you
know
what
is
kind
of
like
a
subject.
What
is
the
the
type
of
message
I'm
sending
and
then
here
I
have
this
group,
and
so
the
group
is
going
to
define
the
identities
using
Firefly
dids
that
are
going
to
get
this
message.
B
So
it
means
these
identities
and
this
of
course
it's
a
randomly
generated
org.
But
this
is
my
member
one
in
this
example,
so
this
is
member
two
sending
it
directly
to
member
one
they're
in
a
privacy
group.
The
private
data
is
going
to
travel
directly
off
chain
from
Member
two
to
number
one.
It's
never
going
to
be
on
chain
directly,
but
then
a
hash
of
that
data
is
put
on
the
Chain,
so
both
of
them
and
potentially
any
other
member
could
always
verify
like
that.
Hash
happened
at
this
time.
B
Right,
yeah
yeah,
so
all
this
we
did
not
tour
that
part
of
the
Firefly
UI,
but
if
I
go
to
my
multi-party
namespace
and
go
to
the
network,
these
are
the
orgs
in
my
network
right.
So
this
is
me:
it's
this
org
ending
in
bf2
a84
right.
This
is
org
one.
So
that's
who
who
was
the
recipient
here,
but
you
can
see
this
org
has
a
did
for
kind
of
specifying
the
identity,
a
high
level
and
then
they're
tied
directly
to
a
well-known
ethereum
address.
B
B
C
B
Yeah
you're
right,
I
technically
didn't
need
to
listen.
I
didn't
act
on
any
polygon
events,
I
I
logged
them,
so
I
I,
probably
should
have
changed
my
logs
to
to
log
something
different,
but
yeah
I
was
logging
them
all.
So
some
of
these
events,
like
the
token
transfer
confirmed
this,
was
the
result
of
the
mint
right.
So
I
was
listening
to
them
just
for
the
purposes
of
logging
them.
Since
I
didn't
act
on
them.
F
A
F
B
B
B
For
instance,
the
UI
opens
an
ephemeral
subscription,
so
you
might
have
seen
it
doing
some
live
refreshing,
but
but
you
know
it
doesn't
care
about
saving
state.
But
if
you're
doing
this
sort
of
create
subscription,
it's
durable
it's
going
to
be
stored
in
the
database.
Your
checkpoint
will
be
retained.
You
know,
as
long
as
that
Firefly
database
is
there.
B
That's
a
great
question
so
generally
your
your
subscription
name
should
be
unique,
so
this
would
usually
be
tied
to
your
application.
I
called
it
Meetup
subscription
right
because
I
was
creating
this
demo
for
the
Meetup.
You
would
usually
only
have
one
application:
that's
using
a
single
subscription.
If
you
have
two
applications
that
are
talking
to
Firefly
for
two
different
use
cases.
They
should
create
separate
subscriptions
when
it
comes
to
horizontal
scaling.
B
E
D
B
E
C
B
Subscriptions
are
at
least
once
yeah
at
least
yeah,
so
there's
an
act,
it's
kind
of
hidden
in
the
API.
When
this
listener
callback
returns,
it
actually
transparently
handles
the
ACT,
but
you
do
have
to
act
each
event
and
but
Firefly
and
in
the
case
of
a
communication
loss
or
a
crash
or
something
you
could
get
an
event,
that's
delivered
twice
so
yeah.
There
is
responsibility
on
your
app
and
your
app
State
machine
to
handle
item
potency.
B
B
All
right,
well,
I'm
sure
we
could
go
on
and
on
with
questions,
but
I
think
it's
probably
about
time
to
call
it
and
say
meet
us
on
Discord
for
the
rest
of
them.
I
really
appreciate
everyone
sticking
around
and
walking
through
this
and
asking
great
questions
and
hope
to
see
you
guys
at
Future,
hyperledger
and
Firefly
events.
B
I
know
later
in
the
spring,
in
March,
Nico
is
doing
a
much
more
involved.
Walkthrough
I
think
two
or
three
hour
session
with
more
interactive
coding,
we'll
go
a
little
slower,
so
definitely
put
that
one
on
your
calendars
and
yeah
hop
on
the
hyperledger
Discord
to
chat
with
us.
In
the
meantime,
yeah.
A
And
Andrew,
if
you
don't
mind
just
one
more
quick
advertisement,
if
you
enjoyed
this
session
or
are
interested
in
the
Firefly
project,
if
you
wouldn't
mind
giving
it
a
star
on
GitHub,
that
would
be
really
appreciated.
It
just
helps
Drive
visibility
of
the
project
and
there's
yeah.
We
would
just
love
to
to
get
more
visibility
on
the
project
and
get
more
as
many
people
as
we
can
involved.
So,
thank
you
so
much
great
job,
Andrew
yeah
thank.
B
You
Nico
and
yeah
links
here.
Please
get
involved
in
the
open
source,
Community
Check
out
Firefly
check
out
evm
connect
check
out
the
blockchain,
connector
and
transaction
manager.
If
you
have
any
desire
to
start
talking
about
better
policy
engines,
different
blockchain
connectors
would
would
love
to
see
more
people
get
involved
in
that
sort
of
public
chain
space
with
us.
So
thanks
again,
I
hope.
Everyone
has
a
great
day.