►
From YouTube: EIP Editing Office Hour 17
Description
Agenda: https://github.com/ethereum-cat-herders/EIPIP/issues/231
A
A
B
So
I
already
went
through
all
of
the
two
final
ones
before
the
call
so
6901
had
a
Content
change
recently,
so
we'll
have
to
restart
the
last
call
deadline
on
that
one
and
4910
I'd
like
to
review
offline,
because
it's
really
long.
A
All
right
not
a
problem,
so
those
with
okay,
perfect
and
you
have
already
immersed
rest
of
them,
which
were
there
so
we
can
quickly.
Okay,
before
we
move
ahead,
6901
author
Stephen,
I
I
believe
you're.
Fine
with
that
I,
don't
know
if
you
get
a
chance
to
take
a
look
at
the
comment
that
Sam
put
just
before
the
meeting.
D
B
D
B
It
literally
one
minute
ago,
it's
just
traditionally,
if
you
make
large
changes
to
the
content,
you
have
to
restart
the
last
call
deadline.
Okay,.
C
But
that
last
change
was
actually
more
days
ago.
Oh
was
it
okay,
I
mean
the
last
commit
probably
was
just
about
so
some
wording,
but
the
actual
interface
I
think
it
changed
like
10
days
ago.
B
Okay,
yeah
so
I'll
take
another.
Look
at
that.
I'll.
Add
it
to
my
to-do
list,
but
yeah
we'll
we'll
have
to
change.
The
last
call
deadline
a
little
bit,
but
maybe
not
the
full
two
weeks
so.
E
C
Yeah
I
will
just
look
for
the
last
time.
The
interface
change,
because
we
yeah.
C
Well,
yeah
yeah,
but
yeah
I
mean
all
substantial
changes.
I
think
we're
done
a
few
days
ago.
Okay,
yeah.
B
So
we'll
we
can
take
a
look
at
that:
yeah,
okay,.
A
Combo,
if
you
are
talking,
we
are
unable
to
hear,
but
if
you
have
any
question
specific
question,
please
share
with
us.
B
B
B
B
B
F
B
B
B
All
right
so
pretty
standard
feedback.
This
is
more
motivation,
because
this
paragraph
here
isn't
describing
like
a
choice
you
made
in
the
standard
itself.
I
think
these
are
okay
yeah.
These
can
stay
just
this
last
paragraph
should
be
in
the
motivation
section,
yeah
governance,
implementation,
good.
B
B
Okay,
so
as
a
non
editor
commented
more
as
a
technical
comment,
functions
that
are
generally
only
called
by
the
deployer
of
a
contract,
don't
necessarily
need
to
be
standardized
in
an
EIP,
so
this
set
holding
whitelist
address
function,
that's
kind
of
like
the
mint
and
burn
functions
that
open
Zeppelin
provides
like
it's.
It's
not
something
that
needs
to
be
standardized
between
implementations.
B
B
H
F
E
G
G
Well,
it's,
as
the
name
suggests,
we
bind
nfts
to
assets
primarily
physical
assets,
so
that's
this
term
vegetal
all
around
and
we
quite
often
the
physically
assets
are
bound
for
a
serial
number,
something
in
the
metadata
and
what
we
suggest
here
is
we
bind
it
directly
on
chain
to
the
Token
ID
one
to
one
and
Inseparable
over
the
whole
lifetime
of
a
physical
object.
G
Basically,
so
you
really
can
reflect
physical
objects
on
chain,
and
that
is
done
and
that's
a
bit
of
a
fancy
thing
through
an
oracle
authorized
transfer.
So
we
sign
an
attestation
of
chain
which
is
then
verified
on
chain,
okay,
interested
Oracle,
so
it
would
be
a
a
drawing
there,
which
makes
it
probably
easier
to
understand.
B
B
One
of
them,
I
think
was
by
plasma
and
it's
specifically
real
estate.
Have
you
talked
with
any
authors
of
like
similar
proposals
or.
E
We're
doing
well-
maybe
maybe
I
can
jump
in
here.
We
even
made
an
implementation
with
CIP
I'm
local,
by
the
way,
the
other
router.
Here
we
looked
into
southbound
tokens
first,
because
we
were
not
sure
how
which
way
you
want
to
approach
it.
Sorry,
who's
better
whose
parts
are
in
the
back.
E
Yeah
we
checked
saltbound
tokens
first.
E
And
we
made
the
first
implementation
on
EIP
5484
with
soul
bonds,
and
then
we
figured
that
this
is
not
covering
the
use
case.
We
looked
at,
for
example,
those
real
estate
EIP,
so
you
mentioned
it's
also
not
the
same
use
case,
because
it's
not
a
hard
link
between
the
asset
and
the
token
actually,
okay,.
E
And
this
is
a
real
Hardware
link.
There
are
similar
Solutions
like,
for
example,
the
erc721a
specifiers.
They
made
an
nft,
but
this
is
an
eoa,
so
then
a
new
highest
owner
and
we
don't,
we
don't
build
any
form
of
Chip
or
Hardware
or
something
like
that
into
into
the
physical
asset.
Actually,
okay,
we
just
have
a
passive
marker.
B
Okay,
so
this
is
mostly
just
a
formatting
thing
to
match
the
style
of
the
other
proposals,
but
we
normally
use
back
texture
signify
code.
So
if
you
wouldn't
mind
using
perhaps
bolded
text
or
or
just
something
else
to
other
than
backticks
for
the
for
those
that'd
be
great.
B
H
B
F
B
B
It
usually
it's
it's
at
most
one
or
two
paragraphs
so
like,
for
example,
like
a
an
asset
example
of
physical
object
is
equipped
with
an
anchor
is
probably
fine,
and
then
this
this
blurb
describing
like
the
properties
of
an
anchor.
You
can
probably
just
move
that
into
the
specification
section.
H
H
B
No,
it
looks,
it
looks
pretty
good
I
think
you'll
need
to
lower
case
this.
B
Okay
I
mean
like
quickly
looking
at
it.
This
looks
really
good.
It's
just
a
little
bit
much
to
go
through
on
on
the
call.
I
will
take
a
look
at
it
offline,
so
this
is
6956.
B
G
G
B
So
so,
yeah
just
just
kind
of
go
ahead
with
your
implementation
and
everything
and
just
update
your
proposal
like
it
should
be
fine
and
and
obviously
don't
wait
for
the
EIP
to
go
to
final
before
you
start
working
on
your
project.
This
is
kind
of
like
a
a
separate
process
that
you'll
be
going
through.
Okay,.
B
Cool
yeah,
so
I'll
yeah
I'll
get
through
that.
Sorry,
it's
taken
two
weeks
so
far,
yeah.
B
No
I
have
all
pings
turned
off
for
the
most
part,
or
else
I'd
be
swamped
with
people
asking
me
to
review
stuff,
and
so
I
will
yeah
it's
on
my
to-do
list.
I'll
take
a
look
at
it.
Yeah.
A
C
B
C
So
he
was
the
first
one
to
request,
changes
and
I
changed
them
right
away.
I,
don't
think
I
I,
don't
know
if
he
needs
to
if
he
specifically
needs
to
approve,
as
he
requested
it,
but
was
the
first
ones.
I
I
changed
yeah.
B
It's
just
Matt
sometimes
comments
with
the
like
hard
request
changes
option
which
means
that
other
people
can't
override
it.
Oh
makes
sense.
That's
all
it
is.
So
let
me
just
make
sure
that
his
all
of
his
changes
are
case,
so
you
approved
there
and
then
you
requested
changes
later
so
open,
zap,
lens,
solid
layer,
efficiency
who
can.
B
Yeah,
okay,
so
that's
done
and
then
did
you
have
any
other
blocking
changes
meant.
B
B
H
Yeah
hey-
this
was
hi.
This
was
actually
made
by
my
colleague,
but
he's
he's
not
here
right
now,
so
I
think
these
were
updated,
as
you
can
probably.
H
B
Was
just
the
pull
request?
Number
yeah
yeah.
H
Yeah
just
looking
to
get
it
reviewed
and
yeah
we're
not
very
familiar
with
the
whole
process.
So
that's
also
why
I'm
I'm
here
to
look
at
see
how
these
things
work.
B
So
the
probably
the
most
important
thing
for
you
to
take
away
from
this
call
is
that
this
is
very
author,
driven
every
status
change
like
going
from
draft
to
review
to
last
call,
that's
all
on
you
to
open
a
pull
request
to
do
that.
So
whenever
you
think
you're
ready
to
make
that
change,
just
go
for
it
and
then
yeah
we
aren't.
We
are
going
to
change
your
EIP
for
you,
except
through
comments
on
here.
Yeah.
E
H
I
have
to
just
a
second
because
I
have
discussed
with
my
my
colleague
about
this
as
well,
but
he
actually
had
to
move
away
from
his
apartment.
Now
they
and
he
couldn't
join.
B
I
B
Just
point
everybody
at
to
make
sure
everybody's
aware
of
all
the
other
ones
that
are
out
there
so.
C
B
Yeah
same
throttle
them
there,
Sports
interface,
okay,.
H
B
Yeah
yeah,
so
that's
good
function,
user,
payment;
okay,
it's
fine
test
cases;
okay,.
B
H
Oh
okay,
we'll
just
reference
that
perfect.
Thank
you
and
after
we
do
this
I'll
also
I
mean
I'll.
Also,
let
him
know
about
the
other
EIP,
the
4910.
B
H
It's
sort
of
we
well
I'm,
just
gonna,
let
out
say
that
we
kind
of
want
to
link
royalties
to
something
else
like
functionality,
and
then
we
want
to
keep
track
of
whose
paid
royalties
for
the
like:
okay,
identifiable,
transfers
and
yeah.
So
we
need
to
sort
of
keep
track
of
that,
because
just
somebody
going
to
the
Creator
and
paying
those
royalties
isn't
like
trackable.
B
H
Yeah
I
think
I
think
those
were
there
just
or
the
tests.
H
I
B
Okay,
then,
the
tests
yeah
Okay
cool,
so
yeah,
it's
just
if
every
project
includes
all
of
their
build
system.
Configuration
files
like
the
repository
grows
super
quickly.
So
we
try
to
keep
just
like
the
core
parts
of
like
the
reference
implementation
there
yeah.
So
sorry.
B
F
F
B
B
B
B
Completely
missed
the
point
of
this,
so
this
isn't
a
like
utility
functions
to
make
interacting
with
an
erc721
easier.
This
is
defining
a
concept
of
a
use
of
an
ERC
721
yeah,
okay,.
H
B
H
That
would
I'll
also
like
update
the
description
to
be
more
helpful
in
that
and
expressing
that
okay
I
appreciate.
B
F
B
Yeah,
just
my
my
reading
comprehension,
there's:
okay
I
must
have
okay
function.
Update
utility
set
utility
URI
get
utility
URI
so
who
can
set
the
utility
URI?
Is
that
yeah,
so
yeah.
H
This
was
this
was
mainly
for
the
creator
of
each
nft,
because
there
are
collections
that
have
like
multiple
creators
like
the
storefront
on
openc
or
other
places,
so
basically
I
think
it
would
be
related
to
there's
an
EIP
about
Creator
and
royalty
that
gives
you
the
Creator
address
for
each
nft,
so
I
think
that
would
be
a
possible
source
of
identification
either
this
or
the
contract
owner.
Okay,.
B
B
H
It
basically
just
adds
the
set
of
utilities
like
from
line
97
downwards.
H
B
Some
of
it
just
because
yeah
so
I'll
just
leave
a
comment
here.
B
B
You
know
what
I
don't
need
to
type
it
out
again:
yeah
I
every
week,
I
type
out
the
same
message:
it's
it's
great!
Okay!
This
standard
is
compatible.
Okay
test
case
is
good
yeah,
so
similar
thing,
I'm,
just
gonna,
be
less
polite.
Here,
don't
take
it
personally.
H
Yeah,
it's
the
test
cases
and
and
the
build
stuff.
It's
also
there,
because
so
we
kind
of
made
them
together,
so
yeah
makes
sense.
B
Okay,
good
CC,
you
know
this
needs
to
be.
This
is
0-1.0.
B
B
H
Awesome
and
then,
if
we
make
all
these
changes,
are
we
coming
back
two
weeks
from
now.
B
You
somebody
should
be
along
to
review
them
and
if
they
aren't,
you
can
definitely
come
back
but
yeah.
It
should
just
happen
on
its
own.
H
Okay,
so
in
case
the
the
merge
should
happen
by
itself
like
automatically
if
there
are
no
more
changes
requested
afterwards,.
B
So
an
editor
has
to
approve
it
so
it'll
either
be
me
or
Panda
or
Matt
or
like
client,
I
guess
but
yeah.
So
when
somebody
approves
it,
it'll
merge.
A
All
right
before
we
move
to
the
next
one.
There
was
this
question
in
chat
by
author
for
the
pull
request
in
last
call
6901,
I
I.
Suppose
you
have
mentioned
last
call
deadline
as
30th
of
May
and
is
checking
if
it
can
be
23rd
or
27th.
B
I
mean
the
safest
would
probably
be
I'm
fine
with
the
27th
yeah.
If
you
just
want
to
make
that
change,
yeah.
A
Sure
all
right,
so
the
next
PR
here
is
a
PR
6969
and
we
are
joined
by
Zach
Cole.
F
B
B
I,
don't
know
why
GitHub
keeps
the
the
old
annotations
around
it's.
It's
infuriating,
yeah.
B
Oh,
did
you
have
any
questions
that
you
wanted
answered
about
it,
or
are
you
just
waiting
for
somebody
to
merge
it
here,
yeah.
D
B
F
B
Yeah,
so
it
will
not
merge
unless
this
line
changes
to
6968.
B
D
It's
just
like
Kevin
is
gonna,
get
a
guy
I,
don't
believe
I'm,
not
I,
don't
know,
maybe
I'm
speeding,
I,
don't
know
if
he
is
or
not,
but
I
we
have
The
Magicians
yeah.
So
he
responded
in
the
comment,
but
he
didn't
update
the
document
itself.
Yeah.
D
The
conversation
yeah
I
can't
really
either
I
can
submit
a
PR
to
his
cork,
but
we
do
want
to
maintain
6969
adjacent.
B
Numbers
yeah
yeah
yeah.
So
if
you
submit
a
new
one
from
your
account
like
another
PR
with
six
nine
six,
eight
I'll
I'll
approve
it
like
that'll,
be
fine.
Okay,
just
make
a
note
of
it
in
the
description
or
as
a
as
a
comment
on
your
own
PR
that
it's
okay,
because
yeah.
F
D
F
B
Yeah
so
just
make
another
PR
exactly
the
same
content.
If
you
want
exactly
the
same,
commit
and
just
put
a
comment
on
it,
that
I
said
it
was
okay.
Okay,.
D
And
so
that
means
we
can
get
6968.
yep
yeah
for.
B
B
B
D
B
D
H
D
D
B
F
I
F
B
I
It'll
be
the
deployer
of
the
contract.
Okay,.
B
So
that
I
think
a
really
easy
way
to
resolve
this
rdf
data
kind
of
disagreement
we've
got
going
on
here
is
to
just
remove
it
entirely.
So.
B
I
All
right,
okay,
so
I,
just
let's
ask-
is
the
option
to
just
keep
that.
B
The
problem
with
it
is
it's
not
defined
like
if
there
was
a
specific
definition
for
this
struct
like
one
exact
rdf
data
struct,
then
it
would
be
totally
fine
to
keep
in,
but
because
this
isn't
defined
by
the
specification.
You
can't
implement
this
interface
like
completely
right,
like
somebody
can't
copy
this
paste
it
into
solidity
and
then
implement
it.
They
have
to
also
Define
this
rdf
data
memory,
struct
or
just
rdf
rdf
data
struct.
A
B
Yeah
I
think
this
is
just
another
case
of
me
not
reviewing.
B
B
J
H
B
B
F
B
I
also
can't
say
anything
that
really
needs
to
be
explained,
so
I
can't
really
help
you
there,
which
is
unique
request.
I
B
That
could
be
used
to
smooth
the
force
which
I'll
use
in
the
commit
withdrawal
function.
Okay,.
F
B
All
right,
otherwise,
I
think
it
looks
good
just
that's
it.
A
So
yeah
Sam
I
think
we
have
covered
pretty
much
all
for
whom
we
have
author
present
here
in
the
call.
But
there
were
a
few
other
authors
who
left
common,
but
we
didn't
get
to
take
it
today.
So
yeah
whenever
you
get
offline
time
to
maybe
take
a
look,
there
are
four
or
five
more
PRS.
A
B
B
Thanks
for
putting
this
together,
I
appreciate
it
talk
to
you
all
in
two
weeks.