►
Description
A virtual workshop run on Thursday, March 23, 2023. In this workshop, Nicko Guyer, Alex Shorsher and David Echelberger, Full Stack Engineers at Kaleido and Hyperledger FireFly maintainers and contributors, will show you how to use Hyperledger FireFly to launch an NFT collection on public chains.
We’ll provide an overview of Hyperledger FireFly features including:
* Web3 Gateway Mode - for connecting to popular public chains like Ethereum, Polygon, Avalanche, Optimism, Arbitrum, etc.
* Public Blockchain Tools - with support for managing and signing transactions
* Enterprise-friendly functionality - to ensure new apps meet both user and compliance requirements.
* Integration capabilities - for connecting your NFT app to existing enterprise systems.
From there, we’ll take you through the steps to create and launch an NFT collection on Polygon using Hyperledger FireFly. With live coding and easy-to-follow steps, you’ll have everything you need to launch your own NFT collection.
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 may 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.
The guide for the workshop is at: https://github.com/nguyer/firefly-nft-workshop-2023-03-023
You can join a discussion about FireFly on the #firefly channel on the Hyperledger Discord server at: https://wiki.hyperledger.org/display/HYP/Our+chat+service
And for more about FireFly, check out their Github repo at: https://github.com/hyperledger/firefly
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Discord: https://discord.gg/rVCn4j7UFd
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #Blockchain
License
Creative Commons Attribution license (reuse allowed)
B
All
right
are
we
ready
to
kick
off
you're
good,
to
go
all
right.
Thank
you.
Everybody
for
attending
today,
I'm
really
excited
about
this.
Workshop
looks
like
we
have
a
a
good
turnout.
It
looks
like
folks
are
still
joining
here,
so
let's
go
ahead
and
get
things
kicked
off.
My
name
is
Nico
Guyer
I'm,
a
software
engineer
here
at
collido
and
I'll
be
joined
by
Alex,
shorcher
and
David
as
well.
B
There
are
two
other
Engineers
here
at
collido
and
also
maintainers
on
hyperledger
Firefly
and
so
Alex
and
David
will
be
helping
out
with
the
workshop
today.
There
is
a
channel
in
Discord
that
you
can
join
if
you
haven't
already
for
for
chat.
This
is
going
to
be
a
very
interactive,
very
Hands-On
Workshop
we're
going
to
go
through
things
slowly
intentionally
so
that
people
can
follow
along
and
do
things
on
their
machine
as
we
go.
B
B
B
The
other
thing
is
the
here's
the
the
channel
That
I
mentioned.
So
if
you
join
the
hyperledger
Discord
server,
if
you
scroll
down
to
the
Firefly
Channel,
there's
a
a
firefly
Workshop
channel
here
in
the
Firefly
section.
This
is
the
channel
that
we'll
use
for
dialogue
during
the
workshop.
So
if
you
have
questions
or
if
you
get
stuck
on
something
or
need
help
post
it
here
and
I'll,
try
to
monitor
this,
but
Alex
and
David
will
be
monitoring
it
and
answering
questions
in
there
as
well.
Okay.
A
B
We
are
going
to
deploy
and
configure
a
custom
token
contract
with
firefly
we're
going
to
start
that
contract
from
scratch
actually
and
I'm,
going
to
walk
you
through
all
the
different
parts
of
that
we're
going
to
upload
nft
assets
to
public
ipfs
with
firefly
and
we're
going
to
an
nft
on
a
public
chain
and
look
at
it
on
a
public
chain
and
we'll
be
able
to
see
it
there.
So
one
other
thing,
I,
actually
I-
think
I,
maybe
mentioned
forgot
to
mention
this
in
in
the
guide
It's
just
now
occurred
to
me.
B
If
you
want
to
actually
see
your
nft
in
a
real
Wallet,
app
I
recommend
the
I
think
I
may
have
I
may
have
mentioned
this
in
the
in
the
top
of
the
guide
here,
but
I
recommend
the
alpha
Wallet
app.
You
can
get
it
here.
This
is
something
you
can
set
up
on
your
smartphone,
it's
open
source,
so
you
know
I
like
to
recommend
open
source
software,
but
this
this
app
has
a
couple
of
features
that
we
need
for
today.
B
It
allows
you
to
connect
to
a
test
net
which
we'll
be
using
a
test
net
for
today,
so
that
you
don't
have
to
spend
real
money
in
order
to
Mint
your
nft,
and
it
also
shows
the
artwork
of
the
nft
in
there.
So
when
we
get
to
the
point
where
we
actually
minted
our
token
and
we
want
to
transfer
it
to
an
address,
you
can
use
your.
B
This
is
kind
of
an
optional
step,
but
you
can
you
can
transfer
it
to
your
wallet
address
from
this
app
and
then
you
can
actually
see
it
to
show
up
there,
and
so
that's
that's
kind
of
like
a
cool
bonus
feature
if
you
want
to
go
ahead
and
get
that
set
up
on
your
phone,
if
you
don't
have
a
wallet
app
already
that
can
connect
to
a
test
net.
So
that's
just
one
other
thing
that
we
can
set
up
all
right
for
the
agenda.
B
We're
going
through
the
housekeeping
stuff
right
now,
I'm,
going
to
give
a
very
brief
introduction
to
hyperledger
Firefly
I'm,
going
to
try
to
keep
it
to
five
to
ten
minutes
and
just
to
kind
of
give
if
folks
are,
are
new
to
the
project
in
general,
just
kind
of
give
an
overview
of
like
what.
What
is
this
thing
and
but
I'm
going
to
keep
that
brief,
because
I
really
want
to
spend
the
bulk
of
the
time
Hands-On.
The
total
Workshop
run.
Time
is
three
hours.
B
I
can't
sit
still
for
three
hours
at
a
time,
so
I've
planned
a
couple
of
breaks
in
between
certain
sections,
so
we'll
see
how
far
we
get
we'll
kind
of
just
we'll
be
flexible.
So
if
we,
you
know
this,
this
may
not
happen
in
exactly
this
order,
but
I
want
to
give
some
people
some
breaks
throughout,
because
you
may
need
to
go,
get
something
to
drink
or
or
food
depending
on
what
time
zone
you're
in.
B
B
B
So,
let's
get
into
just
a
very
brief
introduction
to
what
is
Firefly.
So
Firefly
is
a
platform
to
build
web3
apps.
So
I
like
to
describe
this
to
Developers
I
I
like
to
use
a
stack,
diagram
and
I
think
this.
This
picture
gets
at
the
the
immediate
value
to
a
developer
and
I'm
a
developer
and
I
I
assume.
Probably
many
of
you
are
as
well
or
or
you're
at
least
comfortable
with
code
and
that
sort
of
thing.
So
so
hopefully
this
resonates
with
you
as
well.
B
So
what
do
you
need
to
build
a
web
3
out?
Well,
first,
you
need
a
blockchain
you
need.
If
you're
gonna
have
public
data
available,
you
probably
need
some
sort
of
off-chain
storage
like
an
ipfs
node
and
there's
lots
of
great
open
source
projects
for
these
types
of
things.
So
you
know
that's
that's
great!
That
we're
not
Firefly
is
not
trying
to
be
another
type
of
blockchain.
It's
not
trying
to
be
a
DLT
itself,
but
it
builds
on
top
of
these
really
powerful
Technologies.
B
The
next
thing
you
might
need
is,
you
might
need
a
token
smart
contract.
You
need
something
to
manage
your
transactions
that
are
going
to
that
that
contract
you
need
to
index.
Events
that
are
are
coming
off
of
that
contract.
So
you
need
to
write
some
code
to
do
that.
All
these
Yellow
Boxes
are
are
stuff
that
you
have
to
build.
B
There's
going
to
be
some
coordination
between
data,
that
is
on
the
Chain.
You
know
things
like
token
indexes
or
or
other
pieces
of
data
that
have
been
pinned
to
the
chain
and
also
data
that
you
need
to
keep
off
the
chain
as
well
data,
that's
too,
either
too
large
or
too
sensitive
to
put
on
the
blockchain
itself.
So
you
need
some
some
code
to
to
link
those
things
and
keep
track
of
them
and
treat
them,
as
you
know,
a
transaction
that
encompasses
both
of
those
things.
B
Likewise,
along
with
that,
some
some
data
needs
to
be
public.
Some
data
needs
to
be
private
and
then
then,
finally,
you
start
to
get
up
into
the
what
we
think
of
as
the
good
stuff,
the
the
actual
business
logic
or
your
backend
API
for
your
application.
You
know
what
you
know.
All
of
these
things
below
this
layer
are
just
the
things
that
you
need
to
actually
drive
a
blockchain,
but
then
you
know
what
what
does
your
app
actually
do?
B
What
what
business
value
does
it
provide
and
that
that's
where
we
start
to
get
into
up
in
these
top
layers?
And
then
finally,
you
probably
need
some
sort
of
front
end
for
it.
You
need
something
for
your
users
to
actually
use
like
a
web
UI
or
a
mobile
app,
so
there's
a
lot
of
different
pieces
to
build
in
in
a
web3
app.
B
That
can
help
you
with
that,
but
before
hyperledger
Firefly
there
wasn't
one
platform
that
helps
you
with
all
of
these
things,
and
so
that's
what
hyperledger
Firefly
does
it
takes
this
whole
middle
section
and
says:
hey,
you
know
what
we
have
built
a
a
platform
that
handles
all
of
this
Plumbing,
all
of
the
the
really
hard
and
maybe
not
quite
so
interesting.
It's
interesting
from
a
technical
perspective,
maybe
not
from
a
business
value
perspective,
though
of
all
of
this
stuff,
that
you
need
to
drive
a
web
3
application.
B
B
It
connect
connect
to
private
permission
chains,
public
Chains,
It's,
it's
modular,
so
it
can
be
extended
and
it's
it's
a
common
platform
that
solves
all
of
these
problems
for
you.
So
you
can
focus
on
now
this
really
small
top
layer,
which
is
your
app's
code.
You
can
focus
on
the
thing
that
actually
drives
your
business,
real
value
like
the
business
Logic,
the
user
experience
and
all
this
stuff
and
and
you
can
use
fireflies
API
fireflies
websocket
interfaces
to
work
with
technologies
that
develop
the
web.
B
2
developers
are
already
familiar
with
and
can
pick
up
and
use
right
away
and
really
Leverage
The
Power
of
web3
quickly.
So
that's
that's
I!
Think
the
you
know
the
the
real
value
of
firefly
in
a
nutshell,
for
a
developer.
Is
that,
like
it
takes
care
of
this
huge
portion
of
the
tech
stack
that
you
don't
have
to
recreate
over
and
over
and
over
for
every
web3
app
that
you
want
to
build.
B
If
you
still
want
you
know
down,
maybe
maybe
you
want
more
control
down
here
at
the
contract
layer
and
you
want
to
use
a
Custom
Contract
like
we're
going
to
do
today.
Firefly
absolutely
lets
you
do
that,
and
that's
that's
one
of
the
things
we're
going
to
show
off
today.
You
can
use
fireflies
built-in
token
contracts.
B
If
you
want
you're
not
limited
to
that,
though
you
can,
you
can
plug
in
whatever
smart
contract
you
want,
and
it
still
gives
you
that
if
you
need
to
go
directly
to
the
blockchain
or
use
your
custom
use
a
custom
Smart
contract,
it
doesn't
lock
you
out
of
doing
those
things.
It's
really
meant
to
to
complement
all
of
those
things
and
build
on
top
of
them.
B
So
you
know
where
does
Firefly
fit
into
the
picture
for
for
an
Enterprise?
That's
that's
really
what
you
know
hyperledger
software
is
really
geared
toward
Enterprise
Firefly
can
can
connect
to
public,
and
so
it
can
be
really
useful
for,
for
you
know,
personal
projects
as
well.
It's
I
I
think
it's
a
a
great
fit
for
that
as
well,
but
it's
primarily
geared
toward
Enterprise
applications
and
it
was
designed
that
way
from
the
from
the
get-go.
So
you
know
Firefly,
you
can
think
of
as
a
web
3
Gateway.
C
B
What's
inside
a
firefly
node,
it
is
a
microservice
architecture,
so
it
has
a
lot
of
different
things
inside
it.
I've
hinted
at
that
a
little
bit
that
it's
pluggable
and
that
it's
extensible
I
won't
go
into
the
all
the
detail
of
every
single
thing.
On
this
diagram.
That's
there's:
there
are
some
already
some
great
resources
on
YouTube
that
kind
of
break
down
this
diagram
and
talk
about
all
the
different
components
and
what
it
is.
But
you
know
essentially
at
the
top
here
you
have.
B
This
is
the
application
that
you
can
build
and
you
can
use
fireflies
rest
apis.
You
can
receive
events
through
fireflies
event,
delivery
mechanisms,
which
is
today
a
web
Hooks
and
web
sockets.
But
again
it's
extensible
Firefly
provides
an
open,
API,
Swagger
interface,
which
we
will
be
looking
at
and
using
later
today,
along
with
the
Explorer
UI,
we'll
be
looking
at
that
as
well,
and
those
are
all
hosted
by
Firefly
core.
B
But
I
just
wanted
to
give
just
a
brief
peek
under
the
hood,
so
you
can
see,
but
it's
it's
not
just
one
thing
that
we're
running
there's
a
bunch
of
different
Services
here.
The
Firefly
command
line
interface,
which
is
what
we'll
be
installing
and
running
here
shortly,
is
a
tool
that
is
designed
to
run
all
of
this
in
a
local
development
environment
set
up
on
your
machine
and
it
takes
care
of
setting
up
and
configuring
all
of
these
services
for
you.
So
you
can
just
run
a
couple
commands
and
be
up
and
running.
B
So
that's
what
we're
going
to
run
here
in
just
a
little
bit
to
set
everything
up.
Just
a
quick
shout
out
to
the
Firefly
Community.
We
would
love
for
not
plugged
into
the
community.
Please
join
the
Discord
again
there's
a
dedicated
channel
for
today's
Workshop
in
there,
but
you
can
also
check
out
the
source
code
for
Firefly
on
GitHub.
If
you
haven't
I'll,
just
add
a
brief
plug
for.
B
If,
if
you
like
this
Workshop,
if
you
like
the
project,
please
go
to
GitHub
and
click
on
this
little
button
and
star
the
project.
We
would
love
to
get
some
more
stars
just
to
to
drive
up
visibility
of
the
project
in
GitHub
and
in
whatever
other
algorithms
pay
attention
to
that.
So
just
a
quick
little
advertisement
plug
there.
B
That
is
that's
it
for
slides.
So
I've
tried
to
keep
that
brief.
I
think
I
kept
it
to
15
minutes,
which
was
what
about
what
I
had
allocated
it
for
that.
So,
above
and
beyond
Nico
as
usual,
you
nailed
it.
I
I,
try
I,
try,
okay,
so
let's
go
ahead
and
hit.
This
link
now
should
be
in
the
chat.
I'll
just
drop
it
in
there
one
more
time
in
case
people
have
joined
late
because
I
don't
think
you
can
see
old
messages.
B
A
B
A
good
question,
so
that's
kind
of
a
just
a
general
Firefly
question
I'll,
take
that
one
here,
real,
quick
but
yeah,
so
so
Firefly
has
its
own
database.
It
keeps
it's
basically
so
blockchains
are
not
great
at
answering.
Questions
like
what
are
all
of
the
events
that
have
been
emitted
from
this
particular
smart
contract
with
this
particular
signature,
such
as,
if
you
wanted
to
know,
show
me
all
of
the
token
transfers
for
a
particular
type
of
erc20
token.
B
Well,
you
could
figure
that
out
from
a
blockchain
node
by
starting
back
at
when
that
contract
was
deployed
and
going
through
all
the
different
blocks
for
that
have
been
mined
since
then,
and
looking
for
events
that
have
been
emitted
from
that
contract.
That
could
take
a
long
time
depending
on
how
how
long
ago
that
was
so
Firefly
keeps
track
of.
This
is
one
example
of
the
things
that
Firefly
keeps
in
its
database.
B
You
can
tell
it
to
hair
Index
this
this
contract
and
store
all
of
the
events
that
you
see
in
a
right
now.
It's
it's
some
sort
of
SQL
database,
primarily
postgres,
is
the
the
main
plugin.
That's
most
commonly
used
stores
it
in
there
in
a
fast
access
queryable
way.
So
it's
it
is.
The
short
answer
is
most
of
the
data.
B
That's
in
the
Firefly
database
is
data
that
has
come
from
the
blockchain,
but
we
want
to
store
in
a
way
that
can
be
queried
really
quickly
and
and
searched,
or
it
is
data
that
is
too
sensitive
to
put
on
the
blockchain,
and
so
we
keep
it
in
a
private
database
and
have
a
a
link
or
a
pin
to
a
hash
of
a
transaction
where
that
thing
was
was
pinned
to
the
blockchain.
So
hopefully
that's
a
probably.
That
was
a
an
answer
to
your
question
there.
B
B
B
Let's
dive
in
so
hopefully
you've
had
a
chance.
If
you
don't
have
Docker.
Hopefully
you
had
a
chance
to
set
that
up
we're
going
to
start
at
the
beginning
now
and
I
I've
actually
gone
and
deleted.
My
my
Firefly
CLI
binary
on
my
machine
so
I'm
going
to
start
it
up
I'm
going
to
install
it
from
scratch.
Just
like
you
all
are
here
as
we
go
along
I
want
to
make
this
a
little.
Bigger
is
sorry.
B
Okay
cool,
so
just
a
couple
of
notes
for
for
Linux
users,
it's
it's
recommended
not
to
run
the
Firefly
CLI
as
root
I.
Just
I
try
not
to
run
most
things
as
root.
If
I
don't
have
to
so
it's
it.
It
works
better.
If
you
run
everything
as
a
standard
user
and
add
your
user
to
the
docker
group
for
Windows
users,
I
would
highly
recommend
windows
subsystem
for
Linux
2..
B
B
Workshop,
here's
a
picture
I
like
pictures
to
to
kind
of
just
explain
what
it
is
we're
about
to
do
so
we're
going
to
have
Firefly
running
on
our
local
Dev
machine.
It's
going
to
be
running
a
firefly
core
node,
it's
going
to
be
running
an
evm
connect,
blockchain,
connector
and
it'll
run
a
local
ipfs
node
as
well.
B
B
There
are
a
bunch
of
other
blockchain
nodes
that
are
all
a
part
of
this
network.
So
down
here,
I
have
my
wallet
app
on
my
phone
that
I've
set
up
I've
installed
Alpha
wallet
on
my
phone.
It
has
the
ability
also
to
connect
to
some
RPC
nodes.
I
have
no
idea
where
those
ones
are.
It
also
has
the
ability
to
connect
to
ipfs
nodes.
Now
the
beauty
of
a
completely
distributed
app
is
a
decentralized
app
is
that
it
doesn't
matter
where
those
nodes
are
running.
B
So
the
idea
is
that
we
are
going
to
deploy
a
contract
to
the
public
test
net
and
we're
going
to
Mint
a
token
on
it
and
end
goal
of
being.
Hopefully,
we
should
see
that
token
show
up
in
our
Wallet
app
all
right,
so
we're
gonna
go
through
the
getting
started
guide,
the
first
page
of
it
to
set
up
the
Firefly
CLI,
so
I'm
just
going
to
go
to
the
docs
here,
I'm
going
to
actually
open
that
in
a
new
tab
and
I'm.
A
B
B
We
can
still
hear
you.
If
you
have
go
installed
on
your
computer.
You
can
also
go
install
okay,
excellent!
You
can
also
go
install
the
Firefly
CLI.
If
you
don't
have
go,
don't
worry
about
it.
You
don't
need
to
install
it
for
this,
so
I'm
just
going
to
go
here
and
grab
the
latest
one.
So
there
are
binaries
for
Linux
and
for
Mac
OS
as
well.
Please
be
sure
you
grab
the
appropriate
CPU
architecture.
B
There
is
a
a
difference
between
arm
64
and
x86
64..
If
you
have
an
Intel
CPU
or
an
AMD
CPU,
you
probably
want
x8664.
I'm
on
Apple
silicon
Mac,
so
I'm
going
to
grab
the
arm
64
build
here
and
I'm
going
to
download
that
one.
So
please
make
sure
you
grab
the
the
one:
that's
the
appropriate
architecture,
otherwise
it
it
will
not
work
and
it
it
doesn't
give
you
a
very
helpful
message
as
to
why
your
operating
system
couldn't
run
the
binary,
but
it
won't
work
all
right.
That's
gonna,
download!
B
There
is
a
handy
little
command
here.
Really
you
can
put
this
when
you
extract
it,
you
can
put
the
binary
anywhere.
You
want
this
little
handy
command.
If
you
do
run
it
with
with
root
or
or
sudo,
it
will
basically
just
extract
the
binary
and
it
will
move
it
to
user
local
bin
for
you,
assuming
that
it
is
in
the
downloads
folder
in
your
home
directory.
If
that's
not
true,
then
this
one
liner
won't
work
but
you're
welcome
to
just
extract
the
tar
gz
and
put
it
put
the
binary
anywhere.
B
Okay,
so
now
I
should
be
able
to
which
FF,
okay,
so
I
have
the
Fire
firefly
CLI
installed
in
user
local
bin.
Now,
that's
great!
If
I
try
to
run
it,
Mac
OS
is
going
to
say:
oh
I'm,
not
going
to
do
that.
Okay
I'll
show
you
how
to
get
around
this
real,
quick,
we'll
hit.
Okay,
yes,
terminal,
bigger,
understood!
Sorry
about
that!.
B
It's
not
science,
we
didn't
pay
Apple,
boatloads
of
money,
so
it's
not
signed.
So
we
need
to
go
to
system
preferences
and
tell
it
that
we
want
to
run
this
anyway,
so
go
to
security
and
privacy
and
I
believe
this
is
under
General.
It
says
it
says:
FF
was
blocked,
I'm
going
to
allow
the
next
time
I
try
to
run
it
it'll
say:
are
you
really
sure
you
want
to
run
this
and
I'll
say
yes?
B
B
So
the
like
I
said
the
Firefly
CLI
is
a
tool
for
creating
a
local
development
environment,
so
it
has
a
bunch
of
different
command
line
flags
that
we
can
give
it.
It
has
all
of
the
when
we
ran
just
FF
with
no
sub
commands.
It
listed
out
all
the
different
sub
commands
that
we
can
run
FF
init
is
the
just
make
this
even
bigger
here.
Ff
init
is
the
the
command
that
will
create
a
new
stack
for
you.
B
If
you
run
that
with
daf
Dash
help
the
FF
init
command
has
a
bunch
of
flags
as
well
as
well
as
two
sub
commands.
I
I
recommend
using
the
the
ethereum
or
fabric
specific
sub
commands
they're
newer
and
they
have
some
some
of
the
new
command
line.
Flags
are
on
these
sub
commands.
So
if
we
run
you
know,
FF
init,
ethereum
dash
dash
help.
B
These
are
all
the
flags
that
we
can
customize
for
a
an
ethereum
stack
running
on
our
machine
I'm
not
going
to
get
into
what
all
of
these
are
used
for,
but
we
also
use
the
Firefly
CLI
to
create
test
environments
for
Firefly
as
well.
So
it's
used
in
our
CI
pipeline.
It's
used
for
running
the
end-to-end
tests
against
and
and
all
this
stuff.
B
So
that's
what
these
first
few
things
do:
I'm
going
to
just
I'm,
going
to
set
multi-party
mode
off
I'm
going
to
enable
public
ipfs,
so
it's
private
by
default
today
we're
going
to
open
it
up
to
peer
with
public
ipfs
nodes,
though,
because
we
want
our
nft
assets
to
be
visible
on
the
public
internet
and
we're
going
to
connect
to
a
remote,
RPC
node.
So
we're
not
going
to
run
a
blockchain
node
on
our
machine.
B
We
are
going
to
give
it
the
URL
of
the
blockchain
node
and
you
may
notice
this
URL
has
credentials
in
it.
These
are
temporary
credentials.
This
is
a
a
blockchain.
It's
an
RPC
Gateway
that
is
hosted
by
collido,
and
these
these
Collide
is
the
company
that
I
work
for
these
credentials
are
temporary
for
this
Workshop
only
so
they
will
be
deactivated
afterward,
but
you
all
are
welcome
to
use
this
one
today
during
the
workshop,
we're
going
to
configure
the
chain
ID
for
the
Mumbai
network.
B
This
is
I've
gone
and
just
looked
that
up,
it's
801
and
we
need
to
pass
in
a
connector
config.
So
the
connector
config
is
just
we're.
Gonna
customize
a
couple
of
of
settings
that
are
a
little
bit
different
from
their
default
value,
because
this
is
a
public
chain.
So
what
we're
going
to
do?
Is
we
just
need
to
create
an
evm
connect.yaml
file?
B
I
probably
have
one
already
yep,
okay,
so
so
I
already
have
this
file
on
my
machine
because
I
ran
through
this
earlier,
but
basically
just
create
a
file
called
evmconnect.yml
I,
just
created
it
right
in
my
home
directory
and
that
it
and
then
paste
in
these
contents.
Here
now
what
this
is
going
to
do
is
this
is
going
to
tell
it.
I
want
to
wait
for
four
blocks
to
see
to
make
sure
that
my
transaction
has
been
actually
mined.
B
B
So
it
is,
you
do
need
to
connect
to
a
real
blockchain
node
running
somewhere
in
this
case
we're
connecting
to
one
in
the
cloud
you're
more
than
welcome
to
run
your
own
if
you'd
like
or
connect
to
a
different
one,
if
you
have
one
already,
but
this
is
the
one
that
it
I've
tested
and
we're
going
to
use
for
today.
So
it's
not
something
you
can
just
mock
because
it
actually.
That
actually,
is
the
blockchain
you're
connecting
to.
B
B
Okay,
so
I'm
gonna
copy
this
command.
I'm
gonna
go
over
to
my
terminal
and
close
out
of
them
here
and
I'm
going
to
run
this
that's
going
to
initialize
a
new
Firefly
stack.
It's
going
to
go
great.
Okay,
we've
created
it,
and
now
you
can
type
FF
start
Workshop
to
start
it
up.
I'm
gonna
do
that
and
that
will
take
a
few
minutes.
So
that's
basically
going
to
start
and
configure
all
of
those
services
that
we
were
talking
about
earlier.
B
I
will,
while
this
is
going
I'll
pause
here
to
see.
If
there
are
questions,
I'm
gonna,
I'm,
gonna
check
the
the
Discord
chat
as
well.
Can
we
host
the
application
at
collido?
Yes,
you
are
more
than
welcome
to
host
your
own
blockchain
node.
If
you
want
to
it
is
it's
a
lot
of
work,
which
is
why
we
we
took
that
that's
outside
the
scope
of
the
workshop
today
is
how
to
run
your
own
public
blockchain
node.
It's
a
it's
a
really
fun
project,
if
you're
interested
in
learning
about
that.
B
So
we'll
just
kind
of
take
a
okay,
great
we're
done
here.
Yeah,
it's
pulling
a
lot
of
stuff.
Yes,
there
are
a
lot
of
Docker
containers.
I'll
just
give
you
a
quick
peek
at
what
is
currently
running,
so
we're
running
Firefly
core
we're
running
a
token
connector
for
erc20
and
erc721.
There
is
another
one
for
for
your
c1155
as
well.
We're
running
evm,
connect,
we're
running
a
data
exchange
service,
a
signing
service
and
the
sandbox
as
well.
B
B
So
hopefully
you
are
getting
close
to
to
running
this
as
well.
I'm
gonna
I'm
gonna
keep
going
through
slow
here
any
Docker
image
for
FF
for
the
there's,
not
a
Docker
image
for
the
Firefly
CLI
itself,
which
is
the
the
FF
command.
This
is
the
docker
image
for
Firefly
core
itself
up
here,
but
we
don't.
We
don't
provide
a
packaged
image
that
has
the
command
line
in
it.
B
All
right
I
wanted
to
hop
back
over
to
the
guide
and
talk
about
what
we're
going
to
do
next
so
before
we
can
do
anything
with
our
with
our
Firefly
node.
Well,
actually,
here
let
me
show
you
yeah
I
shouldn't
have
cleared
that
out,
but
it
it
printed
two
URLs
there
and
if
you
don't
clear
your
buffer,
like
I
just
did
you
should
be
able
to
go
to
localhost.
B
B
Yeah,
so
if
you're,
if
you're
running
on
Mac
OS
in
one
of
the
recent
versions,
Apple
very
helpfully
created
a
new
service
and
turned
it
on
for
you
by
default,
even
though
you
didn't
ask
for
them,
because
Apple
knows
what
you
need,
it
is
I,
go
here
and
then
go
to
sharing.
Where
is
sharing
here,
it
is,
and
at
the
bottom
here
there's
an
AirPlay
receiver.
B
Apparently
AirPlay
also
uses
Port
5000,
which
is
the
the
port
that
Firefly
core
by
default
wants
to
bind
to
doesn't
have
to.
You
could
change
it.
It's
just
easier
to
uncheck
this
box
and
start
everything
up
there.
So,
if
you're
getting
a
message
about
something
listening
on
Port,
5000
and
you're
on
a
Mac,
you
want
to
uncheck
this
box
here.
B
Okay,
so
yeah
so
there's
the
sandbox
there's
the
Explorer,
so
we've
got
everything
up
and
running,
and
now
I'm
gonna
go
look
back
at
the
guide
here
and
just
kind
of
talk
through
the
next
couple
steps
before
we
actually
do
anything.
We,
because
this
is
a
public
chain.
We
we
need
to
fund
our
account.
So
the
on
a
public
chain
you
have
to
you
have
to
pay
a
gas
fee
for
the
the
computational
power
that
it
takes
to
to
run
your
transaction.
So
we
need
to
First
Look
up.
B
What
is
the
account
address?
The
wallet
address
that
our
Firefly
node
is
using
when
the
Firefly
CLI
created
everything
for
you.
It
generated
a
wallet
for
you,
that's
on
your
local
machine
and
it
has
an
address
so
I'm
just
going
to
copy
this
bit
here
and
paste
this
in
my
terminal,
I'm
gonna
I'm.
Just
so.
B
If
you
run
FF
accounts
list
and
then
the
name
of
the
stack
it
will
list
all
the
accounts
that
have
been
created
and
their
private
key,
so
I'm,
just
just
grabbing
by
the
address,
so
I
can
just
see
the
addresses
the
private
key.
Is
there.
If
you
need,
it
can
be
useful,
but
just
be
mindful
about
I.
Just
didn't
want
to
leak
that
on
the
screen,
so
I'm
just
grabbing
by
the
address,
and
so
this
is
my
public
address
that
Firefly
generated
when
it
set
up
my
stack.
B
B
So
in
order
to
fund
this
wallet,
what
we're
going
to
do
is
we're
going
to
go
to
polygon,
provides
a
faucet,
so
a
faucet
is
like
for
for
a
test
account
the
for
a
test.
Network
a
faucet
is
basically
a
page
that
you
can
go
to
and
put
in
an
address
and
get
a
very
small
amount
that
blockchain's
native
currency
to
be
able
to
run
test
transactions
on
there.
B
And
hopefully
the
faucet
is
working.
Okay,
there
we
go
yeah,
so
there's
another
question
about
Port
5000.
We
just
just
talked
about
that
a
minute
ago.
If,
if
you're
on
Mac
OS
go
to
system
preferences,
sharing
an
uncheck
AirPlay
receiver
here,
that's
probably
the
most
likely
culprit.
If
it's
not
that,
then
you'll
need
to
do
a
little
bit
more
to
figure
out
what
is
listening
on
that
process.
But
if
you're
on
a
Mac,
that's
probably
the
problem.
B
B
A
B
B
B
I
think
before
we
go
into
before
we
dive
into
actually
creating
the
the
smart
contract
and
deploying
it
I
think
we'll
I
think
we
may
pause
here
for
we're
about
45
minutes
in
maybe
take
a
maybe
take
a
little
break
in
just
a
minute.
I'll
I'll
pause
and
ask
if
there
are
questions
or
if
people
are
stuck
I
want
to
give
people
time
in
order
to
make
sure
their
stack
is
up
and
running
and
they've
got
Firefly
up
and
make
sure
that
they've
gone
up
to
this
point.
B
I
don't
want
to
leave
people
behind
if
we
can
avoid
it.
So
yeah
great
great
question
here
are
the
test
net
funds
into
the
alpha
wallet
or
the
Firefly
nodes
address
great
question
so
I
use
here,
I
went
to
the
command
line
and
I
I
looked
up
the
address.
My
wallet
address
for
the
Firefly
wallet
the
this
is.
This
is
the
signing
key
that
Firefly
will
use
when
it
submits
transactions.
B
If
you
install
the
alpha
wallet
on
your
app
it
probably
I
do
I
believe
you
have
the
ability
to
import
a
private
key
there.
If
you
want
to
what
I
would
suggest
is
having
it
generate
a
a
new
wallet
on
your
app
and
use
a
separate
address
and
we'll
transfer
it
to
that
address
later,
so
we
haven't,
haven't
done
anything
with
Alpha
wallet
yet
we'll
come
to
that
sort
of
at
the
end
of
the
at
the
guide.
If
you
want
to
transfer
it
to
that
address
later.
B
B
B
B
A
B
B
B
Sometimes
it's
able
to
push
files
to
gateways
and,
and
it
just
works
other
times
the
file
just
never
ends
up
replicating.
So
that's
in
a
in
a
production
setting.
You
would
want
to
run
an
ipfs
node
in
probably
the
cloud
or
data
center
or
not
on
a
laptop
behind
a
nap.
You
want
to
run
it
somewhere
where
you
can
configure
the
networking
appropriately
to
expose
the
correct
ports
to
ipfs
so
that
it
has
nothing
blocking
its
peering
ability
with
other
ipfs
nodes.
B
Yeah
ipfs
is
also
running
in
in
Docker
here
as
well.
Yes,
collido
has
the
ability
to
run
ipfs
nodes
in
the
cloud.
There
is
not
currently
a
way
in
the
Firefly
CLI
to
automate
the
configuration
of
a
remote
ipfs
node,
that's
something
that
the
Firefly
CLI
could
be
enhanced
to
do,
but
it
doesn't,
it
just
doesn't
generate
the
appropriate
config
for
that
today.
B
All
right
tell
you
what
we
are
we're
10
minutes
to
the
top
of
the
hour
here.
Let's
take
a
a
five
minute
break
I'm,
going
to
actually
step
away
from
my
computer
go
grab
something
to
drink
and
we'll
come
back
and
I'll
answer
any
more
questions,
and
hopefully,
hopefully
folks.
This
will
give
folks
a
few
more
minutes
if
you're
still
stuck
trying
to
catch
up
and
we'll
make
sure
that
we
get
as
many
people
caught
up
to
to
this
point
as
we
can
before
we
keep
moving
on
in
the
workshop.
B
A
B
B
Absolutely
there
are
ways
to
Firefly
is
very
flexible
when
it
comes
to
Key,
Management
and
signing
the
the
implementation
that
we
have
running
right
now
is
a
very
simple
straightforward
file
based
wallet
on
the
Firefly
signer
node
that
we
looked
at
in
it's
one
of
the
docker
containers
that
I'm
currently
running,
but
there
are
ways
to
to
create
more
keys,
more
wallets
and
and
also
use
an
external
signer
as
well.
Firefly
supports
a
lot
of
different
features
in
that
regard.
B
How
can
you
check
the
data
stored
in
ipfs
using
Firefly
yeah,
we'll
we'll
get
to
the
the
data
apis
and
Firefly
in
just
a
little
bit?
But
you
could
you
know
ipfs
has
its
own
rest
API
you
can
use.
You
can
query
that
rest
API
to
look
up
data,
that's
stored
in
it
just
like
you
could
if
it
was
running
somewhere
else
as
well.
B
Okay,
cool:
let's
give
it
two
more
minutes,
I,
it's
about
lunchtime
here
in
the
U.S,
so
I
actually
grabbed
some
food.
So
I'm
gonna
take
a
couple
bites
here,
we'll
we'll
kick
off
in
the
next
phase
of
the
workshop
here
in
just
a
little
bit,
but
I
think
I
think
we're
running
right
on
schedule
here
right
now,
so
this
is.
This
is
great.
So
hopefully
everyone
is
able
to
work
through
any
issues.
They
have
getting.
Things
started
up
if
you're
still
stuck.
Let
us
know
we're
here
to
help.
C
B
B
B
Okay,
we
are
going
to
move
on,
so
hopefully
everyone
is
got
their
Firefly
stack
running
and
their
wallet
funded.
We're
gonna
go
create
a
smart
contract
now,
so
there
are
lots
of
different
ways.
You
can
create
a
smart
contract
I'm
not
here,
to
be
a
smart
contract
development
expert
I'm
just
here
to
give
you
a
link
to
a
thing
that
you
can
click
and
do
in
your
browser
really
quickly
for
today's
Workshop.
B
There
is
a
fantastic
idea
anywhere
where
I
can
leverage
something
that
is
open
source,
that's
already
built
already
tested,
and
rather
than
writing
it
again
on
my
own
I'm,
going
to
do
that
so
so
this
is
a
great
way
to
to
get
started
really
quickly.
I
also
think
it
happens
to
be
a
a
good
way
to
if
you
really
want
to
go
deep
on
building
your
own
custom.
B
B
B
So
sorry
about
that,
so
here
we
are
in
this
tab
and
all
I
did
was
I,
went
back
to
our
guide
to
scroll
down
here
and
clicked
on.
This
link
open
up
the
contracts
wizard
in
the
new
tab,
and
here
we
are
so
we're
gonna,
give
it
a
name:
I'm,
gonna
call
mine,
Firefly,
nfts
and
the
symbol,
we'll
call
it
FF,
nft
or
whatever
you
can
call
it
whatever
you
want.
We
don't
need
to
put
in
a
base
URI
here
you
can,
if
you
like.
B
So
this
is
where
there's
lots
of
different
ways
to
do:
nfts
lots
of
different
ways
even
to
do
ERC
721.
What
we
are
going
to
do
today
is
we're
going
to
set
a
unique
URI
for
every
token.
Some
contracts
are
set
up,
such
that
there's
a
common
base,
URI
for
all
tokens
and
each
token
it
has
a
unique
index
that
is
appended
to
that.
So
that's
another
way
of
doing
it,
we're
going
to
use
a
unique
URI
for
everyone
and
we'll
set
that
in
the
contract
later
when
check
some
features.
B
Here
we
want
to
make
this
mintable
we're
going
to
let
the
contract
itself
decide
the
IDS,
so
we
don't
have
to
tell
it
what
token
ID
to
Mint
we
just
when
we
call
the
mint
function.
It
will
just
mint
the
next
one
available
and
or,
like
I
said
we're
going
to
turn
on
the
URI
storage
option,
which
allows
us
to
customize
the
URI
per
token
and
I
believe
I'm,
just
going
to
double
check
my
instructions
in
the
guide,
erc721,
mintable,
Auto,
increment,
IDs,
URI
storage
and
a
cool
name.
B
B
Solidity
is
a
easy
to
use,
programming
language
that
you
can
write
and
and
debug
and
test
in
an
IDE,
and
then
it
will
get
compiled
down
to
ethereum
virtual
machine
or
evm
byte
code
and
that's
what
we
actually
deploy
to
the
blockchain
node.
So
the
easiest
way
to
do
this-
and
this
is
what
the
guide
recommends
is-
is
to
just
do
it
all
in
your
browser.
B
Now
you
could,
you
could
hit
download
and
you
could
copy
the
source
code
file
to
like
a
hard
hat
project
or
truffle
project,
and
you
could
compile
it
locally
and
do
all
that
you're
more
than
welcome
to
do
that
if
you
want
to
for
today,
I'm
just
going
to
hit
open
and
remix
I'm
going
to
try
to
do
this,
all
in
my
browser
here
and
we're
going
to
use
remix
to
compile
it
and
so
it'll
just
open
it
up,
because
this
handles
all
the
dependencies
and
everything
like
that.
So
it
really
just
streamlines
stuff.
B
So
I'm
just
going
to
come
over
here
and
hit,
compile
and
I
know.
This
is
probably
pretty
small
on
the
screen.
Okay,
so
great
we've
compiled
it
we're
going
to
come
back
to
this
page
in
just
a
minute,
but
I
wanted
to
point
out
these
two
buttons
right
here,
ABI
and
byte
code
and
then
we'll
copy
it
to
the
clipboard.
So
it
basically
takes
the
compiled
output
and
puts
it
on
your
clipboard.
That's
what
we're
going
to
go
give
to
Firefly
here
in
just
a
minute
all
right.
B
B
It's
going
to
open
the
Swagger
UI
and
automatically
scroll
me
down
to
the
contracts
deploy
endpoint
I'm
going
to
hit.
Try
it
out,
there's
sort
of
some
instructions
here
in
in
the
guide
which
we
can
use.
We
don't
need
necessarily
all
this
is
going
to
list
all
the
different
fields
that
are
possible
to
send
here.
We
don't
need
to
set
all
those
so
I'm
just
going
to
paste
that
in
here
these
are
the
really
the
only
two
that
we
need
to
set
for
today.
B
If
our
contract
had
Constructor
arguments
are
required,
we
could
list
them
out
here,
but
this
one
doesn't
so
I'm
going
to
go
back
to
remix.
It
says
paste
bytecode
here
paste
API
here.
So
that's
what
we're
going
to
do.
I'll
copy
the
byte
code
go
back
to
my
Swagger
UI
and
that's
going
to
be
just
a
big
long,
hex
string.
So
this
is
the
compiled
evm.
Bytecode
that
actually
is
the
program
that
the
blockchain
will
run
so
definition.
This
is
where
we
paste
the
API
here.
B
You
may
notice
these,
these
don't
say
byte
code
and
they
don't
say
ABI
and
the
reason
is
Firefly
works
with
more
than
just
ethereum,
so
we
use
we
sort
of
took
a
step
back
when
we're
naming
things
and
use
more
generic
names,
so
we
call
it
contract.
This
is
the
thing
that
actually
is
the
Smart
contract
and
because
not
all
blockchains
call
the
compiled
thing
bytecode.
They
may
call
it
something
different.
B
Likewise,
not
every
blockchain
uses
a
thing
called
an
ABI.
They
may
call
it
something
different
or
some
blockchains
may
not
even
have
that
concept,
so
we
call
it
contract
and
definition
so
I'm
going
to
copy
the
API
now
and
I'm
going
to
paste
that
here,
it's
important
to
note
this
is
not.
This
should
not
be
wrapped
in
a
string.
This
is
a
big
Json
array
that
I
copied,
and
so
you
want
to
set
when
you
hit
copy.
B
B
So
this,
what
confirm
true
means
is
we'll
actually
block
the
HTTP
request
for
the
the
response
will
block
until
the
message
the
transaction
is
confirmed
on
the
chain
and
we
told
it
that
we
want
four
blocks
of
of
confirmations,
and
so
it's
going
to
wait
for
four
blocks
to
see
that
the
contract
that
it
deployed
is
in
all
of
them
to
make
sure
that
Yep.
This
is
this.
B
The
the
history
of
the
chain
has
not
changed,
and
okay
great
cool
someone
asked
what
the
difference
between
using
Firefly
CLI
FF
deploy
is
and
the
rest
API.
It's
a
great
question.
So
FF
deploy
came
first
and
it
goes.
It
was
before
we
added
this
endpoint
to
Firefly.
So
this
endpoint
is
newer.
It
is
the
more
recommended
way
to
do
it,
because
the
transaction
itself
will
show
up
in
Firefly
we'll
go.
Take
a
look
at
that
in
just
a
second
Firefly.
B
B
B
What
to
do
after
compiling?
Yes,
so
excuse
me,
I
went
I,
went
to
the
guide
and
I
clicked
on
this
link.
This
will
open
up
the
Swagger
UI,
which
has
a
whole
a
list
of
a
whole
bunch
of
different
endpoints
I.
Think
it
automatically
expanded
this
one.
When
you
come
to
any
of
them,
though,
there's
a
button
over
here
that
says:
try
it
out
and
you'll
need
to
click
that,
and
that's
what
makes
this
part
editable.
B
B
B
B
Sorry
that
was
the
input
you
got
to
keep
scrolling
for
the
output
here,
if
I
scroll,
all
the
way
down
here
at
the
bottom
of
the
200
response
body,
we'll
see
down
here,
there's
a
transaction
hash
and
there's
a
contract
address.
This
is
the
important
thing
that
we
will
look
for.
The
other
thing
that
I
want
to
see
is
the
block
number
that
this
was
deployed
in,
so
we
don't
get
that
back
in
the
same
response,
but
we
can
go
look
in
the
Firefly
Explorer
now
and
now.
B
This
refresh
button
has
popped
up
here,
so
there's
new
data
available
so
to
the
question
earlier
of
why?
Why
would
you
use
this
API
instead
of
FF
deploy
is
because
now
we
can
do
this
now.
Firefly
itself
is
aware
that
a
smart
contract
was
deployed,
so
I
can
go.
Look
at
that
contract
deployment,
transaction
I
can
click
on
it
and
then
I
can
click
this
little
button,
which
will
pop
out
this
thing
here
and
I
can
scroll
all
the
way
to
the
bottom.
B
So
so
this
is
a
good
place.
You
can
go!
Look
it
up.
We
can
also
just
go
look
this
up
on
polygon
scan
now.
So
if
we
go
back
and
we
refresh
our
page
for
our
I
still
have
this
polygon
scan
tab
open
if
we
refresh
it
we'll
see
a
transaction
now
from
my
Firefly
node
and
here
was
a
contract
creation,
we
can
oops,
let's
go
into
the
transaction
here
and
we
can
see
like
again
all
the
same
stuff
that
Firefly
was
just
showing
us.
B
B
B
We
haven't
told
Firefly
how
we
want
to
use
this
contract,
though
so
that's
the
next
step
that
we're
gonna
do
we're.
What
we're
the
goal
that
we're
working
toward
is.
We
want
to
tell
Firefly
that
this
is
a
a
token
contract
and
that
this
is
a
an
erc20
token
contract,
but
it
we've
also
customized
it.
So
we
need
to
tell
it
about
some
of
its
custom
ability
looks
like
somebody
in
chat.
Had
an
API
call,
timeout,
maybe
Alex
or
David,
can
can
help.
Look
at
that.
B
Just
check
Discord
here,
okay,
looks
like
all
right,
just
trying
to
keep
an
eye
on
questions
and
make
sure
I'm
not
going
too
far
ahead
of
people
here,
but
it
looks
like
looks
like
we're
doing
well.
So
what
we're
going
to
do
now
is
we're
gonna.
So
like
I
was
explaining
earlier.
Firefly
has
the
concept
of
a
it's:
it's
it's
multi-chain
and
it's
also
not
blockchain
specific.
So
we
want
to
create
and
an
ffi
a
firefly
interface,
which
is
a
generic
way
to
describe
a
contract,
a
smart
contract.
B
B
Interface
generate
API
here
so
I'm,
going
to
click
that
it's
going
to
open
my
Swagger
UI
here
and
I'm
going
to
hit,
try
it
out
and
all
we
need
to
put
here
is
we
just
need
an
input,
ABI,
so
I'm
going
to
paste
that
here
and
then
we're
going
to
go
back
to
remix.
There
was
a
question
about
where
do
I
get
the
API
and
byte
code
from
I
see
in
the
chat,
so
that's
you
get
it
from
remix,
and
it's
this
button
right
here.
B
It's
where
you
get
the
API
this
one
right
here
gives
you
the
about
code.
So
we
needed
that
in
the
previous
step.
I
need
the
API
again,
though,
for
this
step,
so
I'm
gonna,
I'm,
just
going
to
click
that
copy
up
I'm,
going
to
paste
my
API
here
and
I'm
going
to
hit
execute.
So
this
is
just
a
convenience
function.
B
You
can
write
a
you
can
write
an
ffi
by
hand
if
you
want
to,
if
you're
using
hyperledger
fabric,
there
is
not
an
Abi
equivalent
in
fabric,
so
you
you
have
the
ability
to
create
this
ffi
and
Define
it
for
your
contracts,
interface,
but
fortunately
for
ethereum,
which
we're
using
today
there
is
a
a
conversion
available
for
that.
Okay.
So
basically,
this
is
just
a
helper,
so
we're
going
to
copy
this
whole
payload
that
we
get
from
here.
B
Copy
that
and
then
we're
going
to
go
to
the
contracts
interface
endpoint,
which
is
now
we're
actually
going
to
load
the
interface,
the
generated
interface
to
Firefly
again
we'll
hit,
try
it
out
and
then
we'll
paste
this
whole
thing
here.
We
do
need
to
give
it
a
name
and
we
need
to
give
it
a
version.
Those
are
the
only
other
two
mandatory
Fields.
We
call
this
we'll
call
it
Firefly
tokens
I,
don't
think
you
can
put
a
space
in
the
name.
So
just
be
aware
of
that.
A
B
B
B
B
There's
a
question
about
ffis
and
tokens
for
hyperledger
fabric.
In
theory,
tokens
on
fabric
would
work
fantastically
there.
Today
are
not
any
token
connectors
in
existence
for
Firefly
on
fabric,
though
so
that
would
be
a
small
piece
of
software
that
would
need
to
be
written
in
terms
of
how
you
generate
an
ffi
for
fabric.
It's
it's
a
lot
of
Json
writing.
B
A
A
B
A
B
B
B
So
we
have
a
few
pieces
of
information
now
that
we
had
from
multiple
previous
steps,
so
we're
going
to
kind
of
combine
all
those.
So
hopefully
you
remember
where
things
came
from
feel
free
to
scroll
back
up
in
the
guide.
If,
if
you
can't
remember
where
we
saw
certain
things,
but
the
things
we
need
are
the
deployed
contract
address
and
the
block
number
so
the
two
places
we
can
look
up,
those
are
on
polygon
scan.
B
We
can
look
up,
you
can
either
go
to
your
account
and
you
can
look
up
the
the
transactions
and
I
can
see
here.
I've
got
here's
my
contract
address
and
here's
my
block
number
or
you
can
go
to
the
Firefly
Explorer
and
to
find
it
here
that
I
think
the
probably
the
easiest
way
is
to
click
on
this
contract
deployment
transaction
and
then
to
go
here
and
click
this
little
pop
out
icon
and
if
we
scroll
to
the
bottom
all
the
way
to
the
bottom.
B
B
B
If
we're
looking
at
the
output
here
from
our
our
contracts,
interfaces
request
that
we
just
made,
we
need
to
grab
this
interface
ID,
and
what
this
is
going
to
do
is.
This
is
going
to
link
the
token
pool
that
we're
creating
to
this
particular
contract
interface.
This
tells
Firefly
hey.
This
is
an
ERC
20
token,
but
it's
got
some
extra
stuff
on
it
because
we
checked
all
those
little
boxes
in
the
contract.
Wizard
to
add
features
that
are
not
necessarily
in
the
base.
Erc20
spec.
B
B
B
B
B
All
right
we
got
a
202.,
so
that's
the
server
has
accepted
our
request
and
it
is
it's
activating
that
token
pool.
We
should
be
able
to
go
to
the
Firefly
Explorer.
Now
and
now
we
should
see
some
new
stuff
here.
I
can
see
my
one
failure,
because
I
I've
had
that
failed
request,
because
I
had
the
typo
in
it.
B
So
there's
my
token
full
token
pool
that
failed,
but
I
now
I
have
a
token
pool
confirmed
as
well.
So
if
I
click
on
here,
I
can
see
that
I
can
now
also
go
over
to
on
the
left
side.
I
can
go
to
the
tokens.
Dashboard
and
I
can
see
my
FF
nft
pool
here
now.
There's
no
transactions
on
it.
We
haven't
done
anything
with
it,
but
it's
here
and
Firefly
is
Now
tracking.
B
This
token,
from
the
time
that
we
created
it
on
the
blockchain
in
the
original
block
number
that
it
was
deployed
in
so
that
means
any
transaction.
Even
if
I
had
already
minted
some
tokens
in
the
past
say
I'm
pointing
maybe
this.
Maybe
we
want
to
use
Firefly
for
a
a
contract.
That's
already
been
on
a
public
chain
somewhere,
if
you
put
it
in
put
it
point
it
to
the
contract
address
and
the
block
number
that
it
was
deployed
in
it
will
go,
find
all
the
events
that
have
already
happened
on
it.
B
It's
gonna
Firefly
is
going
to
store
those
events
in
its
local
database.
That
was
a
question
that
came
up
earlier,
was
Firefly
put
in
database.
Well,
this
is
a
great
example.
It's
going
to
put
those
events
in
its
database
so
that
you
can
query
them,
and
it
can
also
populate
this
dashboard
here
all
right.
There
was
a
bunch
of
rest
requests.
We
are
through
probably
the
the
most
tedious
and
boring
part
of
the
workshop.
Now
now
we're
going
to
do
some
fun
stuff.
Okay,
now
we're
going
to
upload
some
token
assets.
B
B
For
that
thing,
I'm
going
to
use
this
little
animated,
Firefly,
pixel,
art
you're,
welcome
to
use
whatever
image
you
want
doesn't
even
have
to
be
an
image
could
be
a
document
could
be
a
video
it
could
be
whatever
you
want.
Please
make
sure
you
have
the
the
appropriate
license
and
permission
to
use
it.
B
You
have
my
permission
to
use
my
animated
pixel
art
here,
but
yeah,
so
we're
going
to
upload
this
image,
we're
also
going
to
upload
a
metadata
Json
as
well,
which
will
look
like
this
so
we'll
get
to
that
step
in
just
a
minute
if
you're
not
familiar
with
it
with
the
erc721.
It's
the
thing
that
our
token
will
actually
point
out
is
not
the
image
directly.
It
points
out
a
piece
of
Json,
which
then
points
at
the
image.
B
B
So
we
can
use
the
Swagger
UI
again
to
upload
some
data
as
well
we'll
hit,
try
it
out,
there's
some
instructions
in
the
guide
on
how
to
use
this
endpoint
is
a
little
bit
different
because
we're
going
to
be
uploading
a
file,
so
you
want
to
change
the
the
default
here
is
Json
because
you
can.
You
can
just
post
raw
Json
payloads
here
as
well,
but
we
won't
actually
upload
a
file
so
change
this
to
multi-part
form
data.
B
Open
and
I'm
going
to
execute
okay,
so
right
now
this
just
uploads
the
file
to
Firefly,
and
then
it
gives
me
and
ID
now
there's
lots
of
different
things
you
can
do
with
data
in
Firefly.
Perhaps
I
want
to
share
this
piece
of
data
privately
with
another
Firefly
node
run
by
a
different
organization.
Well,
Firefly
lets
you
do
that.
Perhaps
I
want
to
pin
this
to
the
blockchain
and
send
a
message
to
many
different
Firefly
nodes
that
are
run
by
different
organizations.
Firefly
lets
me
do
that
too.
B
In
my
case,
I
want
to
actually
push
this
piece
of
data
up
to
ipfs
and
share
it
with
the
world.
Firefly
also
lets
me
do
that,
so
it
doesn't
make
an
assumption
about
just
because
you
give
it
a
piece
of
data
automatically
what
you
want
to
do
with
it,
so
handing
the
data
to
Firefly
and
then
telling
it
what
you
want
it
to
do
with
the
data
are
two
separate
steps.
B
So
the
next
step
we're
going
to
do
is
to
upload
it
to
ipfs.
So
you
can
actually
just
so
I'm
going
to
copy
this
ID
you
can
you
can
do
it
in
the
same
tab?
If
you
want
you
can
just
scroll
down
here
to
data
data,
ID
blob,
publish
publishing,
it
will
send
the
data
payload
from
Firefly
itself
to
the
ipfs
node
hit.
Try
it
out,
we
don't.
B
B
This
is
basically
the
ipfs
hash
for
the
data
payload
that
we
uploaded.
So
the
the
guide
talks
about
that.
It's
in
in
the
public
field
at
the
bottom
of
that
request.
So
just
to
recap
what
we
did
there,
we
uploaded
a
gif
to
Firefly,
and
then
we
told
Firefly
hey,
take
this
this
ID
and
push
it
to
ipfs,
and
it
did
that
and
it
gave
us
the
hash
for
that
data
once
it
landed
on
ipfs.
A
B
A
couple
questions
in
the
chat:
is
it
possible
to
use
ERC
4907
an
extension
of
721
instead
of
erc721
off
the
top
of
my
head,
I'm,
not
familiar
with
49.07
but
technically
speaking?
Yes,
as
long
as
a
token
standard
which
I
think
all
of
them
do
have
the
ability
to
Mint
transfer
and
and
to
be
able
to
so
so.
The
the
functionality
that
Firefly
uses
for
tokens
is
mint
transfer
approvals
and
burning
a
token.
B
So
as
long
as
there
are
ways
to
do
that
in
your
token
standard,
which,
as
far
as
I
know
pretty
much
all
of
them,
have
support
that
minimum
capability,
you
could
create
a
token
connector
that
that
works
with
a
different
standard
or
an
extension
on
that
standard.
If
it's
an
extension
of
721,
it
may
just
work
with
the
existing
token
connector.
That's
here
already.
B
If,
if
there's
more
to
that
question
that
I'm
missing,
please,
please
elaborate
I'm
happy
to
try
to
answer
it.
Upgradable,
smart
contracts,
yeah,
that's
that's
a
whole
topic
in
itself.
Firefly
does
support
upgradable
contracts,
I
think
so.
Actually,
the
the
maintainer
who
is
who's
the
resident
expert
on
upgradable
contracts
is
actually
on
vacation
right
now,
but
be
a
great
question
for
him.
I
I'm,
actually
not
sure
off
the
top
of
my
head.
B
B
The
question
about
what
Fields
I
filled
in
for
the
binary
blob
attachment
just
the
ideas
required,
which
would
yes,
so
all
I
did.
There
was
so.
This
is
the
the
where
we
filled
out
here
where
I
uploaded
attached
my
file
here
and
then
I
got
the
ID
right
here.
I
just
copied
that
then
I
scrolled
right
down
here
to
data
data,
ID,
blob,
publish
and
I
pasted
that
data
ID
in
right.
Here
you
don't
need
any
other
fields
in
this
request
body.
It
can
just
be
an
empty
J.
B
So
now
we're
going
to
create
a
metadata
Json
now
the
reason
we
uploaded
the
image
first
is
because
the
metadata
Json
needs
to
actually
reference
that
image.
So
we
needed
to
get
the
ipfs
hash
for
the
image
because
that
needs
to
go
into
our
Json
file.
So,
like
I,
said
earlier,
our
typically
like,
if
you
go,
look
up
an
nft,
that's
for
sale
on
openc,
for
instance,
it
will
the
URI,
for
that
token,
will
point
to
a
metadata
Json
file,
the.
If
you
go
look
up
the
Erp
721.
B
It
says
that
it's
an
optional
thing
that
an
erc721
can
have.
Where
is
so
I'll,
probably
just
scroll
right
past
it
yep
okay,
so
the
metadata
extension
is
optional
for
ERC
721,
but
if
you
do
provide
it,
here's
what
it
looks
like
so
you
can
go
read
up
on
the
the
actual
standard.
If
you
want
to
this,
is
this
is
an
optional
add-on
to
it,
but
pretty
much
anybody
that's
doing
nfts
in
like
a
Marketplace
or
something
like
that.
It's
it!
That's
what
people
do?
B
So
what
I'm
going
to
do
is
I
need
to
create
a
file
with
this
in
it
I
think
I
actually
already
have
one
on
my
disk
already
so
because
I
I
ran
through
this
earlier
when
I,
when
I
set
it
up,
but
you
could
just
you
can
create
a
file
with
contents
like
this.
Just
a
couple
things
to
note,
if
you
did
not
use
the
image
that
I
used,
you
will
have
received
a
different
hash
right
here
and
you
need
to
change
that.
B
So
this
needs
to
be
whatever
whatever
CID.
You
got
from
the
previous
step
here
in
this
field
right
here,
okay,
so
you
can
give
it
whatever
name.
You
want.
Whatever
description,
you
can
give
it
a
different
external
URL
customize.
This,
however,
you
want
this.
Is
this?
Is
your
token
that
you're
minting
you
don't
have
to
use
the
same
thing
that
I
did.
B
This
is
just
provided
as
an
example:
okay,
so
I'm
going
to
go
through
the
same
two
steps
that
I
did
with
the
the
GIF
and
now
I'm
going
to
do
that
with
the
metadata
as
well.
So
here's
my
metadata
hit
open
to
set
that
one
hit,
execute
I,
get
a
different
ID
back
here
and
again,
I'm
just
going
to
scroll
right
down
and
now
tell
it
to
send
that
to
ipfs
hit,
execute
and
boom.
A
B
Think
this
is
due
to
to
my
Nat
configuration
if
I
I
do
for
some
reason
the
GIF
works
fine,
but
the
the
metadata
Json
hasn't,
which
is
a
bummer,
because
I
wanted
to
actually
show
it
to
you
live.
But,
oh,
you
know
what
that's
a
that
was
from
a
different
Workshop.
I
must
have
copied
and
pasted
that
CID
from
something
else
anyway,
so
you
can
yeah
here's!
Here's
the
real
one!
Sorry
about
that.
B
Well,
maybe
maybe
not!
This
is
again
where
I
was
talking
about
the
beginning
of
the
workshop
that
you
know
in
a
production
situation.
You
would
definitely
want
your
ipfs
node
to
be
more
accessible
to
the
public
internet
rather
than
running
on
a
local
Dev
machine.
But
that
is
that's
okay.
It
may
just
take
some
time
it
may
get
there
eventually,
but
we
can.
We
can
keep
moving
on.
We
can
actually
mint
the
data
or
we
can
mint
the
token
and
still
see
the
the
transaction
on
the
public
chain.
B
B
So
these
are
the
only
fields
that
we
need.
So
amount
is
always
one
for
an
nft
If,
This
Were,
an
ERC
20
or
a
fungible
token.
We
could
put
in
any
amount
that
we
wanted
here
if
we
wanted
to
Mint
like
20
of
them
or
a
million
of
them
all
at
once.
We
could
do
that.
Nfts
are
always
because
of
the
way
the
the
transaction
and
the
actual
smart
contract
is
written.
They
are
one
token
per
transaction
and
that's
that's
just
the
way
the
contract
Works.
B
B
B
And
I'll
hit
execute
okay,
and
that
meant
to
the
token
so
now
I
see.
There's
a
few
questions
in
chat.
I
will
come,
I
will
address
those
in
just
a
second.
Now,
if
I
go
back
to
my
Firefly
dashboard,
I
should
see
I
hit
refresh
boom
there.
It
is
it
took
it
a
second
because
it
was
still
waiting
for
that
confirmation
to
come
in
on
the
blockchain.
But
here
it
is
here's
my
mint
event.
B
Here's
my
signing
key
that
minted
it
and
it
was
to
the
same
key.
It
was
a
mint,
so
it
was
from
the
zero
address
and
here's
the
ipfs
URI
that
I
put
in
when
I
minted.
My
token
now,
I
should
also
be
able
to
go
back
to
polygon,
scan
and
I
could
either
look
at
my
wallet
address
and
refresh
this
page
and
I
could
see
that
I've
called
the
safe
mint
function
or
I
should
be
able
to
go
to
the
contract.
Address
and
I
can
see,
because
this
was
a
transaction
on
this
contract.
B
B
B
A
B
B
There's
a
question
about
what
here
is
open
source
versus
what
is
part
of
collido
Stack.
Everything
that
we've
used
today
is
is
completely
open
source.
The
the
only
thing
that
we're,
depending
on
collido,
for
which
you
absolutely
don't
have
to
use
collido's
node
is,
is
the
blockchain
node
itself,
and
that's
just
because
it's
it's
a
lot
of
work
to
stand
up
a
blockchain,
node
and
connect
to
a
public
chain.
B
So
you
know
you're
welcome
to
use
some
other
provider
if
you
want.
There
are
plenty
of
plenty
of
blockchain
node
providers
out
there
that
you
could
connect
this
to.
But
all
the
software
that
we're
running
on
our
machines
is
100
open
source
software.
It's
part
of
the
the
hyperledger
project.
So
that's
that's
really.
What
we're
focusing
on
here.
B
B
B
B
Is
there
a
way
to
do
what
we've
done
in
batch
form,
so
I
mean
I
I
would
recommend
writing
some
code
to
do
what
we've
done.
If
you
want
to
do
a
batch
of
them
and
have
your
application
manage?
What
does
a
batch
mean
for
your
application?
The
like
I
said
the
the
smart
contract
itself
is
going
to
like
each
nft
itself
needs
to
be
a
separate
transaction,
because
that's
the
way
the
standard
works.
B
Each
file
upload
itself
to
ipfs
is
going
to
be
a
discrete
operation
as
well,
and
so
so
there's
lots
of
things
that
are
just
because
of
the
way
the
system
works
are
all
discrete
operations.
The
the
Firefly
SDK
there
is
a
an
SDK
for
node.js.
That
is
it's
it's
a
great.
If
you
want
to
write
an
app
and
node
or
typescript,
you
can
use
that
and
it's
a
great
starting
point.
It
provides
easy
to
use
functions
for
all
of
these
things
that
we're
doing
by
hand.
B
So
today
the
workshop
is
really
to
kind
of
like
go
through
it
and
make
the
make
the
things
by
hand.
Use
use
all
the
apis,
but
obviously
you
wouldn't
want
to
do
all
this
by
hand
in
production,
so
this
is
sort
of
like
you
know,
getting
a
Hands-On
with
the
apis
to
do
by
hand
what
you
would
then
go
write
an
application
to
drive
and
automate
and
build
that
batch
functionality
into.
B
B
B
Other
questions
about
collido,
yeah,
I,
so
I
would
love
to
talk
about.
Collido
I
could
talk
about
collido
all
day
long.
That's
not
the
really
the
focus
of
today's
Workshop.
This
is
a
this
is
a
hyperledger
workshop
and
where,
today,
the
focus
of
the
workshop
is
the
open
source.
Hyperledger
Firefly
project
you
know,
would
love
to
to
get
in
touch.
Collido
does
have
its
own
Discord
server.
If
you
want
to
hop
in
there
and
talk
about
collido,
specific
stuff,
we'd
love
to
chat
with
you
there.
B
So
one
thing
to
note:
when
you,
when
you're
running
in
when
you've
turned
off
multi-party
mode,
the
messages
tab
will
not
show
up
here,
which
I
don't
know
if
that's
what
you're
seeing
but
tokens
and
contracts
Tabs
are
available.
But
messages
is
not
when,
when
you
have
disabled
multi-party
mode
all
right,
so
we
are
we're
almost
at
the
end
of
the
guide
here.
So
at
this
point
we
have
minted
the
token
it
is
available
on
on
a
public
chain.
It's
out
there,
and
so
the
last
step
that
I
could
do
now.
B
B
All
right
so
I've
got
my
metamask
wallet
here.
I've
got
some
stuff
in
here
already
I
have
a
little
bit
of
Matic
some
tokens
from
a
previous
demo
cool.
So
what
I'm
going
to
do
is
I'm
going
to
copy
the
the
address
here
for
my
metamask
account
now,
and
this
could
be,
if
it's
your
Alpha
Wallet
account,
you
can
copy
it
from
your
phone
I.
Just
don't
have
a
great
way
to
screen
share
my
phone
and
and
this
at
the
same
time,
I
I,
know
there's
ways
to
do
that.
B
I,
just
I,
didn't
take
the
time
to
set
that
up
ahead
of
time.
Sorry,
all
right,
so
we
scroll
down
here
now
now
we're
going
to
transfer
the
token
so
we've
minted
it,
but
we
just
minted
it
to
ourselves.
So
this
is
an
example
of
like
as
a
as
someone
who's,
you
know,
defining
or
creating
or
publishing
an
nft
collection.
You
can.
You
can
mint
stuff
ahead
of
time.
B
If
you
want
to
you,
don't
have
to
you,
could
you
do
what's
called
like
a
lazy,
Mint
or
you
know
not
actually
mint
it
until
someone
buys
it?
If
you
want
so
you
don't
have
to
pay
for
the
the
transaction
fee
or
you
know
if
you
needed
to,
for
whatever
application,
You're
Building.
You
need
to
have
just
like
a
pool
of
nfts
that
are
already
there
that
someone
can
then
transfer
you.
Could
you
could
mint
all
these
to
yourself
and
then
have
them
available
to
transfer?
So
that's
that's.
B
What
we're
going
to
do
in
this
example?
Now
we're
going
to
go
to
the
tokens,
slash,
transfers,
endpoint
and
I
would
hit,
try
it
out
and
we
don't
need
all
of
the
fields
here.
So
I'm
just
going
to
paste
this,
we
need
the
sender
address
and
the
recipient
address.
So
sender
is
going
to
be
my
Firefly
address.
Okay,
a
recipient
is
my
metamask
address
I'm
going
to
put
that
in
here
now
and
then,
then
we
need
to
specify
the
token
index.
So
when
we
we
mentioned
the
first
token,
it
was
just
one.
B
We'll
find
out
here,
I
may
have
a
typo
in
the
guide,
or
we
may
have
an
issue
in
the
the
UI
there.
I.
Don't
remember:
I,
don't
remember
if
the
open,
Zeppelin
Auto
index
function
starts
at
one
if
it
starts
at
zero.
I
think
it
starts
at
one
because
I
think
zero
is
sort
of
not
set
but
we'll
find
out
here,
because
if
one
doesn't
exist,
this
transfer
will
not
work
yeah
invalid
token,
ID,
okay,
so
it's
a
typo
in
the
that's
a
typo
in
the
guide.
B
My
apologies,
this
should
say
zero
right
here,
which
that
that's
good,
that's
a
typo
in
the
guide
is
a
lot
easier
to
fix
than
a
bug
in
the
Explorer.
But
okay,
so
we
transferred
token
index
zero
and
if
I
go
look
at
my
Firefly
Explorer
now
I
should
see
in
just
a
second,
it
probably
hasn't
been
confirmed
yet
yep
there.
It
is
now.
This
other
address
has
a
balance
of
one,
and
my
Firefly
address
has
a
balance
of
zero.
B
B
I'm
I'm
c41
metamask
may
need
me
to
tell
so.
Alpha
wallet
will
also
just
automatically
find
the
token,
and
it
shows
up
there.
You
don't
have
to
put
the
token
address
in
I'm,
pretty
sure
which
is
great
I.
Think
metamask
on
the
desktop
does
not
do
that.
So,
if
we
want
metamask
to
know
about
that,
what
we
need
to
do
is.
C
B
B
A
B
B
B
B
Sorry,
I
I,
don't
know
what
I
was
thinking
import
it
and
look.
There's
my
it
says:
I
have
one
of
them
now:
apologies
for
the
the
confusion
there,
but
so
there's
my
token
from
here.
I
could
actually
I
so
I.
Have
this
in
my
in
my
wallet
if
I
wanted
to
I
could
actually
send
it
back
to
Firefly
now
I
could
copy
Firefly's
address
and.
B
B
B
B
Thank
you
all
so
much
for
for
coming
and
just
so
many
people
for
for
staying
this
long.
This
is
a
good
long
Workshop,
where
we
really
got
Hands-On
I'm
happy
to
stay
on
for
as
long
as
people
want
to
for
the
next
hour.
If
you
have
questions
or
want
to
still
work
through,
if
you're
still
trying
to
to
figure
out
parts
of
the
workshop,
but
that
brings
us
to
the
end
of
our
planned
programming.
So
thank
you
so
much.
B
Yeah
so
there's
a
question
about
other
chains:
absolutely
if
a
if
a
blockchain
is
evm
compatible,
it
will
work
today
if
it
is
if
it
uses
some
other
some
other
type
of
blockchain.
That's
not
evm
compatible.
There
Firefly
is
extensible,
so
you
could,
in
theory,
create
a
new
blockchain
connector
for
a
different
type
of
chain
entirely
and
do
all
of
these
same
things.
B
A
B
B
Okay,
so
the
to
the
person
who
who
dm'd
me
about
the
the
transfer
is
to
the
transfers
from
the
incorrect
owner.
So
it's
possible
you've
flipped
the
two
in
the
from
address
there.
It's
also
possible
the
from
address,
isn't
actually
the
right
one
or
perhaps
you
may
not
have
actually
minted
that
token.
So
a
couple
things
to
check
on
there.
B
Advice
for
unchain
data
analytics
using
graph
databases,
that's
a
great
question,
I'm,
not
an
expert
on
that.
I.
Think
that
is
it's
you
know.
On-Chain
analytics
is
certainly
an
interesting
area.
You
could
certainly
build
something
that
can
can
create
an
on-chain
analytics
user
experience
with
firefly
fireflies
a
thing
that
you
could
build
that
with,
but
it
it's
not
necessarily
meant
to
be
an
analytics
engine
itself,
I'm
sure
there
are
also
other
great
open
source
projects
out
there
that
specialize
in
that
particular
thing
as
well.
B
Cool
I'm
going
to
check
Discord
here.
Oh
there's,
a
question
about
showing
metamask
browser
while
to
show
the
nft
yeah
so
basically
metamask
browser
the
browser
wallet
is
really
Bare
Bones
in
the
features
that
it
has.
This
is
why
I
recommend
you
use
Alpha
wallet.
That's
it's!
It's
a
lot
better
user
experience,
but
basically
I
just
went
here.
It
says:
don't
see
your
tokens
import,
your
tokens
right
here
and
then
I
put
the
token
contract
address
in
here.
B
B
That's
where
I
got
that
that's
how
I
got
metamask
to
show
that
there
any
smart
contract
templates
by
business
domain.
Yes,
I'm
sure
there
are
some
out
there.
We
have
found
think
typically
many
business,
many
business
cases
can
can
actually
just
leverage.
Basically
what
we
use
today,
a
a
token
contract.
So
Firefly
comes
with
with
an
erc20
token
contract
and
ERC
721
token
contract
that
allow
you
to
associate
data
with
a
transfer
which
is
a
really
useful
function.
B
B
What,
if
you
want
to
use
your
own
ipfs
node?
Where
should
I
set
up
the
private
ipfs
address
so
I'm
trying
to
exactly
understand
what
that
question
is
getting
at
so
so?
Yes,
we,
we
actually
are
using
our
own
ipfs
node
right
now,
it's
just
running
in
Docker,
I!
Guess.
If
you're
saying
you
already
have
one
running
where,
where
do
you
configure
that
that
goes
into
the
the
Firefly
core
config
file?
B
And
it's
just
the
you
need
to
give
it
the
the
IP
import
number
for
the
ipfs,
API
and
Gateway,
and
that
goes
in
the
Firefly
core
config
file.
I
think
is
what
you're
asking
there
in
terms
of
identity
a
workshop.
Yes,
there
we
we
should
definitely
do
a
workshop
about
identity
and
Firefly.
That's
a
whole!
B
B
I'm
gonna
say
there
was
a
question:
it's
minted
several
images.
On
the
same
token,
how
does
this
differ
from
the
mid
team?
We
did
today,
I'm,
not
sure,
I
understand
what
that
means,
if
you've
minted
several
tokens
that
all
point
to
the
same
image
or
if
you've
minted
one
token
that
points
to
multiple
images
and
if,
if
it's,
the
latter
I'm,
not
sure
how
you
did
that
I
guess
how
it
compares
to
what
we
did
today.
We
we
uploaded
one
image,
and
we
pointed
one
token
to
that.
B
You
could,
if
you
wanted
to
so
like
a
lot
of
nft
collections
will
have.
You
may
have
like,
like
we
minted
a
one
of
one
today,
so
there's
only
one
on
this
smart
contract
there's
only
one
animated,
Firefly,
pixel
art,
you
could
say
well,
these
these
ones
are
rare,
so
there's
only
five
of
them
and
you
could
point
five
different
nfts
to
the
same
metadata,
Json
or
you
could
say,
they're
common
there's.
You
know
20
000
of
them
and
you
could
mint
20,
000
tokens
and
and
point
them
all
the
same
thing.
B
Someone
said
they
got
the
nft
to
their
metamask
wallet.
Is
there
an
easy
way
to
transfer
it
to
the
alpha
wallet?
It
probably
I,
I'm,
not
sure
why
the
button
to
transfer
it
in
metamask
didn't
light
up
honestly
I.
Think
metamask
is
not
the
browser.
Metamask
is
just
not
the
greatest.
It
doesn't
have
very
many
features.
There
is
probably
you
could.
Probably,
if
you
really
needed
to
you,
can
export
your
private
key
from
metamask
and
put
it
in
Alpha
wallet
and
then
it
would
show
up
there.
B
B
B
So
so
it
has
a
history
of
the
ownership
and
it
points
to
some
piece
of
data
that
may
live
off
the
blockchain
somewhere
and
when
you
think
about
it
from
that
aspect,
there
are
lots
of
really
good
business
cases
that
you
can
use
for
that,
and
so
you
know,
one
of
the
other
challenges
is
in
the
public
space.
Every
time
you
transfer
that
nft
or
or
perform
a
transaction
with
it.
B
You
could
transfer
those
freely
between
members
of
an
organization
you
even
using
Firefly.
You
could
potentially
Bridge
those
nfts
to
a
public
chain
in
certain
cases
when
that
was
necessary.
So
there's
a
lot
of
different
Enterprise
applications
to
the
things
that
we've
shown
here
today,
but
you
know
most
people
initially
think
of
an
nft
as
just
an
image.
B
Well,
it's
it's
actually
I
I
would
say
the
the
common
use
cases
for
nfts
that
we've
seen
on
the
internet
today
are
just
the
tip
of
the
iceberg
in
terms
of
what
is
possible
with
the
technology
itself.
So
there's
there's
plenty
of
things
that
are
I,
think
a
more
useful
business
value
that
can
be
done
with
an
nft.
B
Some
other
questions
here
about
encrypting
or
decrypting
attachments
posts
to
ipfs.
Potentially,
yes,
I'm
sure
there
I
know
there
are
some
projects
out
there
that
have
have
done
things
with
that.
It's
not
in
the
scope
of
what
Firefly
does
today,
but
it's
it's
very
possible
that
you
can
plug
another
tool
into
that
and
use
it
for
something
that
is
more
important
than
a
silly
picture.
B
It's
it's
also
probably
worth
thinking
through.
Like
is
you
know,
is:
is
the
data
too
sensitive
that
it
shouldn't
even
be
shared,
even
in
an
encrypted
form
publicly
like
that
or
within
a
multi-party
network?
If
it's
too
sensitive
to
be
shared
with
all
of
the
members
of
the
multi-party
network,
perhaps
sending
it
directly?
Peer-To-Peer
might
be
better
while
still
using
blockchain
as
the
the
distributed
Ledger
and
proof
of
that
transaction.
That
happened,
while
keeping
the
payload
itself
completely
private
yeah
someone.
C
B
B
You
could
so
there's
one
plug-in
today
for
shared
storage,
but
you
know
if
you
read
through
the
code
in
Firefly,
you
don't
see
a
lot
about
ipfs,
it's
really.
We
we
call
it
a
a
shared
storage
system
and
there's
one
implementation
of
that
plug-in
today
and
it
happens
to
be
ipfs,
but
you
could
most
definitely
create
a
another.
Shared
storage
plugin
that
leverages
S3
or
some
other
sort
of
distributed
file,
share,
system
and
and
use
that
as
well.
B
A
B
So
so
this
is
also
something
I've
seen
in
some
nfts,
where
the
metadata
Json
goes
on
ipfs,
but
it
instead
of
that
ipfs
resource
pointing
to
another
ipfs
resource,
the
metadata
points
to
S3,
and
you
could
most
definitely
do
that.
I
chose
not
to
do
that,
because
I
wanted
both
the
image
and
the
metadata
to
be
immutable
and
distributed
so
I
chose
ipfs
for
both
of
them.
B
There's
a
question
about
in
in
Discord
about
RPC,
endpoints
yeah,
so
chain
list
lists
nodes
that
are
its
status
list
nodes
that
are
up
and
available.
That
doesn't
necessarily
mean
that
they
support
all
of
the
functions
that
the
the
Firefly
and
the
evm
blockchain
connector
need
to
function.
If
you
look
at
the
evm
connect,
readme
lists
the
the
different
Json
RPC
functions
that
it
needs
to
to
actually
run.
Not
all
free
public
nodes
support
all
these
functions.
B
This
is
why
we
ran
one
today
that
that
I
know
100
supports
all
these
functions
because
we're
running
it.
But
if
you
just
do
a
search
for
for
free
public
RPC
nodes,
it
may
be
up
and
it
may
support
some
of
these.
It
may
support
all
of
them.
That's
great
you're
welcome
to
use
it,
but
it's
sort
of
you
just
have
to
have
to
test
it
and
see
if
it
actually
works,
because
not
all
of
them
expose
all
these
functions,
because
some
of
them
can
be
more
resource
intensive
than
others.
B
A
B
B
B
B
Yay
great
job,
let's
see,
there's
a
question
in
chat
about
how
we
can
store
on
on
S3
and
maintain
immutability
I.
Don't
know,
that's
why
I
didn't
use
S3.
There
may
be
ways
to
do
it,
but
that's
probably
needs
some
really
deep
architectural
investigation
into
how
S3
Works
itself
I
I,
don't
know
I,
don't
know
if
that's
even
possible.
B
B
If,
hopefully,
this
Workshop
was
was
useful
and
informative,
the
the
guide
will
stay
up
there.
You're
welcome
to
to
plug
in
whatever
RPC
node
you
want
to.
After
today,
I'll
update
the
guide
to
have
a
note
about
that,
but
I
just
really
appreciate
all
the
time
that
everyone
put
into
today's
workshop
and
for
taking
the
couple
hours
here
to
to
sit
with
me
and
and
use
Firefly
and
get
Hands-On
yeah
thanks
for
for
joining
and
hope.
You
have
a
great
rest
of
your
day,
thanks
Nico
thanks
everyone.