►
From YouTube: EIP Editing Office Hour #1
Description
Working document - https://hackmd.io/@poojaranjan/EIPEditingOfficeHour
A
Welcome
to
the
first
eip
editing
office,
r,
thanks
to
everyone
who
joined
and
before
we
go
ahead
with
today's
officer.
Let
me
first
congratulate
all
the
eip
authors
behind
the
merger
paid.
We
have
bellatrix
activated
this
morning,
so
a
huge
congratulations
to
mikhail
kalanin,
dani
ryan,
vitalik,
buterin,
eip
editors,
client,
implementation,
team
and
everyone
supporting
the
upgrade
so
continuing
to
support
eip
authors.
We
have
started
this
eip
editing
office
hour
and
the
main
goal
here
is
to
invite
all
the
current
authors,
as
well
as
aspiring
authors,
to
show
up
on
this
meeting.
A
Thank
you
to
sam
wilson
for
volunteering
for
this
and
helping
out
with
the
questions
that
may
be
coming
up
from
eap
authors,
so
yeah.
Let
me
just
invite
him
to
maybe
provide
a
basic
details
of
how
eips
are
written
in
general,
common
mistakes
and
maybe
pro
tips,
and
after
that
we
can
pick
up
some
new
proposals
which
have
been
submitted
in
the
past
week
in
the
eips
github
repository.
B
Hey
thanks
puja,
so
I
guess
I'm
going
to
be
talking
about
eap,
editing
and
I'll,
be
here
to
answer
any
questions
for
authors
that
want
to
drop
in
and
say,
hi
always
feel
free
to
interrupt
me.
If
you
have
a
question
or
something
you
want
to
talk
about
specifically
say
your
your
eip
but
yeah.
So
I
guess
some
of
the
biggest
issues
that
we
see
in
eip
editing
are
just
not
following
the
template
correctly,
not
filling
out
the
preamble
properly.
B
You
know,
obviously,
spelling
and
grammar,
or
something
that
comes
up
pretty
often
and
mixing
up
the
motivation
and
rationale
section.
So
the
those
are
probably
some
of
the
biggest
easiest
mistakes
that
people
make,
and
you
know
over
the
next
couple
of
meetings
or
whatever
we'll
probably
see
some
examples
of
that.
B
If
and
yeah,
but
yeah
the
eip
process
shouldn't
be
too
onerous
and-
and
I
know
it's
a
kind
of
a
long
process
to
get
through
for
for
proposals,
so
we
kind
of
want
to
make
it
easier
for
everybody,
and
you
know
that's
why
I'm
here
so
drop
in
ask
questions
and
we'll
hopefully
be
able
to
get
you
through
the
process
quicker
thanks.
A
Thank
you,
sam.
That
is
quite
an
advice
like
yes,
these
are
the
common
mistakes
and
I
hope
that
this
can
be
less
seen
in
future
and
yeah
come
up
with
your
questions
so
maybe
for
today
we
can
start
with
couple
of
proposals
which
are
entrapped
some,
it's
totally
up
to
you.
If
you
would
like
to
screen
share
or
we
can
just
quickly
discuss,
I
can
list
the
numbers
of
pull
requests.
B
So
I
think,
right
off
the
bat
we
have
a
title
here
that
isn't
descriptive
enough.
I
think
we
could
do
a
little
bit
better.
B
B
It's
always
hard
figuring
out
how
long
to
make
titles,
because
they
they
do
have
a
very
strict
character
limit.
So
yeah
titles
are
like
hard
for
eips.
B
B
B
D
B
B
B
So
that's
technically
like
a
like
content
feedback
and
I
should
probably
be
putting
on
the
discussion
thread.
But
you
know
what
I
will.
B
Pull
request
only
for
like
feedback
on
the
formatting
and
and
like
not
on
the
content,
then,
and
the
discussion
throughout
the
content.
So.
B
D
B
And
then
what
else
there
was
something
else
I
wanted
to
say
now,
who
is
this.
D
D
A
B
It
sure
do
you
know
the
number
for
that
one.
No
two,
five.
B
These
ones
are
always
hairy,
so
what
is
this
doing?
This
is
moving.
A
Yeah
not
a
problem,
and
that's
why
I
thought
of
mentioning
it.
So
it
looks
like
panda
and
victor
discussed
whether
137
one
should
or
should
not
be
included.
B
Yeah,
I
kind
of
skipped
over
that,
so
I'm
of
the
stance
that,
unless
it's
required
reading
to
implement
the
eip,
you
don't
need
to
put
it
in
the
requires
header.
Other
eip
editors
have
a
different
stance
on
that.
It
just
really
hasn't
been
formalized.
B
A
That's
fine,
I
mean
looks
like
if
the
author
has,
he
put
it
in
mandatory,
I
mean.
B
He
was
in
required
like
20
and
173,
and
they
removed
it.
So,
okay,
yeah.
B
B
Cool
so
looks
mostly
fine.
Yeah
just
needs
a
few
other
little
changes
there
process
stuff.
C
B
B
A
One
other
one
is
about
the
last
call,
pull
request,
number
is
5506..
If
you
can
refresh,
you
will
find
it.
B
A
Do
we
need
do
we
need
like
a
dual
approval,
or
is
it
because
this
approval
was
not
on
the
github?
That's
why
we
are
looking
for.
B
So
it's
because
mr
chico
approved
it
and
then
they
changed
it
after
so
it
removed
his
approval.
So
now
we
have
to
wait
for
his
approval.
A
B
Yeah
yeah,
I
wish
people
would
just
add
themselves
as
authors
more
often
like
if
mr
chico
is
not
responding
like
quickly,
this
frangio
person
should
be
adding
themselves
as
an
author.
B
C
A
And
my
if
my
understanding
is
correct,
when
this
is
again
coming
up
or
with
updates,
we
may
have
to
revisit
and
change
the
last
call
date
and
they
tried.
D
B
B
B
B
A
I
think
that
covers
our
status
change.
We
can
go
with
the
rest
of
the
open
phone
requests.
D
B
B
B
Okay
transaction
flow,
because
refresh
is
an
item
from
online
retailer
checking
out,
leads
the
customer
to
an
option
to
mint
nft.
The
smart
contract
provides
the
user
with
a
digital
receipt
now
token,
when
fulfilling
the
order,
the
retailer
will
upload
the
digital
receipt
specifically
below
is
the
metadata
to
the
previously
mentioned
nmt.
B
All
right,
I'm
just
going
to
assume
this-
is
valid.
Json
schema
because
that's
fine
mine
items,
okay,
communion
previous
tools
to
show
our
receipts.
The
new
property
receipt
contains
a
new
provider
receipt
structure
and
the
signature
property
requires
the
vendor
to
digitally
sign
the
receipt
structure
interesting.
B
B
B
C
B
A
B
B
B
B
A
A
I'm
not
sure
if
this
is
appropriate,
but
I
would
like
to
make
a
mention
looks
like
the
other
editor.
So
the
author
may
have
originally
written
s-I-w-e
cap
quark
extension,
okay
capabilities.
It
is
with
eip
number
and
then
we
are
writing
it
sign
in
with
ethereum
so
yeah.
We
can
definitely
have
siwe
capabilities
right
if
they
want
to
have
it.
B
Yeah,
I
think
siwe
is
isn't
common
yeah.
I
get
that.
B
That's
sad,
isn't.
B
Okay,
so
consistent
capitalization,
there's
some
on
top
of
sun
with
ethereum
form
form
consent
to
telecom
capabilities
with
an
extensible
scope.
B
D
C
B
Yeah,
actually
I'll
be
right
back
just
give
me
one.
Second,
sorry.
B
A
B
B
Okay,
together
how
to
delegate
with
capabilities,
however,
key
authenticates
against
target
resource
is
out
of
scope
of
this
specification
out
of
scope
for
the
specification
and
depends
on
the
implementation
throughout
your
resource.
B
B
B
B
B
B
A
I
I
may
be
in
touch
with
the
authors.
I
have
invited
them
for
peeps,
so
if
there
is
anything
that
needs
to
be
positively
signaled
to
them,.
B
It's
not
super
important,
it's
just
the
way
they
write.
Specifications
is
like,
like
an
old
school
like
rfc
like
very
jargon
heavy
and
it's
like
eaps,
are
generally
written
more
accessibly.
There's
nothing
like
like
technically
wrong
with
it.
It's
just
style.
B
A
I
think
there
are
a
couple
of
points
that
I
would
like
to
mention
about
this
proposal
that
you
are
reviewing
as
the
sam
was
mentioning
earlier
about
the
common
mistakes.
A
One
of
those
is
the
eip
number
allocation,
so
yeah,
if
you
yeah,
if
you
are
listening
to
this
recording-
and
you
are
an
eip
author-
you
must
not
attempt
to
assign
the
eip
number,
and
this
cannot
be
any
random
number.
This
is
an
eip
editors
drop,
so
please
leave
it
for
them
to
assign
it
and
another
important
note
here.
I
see
this
proposal
is
dependent.
It
has
a
required
section
which
contains
another
proposal
which
is
in
review.
A
That
is
not
in
final
status,
so
it
may
be
fine
for
this
proposal
to
get
merged
as
draft,
but
when
it
comes
to
last
call
or
moving
towards
final,
it
is
very
important
that
the
proposal
on
which
your
proposal
is
dependent
must
be
in
final
status.
So
please
work
with
authors
of
proposal
whom
you
want
to
be
like
as
a
required
section
in
your
proposal,
yeah
and
that's
what
I
wanted
to
mention
about
it,
and
I
think
it
was
good
session
today.
A
This
was
the
very
first
session
for
eip
editing
office
hours,
so
authors
this
is
specially
dedicated
for
you.
Please
take
advantage
of
this
time
provided
by
eip
editors
and
do
join
us.
I
will
try
to
share
information
on
ech
github
as
an
agenda
and
also
in
the
related
channels
of
cataracts
discord.
Thank
you,
sam
wilson.
Thank
you
victor
and
everybody
else
joining
us
today.