►
Description
Resources
-----------------
Slides: https://docsend.com/view/5j2vypm283qei8qe
EIP: https://eips.ethereum.org/EIPS/eip-6672
Discussion: https://ethereum-magicians.org/t/eip-6672-multi-redeemable-nfts/13276
PEEPanEIP Playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F
ERC Playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqXee9EMQDIEz2CslTnsW0K
Follow at Twitter
----------------------------
BoYu Chu @chuboyu_ | Pooja Ranjan @poojaranjan19
Topics covered
-------------------------
0:00 - Promo
0:29 - Topic introduction
1:10 - Guest Introduction
1:44 - Presentation
1:55 - Team
2:34 - Motivation
4:08 - Problem statement
4:40 - ERC-6672 specs
6:30 - ERC6672 is not defining
8:30 - How do we handle redeem?
9:26 - What is missing?
11:02 - Rethink NFT properties - Intrinsic & Extrinsic properties
14:54 - Middleware between web2 and web3
15:18 - ERC6672 specification
16:47 - Benefits
18:09 - Usage guidelines
18:48 - Key consideration & guidelines
23:49 - Web3 Commerce
30:02 - What about non-6672 NFTs?
31:05 - The journey of EIP
33:15 - Thoughts
34:05 - Reach out the team
34:25 - End of presentation
35:00 - Is it soulbound or transferable?
38:30 - Project implementing this ERC
40:90 - Security consideration
42:32 - EIP documentation
Contact Ethereum Cat Herders
---------------------------------------------------
Discord: https://discord.io/ethereumcatherders
Twitter: https://twitter.com/EthCatHerders
Medium: https://medium.com/ethereum-cat-herders
Website: https://www.ethereumcatherders.com/
B
Welcome
to
pee
paneer
episode,
108
I'm,
your
host
Puja
ranjan.
Today
we
will
talk
about
a
proposal
to
extend
ERC
721,
which
will
enable
an
nft
to
be
redeemed
in
multiple
scenarios.
Erc
6672,
multi-redeemable
nft
was
proposed
in
February
this
year
and
has
been
moved
to
the
funnel
status
just
this
morning.
It's
the
perfect
day
to
have
this
conversation
with
the
authors
and
learn
about
the
proposal
to
provide
an
overview
of
this
ERC.
We
are
joined
by
boyu
Shu.
Welcome
to
the
show
were
you.
A
So
everyone
I'm
Bo,
Yu
and
I'm,
the
co-founder
and
CEO
of
Redeemer
and
erc6672
is
Hua,
is
an
abstraction
and
a
condense
of
our
past
works
on
a
lot
of
different
projects,
and
today
we
are
also
having
some
of
our
team
members
with
us.
Jason
he's
the
CEO
and
also
a
co-founder
of
Redeemer,
and
we
are
really
focusing
on
building
something
that
will.
We
believe
that
will
change
the
world
and
erc6672
is
just
a
start.
A
So
it's
a
multi-redeemable
nft
which
allows
us
to
redeem
nft
in
multiples,
different
scenarios,
so
I
will
start
with
our
team.
This
is
a
team
that
has
contributed
to
the
standards
and
the
reasons
we
are
like,
including
not
just
the
developers
is
because
we
do
gather
a
lot
of
experiences
and
know-hows
from
past
project,
front
executions
and
these
executions.
A
Actually,
although
you,
it
seems
really
simple,
the
simple
designs
is
actually
what
we
have
gathered
from
a
lot
of
past
experiences,
and
now
we
believe
that
it
is
ready
for
its
first
steps
of
becoming
a
standards.
Of
course,
in
the
future
we
may
have
better
or
more
complete
standards,
but
we
believe
that
Liz
is
the
first
step
and
we
do
have
a
motivation
of
the
reasons
that
we
are
building
this.
The
reason
we
are
building
this
is,
we
see
nfts
as
the
future
of
Commerce.
A
It
forms
the
fundamentals
of
how
blockchain
interacts
with
the
real
worlds,
and
we
often
like
to
cook
William
quickly,
which
really
inspires
us
on
doing
this
project
is
after
tokenizing,
US
Dollars.
It
is
time
for
tokenization
of
real
world
assets,
and
this
is
what
we
like
get
started
with
the
whole
project.
This
is
what
are
we
inclined
to
do
by
changing
the
world
and
because
this
has
a
lot
of
benefits
which
we
have
like
already
like
proven
in
our
past
executions.
A
A
lot
of
our
slides
are
actually
snatched
from
our
like
company
sites,
and
this
is
because
list
EIP
Or
List,
like
standard,
is
what
we
have
like
practiced
in
the
field
tested
by
the
market
and
then
now.
We
believe
that
this
is
the
list,
is
the
time
to
form
it
into
a
robust
fundamental,
so
that
we
can
proceed
on
the
further
steps.
So
we
do
see
that
there
are
a
lot
of
like
great
opportunities
when
combining
nfts
with
Commerce.
A
There
are
like
potentials
to
new
e-commerce
opportunities,
meaning
that
a
manufacturer
can
sell
or
a
designer
can
sell
things
on
all
platforms
supported
by
the
same
chain
immediately
and
creating
hybrid
experiences.
Also,
the
removal
of
physical
constraints
actually
increase
relativity
and
composition
ability
of
everything,
so
it
also
unlocks
like
additional
revenue
streams
through
royalties
and
create
new
business
model.
So
this
is
actually
something
that
is
very
exciting,
but
actually
currently
it
is
poorly
supported.
A
So
we
are
do
building
a
lot
of
infrastructure
on
that
and,
of
course,
today
we
will
be
focusing
on
three,
which
we
observe,
that
lacking
of
an
nft
standards
actually
prohibits
the
general
adoptions
of
NFC
in
Commerce,
because
the
information
is
actually
not
shared
and
everybody
is
building
up
on
their
own
standards.
So
today
why
we
propose
these
multi-redeemable
nft
standards
is
we
want
to
make
the
informations
be
shared
through
nfts,
especially
on
the
Commerce
parts?
A
So
now
we
will
go
into
the
details,
more
details
or
the
descriptions
of
The
Proposal,
but
I'll
make
it
more
on
the
guidelines
of
the
designs
and
how
our
thought
process
is.
So,
let's
take
a
quick
glance
on
erc672.
It
mainly
can
consists
of
three
parts.
One
is
a
read
functions
which
allows
us
to
connect
with
other
smart
contracts,
which
usually
stands
for
the
interactions
of
a
contract
with
nfts
what
can
be
used,
post,
redemptions
and
other
like,
for
example,
future
men's
or
future
engagements
or
other
connectors
that
is
connected
with
this
nft.
A
Also,
we
have
write
functions
that
is
controlled
by
The
Operators,
which
usually
usually
stands
in
the
place
of
platforms,
systems
or
regime
providers,
so
that
they
can
like
write
these
like
values
and
to
fulfill
the
redeem,
and
these
informations
are
shared
by
returning
them
into
nfts.
We
also
Define
a
metadata
standard
so
that
the
app
users
can
easily
integrate
and
they
don't
have
to,
like
all
every
time,
go
back
to
qualities,
readable
functions,
to
check
all
the
statuses.
They
can
easily
get
it
from
a
metadata
extensions,
so
the
implementation
can
be
really
fast.
A
So
this
is
just
a
rough
outline
of
what
erc6
system
to
structuralize,
but
a
lot
of
questions
are
asking:
why
do
we
need
the
standards
to
answer
this
question?
I
will
start
from
what
not
6072
is
doing,
because
redeem
has
a
lot
of
aspects
and
a
lot
of
people
are
thinking
that
we
are
solving
all
the
redeemed
problems
to
6072,
which
is
not.
A
We
also
have
a
redeemed
protocol
that
solves
other
parts,
and
we
also
see
a
lot
of
great
other
eips,
which
also
solves,
for
example,
the
listings
of
privilege
and
other
parts.
So
what
erc67
is
not
solving
is
we
are
not
handling
the
redeem
process.
We
are
already
having
a
protocol,
or
we
have
seen
a
lot
of
great
systems
that
can
handle
this
easily
and
also
there
are
a
lot
of
like
guarantees.
A
For
example,
the
offline
connections
and
the
offline
guarantees
lists
are
not
directly
guaranteed
by
er6672
CRC
6072
provides
a
great
interface
faces
so
that
these
guarantees
or
lease
connections
can
be
done
easily
and
synced
on
chain.
Secondly,
a
lot
of
people
would
say
that
what
is
the
main
difference
between
6072
and
some
kind
of
like
predefined
redeemable
nfts,
which
USC
60102
is
also
not
defining.
It
is
not
defining
the
Redemption
rules,
the
application
logic
or
the
business
logic.
A
We
leave
them
up
to
the
implementers
of
the
1672,
which,
of
course
like
can
integrate
with
other
standards
if
they
are
using
with
6072.
Also
a
lot
of
people
asking
how
do
I
know
what
are
the
available
redemptions.
This
is
also
not
solved
by
erc67d2,
because
what
we
are
handling
here
is
the
status
Parts,
rather
than
what
what
privilege
does
list
certain
NFD
have
the
reasons
that
we
are
doing
this,
because
we
imagine
this
to
be
a
very
open
world
and
open
space.
A
So
everyone
can
actually
attach
a
lot
of
different
perks,
even
without
the
missions
of
the
contract
owner
to
certain
kinds
of
nfts.
So
all
in
all,
nft
is
ERC
6072.
We
are
not
solving
the
above
Redemption
problem.
It
is
solved
by
either
by
our
regime
protocol
by
other
standards
or
other
like
methods
of
approach,
but
what
erc672
is
solving
it?
It
defines
a
interface
for
the
inscriptions
of
the
status,
which
is
the
execution
results
of
a
triggered
redeemed
responses.
A
So
the
reasons
that
we
are
putting
erc6072
and
distance
is
we
see
how
people
did
redeem
in
the
past,
so
there
are
several
ways
of
doing
redeem.
The
first
and
the
main
first
major
part
is
people
usually
code
directly
into
the
nft
contract
of
implementing
a
redeem
functions
and
triggers
like,
for
example,
transfer
or
burn
or
direct
executions
on
the
nfts.
Also
there
are
other
ways
of
doing
it.
A
For
example,
if
you
have
like,
for
example,
eight-
and
you
are
a
redeemed
for
a
point,
you
will
see
it
being
handled
by
an
external
contract
and
for
some
physical
like
operations,
it
also
happens
in
this
manner.
There
are
also
centralized
approach,
which
is
like,
for
example,
like
like
a
lot
of
token
gated
Solutions.
A
These
are
like
centralized
systems,
reading
web
free
data
and
provide
like
web
2,
authentications
and,
of
course,
there's
also
a
really
naive
way,
let's
screenshots
of
pen
and
paper,
which
is
still
very
popular
but
all
of
these
methods
they
have
their
own
like
limitations,
for
example,
when
coding
into
nfts
there.
It
is
actually
not
scalable
Integrations.
Each
nft
has
its
own
different,
like
play
rules
or
different,
so
it
is
actually
not
really
generalized.
A
So
when
integrating
with
these
nfts
each
applications
or
platforms
may
have
to
integrate
all
these
informations
one
by
one
other
parts.
When
you
are
integrate,
you
are
using
external
contract.
It
would
be
really
hard
to
track,
for
example,
who
you
you
know
certain
nfe.
They
may
have
certain
approach,
for
example
claiming
some
tokens,
but
where
is
the
claiming
contract
at
you?
You
wouldn't
even
know
it.
A
A
little
information
is
actually
really
recommended
and
title
it's
not
easy
to
track,
and
this
also
happens
for
the
centralized
systems
with
an
extra
catch
that
it
might
be
banned
someday
and
the
only
information
could
be
lost
or
we
can
take
Twitter
API
when
it
is
banned.
A
lot
of
applications
are
then
stopped
and
also
there's
still
screenshots,
pen
and
paper,
which
we
don't
want
to
continuously
use.
So
we
do
see
that
there
are
both
limitations
on
all
the
different
approaches.
A
So
the
reason
the
thing
we
need
to
do
now
is
to
have
everything
on
the
nft
properties.
So
the
thing
we
see
here
is
the
the
proper
layer
are
actually
properties
of
nfds
that
are
intrinsic
and
intrinsic,
so
intrinsic
nft
is
what
I
Define
here
is
something
that
binds
with
the
NFP,
for
example,
metadata.
A
Like
constantly
holds
on
to
the
nft
or
some
or
everything
that
defines
the
nft
to
be
itself,
the
hash
token
IDs
and
also
there's
extrinsic
values,
which,
for
example,
Market
classes,
it
varies
with
the
user
like
when,
when
the
users
operate
with
the
nfds
or
the,
when
the
nfts
is
put
into
other
usage
like
it
becomes
an
avatar
on
on
your
Twitter
account,
it's
an
intrinsic
value.
It's
the
average
list.
Nft
is
the
Avatar
of
some
famous
people,
listen
to
East
Valley.
A
When
this
is
traded,
this
property
gets
changed
or
it's
gone,
and
also
there
are
some
like
platform
reflex.
That
also
are
the
exchange
again,
that
is
externally
labeled
on
these
nft,
so
nfts
have
a
value
that
is
more
immutable
and
there's
like
properties
that
are
mutable.
But
when
we
look
at
Commerce
things
get
a
little
complicated,
because
what
are
the
Commerce
properties
of
the
token
actually
located,
for
example,
does
the
perks
and
the
utilities
constantly
goes
with
the
nft
or
it's
it
or
is
it
more
fluid
and
attachable
in
our
exit
past
execution?
A
We
do
see
that
there's
a
demand
on
attachable
perks
or
attachable
attachable,
like
utilities,
but
at
the
same
time,
when
these
nfts
are
traded,
these
persons,
you
should
need
to
all
still
come
with
the
NFP.
This
also
goes
with
the
status,
the
validated
the
shipping
status
and
all
these
parts,
and
also
we
have
seen
a
high
growing
demand
of
dynamic
metadatas,
meaning
that
the
nfps
changed
when
doing
redeems.
So
this
part
is
kind
of
tricky.
A
It
actually
needs
to
be
governed
validated,
but
it
still
needs
a
of
flexibility,
of
having
diverse
possibility
and,
for
my
personal
belief,
I
think
it
should
have
a
certain
level
of
openness.
So,
in
the
end
we
believe
that
the
only
or
are
currently
best
solution
to
it
is
make
it
an
interface,
and
that
is
exactly
the
reasons
why
we
are
designing
erc6672
with
all
these
parts.
We
believe
that
should
be
governed
should
be
validated,
but
at
the
same
time
should
be
openly
discussed.
A
So,
in
short,
what
we
are
proposing
here
is
a
combination
of
existing
methods.
We
now
don't
write
the
business
logic
and
codes
directly
in
the
NFD
contract,
making
the
nft
simple,
creating
only
intrinsic
value
properties,
but
we
leave
these
operators.
They
may
be
centralized
operators
or
decentralized
operators.
They
put
their
results
back
into
the
NFD
contract
so
that
it
is
sure
across
multiple
platforms
and
at
the
same
time,
a
different
business
logic
can
be
implemented
in
different
parts
of
the
operators
and,
of
course,
I'm
not
discussing
about
the
screenshots
anymore
yeah.
A
So
this
is
what
we
are
actually
building.
This
is
also
snip
from
our
company
slides.
We
are
building
the
middleware
infrastructures
for
the
Commerce
parts
and
the
reasons
we
need
an
ERC
71
is
to
easily
connect
with
web3,
and
now
we
are
having
ERC
6072,
so
we
can
connect
more
Commerce
status
back
into
the
worlds
of
web3.
So
now
it
becomes
like
a
relative
clear
when
we
look
back
into
the
specification
is
what
are
the
reading
functions
mainly
used?
It's
mainly
connect
back
to
the
web
3
connections.
A
You
can
do
a
lot
of
post,
Redemption
interface
interactions
and
interfaces
with
other
contracts.
For
example,
if
listing
has
been
redeemed,
some
changes
might
happen
to
the
nft
or
other
privileges,
and
it
creates
a
very
fluent
way
of
creating
future
composable
re-engagements
and
a
faster
web
free
Integrations
and
the
most
important
part
would
be.
How
do
you
build
up
The
Operators,
since
it
handles
the
redeem
process?
Eventually,
The
Operators
needs
to
connect
with
the
bits
of
the
logic
and
the
providers
to
fulfill
the
complete
experience,
so
I
will
leave.
A
I
will
give
out
some
examples
of
how
these
operators
can
be
combined
and
built
to
fulfill
some
like
interesting
use
cases
and,
finally,
the
apps.
They
can
directly
read
from
the
metadata
extensions
so
that
they
can
create
a
very
smooth
and
very
easily
displayed
user
interfaces
in
a
very
short
time,
and
also
since
there
are
t-apps
or
they
are
platforms,
they
can
apply
any
filters.
A
They
want
to
enhance
the
user
experience,
meaning
that,
if
I'm
building
a
app
for
only
ticketing
I
can
filter
all
the
like
a
Redemption
requests
or
the
Redemption
results
not
related
to
what
I'm
building.
So
these
are
the
benefits
directly
derived
from
what
we
have
or
using
erc672
is
we
have
a
predefined
framework
on?
How
do
we
log
lower
Redemption
results?
A
So
we
don't
have
to
design
it
over
and
over
again
when
we
are
launching
new
nfts
and
making
mistakes,
and
since
all
people
are
using
the
same
framework,
it
makes
it
very
easy
and
self-driven
on
the
Integrations.
If
you
need
to
connect
with
a
redeemable
nft
and
that's
that's,
the
best
part
of
the
standards
is
like
people
doing
the
same
way
and
reducing
the
cost
of
each
other
and,
of
course,
the
Mana
data
exchange.
A
Extensions
enables
the
apps
to
better
display
their
informations
and
create
a
lot
of
like
great
different
usage
and
the
things
that
we
are
designing,
ercc72
a
lot
different
from
other
nfts.
Is
we
embrace
the
progressive
decentralization?
We
don't
need
every
operators
to
be
centralized.
In
the
first
day,
some
can
be
Central,
because
a
lot
of
like
supply,
chain
or
real
world
are
actually
managed
by
centralized
systems.
We
enable
them
to
connect
in
the
first
day
and
gradually
become
decentralized
when
they
enjoy
the
benefits
of
decentralization.
A
So
these
are
the
benefits
we
are
seeing
from
a
high-level
description
of
ERC,
6072
and
now
I'm
going
to
describe
some
of
the
usage
examples
and
guidelines,
and
so
this
is
what
we
have
already
done
before
all
the
potential
scenarios,
and
you
can
see
that
there's
actually
a
lot
and
you
can
see
these
demos
from
our
YouTube
these
having
already
been
tested
and
built.
But
all
these
scenarios
are
really
are
really
terrifying,
because
you
would
say
that
oh
I
don't
know
how
to
design
you.
A
There
shouldn't
be
a
guideline
that,
like
connects
all
the
different
scenarios,
which
is
true
because
when
you
are
designing
new
nfps,
there
are
a
lot
of
things
that
you
need
to
think
about
and
when
you
are
designing
physical
nfts,
we
have
summarized
some
of
the
guidelines
from
our
past
experience.
The
first
part
is
what
to
put
into
erc60mp,
because
a
lot
of
people
has
asked
about
this.
It's
so
General
in
ercc
72.
We
can
put
this.
We
cannot
put
this.
How
it
is
determined,
I,
don't
have
a
clear
answer
for
that.
A
But
I
have
a
guideline
is
to
try
distinguishingly,
intrinsic
and
extrinsic
properties
of
your
nft.
It
may
differs
for
different
business
logic,
even
if
you
are
having
less
similar
properties,
and
these
are
the
three
main
directions
that
I
would
suggest
people
think
about
is
first,
the
user
experience.
For
example,
in
what
scenarios
would
the
user
care
about
the
things
that
you
logged
into
erc672,
for
example,
if
you
intend
to
log
the
shipping
status
into
erc672,
does
your
user
care
about
it?
A
Do
they
look
up
on
it
when
they
are
trading
in
like
decentralized
nft
marketplaces,
for
example,
if
an
nft
has
been
redeemed
or
not,
would
be
a
very
Vital
Information,
so
list
differs
from
your
NFD
design,
and
does
this
enhance
the
probability
of
people
building
more
and
more
interesting
applications
on
your
nft?
Also
privacy
is
an
issue.
A
You
need
to
think
about
something
when
you
put
it
into
your
RC
sent
you
because
it
becomes
open,
you
can
encrypt
it,
allowing
the
users
to
decrypt
it
when
they
need
it,
thus
providing
a
way
of
building
decent
like
a
more
like
user-facing
or
privacy
oriented
applications
without
revealing
their
informations
to
a
centralized
holder.
Also,
there
are
like
an
engineering
considerations.
A
The
frequency
latency,
the
throughputs-
is
the
chain
like
efficient
enough,
or
is
your
design
efficient
enough
so
that
it
is
cost
efficient
on
the
business
that
you
are
actually
doing
and
you
need
to
like
really
know
how
your
users
interact
or
varies
your
attributes,
and
this
is
some
parts
which
I
can
only
provide
the
guideline.
I
cannot
design
it
for
you,
but
these
are
very
important
when
you
are
working
with
erc6672
and
the
second
part
is
how
do
you
build
up,
The,
Operators
so
and
generally
for
things
past
the
operators?
A
There
are
mainly
three
components:
one
is
that
Redemption
Handler
or
the
Redemption
operators.
The,
secondly
is
the
business
logic,
and
the
final
is
the
display
and
the
best
recommendations
I
can
have
is
to
separate
these
parts
and
use
existing
solutions
for
the
part
that
has
been
built,
built
and
rebuilt,
for
example,
for
the
validations
and
authorizations
and
linking
to
existing
providers.
There
are
actually
a
lot
of
several
existing
Solutions,
including
ours.
A
We
would
like
man
directly
read
from
mental
data
extensions,
but
keep
an
eye
on
the
synchronizations
of
the
mismatch
of
the
information
between
what
is
written
into
672
and
the
think
of
metadata,
especially
when
the
metadata
is
centralized.
The
last
part
you
can
decide
on
which
is
an
interesting
topic
that
I
think
only
exists
in
web3.
Is
you
need
to
design
determine
level
of
like
decentralization,
so
when
in
1672
you
actually
have
the
power
to
determine
whether
a
regime
can
take
place
or
not
based
on
the
operators?
A
So
you
can
have
a
like
very
limited
number
of
The
Operators.
Only
lowslet
has
already
written
when,
during
the
deployment
of
your
nft
contracts
are
allowed
to
do
all
these
write.
All
these
like
redeemed
transactions
into
the
nfts,
and
also
you
can
open
up
to
all.
However,
limiting
the
nft
lead
operators
does
not
actually
prohibit
people
by
doing
external
contracts
and
doing
external
redeem.
A
It's
just
prohibits
them
from
writing
things
into
the
nft
from
my
personal
belief,
I
believe
that
people
can
do
it
as
open
as
possible,
so
I'll
definitely
root
fully
open
to
all
and
The
Blacklist,
since
they're
eventually
will
may
have
some,
especially
when
you
are
linking
with
real
world.
They
may
have
some
regulation
issues,
so
I'll
definitely
root
for
open
to
all
and
Blacklist
manners.
A
But
to
be
honest,
that
it
is
really
up
to
you,
but
there's
a
catcher
is
even
if
you
are
allowing
people
to
write
different
different
operators
to
write
into
your
nfts.
You
can
still
filter
out
them
in
your
D
apps,
so
people
can
choose
whether
they
want
to
be
filtered
or
not
and
I
believe
that
is
probably
the
best
solution
for
me.
So
these
are
some
of
the
ideas
and
the
guidance
that
we
will
seek
and
now
it's
time
for
some
of
the
examples
that
we
can
build
using
erc672.
A
So
this
one
is
like
relatively
simple:
it's
a
web
3
Commerce.
So
for
web
3
Commerce,
you
get
your
nfts
that
is
redeemable
into
actual
physical,
like
products
or
assets,
and
this
example
is
a
toilet
paper
which
is
like
real,
but
you
can
it
can.
Actually
it
come
from
anywhere
it
can
come
from
Main
Events.
It
can
come
from
secondary
marketplaces.
It
can
also
come
from
e-commerce
license.
Some
of
them
are
actually
seeking
like
integration
with
these.
It
can
also
come
directly
in
your
games.
A
You
don't
have
to
like,
for
example,
buy
a
toilet
paper.
You
may
like
play
it
in
games
and
earn
it
as
a
reward,
or
you
get
some
like
from
like
certain
like
strange
people
from
your
metaverses
yeah.
When
you
have
this
nft
of
toilet
paper,
which
is
guaranteed
by
certain
providers,
they
will
ship
out
toilet
papers
for
you
and
what
you
can
do
is
you
can
put
each
status
in
the
forms
of
the
redeem
so
that
it
forms
a
decentralized
tracking
with
immutable
records.
A
Of
course,
the
suggestion
I
would
put
here
is,
if
you
are
putting
address
or
locations
onto
the
memo,
I
would
suggest
you
encrypt
it
so
that
when
users
are
or
or
the
app
Builders
are
building
it,
they
can
have
the
users
decrypted
and
show
on
their
Edge
rather
than
governed
by
Central,
centralized
centralized
servers,
so
that
creates
a
whole
new
level
of
privacy.
So
it
allows
people
to
create
a
lot
of
different
tracking
applications
or
uis.
It
may
be
in
the
forms
of
web.
A
It
may
be
in
the
forms
of
app
or
it
may
be
in
the
forms
of
an
iot
device
on
your
refrigerator.
It
allows
people
to
build
all
this
based
on
decentralized
and
immutable
records,
but
at
the
same
time
guarantees
the
privacy
of
this
redeemable
entity
and
eventually
these
nft
will
get
burned
when
the
whole
redeem
process.
Redemption
process
is
done
so
hope,
coding
list
nft
is
essentially
like
holding
a
virtual
toilet
paper.
This
is
another
example
that
we
are
seeing
are
actually
bringing
changes
to
Road.
A
This
is
I
crossed
out
the
ticket
and
making
it
into
pass,
because
what
we
are
seeing
is
it
has
much
more
different
levels
of
Engagement
compared
to
a
ticket.
It's
not
just
a
one-time
entry.
Now
it
becomes
a
pass
that
allows
users
to
engage
in
different
scenarios.
So
in
normal
user
normal
use
cases,
you
will
see
that
the
ticket
becomes
invalid
after
you
have
entered
the
venue
or
something-
and
this
part
it
is
handled
by
redeemed
through
the
ticketing
systems
provided
by
operator
a
but
for
the
group
of
operator
B's.
A
The
operator
B
can
serve
a
lot
of
providers
that
may
provide
Refreshments
May,
provide
props
May,
provide
some
EI
VIP
experiences.
They
may
need
to
check
if
you
have
already
reading
or
not
and
so
is
redeemed
function
is
used
there
and
once
they
checked
it
yeah
they
can
go
on
with
the
redeem
and
continually
process
and
interact
with
the
existing
nfts
and
also
after
all,
the
event
experience
happen
at
the
venue.
We
can
also
do
constant,
like
brand
engagements
after
the
whole
venue
based
on
the
behaviors,
so
now
get
the
redemptions
functions.
A
It's
not
really
important
because
you
get
the
redemptions
from
what
the
users
has
already
interact
at
the
event
at
the
venue
and
there's
all
a
lot
of
different,
like
Integrations,
like
shopping,
like
game
passes
like
discounts
at
e-commerce
sites,
and
these
are
relatively
simple
by
putting
the
informations
back
into
ERC
6072.
So
this
provides
a
constant
re-engagement,
for
example,
future
Hawaii.
A
If
you
are
selling
your
next
concert
tickets,
the
best
way
to
do
it
is
to
find
the
users
that
engage
with
their
past
the
most
and
then
like
quite
the
stem
and
sell
the
tickets
to
them
yeah.
So
these
are
two
examples
that
we
have
already
like
executed,
not
directly
with
6072,
but
we
have
tested
a
lot
of
mechanisms
of
6cm
to
do
in
this
showcases
and
what
we
believe
that
the
future
like
is
well.
A
This
is
slightly
terrifying,
but
this
is
what
imagine
like
the
future
will
be
like
it's
a
constant
interactions
between
the
digital
world
and
the
real
world.
So
you
may
have
some
game
platforms.
You
have
an
avatar
nft,
you
have
consumer
posts,
you
have
equipment,
you
have
resources,
you
can
redeem,
for
example,
the
simplest
way
is,
you
can
redeem
for
a
bread
and
it
connects
directly
to,
for
example,
some
like
delivery
services,
and
it
calls
the
regime
should
interact
with
the
NFD
itself
and
deliver
the
things
to
your
doorsteps.
A
So
your
virtual
bread
becomes
a
real
breath.
Also,
if
you
have
an
equipment,
you
can
constantly
engage
on,
for
example,
Gatherings
or
you
can
redeem
for
a
actual,
like
figure
sword
when
combined
with,
like
manufacturing
providers
or
e-commerce
platforms,
for
like
special
discounts,
when
you
like
slash
the
prices
for
for
some
like
certain
accessories
and
all
these
can
be
accumulated
into
the
nft
itself.
A
So
it
creates
a
constant
engagement,
re-engagement
interaction,
Intelligence
on
training
off
chain
together
and
creates
a
very
blurred
experience.
You
cannot
distinguish
what
is
in
game
or
what
is
in
real
life,
and
we
believe
that
that
is
actually
the
future
of
Commerce
in
the
future
world
yeah,
so
we've
seen,
but
people
would
ask-
and
this
is
a
slightly
off
topic,
but
people
would
ask
how
about
existing
nfts.
A
Of
course,
you
can
always
airdrop
or
you
can
upgrade
if
your
nfts
are
upgradable,
but
these
two
are
not
that
of
Ideal,
because
a
lot
of
activities
have
already
accumulated
on
these
kind
of
nfts.
So
what
we
imagine
here
is
there
is
a
third
alternative
is
to
manage
a
well-recognized
contract
or
systems,
and
this
we
believe
that
should
not
be
handled
by
a
single
entity.
We
need
it
to
be
built
by
the
communities,
so
yeah
follow
the
QR
code.
A
We
are
looking
for
people
to
build
and
maintain
all
these
with
us
and
also,
if
you
are
interested
in
other
parts
of
the
ERC
6072,
we
are
launching
our
developers
of
Dell,
so
definitely
come
and
join
us
apply
for
the
grants.
We
are
happy
to
have
you
all
developed
with
us
yeah,
so
that
covers
the
most
parts
of
what
erc672
is
capable
of
what
the
thought
process
is.
A
A
But
when
you
are
designing
the
interfaces,
you
are
solving
an
uncertain
future
problems
and
you
need
to
be
very
clear
of
that
and
think
of
all
the
possible
cases
which
is
like
really
like
tedious,
painful,
but
also
like
interesting.
At
the
same
time,
it's
like
a
lot
of
contradictions
in
there,
but
the
reasons
we
are
doing
this
is:
we
believe
that
this
actually
forms
a
robust
fundamental
so
that
we
can
March
forward
and
the
best
part
is
we
make
new
friends
along
the
way
we
are
forming
an
EIP
Style
on
like
group.
A
We
have.
We
have
a
telegram
group
and
a
lot
is
going
to
be
launched
because
EIP
is
a
process
and
I
do
believe
that
when
people
like
talk
to
each
other,
we
can
have
a
more
clear
understanding
or
or
clearer
way
of
how
to
process
this
or
how
to
build
this,
and
also
we
often
discuss
on
a
lot
of
like
different
eips
that
are
newly
launched.
What
is
the
purpose?
What
are
the
potentials
of
it?
A
And
we
believe
that
this
heavily
brings
everything
together
and
here's
a
little
little
timeline,
and
we
are
happy
that
everything
gone
past
and
we
are
ready
for
our
next
steps.
So
yeah
really
happy
that
to
be
here,
and
these
are
some
of
our
thoughts.
We
are
very
happy
that
we
are
having
this
process
and
for
our
GSR
CTO
he's
very
happy,
because
he
is
able
to
present
these
thoughts
to
the
community
and
invite
a
lot
of
Builders
to
constantly
build
with
us
and
Jason.
A
Our
co-founder,
he's
being
is
that
we
only
unleashes,
like
perhaps
like,
like
one
in
one
thousands
of
the
powers
of
blockchain
and
there's
much
much
more
to
be
built
and
from
my
side,
I
think
the
best
part
is
yeah.
We
just
go
for
it,
because
a
lot
of
people
may
question
the
necessity
of
building
an
open
standard
or
open
protocol,
but
actually
the
openness
and
the
composability
is
actually
core
beauty
of
web
free
and
we
intend
to
involve
a
lot
of
different
Builders
to
keep
on
building
with
us.
A
B
Awesome
that
was
a
great
presentation.
Quite
colorful,
vibrant,
as
I
can
see
the
logo
of
red
dreamer.
The
presentation
basically
covered
a
lot
of
questions
that
we
had
in
my
mind,
as
well:
I
really
loved
the
concept
of
intrinsic
and
extrinsic
properties
that
you
mentioned
that
you
know
implementer
should
keep
in
mind
while
deciding
what
to
include
and
what
not
to
include
overall
I
think
this
was
a
great
presentation.
B
A
So
of
that
part,
it
is,
let's
just
say,
frequently
asked
questions,
usually
in
two
steps.
Some
nft
provides
extra
control
or
extra
like
permission,
control
or
interactive
controls
to
the
nft
itself.
So
what
this
ERC
is
different,
is
we
don't
Define
that
Parts,
but
we
can
combine
it
together.
You
can
have
an
ERC
6072,
which
is
at
the
same
time
a
so-bound
token.
You
just
Implement
a
lock
on
it,
which
we
have
also
done
before,
because
us,
for
example,
there
are
some
like
ticketing,
vendors.
A
On
the
contrary,
they
don't
want
royalties,
they
don't
want
high
frequency
resales.
They
want
their
tickets
to
be
stick
to
their
buyers,
so
you
can
have
a
redeemable
fees
that
is
so
bound
at
the
same
time,
and
so
this
also
covers
the
the
question
list.
For
example,
5192
the
so-bound
nfts,
the
2135
2135
consumable
interfaces
and
like
a
55
one,
lorento
nfds.
These
are
all
control
oriented
which
can
also
be
integrated
together.
A
We
have
also
talked
with
several
protocols
that
are
handling
rentals,
which
they
want
to
preserve
some
of
the
redeemable
properties
during
the
rental
protocols,
and
so
it
is
combinable
and
that
is
actually
a
beauty
of
erc's.
They
are
usually
combinable
and
also
they
are
other,
like
nfts,
that
are
aimed
to
list
out
the
privilege,
for
example
like
55
80
5,
the
nft
authorizations
or
the
5007
time.
Nft
lay
list
out
the
privilege
or
or
the
characteristics
of
the
nft
which
again
it's
still
compatible,
because
what
erc670
is
not
doing.
A
It
is
not
handling
the
listing
of
the
privilege.
It
is
handling
the
results
of
the
execution
of
the
redeem
and
as
for
50
57
5007
time,
nfts
I
also
have
found
another
that
is
very
similar.
It's
called
multi-privileged
NFD,
it's
54.96
I
believe
it
is
very
similar,
except
that
it
has
several
different
privileges
and
you
can
set
the
different
like
expiration
time
and
I.
A
A
Build
up
their
projects
exactly
that's
pretty
interesting.
The
reason
we
are
providing
this
Lego
piece
is:
we
see
that
a
lot
of
people
are
doing
the
control
parts
of
the
NFP
or
the
privileged
listing
parts
of
the
nft,
but
we
don't
really
see
anyone
focusing
on
the
execution
results
and
the
connection
with
the
real
world
providers
parts
and
that's
the
reason
we
provide
these
Lego
piece
here
so
that
it
forms
a
complete
experience.
Awesome.
B
In
the
presentation
we
looked
into
quite
a
different
use
cases,
some
of
our
like
iot
integration,
retail
and
displays,
and
that,
if
you
would
like
to
maybe
pick
any
of
any
of
those
and
give
an
example
by
any
chance,
if
you
are
aware
of
any
project
who
may
be
implementing
this
proposal
for
any
of
these
listed
features,
that
would
be
great
to
have.
Okay.
A
So
for
a
lot
of
project
Builders,
you
only
need
to
select
the
solutions
which
I
and
practice
guideline
I
suggest
a
lot
of
Builders
to
use
existing
Solutions,
because
that
makes
you
much
more
easy
to
follow
existing
standards
and
build
a
comp
on
top
of
the
things
that
has
been
tested
over
and
over
again.
So
we
are
very
confident
that
in
the
next
few,
like
months,
a
lot
of
people
will
integrate
6072
into
their
physical
platforms,
businesses
or
a
pure
web
through
business.
B
A
The
first
list,
part
I,
believe
that
is
mentioned
in
our
in
our
standard
description-
is
that
because
what
we
do
here
is
adding
a
extra
layer
of
inscription,
it
usually
does
not
generate
extra
security
concerns.
However,
there
are
some
basic
implementations
when
you
are
doing
smart
contracts
that
you
need
to
be
extra
care
of,
for
example,
you
should
separate
logic
as
possible
and
don't
because
it
it
would
be
quite
convenient
to
do
so.
A
B
B
Very
well
said,
and
my
next
set
of
questions
I
know
Daniel
status
yesterday
and
you
and
the
rest
of
the
team
definitely
have
followed
their
guidelines
for
documenting
a
proposal.
I
would
be
curious
to
hear
your
journey
throughout
the
documentation
process
and
if
you
may
have
any
suggestion
for
us
for
improvement
and
think
that
make
author's
life
easier.
This.
A
Is
some
part
that
we
are
very
satisfied?
So
to
be
really
honest,
we
are,
of
course,
the
first
time
we
are
like
slightly
frightened,
because
we
have
never
done
this
before
and
we
have
debates
on
whether
we
should
like
go
through
it
or
not.
But
again,
as
far
as
I
said
just
go
for
it,
and
the
reasons
that
we
are
forming
communities
is
to
ease
the
process.
So
I
believe
that
this
should
not
be
like
directly
done
by
changing
the
procedure
itself.
A
The
procedure
we
we've
seen
from
now
from
our
chief
from
Randy
RPM
are
actually
giving
us
like
feedbacks
that
this
process
is
actually
a
very
like
thorough
and
robust
process
in
including
all
these,
like
other
checks
and
stuff,
and
it's
a
great
way
to
sit
down
and
clarify
your
thoughts
so
that
you
don't
write
a
standards
which
does
not
provide
anything.
So
I
think
that
it
is
like
actually
really
helpful
for
the
process
to
become
smoother.
A
I
believe
that
it
is
actually
the
job
of
different
Community
or
Community
groups
and
that's
the
reason
we
are
from
like
forming
a
forums
like
eip's
fund,
or
perhaps
there
are
many
more
groups
out
there,
which
I
believe
that
developers
should
join
and
at
the
same
time,
I
can
like
promote
again
apply
for
developing
with
us,
and
you
can.
We
can
share
our
experience
and
we
can
like
together,
discuss
what
can
be
like
what
can
be
overcome
and
what
needs
to
be
noticed
or
to
be
extra
care
of
during
this
journey.
Yeah.
B
We
had
a
chat
with
the
tiffan
and
I'm
sure
we
are
trying
to
explore
ways
to
have
eips
related
information,
more
public,
so
people
know
about
it
and
make
good
use
of
that.
Yes,
that
said,
I'd
be
curious
to
hear
about
some
of
the
supporting
programs
that
cat
holders
are
running
alongside
this
Peep
and
Eep,
and
the
eips
editing
office
hour.
Do
you
think
these
programs
are
helpful
to
users
and
authors.
C
A
Yeah,
because
during
the
process
we're
actually
getting
like
like
clear
feedbacks
and
of
course,
the
reasons
that
we
are
not
like
facing
a
lot
of
problems
is
because
we
are
actually
quite
clear
on
what
we
are
doing
and
we
do
have
a
like
a
a
like
tested
purpose
on
this
part.
So
I
believe
that
being
sincere
is
really
helpful
and
we
are,
since
we
are
providing
sincere
informations.
A
We
are
getting
like
sincere
feedbacks
from
the
editors
and
it
has
been
really
helpful
and
also
I,
really
like
the
way
of
like
managing
all
this
through
GitHub,
which
makes
it
like
really
trackable
and
although
it's
a
little
bit
developer
like
oriented.
But
it's
not
that
hard
to
understand
it.
So
it's
explainable
yeah,
so
I'm
really
happy
with
the
current
process.
I
just
I
want
to
hear
more
of
like
different
discussions
all
over
the
places,
but
I
believe
that
this
is
some
not
something
that
we
can
like
force
it
to
happen.
A
B
Very
well
said:
yeah
I
think
we
are
also
trying
to
make
some
effort
in
that
direction.
From
today
we
are
starting
a
new
call,
which
is
going
to
be
called
as
all
ERC
Dev
call
where
we
are
inviting
all
ERC
authors,
all
ERC
developers
to
maybe
come
share
their
proposal,
and
you
know,
learn
something
from
someone
else's
proposal
that
may
be
solving
problem
that
you
were
trying
to
solve
in
your
project.
So
that's
an
effort
in
that
direction.
Hopefully
that
helps,
as
we
mentioned,
that
we
need
to
discuss
these
things
on
more
forums.
A
And
we
do
learn
a
lot
from
past
ercs.
We
we
read
their
their
descriptions
so
and
we
we
read
a
lot
of
their
like
motivations,
so
that
we
can
get
a
hint
of
what
is
actually
the
best
way
to
cooperate
or
co-work
with
the
rest
of
the
community
and
I
believe
that
this
is
something
that
can
like
constantly
accumulate
and
gathered
into
something
that
is
really
Irreplaceable
and
valuable.
B
A
I
think
it's
mostly
the
same
that
I
really
agree
with
this
process
of
being
open
to
the
community
and
being
sincere
and
there's.
Nothing
to
afraid
of
things
will
eventually
like
get
done
with
the
help
of
the
community,
and
we
only
unleash
a
very,
very
small
portion
of
the
blockchain
blockchain
technology,
and
this
is
because
blockchain
technology
is
inherited
from
open
source,
which
is
also
a
Community
Driven
like
an
a
Community
Driven
like
spirits.
A
So
I
think
that
people
should
like
actively
engage
with
a
lot
of
like
different,
like
people
and
I
also
expected
to
see
a
lot
of
like
things
happening
here.
Also
at
at
con,
and
a
final
shout
out
is
join
us,
build
with
us
or
build
with
any
other
communities,
because
I
think
that's
how
everything
improves.
Definitely.
B
Yes,
this
is
be
a
part
of
the
community,
yeah
very
well
said
by
you.
We
really
appreciate
you
and
team
taking
out
time
to
provide
an
overview
of
ERC
6672
multi-deter
Maple
nfts,
and
we
congratulate
you
for
coming
this
proposal
into
final
status
today.
Thank
you
for
adding
another
nft
standard
for
ethereum
Repository.
B
Thank
you
so
much
on
this
note,
thanks
to
all
our
YouTube
viewers
who
are
watching
and
podcast
subscriber
for
listening
to
this
nft
special
episode.
Should
you
have
any
question
on
this
or
any
other
EIP?
Let
us
know
at
epcat
her
business
card
next
week,
we'll
be
back
with
another
interesting
talk
till
then
keep
watching
listening
and
sharing
your
love
with
ethereum
Caterers
cheers.