►
From YouTube: EIP Editing Office Hour 5
Description
Agenda: https://github.com/ethereum-cat-herders/EIPIP/issues/186
A
A
I
know
there
is
one
proposal
that
is
here
for
last
call.
The
number
is
eip5496,
so
maybe
we
can
start
from
there
over
to
you
Sam
and
anyone
joining
the
call.
If
you
have
a
proposal,
please
list
your
number
here
in
the
chat,
so
we
can
take
that
one
by
one.
B
This
is
the
correct
Eep.
That's
right!
Yes,
okay,
cool!
It's
so
did
every
particular
questions
about
it.
Or
did
you
just
want
to
go
through
it
or.
C
Yeah,
we
just
wanted
you
to
yeah
go
through
it
like
two
weeks
ago.
We,
you
had
some
feedbacks
and
we
changed
according
to
your
feedback,
just
get
an
idea.
Sure
yeah
I'll
take
a
look.
Thank.
B
D
B
Okay,
so
did
you
clear
up
whether
expires
was
a
duration
or
a
deadline
or
or
okay.
B
Yeah,
that's
perfect
and
then
we've
got
we'll
turn
the
expiry
timestamp
privilege
yep,
that's
good.
B
B
Okay,
so
but
errors
may
occur
when
the
owner
tries
to
withdraw
the
original
Eep
712
token
from.
E
B
B
Whatever
something
like
that,
so,
generally
speaking,
we
try
to
discourage
like
linking
to
your
own
EIP
in
the
EIP.
If
that's
all,
right
just
use
this,
if
it's
not
just
use
a
slightly
different
wording,
whatever
you
think
is
right.
Oh
okay,
weird
functions,
unwrapping
our
implementation.
D
B
B
B
B
B
B
E
Just
remove
that
prevent
it
transformed.
E
B
It's
not
a
huge
deal.
I
think
it
just
needs
to
be
yeah.
Just
just
don't
forget
to
remove
that
that
event
it
doesn't
line
up
with
the
standard
here.
That's
all
okay,
yeah.
D
B
D
B
B
About
this
one
or
or
if
not
we'll,
move
on
to
whoever
the
next
author
is.
A
Thank
you
so
the
next
one
we
have
is
five,
seven,
seven,
three
sure
it
looks
like
it
is
added
as
review.
But
to
me
it
looks
more
like
a
new
proposal,
so
maybe
you
could
take
a
look.
D
B
Okay,
so
I
guess
these
are
like
comments
that
come
out
all
the
time
when
I'm
reviewing
eips
and
I'm
very
bad
at
making
suggestions.
So
your
title
and
description
don't
give
enough
context
for
somebody
who's
looking
through
a
list
of
VIPs
to
kind
of
understand
what
this
EIP
does
so
I
I'd
recommend
probably
expanding
on
these
a
little
bit
so.
B
G
I
do
have
a
a
question
about
yeah
context:
dependent
output.
Can
you
like
give
me
an
example
of
like
context
dependent?
Is
it
like
formatting
of
the
asset
or
is
it
like
all
the
visual.
F
Well,
yeah:
this
is
the
context,
so
it
basically
means,
depending
on
how
you
try
to
access
the
nft,
your
server,
you
are
served
a
different
resource,
so,
for
example,
if
you
open
it
with
an
audio
book
reader,
then
you'll
get
an
audio
file.
If
you
open
it
with
an
ebook
reader,
you
would
get
a
PDF
file.
D
D
B
H
Yeah,
it's
a
bit
more
complex
because
in
order
to
to
know
ways
much
gas
we
have,
but
we
use
lists,
but
we
also
use
mappings
so
yeah.
We
could
be
more
detail
here.
H
Okay,
yeah
there's
something
like
maybe
different.
We
do
and
it's
that
we
store
Resources
by
ID,
so
we
can
reuse
resources
in
different
tokens.
Okay,
a
lot
of
storage
in
gas,
but
also
yeah.
That
kind
of
would
provide
a
sample
implementation
on
this,
but
there
are
obviously
different
ways
to
do
it.
So
would
we
explain
like
how
we
suggest
to
do
it
or.
B
Just
just
what's
in
the
interface
generally
so
like
if
your
design
has
like
a
the
special
feature
being
able
to
reuse
these,
these
outputs,
these
resources,
then
you'd
want
to
you
know
mention
that
that's
possible
in
your
abstract,
I.
Think,
okay,.
B
G
It's
all
about
the
metaverse
definition.
It
is
still
like
vague
right,
because
everyone
has
a
different
definition
about
metaverse
yeah.
G
H
Think
we
should
do.
The
best
part
is
to
actually
remove
this
and
make
more
specific
samples,
because
there
is
yeah,
there's
no
clear
definition
of
that.
Yet
exactly.
B
B
Okay,
so
there
is
actually
another
EAP
that
does
something
similar
to
this
cross.
Metaverse
compatibility,
I'm,
not
sure
if
you
guys
know
about
it
or
or
or
or
are
on
the
team,
I
think
it
was.
B
There
it
is
so
this
one's
somewhat
similar.
It
also
lets
you
add,
specific
assets
and
resources
that
depend
on
the
viewer
to
your
nft.
B
So
I,
don't
know
if
you
want
to
take
a
look
at
this
one
as
well.
I
can
put
it
on
your
discussion
thread
if
you
haven't
already
seen
it
yeah.
H
Please
yeah,
we
will
definitely
look
at
it.
B
Yeah
I
think
this
is
actually
the
third
EIP
I've
seen
that
tries
to
provide
different
types
of
assets
to
different
types
of
viewers.
So
yeah
I'd
recommend
you
know
everybody
getting
together
and
talking
about
it
at
some
point,
because
it
seems
like
everybody's
trying
to
solve
similar
ideas.
D
B
B
B
B
B
Yeah,
so
I
would
definitely,
in
this
section,
go
into
a
little
bit
of
how
this
is
different
from
just
changing
the
token
URI,
because
I
don't
think
that
that's
like
what
you're
describing
here
isn't
that
different
I
don't
think
it's
just.
Maybe
the
fact
that
the
owner
can
accept
or
reject
the
change
but
I'm
not
entirely
sure
so.
I'd
probably
clear
that
up
a
little
bit
in
there.
B
H
B
H
Yeah
I
think
thinking
of
indexers
is
feels
much
easier
to
to
keep
track
of,
but
maybe
well
yeah.
Actually,
we
could
merge
them
if
we
have,
if
we
always
include
the
overwrites
and
it's
just
zero,
when
it's
not
trying
to
override
anything
and
just
use
the
other
one.
The.
B
So
it's
an
overwrite
like
a
removing
a
resource
like
with
the
new
okay,
so
I
haven't
read
the
rest
of
the
interface.
Obviously
I'm
just
going
off
the
events
here
so
bear
with
me,
but
so
is
overwriting
a
resource
like
removing
an
old
resource
ID
and
adding
a
new
resource
ID
or
that's.
B
B
Okay,
yeah
I'm,
just
I'm,
always
nervous
about
events
doing
too
much
because
like
if
the
code
that
emits
the
event
has
to
like
be
aware
of
like
whether
it's
removing
something
or
adding
something
and
then
there's
a
lot
of
gas
to
calculate
that
so
or
there
might
be
a
lot
of
gas
to
calculate
that
so
I
I
don't
know
I,
just
I'm,
always
leery
about
that.
So
I
I
you,
you
can
feel
free
to
ignore
I'm,
not
like
an
expert
on
solidity
or
anything
but
yeah.
Okay,
so.
B
H
A
question
before
you
will
continue
on
I,
don't
forget
regarding
the
this
emps
that
also
try
to
address
the
multi-resource
problem.
We
will,
of
course,
take
a
look
at
them
and
review
where
we
are
different,
so
where
should
we
put
that
in?
Can
we
like
specifically
name
like
this-
is
different
from
EAP
X
on
this
or
how.
B
How
should
it
be
so
if
you
specifically
they'll
so
you
can
be
like
you
know
this.
This
EIP
differs
from
other
proposals
because
and
then
put
some
texts
there.
B
You
can
link
to
other
eaps
if
you
want,
but
if
your
EIP,
let's
say
you
know,
goes
like
you're
trying
to
go
to
final
and
the
other
EIP
is
still
in
draft,
your
EIP
will
be
blocked
if
you
directly
link
to
it
so
I
I
recommend
just
avoiding
linking
to
it
directly,
but
you
can
definitely
say
something
like
you
know,
we're
different
from
other
other
proposals
because
and
that's
fine
okay.
G
I
think
if
you
can
actually
State
the
key
differentiators
and
the
functionality
that
would
be,
you
know
visible
to
everyone.
B
Okay,
so
is
this
a
like
a
race
condition
if,
like
let's
say
I,
don't
know,
I,
don't
know
if
this
is
possible,
it
just
bear
with
me
for
a
sec,
but
let's
say
two
people
have
the
like.
Let's
say
you
have
an
approval
on
your
token
for
somebody
else
and
the
operator
and
you
both
have
permission
to
accept
resources
if
I
send
a
transaction
accepting
a
resource
and
it
reorders.
The
array
and
the
operator
sends
a
transaction
accepting
a
resource
and
it
also
reorders
the
array.
H
So
they
are
both
approved,
but
yeah
yeah
you're
right.
Actually,
if
both
try
to
approve
the
same
one,
maybe
you
we
will
be
accepting
an
additional
one,
exactly
yeah
not
intended
yeah.
This
is
a
really
good
point.
H
One
thing
we've
thinked
off,
because
we
I
kind
of
seen
this
as
to
pass
the
idea
of
the
resource
you're
trying
to
accept.
We
pass
here
here
the
index,
because
the
resources
like
that
we
have
a
list
of
pending
resources,
which
is
what
is
a
list.
So
you
need
the
index,
and
so
you
don't
have
to
go
through
it.
H
Looking
for
an
ID
which
is
more
expensive,
but
we
could
also
pass
the
ID
just
to
to
be
extra
safe
that
when,
once
it
finds
the
index,
it's
actually
that
resource
that
is
expected
to
avoid
these
race
conditions.
So
the
second
one
would
fail,
because
the
one
the
resource
you
want
to
accept
is
no
longer
in
that
index.
C
B
D
B
So
that
removes
it
from
the
pending
array
yeah,
so
that,
like
doing
it
off
chain,
would
be
so
nice
because
you
wouldn't
have
to
maintain
this
array
of
changes.
You
wouldn't
have
to
worry
about,
like
out
of
out
of
order.
Transaction
executions,
I
think
like
if,
if
you
can
do
that
approach
with
a
signature
instead
of
a
array
of
pending
that
that
might
be
really
nice
rejects
our
resources.
B
H
So
this
is
more
intended
to
avoid
a
pump,
because
oh
I
see
yeah
because
maybe
maybe
you'll
have
a
lot
of
resources,
although
this
is
there's
actually
not
a
problem
here,
because
only
the
issuer
into
the
full
implementation
like
we
expect
only
the
issuer
of
the
collection
is
supposed
to
send
tokens.
So
it
would
be
weird
if
he
was
spamming
right,
but
yeah
yeah.
This
is
also
a
possible
race
conditioning
right.
H
B
H
B
So
I've
seen
it
before
that
these
kind
of
functions
here
often
take
a
length
and
a
get
index
and
I.
Think
it's
because,
if
like
like
that
lets
you
do
pagitation
I,
don't
know
if
you
want
to
maybe
look
into
that
or
not
I'm
not
going
to
make
a
comment
about
it,
but
it
might
be
worth
looking
at.
Yes,.
H
B
Yeah,
so
this
this
one
also
seems
a
little
weird,
because
so
this
is
looking
in
the
pending
resources
right.
This
function
get
resource.
H
Overrides
not
exactly
when
we
add
a
resource
and-
and
we
are
trying
like
that
resource
intends
to
overwrite
some
other
one.
It
gets
stored
in
a
different
list
or
actually
mapping
of
ID
to
ID
to
be
replaced.
So
this
is
how
you
would
get
like
if
you
accept
this
resource
ID.
On
this
token,
what
would
it
be
replacing.
H
So
multiple
resources
ID
could
be
pointing
to
replace
the
same
one,
but
you
cannot
have
multiple
times
the
same
resource
ID
on
the
pending
or
on
the
active
list.
For
a
token.
B
H
H
H
That
makes
sense,
so
in
this
case
the
first
one
which
is
accepted
would
override
the
other
one
and
the
second
one.
It
would
just
ignore
the
override,
because
it
wouldn't
find
the
the
one
to
to
overwrite.
D
B
D
B
B
D
H
H
B
F
B
D
I
C
D
B
Cool,
so
that's
that's
pretty
much
it
for
this
one.
Hopefully
that's
some
useful
feedback,
I'm,
not
the
the
best
of
solidity.
H
We
have
it's:
it's
a
standalone
contract
that
could
be
used
to
to
query
any
other,
any
contract
that
implements
this
EIP.
How
should
we
handle
that?
Should
it
be
like
Annex,
because
it's.
B
Okay,
yeah,
so
do
you
expect
there'd,
be
multiple
implementations
of
it
or
just
a
single
implementation
of
it?.
B
That
it
doesn't
need
to
be
an
EIP
then,
so
you
can
just
make
it
to
put
it
up
on
like
a
website
or
or
like
try
to
get
it
into
open,
Zeppelin,
maybe
or
anything
along
those
lines,
but
it
doesn't
need
an
EIP
if
there's
only
going
to
be
one
implementation
of
it.
B
You
very
much
for
joining
no
problem
thanks
for
proposing
it's
I
I,
don't
know
much
about
the
NFP
space,
but
it
just
seems
to
be
a
problem
that
a
lot
of
people
are
working
on
so
I'm
happy
to
see
people
working
on
it.
Yeah.
H
B
There
is
another
EIP,
that's
about
layering
svgs
together
on
chain
and
I.
Think
the
use
case
was
something
like
you
could
equip
items
onto
your
character
and
the
the
items
would
appear
in
the
thumbnails,
not
exactly
related,
but
I.
Think
they're
working
on
a
similar
kind
of
problem.
So
take
a
look
out
for
that.
Eip
I!
Don't
remember
it
offhand,
but.
H
B
Well,
so,
do
you
think
there'd
be
any
value
in
getting
all
of
the
people
who
are
working
on
these
nft
composability
projects
together
to
talk
about
it
is
that
is
that
something
you'd
find
useful
or.
A
All
right,
the
next
one
that
we
have
here
is
five,
eight,
five,
seven,
sorry
Felix
do
you
have
any
question
or
anyone
yeah.
E
Back
to
the
file,
you
just
point
out
that
you
see
someone
still
there
or
I
can
share
my
screen.
Is
that
impossible
yeah?
It
should
be
yeah.
Okay,.
E
Yes,
because
you
just
point
out
this
is
the
line
still
here
right,
you
can
see
if
I
click
here
to
View
files
ready
to
jump
here,
you
see,
there's
no
probability
transfer
but
I
think
the
property
is
not
I.
Don't
think
this
merge
into
the
main
branch
there
right,
here's
the
membrane,
so
you
can
see
this
one
still
here
is
that
this
is
why
you
still
see
that
one
or
anything
I
missed
so.
F
D
E
E
B
A
Sam,
if
you're
aware
it's
fine
I
just
wanted
to,
let
you
know,
we
can't
see
your
screen
anymore.
A
That's
all
good
and
yeah.
There
was
another
proposals
author
joined
in
the
call
today,
so
we
can,
if
possible,
we'll
take
it
today,
otherwise
we'll
have
it
on
the
following
week,
but
karang
and
came
Raj.
If
you
have
any
specific
question
that
you
can
type
it
in
the
chat
in
the
meanwhile,
while
we
are
looking
into
54.96
here,
please
go
ahead.
B
So
so
before
we
jump
to
that
so
on
on
the
privilege,
transfer
thing
and
get
I
have
no
idea.
What's
going
on
there,
I
will
I
guess,
take
I'll
try
to
do
the
review
on
my
computer.
It
might
have
something
to
do
with
the
fact
that
you're,
using
the
master
branch
on
your
repository
but
I
really
don't
know
I'll
I'll
look
into
it.
A
Okay,
so
I
have
shared
the
number
here:
five,
eight
five:
seven
Sam
for
the
next
discussion:
five.
B
I
Yeah,
so
we
haven't
like
made
through
changes
to
our
VIP
and
that
PR
is
much
and
now
we
want
to
take
this
from
draft
to
real
estate.
So
that's
the
first
thing
all.
B
Okay,
this
is
actually
remarks
seems
like
it's
solving
a
remarkably
similar
problem
to
the
previous
proposal,
where
each
item
has
platform
specific
data
associated
with
it.
D
B
Sure,
sorry,
can
you
hear
me
now
yeah,
okay,
so
this
seems
similar
like
very
similar
to
the
previous
eipers,
reviewing
because
I
guess
the
idea
of
this
one
is
that
each
platform
gets
its
own
specific
information
about
the
nft.
The
only
difference
is
that
this
one
is
implemented
as
like
sub
nfts,
and
the
previous
one
was
implemented
as
like
metadata
on
the
same
nft.
I
D
B
Yeah
I
think
this
one
would
probably
work
with
less
support
from
the
like
vendors,
whereas
I
think
the
first,
the
the
previous
one,
we're
looking
at
would
work
better
for
like
if
the
vendors
are
on
board,
so
I'm
going
to
assume
that
do
do
either
of
you.
Authors
work
on
a
platform
that
renders
nfts
in-game.
B
Cool
all
right,
I'm
glad
that
there
is
at
least
someone
on
on
the
the
rendering
side-
that's
also
working
on
this
stuff.
So
that's
good,
okay,
okay,
so
that
looks
fine.
D
B
B
I
assume
you're
aware
we're
going
to
say
it
anyways.
So
the
review
process
is
up
to
you.
You
need
to
go
out
and
find
people
that
you
think
are
relevant
to
review
the
CIP,
get
them
to
comment
on
your
discussions
thread
and
you
know
try
to
come
to
a
consensus
on
what
the
best
implementation
is
and
then,
when
you
decide,
is
ready
to
move
to
last
call
that's
up
to
you
guys
to
to
make
the
pr
to
do
that.
B
Foreign,
usually
too
long,
I
think
but
not
the
fault
of
the
authors.
That's
usually
my
fault,
I,
don't
review
very
often,
but
yeah
leave
it
here
until
you
are
relatively
confident
that
you
have
solved
the
problems
in
the
EIP
that
anybody
else
who
might
be
interested
in
implementing
it
has
had
a
chance
to
comment
on
it.
B
Usually
this
is
a
good
time
to
build
prototypes
and
Integrations,
because
the
review,
the
review
status
kind
of
indicates
that
the
EIP
is
mostly
done.
So
it's
safe
to
start
implementing,
so
yeah
I
guess
try
to
get
some
implementations
going
and
socialize
it
with
other
people,
who'd
be
interested
in
and
would
be
using.
It.
I
A
All
right,
so
we
are
almost
close
to
a
time,
but
if
we
have
time
to
take
one
last
one,
maybe
we
can
take
the
one
proposal
which
is
ready
for
moving
into
final.
That
is
two
six
one.
Two
and
the
pull
request
number
is
five.
Seven,
eight
two.
We
do
not
have
the
author
on
call
but
looks
like
he
has
done
whatever
was
requested
by
another
EIP
editor.
B
B
Why
didn't
I
merge
this?
That's
fine
I
guess
so
it's
approved,
and
why
does
this
need
to
be
manually
merged?
Because
it's
failing
that?
Why
is
it
failing
that
foreign.
B
B
A
Reminder
for
everyone
it's
going
to
be
at
1500
UTC,
especially
for
people
living
in
the
United
States,
because
we
are
hitting
Daylight
Saving
next
week,
so
the
next
meeting
will
be
at
1500
UTC,
please
be
sure
to
be
there
in
according
to
your
time
zone.
Thank
you
for
joining,
have
a
good
one,
and
thank
you
Sam,
for
all
these
hard
work
here
have
a
good
one.