►
Description
A virtual meetup on April 20, 2022 with Nicko Guyer from Kaleido. In this session he shows you how building an app on a FireFly SuperNode can radically speed up your development time. With live coding and easy-to-follow steps, you’ll have everything you need to build and run your own blockchain powered app.
The guide for the workshop is at: https://gist.github.com/nguyer/a5ea1cc1181de58ffb0d693d5ca50fb9
More about FireFly is at: https://wiki.hyperledger.org/display/FIR/
Join the discussion about FireFly in the #firefly channel on Hyperledger's Discord server at: https://discord.gg/hyperledger
----
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
Okay,
you're
live
welcome.
Everybody
thank
you
for
joining
us
for
our
hands-on
workshop
today
on
how
to
build
web3
apps
with
hyperledger
firefly
supernodes.
I
really
did
have
everyone.
Today.
We
had
a
great
webinar
last
week
talking
about
firefly
and
the
1.0
launch,
and
there
was
a
brief
demo
at
the
end
of
it,
but
I
think
there
was
a
lot
of
desire
to
go
deeper
on
some
things
and
to
really
get
more
hands-on.
A
So
today
is
today's
gonna
be
hands-on
and
I'm
really
looking
forward
to
it
before
we
get
in
just
here.
Here's
the
the
agenda
of
the
things
that
we're
gonna
be
going
over
today.
I'm
gonna
cover
a
couple
housekeeping
items.
I
have
a
few
slides
to
kind
of
set
the
context
for
the
workshop
as
well.
As
you
know,
introducing
firefly
the
bulk
of
this
time
will
be.
The
hands-on
workshop
will
actually
be
in
a
terminal
and
in
a
web
browser
using
firefly
and
doing
blockchain
stuff.
A
So
it's
going
to
be
really
exciting.
We're
going
to
leave
about
20
minutes
at
the
end
for
some
road
map,
discussion
and
q,
a
but
again
the
the
bulk
of
it
is
going
to
be
the
workshop.
The
whole
session
will
be
an
hour
and
a
half,
so
that's
the
agenda
onto
some
housekeeping
items.
Please
note
that
this
workshop
is
being
recorded.
This
workshop
must
abide
by
hyperledger
code
of
conduct
and
the
antitrust
policy.
If
you're
not
familiar
with
those,
you
can
find
them
both
on
the
hyperledger
foundation.
A
Wiki
or
I
guess
you
can't
really
click
the
link
there,
but
my
slides
are
linked
to
them
a
couple
other
housekeeping
notes.
There
are
a
lot
of
us
in
this
zoom
which
is
awesome.
I'm
I'm
happy
to
see
such
a
great
turnout.
Please
keep
your
mic
muted.
If
you're,
not
speaking
right
now,
I'm
the
only
one.
That's
speaking
so,
if
you're
not
me,
please
please
go
ahead
and
go
on
mute
just
to
cut
down
on
background
noise.
A
Please
please
prefer
chat
as
the
first
resort
for
asking
and
getting
questions
answered
and
again
we
would
prefer
using
the
discord
chat.
As
david
was
mentioning
earlier.
The
the
discord
chat
in
the
hyperledger
discord
server
under
the
firefly
section,
there's
a
a
dedicated
firefly
workshop
channel
that
we
just
created
this
morning
so
go
in
there.
Some
of
the
other
maintainers
are
monitoring
that
and
I
will
be
happy
to
to
answer
questions
as
we
go
along
if
you'd
like
to
speak
during
the
the
workshop.
A
That's
okay,
I
would
love
to
keep
this
interactive,
but
just
please
go
ahead
and
raise
your
hand
and
wait
to
be
called
on
again.
There's
a
lot
of
us
in
here,
and
this
will
just
kind
of
help
us
keep
it
organized
and
keep
on
time.
I'm
happy
to
take
some
questions
as
we
go,
but
there's
a
lot
to
cover
and
I'd
really
like
to
keep
us
on
track
and
on
time.
So
that's
that's
it
for
housekeeping
items
thanks
for
bearing
with
me.
A
While
we
go
through
that,
let's
talk
about
what
we're
going
to
do
in
the
workshop
today,
so
we're
going
to
use
some
some
pretty
cool
tools
here
today,
you
may
be
familiar
with
heart
hat
already.
Hard
hat
is
a
pretty
common
tool
for
doing
ethereum
development
testing,
contract
deployment
and
that
sort
of
stuff.
A
So
we're
going
to
use
hard
hat
and
we're
going
to
compile
a
custom
smart
contract,
we're
going
to
deploy
it
to
a
blockchain
node
running
on
our
machines
and
we're
gonna
use
fi
we're
gonna
use
that
contract
with
firefly
and
what
we're
what
we're
gonna
be
doing
today
is
I'll
get
again
I'll
have
a
slide
on.
You
know
the
end
result
and
goal
of
the
the
workshop
in
just
a
minute,
but
the
other
awesome
tool
that
we're
going
to
be
using
is
hyperledger
firefly.
A
That's
probably
what
most
people
are
here
to
learn
about
today,
hyperledger
firefly,
if
you
have,
are
not
familiar
with
it
or
didn't,
get
a
chance
to
watch
our
webinar.
Last
week
we
described
firefly
as
the
first
open
source
super
node,
which
is
a
complete
stack
for
developers
to
build
and
scale
blockchain
web3
applications.
A
So
what
is
the
value
of
firefly?
Where
does
it
fit
in
the
in
the
blockchain
ecosystem?
Well,
it's
not
a
blockchain
itself.
It's
not
a
dlt!
It
sits
a
layer
above
that,
but
but
firefly
the
value
to
a
developer,
I'm
assuming
that
most
of
us
are
developers
in
in
this
room
and
so
kind
of
looking
at
things
through
that
lens.
The
value
to
the
developer
is
that
it
takes
care
of
this
whole
stack
of
things
that
a
developer
needs
to
build.
A
You
can
see
on
you
know
on
the
left.
We
have
this
diagram
of
like
okay
at
the
bottom,
we
have
our
our
blockchain
and
our
smart
contract
and
that's
kind
of
like
oftentimes
when
we're
building
a
web3
app.
That's
what
we
think
of.
First
we
go
to
okay,
what's
the
what's
the
logic
that
goes
on
chain?
What's
the
smart
contract
look
like
and
then
all
the
way
at
the
top?
We
have.
A
You
know
our
business
application,
our
web
ui,
our
user
portal,
or-
or
maybe
you
know,
some
sort
of
business
back
office
system
that
needs
to
be
integrated
there,
but
like
how?
How
do
you
connect
all
of
the
things
in
the
middle
of
that
there's?
There's
once
you
start
getting
into
building
an
enterprise,
web3
application?
A
You
realize
that
there's
a
lot
of
plumbing
and
a
lot
of
you
know
electrical
work
and
all
these
things
that
are
that
are
not
very
fun
things
to
develop,
that
you
still
need
in
order
to
actually
build
out
an
entire
enterprise
grade
web
3
application.
So
that's
that's
the
gap
that
firefly
fills
it's
a
platform.
It's
a
common
foundation
to
build
enterprise,
web3
apps.
A
So
what
types
of
things
does
it
have
in
it?
It's
got
a
lot
if
we,
if
we
kind
of
break
it
down
into
to
three
main
groups,
though,
you've
got
apps,
you've
got
flows
and
you've
got
digital
assets
and
we'll
actually
walk
through
a
bunch
of
these
use
cases
in
a
little
bit
kind
of
breaking
them
down
into
into
these
three
groups.
A
So
at
the
center
you've
got
the
firefly
core.
The
firefly
core
is
an
orchestration
engine
and
it's
coordinating
things
that
are
happening
on
the
blockchain
things
that
are
happening
off
chain.
It
provides
a
really
easy
to
use
rest
api
for
for
developers
to
to
access
all
these
functionalities.
It
provides
an
event,
delivery
mechanism
over
web
sockets.
Some
of
the
other
really
cool
things
about
it
is
that
it's
it's
a
it's
a
micro
service
architecture
and
it's
very
pluggable.
So
there
are
specific
implementations
that
we'll
talk
about.
A
You
know
the
things
that
we're
going
to
be
running
on
our
machine
later,
but
you
know
if
you
want
to
use
a
different
database,
for
instance,
or
if
you
want
to
use
an
entirely
different
blockchain.
Those
are
plugins
into
firefly,
and
so
so
firefly
is
very
modular.
It
can
adapt
to
meet
specific
needs
for
specific
business
cases
and
it's
it's
a
it's
a
really
cool
architecture.
A
So
I'm
not
going
to
spend
a
ton
of
time
on.
You
know
what
firefly
is
and
all
the
value
that
it
brings.
There
was
a
great
webinar
on
that
last
week.
I
hope
that
as
we
use,
it,
you'll
start
to
see
the
value
and
some
of
the
power
behind
it
and
and
the
really
cool
features,
but
I
just
wanted
to
paint
a
little
bit
of
a
picture
before
we
jump
in
here.
A
A
We're
going
to
use
hard
hat,
we're
going
to
compile
and
deploy
a
custom
erc20
contract,
we're
going
to
use
the
firefly
sandbox
to
walk
through
using
fireflies
apis
in
a
very
approachable,
user-friendly
manner,
which
will
provide
us
sample
code
snippets
that
we
can
look
at
to
see?
Okay.
How
would
we
go
build
this
feature
into
our
back
end
into
our
application
that
we're
going
to
build
in
the
future?
A
A
So
what
what
goes
into
a
super
node
here?
So
what
we're
going
to
be
running
when
we
run
the
firefly
cli
and
it
starts
up
a
development
stack
is
so
we're
going
to
you'll.
Hear
me
talk
about
different
members
of
the
firefly
network,
so
you
can
think
of
different
members,
as
perhaps
different
organizations
or
different
companies.
Remember.
This
is
the
context
here
is
building
enterprise
web
3
apps,
so
you
may
have
different
businesses
that
need
to
transfer
data
transfer
tokens
perform
business
transactions
backed
by
blockchain.
A
So
that's
what
each
of
the
members
are
going
to
be
in
our
firefly
network
that
we're
going
to
stand
up
or
our
firefly
stack.
Each
of
those
members
has
their
own
super
node
and
so
inside
the
super
node.
You
have
a
firefly
core
over
here.
Each
each
firefly
core
is
connected
to
a
database
data
exchange,
blockchain
connector
tokens
connector,
so
on
and
so
forth.
There
is
for
to
keep
things
simple
and
and
as
lightweight
as
possible.
A
There's
one
blockchain
node
that
will
run
on
your
machine
and
both
both
super
nodes
will
end
up
actually
just
sharing
that
same
blockchain
node.
So
as
we're
going
through
we're
going
to
be
using
firefly
cores
api,
we're
going
to
be
using
the
web
ui
the
firefly
explorer
to
look
at.
What's
going
on
inside
there
that
that
web
ui
is
actually
hosted
by
the
the
firefly
core,
we're
also
going
to
be
looking
at
the
firefly
sandbox.
You
can
think
of
sandbox
as
an
application
that
sits
outside
the
supernode.
A
It's
it's
an
example
of
an
end
user
application
that
is
written
to
use
fireflies
api.
So
so
it's
not
part
of
the
super
node,
but
it's
we
ship
it
with
the
firefly
cli,
because
it's
an
awesome
tool
to
learn
about
firefly
and
try
it
out
all
in
a
web
browser.
It
will
also
provide
code.
Snippets
of
you
know
how
to
use.
You
know
how
to
build
these
functions
in
the
back
end.
A
B
A
A
Okay,
that's
great
if
I
need
to
if
I
need
to
adjust
font
size
or
anything,
please
just
let
me
know
I'm
happy
to
zoom
in
on
stuff.
Hopefully
the
screen
size
should
be
good,
though
okay,
so
hopefully
you've
had
a
chance
to
go
through
the
before
the
workshop
section
and
make
sure
you
have
docker.
The
firefly
cli
will
also
use
openssl.
A
A
Okay,
so
if
you
happen
to
be
a
go
developer
and
you
have
go
set
up
on
your
machine,
you
can
you
can
just
go
install
the
firefly
cli.
If
not
that's!
Okay,
if
you
don't
want
to
worry
about
setting
up
a
go,
dev
environment,
that's
not
a
requirement!
In
that
case,
we
can
go
to
the
releases
page.
So
we'll
see
you
know,
go
to
download
the
package
for
your
os.
Go
to
the
latest
release
page
on
github
and
we
will
just
download
the
appropriate
binary
for
our
machine.
A
A
If
you
are
running
on
windows,
you
should
be
able
to
use
the
the
linux
binaries
in
windows,
subsystem
for
linux
2
and
if
you
have
docker
set
up
to
use
wsl
2
as
well
that
that
configuration
should
work
for
you,
okay,
I'm
just
gonna,
there's
a
handy
command
here.
Basically,
basically,
we
just
need
to
unzip
this
thing
and
put
it
somewhere
on
our
machine
that
we
can
call
it.
I've
got
a
command
here
that
I
can
copy
and
paste
to
put
it
in
my
bin
directory.
So
I'm
just
going
to
do
that
here.
A
I'll
make
my
font
a
little
bigger
in
my
terminal.
It's
going
to
ask
me
for
my
password
because
that's
a
directory
and
type
it
correctly.
Okay,
there.
We
go
so
now
that
we've
got.
I
have
the
firefly
cli
binary
installed
in
my
bin
directory,
so
I
should
be
able
to
run
ff
version,
and
you
know
what
I
have
a
version
compiled
from
source
hang
on.
Let
me
let
me
get
rid
of
that.
A
A
You'll
go
to
system
preferences,
go
up
to
security
and
privacy
and
then
so
it'll
say
ff
was
blocked
because
it's
not
from
an
identified
developer.
We'll
allow
that
that's
fine!
The
next
time
we
run
ff
version,
it'll
say:
hey.
Are
you
really
sure
you
want
to
run
this?
Yes,
okay
and
then
there
we
go
okay,
so
I'm
running
0.0.48.
A
A
Okay,
let's
go
back
to
our
guide
and
see
where
we're
at
next.
So
we've
got
the
firefly
cli
installed.
Now
we're
going
to
create
an
environment.
So
this
is
kind
of
step.
Two
in
the
fireflight
getting
started
guide
is,
you
know,
set
up
a
dev
environment,
I'm
going
to
use
a
slightly
different
command
than
what's
in
the
firefly
docs,
because
a
I
want
to
use
erc20
and
the
default
is
erc1155,
and
then
I
also
want
to
customize
the
names
of
the
organizations.
So
so
this
command
is
going
to
initialize
a
new
stack.
A
It's
going
to
call
it
workshop.
It's
going
to
it's
going
to
create
a
network
of
three
members
that
way
we
can
demo
both
public
and
private
transactions,
and
I'm
going
to
use
the
erc20
erc721
token
connector,
and
then
the
prompt
names
command
here
is
is
going
to
just
let
me
type
in
my
own
names
for
all
the
the
organizations
and
and
nodes
before
we
before
we
create
it.
I
just
want
to
highlight
real,
quick,
all
the
different.
A
So
if,
if
you
want
to
see
all
the
different
things
the
firefly
seal,
I
can
do
you
can
run
ff
help,
it
will
print
out
here's
all
the
commands
that
the
firefly
cli
can
do.
If
you
want
to
know
hey
what
are
the
different
things,
I
can
customize
in
a
firefly
stack.
When
I
create
it,
you
can
run
ff
init
help
and
here's
the
the
full
list
of
options,
so
you
can
customize
which
blockchain
it
uses.
A
If
I
add
a
dash
b
space
fabric,
it
will
use
a
fabric
block
chain,
we're
not
going
to
demo
that
today
we're
going
to
focus
on
erc20
on
an
ethereum
node,
but
but
you
can
do
that
you
can
have
it
use
postgres.
Instead
of
the
built-in
sqlite
database,
you
can
enable
prometheus
metrics,
there's
a
bunch
of
different
options
that
you
can
set
here.
A
Okay,
so
we
are
going
to
I'm
going
to
just
copy
this
command
here
oops
and
I'm
going
to
run
this
and
for
for
clarity
of
the
workshop
and
the
demo,
I'm
going
to
name
my
my
organizations
and
nodes
red,
green
and
blue,
and
I
have
three
different
themed:
chrome,
browsers
that
should
match
those
colors.
If
I
get
the
order
right
here,
and
so
you
can
name
them
whatever
you
want.
The
name
here
is
not
important.
If
you
don't
use
prompt
names,
then
it
will
just
go
with
default,
name.org0
or
one
etc.
A
This
will
just
visually
help,
give
a
little
bit
of
an
indicator
of
when
we're
looking
at
the
three
different
browsers,
which
perspective
we're
looking
at
the
network
from
okay
great.
So
we
have
initialized
the
stack,
we're
not
running
it
yet,
but
let's
go
ahead
and
do
that
before
we
run
it
just
wanted
to
call
out.
If
you
are
running
on
a
machine
like
mine
on
a
mac
that
actually
runs
docker
containers
inside
of
vm.
A
I
recommend
at
least
a
gigabyte
of
ram
per
member,
so
I'm
using
three
members
here
I
usually
have-
I
usually
give
my
docker
vm
like
seven
or
eight
gigs
of
ram,
and
that
tends
to
be
great
so
just
wanted
to
point
that
out.
If
you
don't
have
enough
ram.
Unfortunately,
some
of
the
yep.
Unfortunately,
some
of
the
processes
struggle
a
little
bit
with
with
not
having
enough
ram
okay.
A
So
now
we're
going
to
run
ffstart
and
then
we're
going
to
start
the
workshop
all
right
so
we'll
let
this
go
for
a
little
bit.
It's
going
to
pull
some
docker
containers,
it's
going
to
going
to
going
to
initialize
our
blockchain
node
and
start
everything
up,
I'm
going
to
pause
and
and
kind
of
catch.
My
breath
here
a
little
bit.
I
I
also
got
feedback
that
I
may
need
to
slow
down
a
little
bit
cause
folks
are
trying
to
follow
along.
A
C
A
A
A
A
C
A
Yes,
okay,
yeah!
Let
me
thank
you
for
that
reminder
that
was
a
while
ago.
I
forgot
about
that.
Okay,
so,
in
the
thanks
apple
for
this
in
the
latest
version
of
mac
os,
there
is
a
new
feature
that
apple
added
and
it
it.
It
happens
to
listen
on
port
5000..
If
you
want
to
disable
that
I'll
walk
you
through
that
right
now
it
is
it's
an
airplay
receiver,
and
so
I
just
go
to
system
preferences.
A
I
go
to
sharing
and
there
is
a
thing
at
the
bottom
here
called
airplay
receiver.
This
will
listen
on
the
port
that
the
firefly
core
wants
to
allocate
to
itself.
So
if
you
just
uncheck
this
and
then
try
to
run
ffstart
that
should
solve
that
problem.
If
you're
running
on
a
mac
and
running
into
the
port
collision
there,
that
was
a
good
callout
peter
and
thank
you.
I
had
forgotten
about
that.
A
Okay,
let's
go
back
to
our
guide
here,
all
right,
so
we've
run,
we
have
ran
start
workshop
now
we're
going
to
shifters
and
look
at
our
contracts
that
we're
going
to
deploy.
So
so
what
have
we
done?
So
far?
We've
set
up
a
firefly
development
environment
on
our
machine.
We
have
a
blockchain
node
running.
We
haven't
done
anything
with
it.
We
will
go,
look
at
it
in
a
little
bit,
but
we're
going
to
kind
of
shift
gears
now
and
then
go.
A
Look
at
hard
hat,
which
is
a
different
tool
to
this
is
a
tool
that
ethereum
developers
are
probably
familiar
with,
and
so
we're
going
to
look
at.
You
know
how
do
we
take
an
existing
workflow
that
people
are
probably
familiar
with,
or
at
least
some
of
the
concepts
that
they're
familiar
with
and
and
use
that
with
firefly?
So
firefly
has
a
this
concept
of
a
tokens
connector
and
a
tokens.
Connector
is
a
a
bridge.
I'm
sorry,
it's
not
a
it's,
not
not
a
bridge.
A
It's
a
it's
a
a
component
that
sits
in
between
the
firefly
core
and
the
and
the
the
blockchain
node
itself,
and
it
is
written
in
such
a
way
that
it
knows
about
what
type
of
contract
that
it's
supposed
to
be
working
with.
So
in
the
firefly
hyperledger
github
repos,
there
are
two
different
reference
implementations
of
what
a
token
connector
might
look
like
if
you
are
building
your
own,
your
own,
smart
contract,
your
own
token
implementation,
and
you
want
to
run
on
firefly.
We
highly
recommend
you
should
build
a
token
connector.
A
That
is
knowledgeable
about
your
specific
contract,
but
there
is
a
reference
implementation
provided
for
erc,
20
and
721,
which
we're
going
to
be
looking
at
today.
So
we're
going
to
clone
that
github
repo
hop
back
over
to
my
terminal,
I'm
going
to
go
ahead
and
just
open
a
new
tab
in
my
terminal
here
and
then
I'm
going
to
go
to
my
code
directory
and
I
have
a
workshop
directory
in
there.
There's
nothing
in
here
right
now,
so
I'm
just
going
to
clone
this
repo
here
you
can
clone
it
anywhere.
A
The
whole
token
connector
we're
not
going
to
run
the
whole
token
connector,
because
we're
actually
already
running
it
in
our
docker
environment.
But
what
we
need
is
the
solidity
files
that
are
in
there.
So
if
we
look
at
this
directory,
it
has
some
some
files
in
it.
If
we
look
at
contracts
directory,
there
are
some
solidity
files
in
there.
So
I'm
just
going
to
actually
open
up
my
ide
real,
quick
and
show
you
what
is
in
there.
That's
probably
a
little
too
big
there
we
go.
A
So
we
look
at
contracts,
we
see
there's.
This
is
the
contract
that
we're
going
to
deploy
it's
erc20
with
data.
This
extends
the
open,
zeppelin
erc20
contract.
I
haven't
installed
dependencies,
which
is
why
we're
getting
all
the
red
underlines
here
we'll
solve
that
in
just
a
minute
and
so
yeah.
So
this
this
extends
open,
zeppelin
and
implements
erc20
and
firefly.
Has
this
concept
of
being
able
to
associate
data
with
transfer?
So
that's
that's.
What
erc20
with
data
is
all
about,
there's
also
a
contract
provider
for
721.
A
We
don't
have
time
to
look
at
that
as
well.
Today,
we'd
love
to
do
a
separate
talk
on
nfts,
but
you
should
be
able
to
take
everything
that
we
have
talked
about
here
today
and
with
you
know
some
some
minor
changes
also
you
could
do
the
same
with
721
if
you
wanted
to,
but
we're
going
to
focus
on
erc20
today,
okay,
so
I'm
going
to
hop
back
over
to
my
terminal
and
actually
I'm
going
to
go
back
to
the
guide
and
it
says
now
run
npm
install.
So
that's
what
we're
going
to
do
next.
A
A
A
A
Hopefully,
everyone
can
clone
that
repo
run
npm
install
and
get
the
dependencies
installed
again
we're
working
in
the
solidity
directory
inside
there
there's
a
question:
is
it
possible
to
use
rust
rather
than
solidly
on
the
dev
side?
I
I
you
know
as
long
as
you
can
compile
and
deploy
an
ethereum
smart
contract
onto
the
chain,
you're
welcome
to
use
whatever
tooling
chain
or
or
language
you
would
like.
The
the
the
end
goal
here
is
to
get
a
smart
contract
on
chain.
A
So
that's
hard
hat
and
solidity
are
the
the
tools
of
choice
here
for
today.
But
you
know,
as
long
as
you
can
get
an
ethereum
contract
deployed
to
the
blockchain
node
you're
running
locally
you're,
welcome
to
use
whatever
tooling
you
want
use,
truffle
or
or
any
other
tools
that
are
common
ethereum,
smart
contract
development
tools.
A
Okay,
now
we're
gonna
run
it
so
sorry
we're
gonna,
compile
and
deploy
it.
So
if
we
look
in
just
just
so,
you
can
see
what's
going
on
here
inside
the
solidity
directory.
There
is
a
scripts
directory
and
there's
a
deploy
script
here.
This
is
we're
going
to
run
this
script,
and
this
will
compile
and
deploy
our
smart
contract
and
it
will
print
out
the
the
addresses
that
it
has
deployed
the
contracts
to
at
the
end,
I
see
someone
has
raised
their
hand,
yeah
go
ahead.
B
A
Yeah
so
great
great
question,
and
I
can
just
show
you
real
quick
what,
after
we
ran
our
stack,
I
could
run
docker
ps
and
we
can
see
all
the
things
that
we
have
running
here.
So
sorry,
some
of
my
zoom
windows
are
in
the
way
a
little
bit,
but
we've
got.
We
have
three
firefly
cores.
We
have
three
token
connectors
three
blockchain
connectors
and
then
right
here.
This
is
our
go:
ethereum,
blockchain,
node,
that's
running
on
our
machine
and
so
internally
it's
listening
on
eight
five,
four.
A
A
I've
already
put
in
this
repo
a
configuration
to
use
the
firefly
network,
that's
running
locally
on
your
machine,
and
so
here
we've
we've
configured
a
network
called
firefly
and
we've
told
it.
This
is
the
url,
the
blockchain
node,
and
this
is
what
hard
hat
will
talk
to
when
it
goes
to
deploy
this
contract.
So
hopefully
that
clarifies
there.
A
Okay,
maybe
not
okay,
so
yeah,
it's
a
great
question
about
you
know:
how
does
the
deployment
work
so
that
you
know
we
have
a
blockchain
node
running
here?
That's
what
we're
going
to
deploy
to
and
this
script
is
what's
actually
going
to
do
it
so
to
run
this,
we
can
just
go
back
to
our
guide
and
run
npx
hard
hat
run
scripts
deploy.ts.
A
A
A
A
So
I
want
to
make
sure
that
you
know
if,
if
people
are
following
along
and
trying
to
keep
up,
we
get
at
least
to
this
point
where
we
have
the
contract
on
chain,
because
that's
that's
a
kind
of
a
big
milestone
in
the
workshop
is
making
sure
we
get
our
contract
actually
deployed.
So
I'll,
just
I'll
just
kind
of
pause
for
a
minute.
Folks
have
a
couple
questions
I
can.
I
can
take
a
minute
to
answer
those
as
we
go
here.
B
A
A
Okay,
yes,
there
we
are
recording
this
and
the
recording
will
be
made
available
afterward
as
well
all
right.
So
I'm
conscious
of
time
here
and
I
want
to
make
sure
that
we
we
get
to
to
look
at
some
of
these
really
cool
features
of
firefly,
so
we're
gonna
we're
gonna
jump
into
the
firefly
sandbox
now.
So
there
is
a
guide
in
the
docks
on.
A
This
is
kind
of
you
know,
step
three
of
the
the
getting
started,
experience
and
firefly,
which
is
using
the
sandbox
there's
a
video
walkthrough
from
the
webinar
last
week,
a
little
bit
of
a
description
of
what
the
sandbox
is
yeah
again,
it's
an
end
user,
it's
written
as
an
end
user
application,
so
it
sits
outside
the
supernode.
It
uses
fireflies
api
and
it's
kind
of
broken
up
into
these
three
columns.
Here,
I'm
going
to
actually
open
it
up
there
is.
A
There
is
a
link
here
right
in
the
docs
that
should
open
up
the
ui
for
the
first
member,
I'm
going
to
try
to
keep
things
straight
by
using
these
color
themed,
chrome.
Browsers.
Remember
when
I
set
up
my
network,
I
named
them
red,
green
and
blue,
and
so
I'm
going
to
open
up
the
sandbox
for
the
first
node
here.
So
this
is
what
the
sandbox
looks
like.
A
It
is
kind
of
broken
up
into
three
columns
and
on
the
left
here
we
have
a
form
that
we
can
fill
out.
That
will
prepare
requests
for
us
in
the
middle.
We
have
an
example
of
some
server
code.
That
will
you
can
you
can
think
of
this
as
like,
if
I'm
building
a
back-end
application
that
is
designed
to
use
firefly.
Here's
an
example
of
some
code
that
I
can
go,
take
and
put
right
in
my
application.
This
uses
the
firefly
sdk.
A
A
It
represents
an
imported
node.js
sdk,
we're
going
to
start
on
the
contracts
panel,
so
there's
three
different
panels
here:
messaging
tokens
and
contracts,
we're
going
to
start
with
our
custom
contract
that
we
deployed,
and
so
so
you
can
imagine
a
use
case
where
you
know
I'm
building
an
app
that
has
a
an
erc20
token
economy
built
into
it.
But
it's
a
custom
contract.
It
has
extra
features,
it
has
things
that
are
are
not
in
the
the
standard,
erc20
interface
and
I
want
to
use
firefly
to
interact
with
those
features.
A
B
A
A
I
want
to
just
take
a
brief
moment
and
talk
about
contract
interfaces
and
contract
apis,
because
these
are
some
some
building
blocks
of
really
powerful
features
inside
firefly.
So
in
the
ethereum
world
we
have
ethereum
abi
format,
which
describes
the
inputs
and
the
outputs
and
events
and
all
the
type
information
in
a
smart
contract
and
all
the
functions
that
it
has,
and
this
is
a
great
way
to
to
just
inform
a
system
about
the
the
shape
of
a
smart
contract.
A
Now
firefly
is
is
multi-chain
multi-protocol,
and
so
so
it
works
with
ethereum,
but
it
also
works
with
fabric,
and
it
could
also
be
extended
to
work
with
other
types
of
block
chains.
So
we
wanted
a
way
to
be
able
to
describe
a
smart
contract
in
for
for
any
blockchain.
So
that's
what
the
firefly
interface
format
is
all
about.
It
is
a
way
to
describe
a
contract
in
a
blockchain
agnostic
format,
yet
still
encapsulating
blockchain
specific
important
information,
like
the
type
for
instance
for
ethereum
you'll,
see
inside
an
ffi.
A
It
still
embeds
the
the
specific
evm
type
that
a
variable
will
be
treated
as
in
the
evm,
and
so
so.
This
also
has
the
advantage
of
now.
We
have
a
way
to
define
an
interface
that
can
describe,
for
instance,
a
fabric
chain
code,
and
it
doesn't
matter
what
language
the
the
particular
chain
code
is
implemented
in.
We
have
a
way
that
we
can
talk
about
smart
contracts
in
in
a
way
that's
blockchain
agnostic.
A
A
So
so
you
don't
have
to
go
digging
for
it,
but
just
just
for
for
your
knowledge,
it's
going
to
be
under
artifacts,
it's
going
to
be
in
build
info,
and
it's
going
to
be
in
this
big
long,
ugly,
json
document
it's
in
here.
I
promise
there's
a
bunch
of
other
stuff
in
here,
though,
so
to
save
time
from
sorting
through
that
I've
actually
already
copied
that
out-
and
I
have
put
it
in
the
guide
here.
A
This
is
for
convenience.
I've
also
included
a
copy
here,
so
you
can,
you
know,
select
this
whole
thing
and
again.
This
is
just
the
ethereum
api
for
that
contract
that
we
have
compiled
and
we're
going
to
copy
this.
I'm
going
to.
Oh
sorry,
I'm
going
to
go
back
to
my
red
browser
for
my
red
member
here
and
I'm
just
going
to
paste
this
whole
thing
into
this
box.
Here.
A
A
Now
I'm
going
to
go
over
here
and
on
the
on
the
server
code
I'm
going
to
hit
run.
So
this
is
what
I'm
basically
doing
is
I'm
telling
the
sandbox
backend
server
make
a
request
to
fireflies
api
to
broadcast
this
contract
definition,
and
what
do
I
mean
by
broadcast?
Well,
so
a
variety
of
things
just
happened
there
we
see
that
there
was
a
transaction
that
was
submitted
so
so
actually
sorry.
First
immediately
we
see
it.
We
got
a
202
accepted
and
then
we
got
an
id
back.
A
That's
a
message
id
that
we
can
look
up
in
firefly
to
see
what
what
happened
with
that
message
later
and
we
can.
We
can
see
what
the
results
of
that
request
was
so
so
firefly
uses
an
asynchronous
programming
model.
So
when
you,
when
you
make
a
request,
oftentimes,
you
get
an
id
back
and
you
can
use
that
id
to
look
it
up
later.
You
can
also
set
up
an
a
websocket
listener
to
to
listen
for
events,
if
you
don't
want
to,
and
that's
actually
the
encourage
model
so
rather
than
polling
for
status.
A
Your
application
can
receive
updated
status
in
real
time.
Okay,
so
over
here
on
the
right
side,
we
do.
The
sandbox
does
have
a
websocket
set
up
and
it's
listening
for
events
coming
from
firefly
and
we
can
see
we
got.
There
was
a
transaction
that
was
submitted.
We
received
a
blockchain
event,
there
was
a
contract
interface
that
was
confirmed
and
the
message
that
was
used
to
broadcast.
That
was
confirmed.
So
what
happened
there
under
the
covers?
Let's
go
to
to
answer
that
question:
let's
go.
A
Take
a
look
at
the
firefly
explorer
and
see
what
happened
in
firefly
now
real,
quick
all
right,
so
I'm
just
going
to
open
a
new
tab.
This
is,
if
you're,
curious,
how
I
got
here.
If
you
go
back
and
look
at
where
you
started
up
your
firefly
stack,
there
were
some
urls
that
got
printed
out
here,
and
so
I'm
just
looking
at
web
ui
for
member
xero-
and
this
is
the
this-
is
the
link
right
here
that
I
that
I've
just
opened
in
my
red
browser.
So
this
is
the
firefly
explorer.
A
This
is
kind
of
a
view
into
the
system,
a
view
into
the
both
my
node
and
my
node's
perspective
of
the
network.
So
we
can
see
a
network
map.
We
can
see
our
red,
blue
and
green
members
here
and
each
of
their
nodes.
We
can
see
some
information
about
my
node.
That
was,
you
know
all
the
plugins
that
I'm
currently
using
and
we
can
see
there's
a
little
bit
of
activity
here
now.
So
there
was
a
batch
pin.
A
There
was
a
message
confirmed,
contract
interface
confirmed,
and
so
so
what
is
a
batch
pin,
you
might
be
wondering
well,
firefly
will
will
take.
You
know
if
there's
a
bunch
of
requests
coming
in
all
at
once.
It
will
batch
them
together
for
efficiency,
it
will
hash
them
and
then
it
will
pin
data
to
the
blockchain.
Hence
the
name
batchpin,
and
so
so
so
what's
happened
here
is
when
we
broadcasted
this
contract
interface
it
was
sent
to.
A
A
A
It
pinned
the
hash
of
that
to
the
blockchain
and
it
put
the
actual
json
payload
on
ipfs
and
then
all
the
other
members
are
listening
for
blockchain
events
that
are
happening
on
the
firefly
batch
pin
contract.
They
all
saw
the
event.
Oh
hey
something
was
pinned
to
the
blockchain.
What
is
that?
Let
me
go
get
the
the
data
payload,
that's
associated
with
this.
Oh,
it's
a
it's
a
contract
interface
great!
Let
me
store
that
in
my
database
now
now
I'm
aware
of
this
contract
interface
that
was
just
declared.
A
So
if
we
go
to
any
of
the
members
now,
we
should
be
able
to
look
at
the
blockchain
section
here
in
the
dashboard,
and
we
see
there
was
a
batch
pin
event,
but
we
can
also
go
here
and
we
can
look
at
interfaces
and
we
see
that
there
is
this
interface.
That's
been
defined
here,
that's
cool,
not
very
useful,
yet
we'll
get
to
where,
where
it's
going
to
be
really
useful
in
just
a
second,
I
just
kind
of
wanted
to
describe
something
you
know
kind
of.
A
What's
going
on
behind
the
scenes
when
we're
doing
all
these
things.
Okay,
let's
go
back
to
our
red
members
sandbox
here
and
now.
What
we
want
to
do
is
we
want
to
actually
use
this
thing
so
right
now,
we've
just
told
firefly
about
the
shape
of
it
and
that's
it,
and
so
next
I'm
going
to
go
to
to
register
a
contract
api.
A
So
what
this
is
going
to
do
is
it's
going
to
build
an
http
api
and
it's
going
to
build
a
swagger
ui
for
us
to
work
with
all
the
functions
on
here.
I'm
also
conscious
of
the
time.
I
realized
that
I
want
to
leave
time
for
for
discussion
at
the
end
and
we
are
rapidly
running
out
of
time.
So
I'm
going
to
try
to
speed
things
up
a
little
bit.
I
hope
you
can
follow
along
if,
if
you
get
lost
in
this
part,
this
will
all
be
recorded.
A
A
We're
going
to
copy
the
address
for
the
erc20
contract
and
we're
just
going
to
paste
that
into
this
box
right
here,
so
this
is
going
to
tell
firefly
hey
that
contract
interface
that
I
broadcasted
earlier.
I
want
you
to
generate
a
rest
api
for
me
and
when
somebody
calls
http
methods
on
it,
I
want
you
to
send
blockchain
requests
to
this
address
here,
so
we're
going
to
broadcast
that
this
also
gets
broadcasted
and
pinned
to
the
blockchain
the
same
way
as
our
interface
did
now.
A
A
So
let's
do
something
with
our
contract
now
this
is,
you
know,
kind
of
the
the
whole
point
of
everything
that
we've
been
building
up
to
here.
So,
let's,
let's
mint
some
tokens.
First,
we
don't
have
any
right
now,
so,
let's
we'll
we'll
mint
so
in
this
in
this
case,
we're
going
to
call
the
invoke
mint
with
data
function
or
endpoint.
Rather
here
it
is
I'm
going
to
hit,
try
it
out.
A
I
need
to
fill
out
a
couple
things.
I
need
to
first
tell
it
how
many?
Let's
just
do
we'll
do
a
hundred.
I
can
give
it
some
data.
I
don't
actually
need
to
give
it
any
data
at
the
moment.
So
I'm
going
to
do
I'm
just
going
to
put
0x00
here
and
then
I
need
to
tell
it
who
to
send
it
to
I'm
going
to
mint
it
to
myself
and
then
we'll
do
some
transfers
to
the
other
members
here
in
a
second
to
find
out.
A
You
know
what
what's
the
red
nodes
ethereum
address,
because
that's
an
important
thing
to
know
here:
I'm
going
to
go
back
to
the
firefly
explorer
look
under
network
and
organizations,
and
I
can
see
there's
one
labeled,
your
org
here,
okay,
so
this
is
me
I'm
going
to
click
here.
There
is
a
verifiers
section
here,
and
it
has
that.
A
Has
my
ethereum
address,
I'm
just
going
to
hit
this
button
to
copy
it,
I'm
going
to
go
back
to
my
swagger
ui
and
paste
that
here,
okay
again,
if
you're
looking
to
figure
out,
you
know
what,
where
did
I
get,
that
I
went
back
to
the
firefly
explorer?
I
went
network
organizations
and
I
clicked
on
an
org
here.
Okay,
so
that's
that
should
be
enough
to
mint
100
tokens,
we're
going
to
run
that
we
get
a
202
back,
it's
great!
A
Let's,
let's
go
query
this
smart
contract
and
see
you
know:
do
we
actually
have
a
balance
now
and
so
to
do
that,
we're
going
to
scroll
down
to
the
query
endpoint
and
we're
going
to
check
balance
of,
and
I'm
just
going
to
paste.
My
my
ethereum
address
here
run
that
and
we
get
100..
So
that's
cool,
let's
check
one
of
the
other
members
and
see
if
they
have
any
balance.
A
Just
for
the
sake
of
the
example
we'll
copy
the
green
members
address
we'll
paste
it
here,
we
would
expect
none,
and
indeed
we
have
none
okay.
So
so
only
the
red
member
has
a
balance
right
now.
Let's
do
a
transfer
real
quick,
so
I'm
gonna
go
to.
Let's
see,
I'm
gonna
just
scroll
back
up
here,
I'll
collapse.
This
just
save
some
space.
Okay
invoke
transfer
is
what
we
wanna
do
I'll
hit.
Try
it
out:
let's
send
the
we'll
send
the
the
green
member
send
them
10.
A
and
I'm
going
to
paste
the
green
members
address.
There
run
we
got
a
202.
So
so
that's
you
know
the
the
request
was
accepted.
We
don't
know
that
it
necessarily
went
through,
but
we
can.
We
can
go
back
down
here
and
then
check
their
balance
again,
so
it
was
previously
zero.
I'm
just
going
to
execute
the
same
one
and
then
now
we've
got
10..
Okay,
great.
So
we've
done
a
mint.
We've
done
a
transfer.
A
We've
done
that
through
firefly's
custom,
smart
contract
support
which,
which
is
really
cool,
so
you
know
we're
working
with
an
erc20
contract
here,
but
but
maybe
again
maybe
your
contract
has
custom
functions
on
it
that
you
want
to
be
able
to
use
through
firefly
as
well
or
or
maybe
you're
working
with
an
entirely
different
type
of
contract.
That's
not
an
erc
or
something
like
that.
The
firefly
is
it's
approachable.
It
has
really
easy
to
use
apis,
but
it
also
is
powerful
and
gives
you
full
control
of
using
any
smart
contract
with
it.
A
But
this
was
still
quite
a
few
steps
and
there's
there's
still
you
know
if
I
want
to
build
an
app
that
has
a
whole
token
economy,
there's
still
a
bunch
of
things
that
I
need
to
actually
build
a
robust
app,
for
example,
I'll
just
throw
one
of
them
out
there.
What?
If
I
want
to
see
the
whole
transaction
history
of
everything,
that's
happened
on
this
coin
or
what
are
the
wallets
that
have
been
interacting
with
it
or
what
are
people's
current
balances?
A
So,
let's
take
a
look
at
the
firefly
explorer
real,
quick.
There
is
a
token
section
here
and
it
has
a
dashboard
and
you'll
notice.
There's
nothing
in
here
we
have
we've
been
working
with
our
erc20
contract
through
the
the
custom
contract
support
in
firefly.
But
at
this
point
there
was
a
question
that
was
asked
earlier.
What
is
the
role
of
the
token
connector,
and
I
haven't
answered
that
question
yet
and
I'm
about
to
now.
This
is
where
the
token
connector
comes
into
play.
We
haven't
actually
told
firefly
to
to
go.
A
A
So
now,
let's
hop
back
over
to
the
explorer
we'll
just
reload
it
and
all
of
a
sudden
we
start
to
see
this
dashboard
come
alive.
We've
got
some
token
transfers
that
have
happened.
We
have
a
history
of
a
mint
and
a
transfer.
We
have
a
you
know.
We
can
see
our
account
balances
here
of
you
know.
This
is
the
original
100
that
we
we
minted,
and
then
we
transferred
10
of
it
to
the
other
member,
and
we
can
see
our
token
pool
here.
We
can.
A
A
It
has
18
decimal
places
and
we
can
see
you
know
the
the
contract
address
and
all
this
good
stuff,
and
so
so
all
this
just
became
available
to
us,
because
we
we
told
we
created
this
token
pool
and
told
the
tokens
connector
that
firefly
is
using
about
this
contract
and
it
has
built
kind
of
this,
this
rich
dashboard
for
us
to
use
here
now.
This
also
opens
up
the
the
firefly
first
class
minting
transferring
and
burning
apis
as
well.
So
we've
already
minted
some
we
can
see
our
balance
here
is
90..
A
A
A
The
the
first
member
has
80
and
both
of
the
other
members
have
10.
Now
we
can
see
both
transfers
here
and
again.
If
we
were
transferring
with
data,
we
could
also
look
up
the
actual
the
blockchain
event
and
see
what
that
data
was.
That
was
attached
to
the
transfer
as
well.
So
there's
a
lot
of
information
you
can
kind
of
dig
into
here
and
then,
let's
you
know
for
the,
for
the
sake
of
the
completeness
of
the
demo,
let's
burn
some
tokens
too.
Let's
burn
10..
A
I
mostly
wanted
to
show
this
because
I
just
think
the
the
burn
icon
is
the
coolest
one
in
the
dashboard.
Here
I
refresh
there's
our
burn
icon,
it's
just
straight
fire,
okay
and
then,
let's
just
make
sure
our
our
accounts
have
updated
yep,
so
we
had
80
and
we
burned
10..
So
we've
got
70
because
we've
transferred
10
to
each
member
and
we
burned
10..
So
our
account
balances
are
continuing
to
update
there.
A
So
so,
hopefully,
you've
been
able
to
kind
of
follow
the
journey
here,
if
not
actually
doing
it,
but
you've
been
able
to
follow
along,
and
it's
made
sense
of
you
know.
We've
we've
started
with
our
own
erc20
contract
that
we
compiled.
We
deployed
it
to
the
chain.
We
told
firefly
about
it.
We
we
accessed
it
directly
with
our
swagger
api
and
then
and
then
we
we
used
fireflies
rich
token,
support
to
to
start
indexing.
The
the
complete
history
of
the
token
contract.
A
A
Sometimes
I
just
need
to
get
a
piece
of
data
from
from
one
organization
to
another.
I
want
to
use
blockchain
to
do
that,
and
sometimes
I
I
need
that
the
data
itself
to
be
public
sometimes
I
need
it
to
be.
Private
firefly
supports
a
variety
of
different
combinations
there,
so
in
the
sandbox,
if
I
just
hit
expand,
send
a
broadcast
message
and
sure
we'll
just
send.
This
is
a
message
we'll
wait
for
the
event
to
go
through
that.
That's
great
now
to
see
messages.
A
A
It
could
be
a
a
file,
it
could
be
a
binary
attachment
that
was
referenced
by
id
and
I'll
demonstrate
that
in
just
a
second
as
well
just
for
the
sake
of
the
the
demonstration,
let's
pop
over
to
one
of
the
other
members,
we'll
look
at
their
sorry,
we'll
go
to
off
chain
look
at
messages.
We
should
be
able
to
see
that
same
exact
yep.
This
is
a
message
here
we
go
so
that
went
to
everyone.
A
We
can
look
at
the
blue
member
as
well.
Look
at
their
messages.
Okay,
this
is
a
message
great.
Let's
do
a
let's.
Let's
do
a
slightly
different
scenario
here:
let's
send
a
private
message
in
this
case.
As
a
hypothetical
example,
I
have
a
file
that
I
need
to
send
from
one
member
to
another,
and
so
I'm
gonna
go
to
the
the
file
attachment
toggle.
Here
I'm
going
to
choose
a
file
on
my
desktop.
I
have
a
really
cool
picture.
It's
it's!
The
firefly
logo.
It's
a
png!
A
It's
you
know
it's
not
too
big.
It's
20k,
but
20k
is
still
a
lot
to
store
on
chain.
So
what
we're
going
to
do
is
this
file
will
actually
get
stored
in
ipfs
and
then
we're
going
to
send
a
basically
it
will
send
the
sorry.
This
is
a
private
message,
so
it
is
not
stored
in
ipfs.
This
uses
fireflies
data
exchange.
I'm
sorry
for
the
I
misspoke
there
briefly.
A
This
will
use
fireflies
data
exchange
to
directly
transfer
this
file
from
one
member
to
another
and
it
will
still
hash
and
pin
the
the
file,
the
payload
of
it
to
the
blockchain,
so
that
I,
as
the
red
member,
can
attest
that.
Yes,
I
actually
had
this
data
and
I
I
can
prove
that
I
had
this
data
on
this
date,
so
we're
going
to
send
it
from
red
to
we'll,
send
it
to
blue
and
then
I'll
hit
run
that
will
upload
the
file.
A
It
will
send
the
private
message,
and
so
we
should
be
able
to
go
over
to
the
the
blue
members
dashboard
now
and
let's
look
at
the
data
tab
here
and
here
we
can
see.
We
received
this
data,
it's
about
20k
and
I
can
just
click
right
here
and
I
can
download
that
thing.
I
can
open
it
up
and
there's
my
image
that
I
just
sent
that's
great,
just
to
prove
that
it
was
indeed
a
private
transfer.
A
Let's
go
to
the
green
member
who
should
have
been
completely
in
the
dark
about
the
contents
of
that
message
that
was
sent
and
we
will
jump
over
to
the
the
data
tab
here.
Sorry,
and
we
can
see
that
the
last
thing
that
it
has
was.
This
is
a
message
it
does
not
have
the
the
private
data
that
was
sent
from
the
the
red
member
to
the
blue
member
okay.
So
so,
hopefully
you
get
an
idea
of
you
know
the
things
that
you
can
do
in
the
sandbox
kind
of
these.
These
the
three.
A
What
I
would
describe
is
the
three
pillars
of
of
firefly
features,
messaging
tokens
and
smart
contracts
and
there's
a
lot
that
you
can
do
with
them.
They
give
you
the
very
powerful
building
blocks
to
to
build
enterprise
grade
web
3
applications,
and
hopefully
this
gives
you.
You
know
enough
of
a
starting
point
that
okay,
I
can
I
can
go
from
using.
You
know,
command
line,
tooling
and
and
building
my
own
contract.
I
can,
I
know
how
to
deploy
it
to
a
chain.
I
know
how
to
how
to
use
firefly
with
that
contract.
A
A
So
hopefully
this
has
given
you
enough
of
a
starting
point
that
now
you've
got
the
creative
juices
flowing
and
you're
thinking
of
all
the
different
things
that
can
be
built
with
these
functionalities,
just
real
quick
would
like
to,
but
before
we
jump
into
open
discussion
at
the
end,
I
I
never
like
to
let
a
good
opportunity
go
to
waste
to
to
invite
people
to
to
join
in
the
firefly
community.
This
is
an
open
source
community
and-
and
it's
in
my
opinion,
a
very
open
open
source
community.
A
We
would
love
for
you
to
join
us
on
discord
if
you're,
not
already
in
there
chatting
in
in
the
in
the
channel
for
the
workshop
there's
please
come
over
and
join
us
we'd
love
to
continue.
The
dialogue
myself
and
a
bunch
of
the
other
maintainers
are
are
in
there
on
a
daily
basis,
chatting
with
folks
answering
questions
about
firefly
and-
and
it's
also
a
great
place
to
to
give
for
for
us
to
receive
feedback
too
of
like
hey,
I
tried
this
thing
and
it
didn't
work.
Oh
well,
that's
not
expected!
A
You
know,
let's,
let's
take
a
look
at
that
together,
also
you're
the
source.
It's
all
open
source.
It's
on
github
go
check
out
the
source.
We
would
love.
If
you
have
ideas
of
of
things
that
you
know
you
want
to
build
on
firefly
or
new
plugins
or
feature
enhancements,
we
would
welcome
contributions
to
the
project
so
come.
A
A
I
think
at
this
point
we
are
going
to
kind
of
transition
now
into
I
peter
broadhurst,
one
of
the
other
maintainers
on
the
project
wanted
to
talk
a
little
bit
about
kind
of
future
road
map
and
where,
where
is
the
project
going
from
here,
because
I'm
sure
a
lot
of
people
are
really
curious
about
that,
and
then
we
will
open
it
up
for
for
just
open
discussion
after
that.
If
people
have
questions
we
can
discuss,
you
know
whatever
topics
that
people
want
to
talk
about.
A
C
Thank
you
so
much
nico,
I'm
just
gonna
start
showing
my
screen
here.
So
before
we
go
into
roadmap.
I'm
just
gonna
recap
a
little
bit.
I
hope
everyone's
enjoyed
getting
your
hands
on
firefly,
no
matter
how
fast
food
you
got
during
the
session
today,
the
discord
is
there
keep
going
with
us
keep
chatting
with
us.
It
will
be
great
for
you
to
make
sure
you
you
get
to
the
point
that
you've
got
that
sandbox
there.
C
C
It's
not
a
production
deployment
tool,
so
production
deployment.
How
does
that
work?
Kubernetes,
helm,
devops,
tooling?
I
would
love
to
have
that
conversation
on
on
discord,
but
that
tool
gets
you
that
environment
running
on
your
laptop.
You
then
have
the
firefly
explorer
ui,
which
is
a
lot
like
a
block
block
explorer
will
be
for
just
the
blockchain
layer.
C
This
is
the
tool
that
lets
you
see.
What's
going
on
in
firefly
and
all
the
layers,
the
blockchain
and
then
all
of
the
off
chain
pipes
and
the
tokens
and
everything
as
well,
and
then
this
absolutely
fantastic
tool
which
you
saw
nico,
demonstrating
and
hats
off
to
the
community
members
that
felt
less
over
the
last
few
weeks.
It
just
lets
you
experiment
with
all
the
different
things
that
powerful
I
can
do
so
I
hope
you
get
to
the
point.
You've
got
all
those
tools
there
and
you
can
really
experiment.
C
C
C
Apis
that
allow
you
to
connect
to
custom,
smart
contracts
that
use
builds
and
apis
that
let
you
do
kind
of
really
quite
complicated
things
like
on
chain
off
chain
data
coordination,
broadcasting
data
to
everybody
in
the
network
that
needs
to
be
put
on
a
system
like
ipfs,
so
it's
shared
with
everybody.
It
doesn't
fit
on
the
blockchain,
sending
data
securely
directly
from
one
member
to
another
member
or
to
three
different
members,
backed
by
the
blockchain,
but
data
database
can't
go
onto
the
blockchain
because
it's
too
sensitive
or
it
needs
to
be
deleted.
C
So
these
flows,
the
sort
of
data
exchange
patterns,
multi-party
business
process
flows,
apis
that
just
do
that.
There's
a
pattern
on
top
of
those
core
core
w3
capabilities
and
then
digital
assets,
and
we,
you
know
anyone
who's
seen.
Blockchain
knows
just
how
important
those
digital
assets
are
to
building
use
cases,
whether
it's
uniqueness,
these
nfts
in
an
enterprise
context,
knowing
that
everybody's
referring
to
the
same
thing
in
the
world,
those
nfts
or
whether
it's
exchange
of
real
value
of
value,
digital
settlement
exchange
of
value
in
a
tokenized
economy.
C
C
I
hope
you
find
that
that
when
he
comes
through
as
you're
using
the
sandbox
is
everything
in
blockchain,
whether
you
use
firefly
or
not.
The
only
way
to
program
blockchain
is
through
an
event-driven
model,
so
so
firefly
helps
you
with
that.
It
makes
it
easier
for
your
applications
that
you
use
things
like
web
sockets
to
try
and
make
it
easier
to
build.
So
it's
a
platform
for
building
on
and
if
we
just
look
at
a
more
technical
view,
rather
than
a
feature
function
viewer.
So
the
last
chart
was
the
architecture.
C
This
is
the
architecture
and
look
at
the
components
of
it.
It
sits
as
a
layer
in
parts
generation
invented
by
software.
We've
called
this
middleware.
It
sits
between
the
application
and
all
of
those
core
back-end
data
systems,
so
whether
that's
public
blockchain.
I
know
those
questions
about
public
drop
chain.
We're
going
to
talk
for
a
minute
about
that,
whether
it's
your
own
plugable,
private
blockchain.
C
C
So
you
know
you
can
choose
your
enterprise
version
of
blockchain
that
we'll
talk
about
about
side
chains
as
well,
but
all
pluggables
about
these
core
sort
of
blockchain
native
technologies,
but
then
also
it
sits.
On
top
of
the
sort
of
off-chain
data,
again
plugable
things
like
shared
storage
ipf
as
we
talked
about
and
then
your
own
private
data
bus,
because
almost
certainly,
if
you're
building
for
enterprise
there's
going
to
be
data,
that's.
B
C
Private
to
go
onto
the
blockchain
itself,
so
it
sits
as
this
layer
in
between
and
it's
a
microservices
architecture.
So
the
reason
why
we're
talking
about
how
much
memory
do
I
need?
Well,
you
first
need
docker
when
you
need.
You
know
you
need
to
have
all
these
containers
running
on
your
laptop,
because
it's
designed
to
be
pluggable
and
nowadays
plugable
means
microservices.
C
It
means
a
docker-wise
kubernetes
native
deployment
model.
So
so
that's
what
it
is.
The
way
it's
constructed
with
no
detail
and
no
time
to
talk
about
the
detail
of
what
all
of
these
different
components
are
in
this
session
and
at
its
core.
It
has
a
database
a
private
database-
and
this
is
this-
is
something
that's
really
important.
C
C
C
If
you
are
interested
in
contributing
key
key
focus
areas,
one
is
no
surprise
being
an
enterprise
focused
technology
and
where
enterprise
adoption
of
blockchain's
been
for
the
last
few
years,
firefly
evolved
and
actually
many
of
the
components
have
evolved
over
the
last
four
years
of
production
deployments
on
sidechains
on
enterprise,
private
blockchains
that
are
secured
with
a
sort
of
hard
boundary
you
have
to
be
permissioned
in.
You
have
to
be
able
to
join
the
club
to
have
access
to
it.
Technologies
like
hyperledger
fabric.
C
I
pledge
a
betsu
and
even
corda
nowadays
the
lines
between
what
you,
where
whether
a
use
case
or
website
use
case
needs
just
a
side
chain
or
just
public
is
being
blurred.
It's
really
common
to
need
a
mix
inside
of
your
inside
of
your
business
inside
of
your
projects,
so
we're
seeing
the
the
the
the
lines
of
separation
between
what
used
to
be.
You
know.
Obviously,
this
is
going
to
be
on
the
side
chain
and
what
used
to
be
well.
Obviously,
this
is
going
to
be
public
public.
C
Those
lines
are
blurring
as
more
and
more
layer,
two
and
another
sort
of
proliferation
of
public
blockchains
and
permission
public
blockchains
are
happening,
ck,
roll-ups
and
all
these
technologies
that
are
meaning
that
those
things
are
happening.
Lots
and
lots
more
and
and
as
enterprises
are
thinking
more
about
digital
assets,
business
to
consumer
use
cases.
So
so
this
is
a
big
area,
but
we've
got
a
big
focus
on
at
the
moment.
There's
another
focus
around
additional
sample
applications
that
show
things
end
to
end.
C
The
sandbox
is
so
fantastic
for
seeing
what
firefly
does
all
the
different
individual
operations,
but
what
does
an
end-to-end
web
3
use
case?
Look
like
sdks,
there's
a
node.js
sdk
hats
off
to
to
andrew
richardson,
who,
who
led
the
development
on
that
one,
but
there's
a
goal
to
have
sdks
for
other
languages,
javascript
etcetera
to
be
for
all
the
variety
of
application,
development
platforms
that
people
work
in
and
and
then
sort
of
slightly
beyond
that,
I'm
supporting
talking
to
lots
of
different
blockchains
from
a
single
firefly
instance.
C
Some
of
this
is
available
today.
You
can
actually
connect
token
connectors
to
token
economies
and
multiple
blockchains
today
on
firefly,
but
and
that
core
sort
of
bus,
where
you're
doing
the
you're
doing
the
you
know
the
smart,
the
the
customer,
smart
contracts,
etc,
you're
tied
to
one
blockchain
today,
so
that's
that's
a
model.
That's
going
to
sort
of
evolve
very
quickly.
We
think
and
then
another
area
there's
a
big
focus
is
on.
C
C
C
To
date,
we've
had
a
connector
for
ethereum
called
ethernet,
which
is
a
very
mature
technology.
It's
been
involved
over
the
last
four
years.
We
have
similar
solid
there
projects,
hyperledger
fabric
and
there's
another
project
for
chord
apps
encoder,
which
is
you
need
to
customize
a
little
bit
more
to
your
core
down.
C
Those
are
really
focused
on
chains
that
work
really
predictively,
they
that
they
have
enterprise-grade
features
inside
of
them
for
streaming
transactions
to
a
predictable
blockchain,
getting
transactions
there
really
quickly,
but
if
they
expect
those
transactions
to
be
really
final
very
quickly,
so
once
they're
on
the
chain.
You
know
you
know
that
they're
there
that's
not
the
way.
Most
public
blockchains
work,
most
public
blockchains
work.
C
It
takes
a
lot
of
time
and
effort
and
gas
management
and
resubmission-
and
you
know
maybe
you're
going
to
need
to
increase
the
value
that
you
you've
given
to
the
people
to
include
your
your
your
transaction
in
the
block
public
blockchains
work
in
a
slightly
different
way.
So
we
have
this
evolved
architecture
which
has
come
along
specifically
for
public
blockchains.
C
I'm
not
going
to
go
into
detail
here,
but
come
along
to
the
community
sessions
which
one
on
alternate
wednesdays.
To
learn
more
about
this.
It's
going
to
do
a
deep
dive
on
this
in
one
of
the
upcoming
firefly
community
sessions,
but
here's
here's
the
highlights
a
new,
quite
significant
component,
microservice
components
inside
the
firefly
called
the
blockchain
transaction
manager.
C
Connect
has
been
all
the
way
down
in
the
connector
to
the
particular
blockchain
are
moving
up
into
this
blockchain
transaction
manager,
so
this
becomes
the
heavy
lifter
and
then
the
blockchain
specific
api,
connectors
and
ethernet
now
has
the
first
one
of
these
there
in
the
repo
are
really
easy.
You've
got
a
new
blockchain.
C
C
I
want
to
add
that
blockchain
in
building
one
of
those
connectors
is
now
a
very
small
job
with
this
new
architecture,
because
you
don't
need
to
rebuild
the
heavy
lifting,
ethernet
and
fabricate
both
have
all
of
that
stuff
inside
of
that.
So
so
this
is
a
really
significant
evolution
of
the
architecture
of
the
firefly
overall
picture,
and
this
means
that
plugging
in
to
tens,
you
know
increasingly
we're
seeing
hundreds
of
different
blockchain
ecosystems
out
there.
C
A
Thank
you
peter
appreciate
the
the
recap
and
kind
of
the
look
ahead
there.
It's
really
exciting
stuff
and,
as
peter
said,
you
know
if,
if
this
sounds
exciting
to
you
and
you,
you
wanna
get
involved
in
the
discussion
about
the
future
of
the
project.
The
you
know,
in
addition
to
getting
involved
in
chat
and
discord,
are
our
every
other
week.
Community
calls
are
a
great
place
to
to
have
kind
of
the
the
deeper
discussion
and
dialogue
with
maintainers
and
other
community
members
all
right.
A
So
at
this
point
we've
got
a
few
minutes
left.
I
will
open
it
up
again,
please
just
there's
quite
a
few
folks
still
on
here
over
100
people
here
and
still,
which
is
super
exciting.
So
let's
just
try
to
raise
your
hand
if
you
have
a
question
or
something
you'd
like
to
chat
about-
and
I
see
mustafa
has
their
hand
up.
So
you
have
the
floor.
B
C
Just
wanted
to
be
really
clear:
there's
two
types
of
connector
that
we've
talked
about
two
completely
separate
ones:
one
is
a
blockchain
connector
ethernet
fab
connect
cord
to
connect
that
actually
they're
written
in
go
those
connectors
today
the
example
ones,
and
these
connectors
will
talk
to
any
smart
contracts
and
in
the
demo
and
the
walkthrough
you
actually
saw
nico
just
teach
firefly
about
a
new
smart
contract
and
that
could
have
been
any
smart
contract
in
the
world.
As
long
as
you
can
find
this
information,
you
can
talk
to
it.
C
You
can
listen
to
the
events,
then
there's
this
separate
connector.
That
nico
was
just
talking
about
which
is
written,
that
the
base
ones
the
examples,
the
sdk
for
writing
these
is
in
typescript.
You
don't
have
to
use
typescript,
but
that's
where
the
sample
is,
and
these
are
tied
to
a
particular
contract
standard.
C
And
here
we
have
an
api.
That's
specific
to
tokens
and
firefly
understands
things
like
what
is
a
transfer?
What
does
it
mean?
What
is
the
burn?
What
is
an
approval
that
you
can
then,
inside
of
your
connector,
you
can
tie
it
to
your
particular
token
economy.
Maybe
you're
doing
a
security
token
with
an
erc
1400
standards,
and
you
need
to
sort
of
customize
to
that.
That's
why
you
might
actually
need
a
connector
for
that
as
well.
B
A
B
C
A
C
I've
got
a
bidding
system
that
you
know
like
a
like:
a
an
on-chain
version
of
an
auction
site
right.
That's
going
to
be
very
bespoke
to
the
way
that
you've
written
now
or
a
lending
library
for
books,
or
you
know,
or
a
supply
chain
use
case
or
like
100
different
different
things.
So
for
those
you
don't
need
a
connector,
because
firefly
will
generate
you
an
api
just
like
that.
B
B
B
B
Supports
any
smart,
smart
contract
implementations,
but
because
tokens
are
such
a
useful
construct
in
the
programming
model
world,
we
decided
to
make
it
a
first-class
thing
in
car
flight
programming
model.
So
specific
token
standards
can
be
supported
as
a
first-class
thing.
So
yeah,
the
firefly
ui,
can
understand
specifically
the
workflow
of
different
types
of
topics.
B
A
A
B
So
I
in
my
head-
I
I
have
specific
use
case
for
polka
dots,
so
if
I
am
to
write
an
adapter
for
a
connector
for
polka
dots,
what
I
need
is
something
that
can
talk
to.
Pocket.Barchain
asked
for
for
deployed
contracts
asks
for
the
abi
like
thing
of
those
contracts
and
converted
to
a
standard
format
read
by
the
firefly
apis
right.
C
C
So,
if
you're,
if
you're,
literally
looking
to
like
start
coding
within
the
next
five
days,
we
should
sing,
because
I
think
you'll
find
it's
like
there's
components
moving
about
a
lot,
but
I
think
in
about
a
week's
time,
there's
sort
of
like
instructions
for
like
what
what's
the
recipe
for
a
new
connector
in
about
a
week.
We
should
have
that
written
down
and
that
would
be
a
great,
a
great
place
to
start.
B
Okay,
thank
you.
Yeah
mustafa
ck
had
a
similar
question
like
what
about
supporting
other
layer,
1
public
chains-
and
I
mentioned
any
of
the
evm
based
or
any
chain
that
supports
evm
and
the
json
rpc
would
be
a
really
good
candidate
for
sort
of
the
first
wave
of
new
connectors,
because
we
already
got
the
the
awesome
youth
connect
that
does
most
of
the
evm
based
interactions
already
so
a
pair
chain
on
polka
dot.
You
know
like
moonbeam,
for
example,
avalon.
C
Right
yeah,
it's
definitely
possible,
but
it
will
just
make
it
a
little
bit
more
work,
but
definitely
custom
power
chain
support
is
not
a
would
fit.
The
firefly
model.
We've
thought
about
it
along
the
way.
So
so
I'm
sure
there
will
be
a
way
to
fit
it
in.
It
will
just
need
a
little
bit
more
because
you'll
have
to
think
about.
Like
you
said
the
modeling
of
what
does
the
transaction
look
like,
because
you
see
an
ability
gives
you
that
for
free,
but
we
actually
did
that
for
the
fabric.
Didn't
we
jim.
B
A
All
right
well,
once
again,
thank
you
everyone
for
coming
out
today.
This
was
a
a
great
session.
I
was
just
really
excited
to
see
the
turnout
and
the
participation
and
I've
I've
had
a
chance
to
look
over
some
of
the
chat
going
on
in
discord
and
excited
to
continue
the
conversation
with
folks
over
there.
Thank
you
very
much
for
coming
out
and
I
hope
you
have
a
great
rest
of
your
day.