►
From YouTube: Spotlight: MIP-721 | Community Conversations
Description
Mina Protocol – the world's lightest blockchain
A
That's-
and
that
is
why
we're
here
today,
because
we
want
to
contribute
to
to
that
new
evolving
ecosystem
of
Decay
tanks
and
especially
to
the
nft
standards
and
ft
ecosystems,
because
this
is
where
we
are
good.
At
my
opinion,
we
are
pretty
good
experience
with
nfts
and
yeah.
We
want
to
bring
that
experience
to
vacations
to
make
a
new
generation
of
FTS
possible
and
that's
why
I'm
here
today.
B
A
A
It
was
not
really
the
first
implementation
of
nfts
on
the
period
about
this
was
the
first
standard
for
the
first
widely
adapted
standard
of
nfts
ethereum,
and
what
I
like
about
it
is
that
it's
pretty
bare
bone
concentrates
on
tracking
of
ownership
and
token
uis
on
chain,
and
you
also
have
some
a
mechanism
called
approvals.
Onshine,
where
you
can
get
approved,
give
approval
to
another
contract,
as
a
user
can
give
approval
to
another
contract
that
he
manages
your
FTS
so
that
that
contract
can
then
transfer.
A
You
have
keys,
and
this
is
I
mean
this
is
a
huge
enabler
for
marketplaces
and
all
other
sorts
of
nft
10
for
gaps,
also
nft
lending
or
fertilization.
All
these
protocols
make
use
of
the
approvals,
but
ESC
721
is
pretty
much
or
pretty
much
only
defines
this
free
core
functionalities,
tracking
ownership,
having
a
token
UI
and
having
approvers,
and
this
makes
so
simple
on
the
one
hand,
and
enables
such
a
huge,
huge
ecosystem
to
integrate
with
that
standard.
A
But
it's
also
easily
extendable,
because
because
the
standard
also
doesn't
Define
too
much
functionality
which
you
have
to
have-
or
you
are
I'm
not
allowed
to
that
yeah.
This
is
pretty
pretty
cool
about
UFC
721.
In
my
opinion,
and
this
is
why
you
propose
that
the
MRP
721,
the
standards
for
Amina,
is
or
relies
on
the
same
guiding
principles
as
es6721
and
also
has
a
pretty
similar
interface,
because
I
mean
most
devs.
A
Number
three
today
are
familiar
with
ESC
721
in
my
opinion,
and
has
to
build
something
with
it,
and
this
also
enables
all
these
steps
to
come
to
Mina
and
build
with
our
MRP
721
standard,
because
they're
familiar
with
the
guiding
principles
and
they
are
familiar
with
the
approval
pattern.
They
are
also
familiar
with
the
interfaces.
B
A
A
Eight
Fields
with
32
bytes-
and
this
is
obviously
not
enough
to
track
the
whole
state
of
one
LSG
collection,
because
I
mean
we
have
thousands
and
even
many
more
nfts
and
one
of
the
key
collection
and
eight
years
are
not
enough
to
store
the
information
or
to
store
the
metrics
from
owner
through
token
ID
for
10
000
people.
Obviously,
so
this
is
one
of
the
first
challenges,
or
this
is
the
main
challenge
in
my
opinion,
that
the
state
of
one
Decay
app
on
Mina
is
pretty
Limited.
C
A
A
So
one
information
piece
about
the
owners
want
to
token
ID,
so
remote
assets
all
the
time,
and
if
we
have
high
throughput
through
a
collection,
then
the
market
would
updates
all
the
time
and
a
lot
of
transactions
would
actually
be
invalid
because
the
work
route
has
changed
while
the
user
made
the
transaction,
and
so,
for
example.
Yes,
we
all
have
seen
the
high
commands
on
different
chains
in
the
last
years,
and
even
now,
when
nfts
are
down
pretty
bad
and
I
mean
most
NLP
collections.
A
B
Yeah
I
I
think
you're
touching
on
some
really
interesting
things
that
I'm
sure
a
lot
of
people
have
opinions
on
too,
particularly
on
train
State
versus
of
Trans
State
of
trend,
debt
management.
Things
like
that
perhaps
now
might
be
a
sort
of
a
nice
time
to
give
a
bit
of
an
overview
of
of
your
solution
and
how
you
sort
of
tackle
some
of
these
challenges.
C
A
C
A
A
So
how
many
nfps
one
address
owned
is
in
that
collection
and
also
the
approval
for
all
root.
We
can
deep
dive
a
little
bit
more
on
that
later,
and
this
is
basically
the
information
to
which
other
accounts.
This
account
has
given
approval
for
all
its
nfts,
and
then
we
have
some
other
nft
account,
which
is
also
a
Decay
app
which
Stores
the
owner
address,
which
owner
does
currently
owned.
This
token
ID
the
token
ID,
obviously
and
then
also
one
field
for
approval
so
yeah.
A
This
is
our
idea
that
we
kind
of
produce
one
Decay,
app,
nft
and
also
per
owner,
and
this
might
seem
I
mean
it
looks
a
bit
weird.
I
think
that
we
produce
so
many
smart
contracts
per
collection,
I
mean
potentially
10
000
contracts
per
collection,
but,
for
example,
on
zulana.
That's
also
pretty
common
that
you
have
separation
and
different
accounts.
E
A
Yeah
but
I
realized
that,
but
it's
not
really
right
because
I've
seen
that
if
you
use
the
native
total
implementation
of
Mina,
that
would
cost
one
minute
as
well.
But
it's
I
mean
this
is
the
alternative
that
we
use
the
native
tool.
Documentation
yeah
in
general
I
realized
that
there
is
a
lot
of
cost
involved
and
I
think
there's
a
lot
of
Improvement
potential.
A
A
To
all
the
nfts,
but
from
one
account
to
their
range
that
they're
minted.
So
if
somebody
for
example,
means
100
of
our
nfts-
and
we
just
says:
okay,
the
information
that
this
owner
minted
the
range
from
100
to
200
on
the
token
IDs.
So
we
already
reduced
the
cost
by
100
excellent
case,
because
we
only
deploy
one
contract
or
one
NXT
account.
Instead
of
hundreds
and
this
pretty
much
solved
because
admined,
and
if
that
collection
then
gets
more
and
more
traction,
then
the
cost
is
okay,
in
my
opinion,
so
yeah.
This
is.
A
This
is
something
that
we
thought
about
regard
to
one
possibility
they
could
take
to
reduce
the
cost
of
deploying
all
the
contracts
that
you
instead
only
save.
The
token
ranges
that
somebody
mentioned
because
I
mean,
if
you
look
at
the
nft
system
realistically,
that's
so
that
most
people
just
meant
10
to
100
nfts
of
a
collection
in
the
beginning
and
either
that
collection
gets
more
and
more
interest
and
then
the
token
get
distributed
or
it
just
doesn't
get
much
interest
and
but
then
also
not
much
minting
fees.
F
A
Yeah,
what
I
think
you
mean
is
esc-1155.
It's
kind
of
a
a
lot
of
people
saw
it
as
the
Next
Generation
ESC
721
and
the
the
esc-1155
Implement,
something
that
a
lot
of
people
call
semi-funk
or
semi-fungible
tokens,
because,
instead
of
having
is
each
token
individually,
you
have
token
classes.
For
example,
it's
perfect
for
games.
Imagine
that
it
has
a
game
where
you
can
own
resources,
for
example
a
gold
or
I
mean,
and
let's
say,
gold
and
silver
and
with
the
ESU
721.
A
If
you
own
five
pieces
of
gold
and
five
pieces
of
silver,
then
you
have
10
nfts,
and
that
is
of
course
pretty
costly.
At
least
on
ethereum
on
Twitter
is
pretty
costly,
so
people
thought
about
okay.
How
can
we
change
that
situation
and
build
a
better
standard
for
games
and
then
the
esc-1155
you
can
mint
a
user
five
pieces
of
gold,
five
pieces
of
silver
and
just
and
behind
the
scene
is
just
the
balance
change.
A
So
you
don't
need
somebody
nft,
but
you
just
change
this
balance,
and
this
is
it's
all
about
gas,
optimization
and
yeah.
We
could
easily
build
that
for
mina
as
well,
but
for
the
most
popular
nft
applications
of
today,
which
is
Art
and
PCs
and
I,
would
say,
rare
gate,
game
items
so
not
see
my
phone
game
items.
A
That
would
be
perfect
in
my
opinion.
So
if
we
have
solutions
for
that,
I'm
I'm
super
open
for
it,
because
I
mean
behind
the
interface
we
can
do
whatever
we
want
actually,
and
also
the
interface
is,
of
course
flexible.
Might
it's
just
my
opinion
that
we
shouldn't
and
differ
Too
Much
from
the
most
successful
interface
or
the
most
common
interface
which
existence
because
I
mean
most
devs
are
familiar
with
it?
Most
Builders
are
familiar
with
it
and
there's
a
lot
of
there's
really
a
lot
of
nft
infrastructure
on
on
ethereum.
B
Awesome
I
have
one
more
question
and
then
we
can
sort
of
open
it
up
for
further
discussion
and
ideas
that
others
have,
but
specifically
with
the
standard
that
you're
working
on
what
sort
of
community
feedback?
What
feedback
do
you
need
from
this
group?
What
questions
are
you
looking
for?
What
collaborations
do
you
need
to
help
run
a
standard
to
Market.
A
Yeah,
that's
cool,
so
I
mean
it's
obvious.
I
built
a
lot
in
the
ethereum
ecosystem,
one
both
of
us
and
me
we
never
really
put
in
the
ethereum
ecosystem
in
the
last
years,
so
we
don't
have
too
much
domain-specific
experience
with
Mina.
So
whatever
concerns
you
have
with
that
implementation
in
regards
to
like
issue.
A
And
if
you
have
any
good
ideas,
how
we
can
like
better
implement
it
also
throw
it
at
us
yeah,
and
so
this
is
what
I
think
help
us
a
lot,
but
also,
if
you
are
somebody
else
or
somebody
who
wants
to
build
something
else
in
the
FP
ecosystem,
not
the
standard.
For
example,
a
Marketplace
or
I
mean
a
platform
where
people
can
easily
mint
nfts,
also
through
your
requirements
at
us.
A
A
A
E
Could
you
maybe
walk
us
through
the
technical
details
of
how
this
would
work
like
end
to
end?
So,
let's
imagine
that
I'm,
an
artist
deploying
an
ft
collection.
So
on
a
technical
level?
How
do
you
see
this
working
from
an
end-to-end
from
meeting
the
collection
to
initial
distribution
and
then
the
nfts
themselves
being
sold
like
a
third
party
Marketplace,
let's
say.
A
It's
just
not
open
for
a
large
part
of
the
lifestyle
key
contract.
So
that's
the
Supreme.
Why
it's
not
part
of
the
standard
and
usually
within
the
nft
or
within
that
admin
function?
You
also
enforce
a
price,
and
maybe
you
have
a
white
list
which
is
often
I
would
say,
Mercury
root,
based
so
that
only
certain
people
can
submit
certain
amounts.
A
This
is
pretty
pretty
much
a
standard
way:
2017
collection,
marketing
and
after
after
the
event,
all
people
have
the
nfts,
which,
on
a
technical
level,
only
means
that
we
in
some
way
store
the
information
that
certain
Networks
has
a
certain
attitude
and
that
nft
has
a
token
UI,
which
is
also
stored
and
okay,
it's
missing
here.
Just
here,
usually
you
have
on
it
it's
okay.
The
base
UI
is
missing,
usually
on
collection
level.
You
have
a
base
UI
and.
A
That
plays
URI,
you
just
attend
the
token
ID,
and
this
then
you
have
an
URL,
and
if
you
on
that,
behind
that
URL,
you
have
metadata-
and
this
metadata,
for
example,
has
a
description
but
also
an
image.
So
in
the
in
the
case
of
the
artist,
the
image
is
pretty
important,
so
we
met
from
a
token
ID
to
a
UI
and
behind
that
URI
or
the
in
the
imagery
centimeter
that
I've
stored.
And
then
you
need
the
next
part
of
the
nft
ecosystem,
namely
platforms
that
we
can.
A
C
A
So
we
need
other
actors
in
The
NFP
ecosystem
who
provide
these
Lounge
pads,
where
the
artist
can
also
production,
but
yeah
I
mean
this
is
nothing
that
if
you
have
the
solid
NXT
standard,
this
is
nothing
that
is
really
really
complex
for
good
Builders
I
mean
it
happens
on
ethereum
all
the
time
and
I've
done
it
myself
pretty
often
and
yeah.
It's
just
just
I
think
just
nft
stand
is
missing
in
the
moment.
For
that.
E
A
Sir,
so
yeah
this
is
I
mean
this
is
not
the
state
we're
at
in
the
moment.
So
far,
we
only
have
done
this
proposal
about
the
interface
and
rough
overview
of
how
we
I
think
would
be
able
to
implement
it,
but
we
wanted
to
wait
for
this
community
call
first
to
gather
more
feedback
and
then
start
the
example.
Implementation
and
all
this
will
happen
in
public.
A
F
A
Is
so
the
current
idea
is
to
store
as
much
possible
as
much
as
possible
onshine
regarding
the
ownership,
because,
because
of
the
race
conditions,
I
explained
earlier
that
we
have
with
the
with
with
the
information
about
the
ownership.
But,
for
example,
one
thing
that
would
be
in
the
user's
responsibility
to
store
off
chain
is
the
route
about
or
the
information
about,
the
approvals
and
they
have
given
on
ownership
level
to
other
accounts
and
because
this
can
also
bloat
up
a
lot.
A
In
my
opinion,
for
example,
I
remember
times
when
we
had
like
I,
don't
know
a
few
dozen
smaller
Marketplace
on
ethereum
different
Landing
protocols
and
different
fractionalization
platforms.
So
it
was
kind
of
common
that
the
US
user
had
I,
don't
know
20
30
40
approval
for
all
approvals,
for
all
your
nfps
within
one
collection
given
to
other
accounts
and
I
mean
the
cool
thing
about
this.
Approval,
for
all
information
is
that
race
conditions
are
pretty
unlikely,
because
only
the
user,
or
only
the
owner
of
these
nfts
can
influence
that
route
and
I
mean.
A
I
mean
it's
other,
it's
different
for
the
for
the
ownership,
information
about
all
nfts
for
different
users,
submit
different
transactions
for
different
transfers
and
all
these
transactions
complete
with
each
other
on
update
the
Mercury
root
for
the
hypothetical
Mercury
that
stores
all
the
ownership
data.
But
in
the
approved
for
All
Case
yeah,
we
would
require
to
require
the
user
to
stores
of
chain
and
yeah.
My
opinions
also
that's
also.
B
I
have
a
question:
how
do
wallets
discover
ownership
of
nfts
I
know
sort
of
metamask
only
recently
have
come
out
with
features
that
enable
people
to
discover
nfts
that
they
are,
for
example,
or
in
the
past.
We
would
all
go
to
somewhere
like
open
C,
to
discover
what
nfts
we
owned
or
what
nfts
were
minted
To
Us
by
various
projects
for
some
reason
or
other?
A
Yeah,
that's
a
that's
a
pretty
good
question,
a
pretty
interesting
one,
because
I
mean
also
on
ethereum,
like
or
other
nft
people
try
to
minimize
State
as
much
as
possible.
So
let
them
that
information
that
which
nfts
also
with
on
within
one
collection,
one
what
it
holds
that
is
not
really
stored,
at
least
not
the
index
about
it.
But
instead
events
are
emitted
and
then
it's
on
in
on
then
the
logic
for
the
indexing
happens
off
chain.
A
So
there
are
people
like,
for
example,
open,
C
and
brother
and
all
these
marketplaces.
They
collect
all
transfer
events
that
are
thrown
by
in
a
free
contract
on
Shane
and
build
up
indexes,
and
these
indexes
will
be
and
container
mapping
which
accounts
or
which
address
is
called
which
nfts
in
which
collections.
B
A
D
A
Yeah
so
my
opinion,
it
also
it
makes
it
easier
for
a
lot
of
developers
to
understand
the
standard
to
build
with
it,
because
I
mean
most
enough.
People
today
are
familiar
with
erc721
and
it
just
makes
sense
to
give
them
a
familiar
interface
and
also
the
approval
pattern,
and
so
on,
because
I
mean
that
this
is
what
these
people
are
used
to
build
with,
and
why
make
it
hard
for
them
to
build
with
a
super
Advanced
standard
and
I
mean
two
years
ago.
A
I
also
thought
differently
about
that,
because
esc-721
I
mean
there
are
some
some
things
and
some
methods
that
maybe
don't
make
too
much
sense
with
the
experiences
we
had
today
and
also
the
approval
pattern.
This
is
something
a
lot
of
people,
don't
sometimes
don't
really
get
and
there's
disadvantages
and
so
on.
But
then
sunana
came
and
implemented
it
completely
different
standard
and
at
the
startup,
where
which
I
co-founded
and
some
of
our
developers
had
to
build
with
the
Solano
standard,
and
it
was
just
awful
experience
to
send
because
you
have
to
learn
a
new
standard.
A
You
have
to
learn
a
new
language
and
so
on
and
just
makes
it
complicated
and
hard
to
to
implement
the
scanner
for
for
Builders
and
I
mean.
This
is
the
last
thing
that
we
want.
We
want
to
it's
like
officer
that
it's
easy
for
Builders
to
come
and
to
come
to
Mina
and
build
the
NSP
applications,
and
this
is
one
point
in
my
opinion-
make
it
easier
for
developers
and
Builders
to
come
to
me
now,
and
the
other
point
is
that
also
security
aspect.
I
mean
ESC.
A
It's
just
a
proven
concept
and
I
think
why
not
sticking
to
it
as
long
as
we
don't
see
massive
upside
by
changing
it
and
I
didn't
see
it
so
far.
Actually
I
mean
I'm
completely
open
to
it
to
adapting
the
the
standard
and
To
Go
in
different
directions.
If
some
of
you
has
a
good
idea
which
brings
massive
upside
but
yeah
foreign.
H
Yeah
hi
there
sorry,
yes,
there
has
been
a
discussion
in
in
the
Discord
channel
with
a
question
on
the
on
the
on
the
ctec
CK
apps
questions
channel,
which
is
called
custom
tokens
for
nfts
and
Gregor
proposed
some
quite
interesting
idea,
which
is
using
actions
to
store
nfts.
Mainly
actions
have
quite
an
interesting
property
in
that
they
are
not
limited
to
to
the
same
limitations
that
can
that
that
to
the
eight
fields
are
gonna,
an
account
have
so.
Actions
can
have
quite
more
information
and
also
actions.
H
All
all
actions
of
a
given
contract
can
be
accessible
through
through
this
contract
to
this
contract,
using
a
reducer
or
using
the
the
Clash
of
of
the
action
tools,
and
that
is
stored
in
in
the
in
the
archives.
So
you
will
have
also
access
to
a
long
set
of
actions.
I
think
the
ideas
are
quite
interesting.
H
I
cannot
speak
for
Gregor
because
he
he
knows
much
more
than
Mia,
and
it
was
his
idea,
but
I
think
it's
quite
an
interesting
way
of
storing
additional
information
that
will
not
have
the
limitation
that
an
account
has
Matthew
also
has
been
in
this
in
in
this
discussion
too.
So
he
may
explain
a
little
more
about
this
and
also
brush
world
right.
Sorry
for
for
I
cannot
pronounce
it
I
think
it's
in
this
chat
is
in
the
in
this
conversation.
H
Two
has
been
talking
about
this
and
there
are
quite
interesting
properties
in
this
in
this
idea
that
Gregor
had
so
I
think
it
you
might.
You
might
at
least
look
at
this
as
a
different
weight
of
storing
state
or
storing
additional
information
for
nfts,
because
what
you're
proposing
has
some
additional
problems.
If
you
have
one
account
per
nft,
it's
not
the
pro.
H
The
only
problem
is
not
the
the
the
minor
value
you
have
to
provide
one
one
mean
a
per
account,
but
also
that
creating
an
account
takes
a
long
time.
I
have
been
experienced
that
myself,
because
in
our
credential
protocol
we
create
one
credential
One
account
per
credential
and
creating
a
credential
takes
between
three
to
ten
minutes
till
the
account
is
ready.
So
that
may
be
a
big
problem
when
you
are
creating
lots
of
nfts.
A
D
B
B
B
H
D
H
H
It's
it's
not
a
magical
solution
anyway,
but
but
I
think
it
has
some
interesting
features
that
that
may
be
available
or
or
even
having
a
combination
of
of
of
of
these
things,
what
what
they
fit,
proposing
and
and
also
but
registering
transfers
or
nft
state
changes
by
using
actions
can
also
be
something
interesting
too.
Okay,
that's
all
with
me.
Thank
you
very
much.
I
I
posted
the
link
there.
Okay,
in
the
in
the
we.
B
B
G
Hey
I,
don't
have
a
specific
file
on
this
I.
Just
I
want
to
thank
you
and-
and
we
for
setting
this
up
just
because
I
think
it's
the
first
time
that
we're
doing
this
and
I
think
it's
really
important
that
these
type
of
discussions
happen
before
we
get
to
the
design
phase.
I
just
think
it's
a
lot
more
efficient
and
you
can
get
a
lot
more
people
on
board
earlier
on
so
I
know
it's
not
an
easy
thing
to
do,
but
I
think
it's
really
important
and
wanted
to
say
thanks.
G
B
Personally,
I
think
I
have
one
more
question
to
ease
up
a
little
bit
more
time,
but
I
think
one
interesting
topic
that
you're
touching
on
in
your
proposal.
That
is
not
hidden
away,
it's
quite
obvious,
but
I
think
it
needs
to
be
stated.
But
these
approaches
on
a
much
larger
topic
of
composability.
So
with
your
sort
of
separation
of
State
across
two
contracts,
inherently
the
topic
is
composability
of
of
smart
contracts
on
Mina
and
I.
Think
that's
a
really
interesting
topic,
not
just
for
an
nft
project.
B
It's
a
standalone
product,
but
also
as
nft
project
used
across
the
ecosystem
for
many
different
things.
So
I
think
that's
a
really
important
topic
and
we
should
be
proud
of
of
that
being
an
idea,
because
it's
incredibly
useful
so
yeah
and
we've
got
sort
of
eight
minutes
left.
If
anybody
has
any
questions
feel
free
to
go
now.
Otherwise
we
can.
We
can
start
wrapping
up
early.