►
From YouTube: EIP editor apprenticeship meeting
Description
Agenda: https://github.com/ethereum-cat-herders/EIPIP/issues/93
Resources
- https://eips.ethereum.org/EIPS/eip-1
- https://hackmd.io/@poojaranjan/EIP-ERC-Editor-handbook
- https://docs.google.com/presentation/d/1tG68sf9dq0U6_zy_zb_FmwePfMqkyTgGM1BPJkueriE/edit#slide=id.g10207481046_0_0
- https://hackmd.io/@poojaranjan/EthereumImprovementProposalsInsight/https%3A%2F%2Fhackmd.io%2F%40poojaranjan%2FEIPsInsightNovember2021
A
A
A
A
With
this
meeting,
I
hope
to
help
on
board
some
of
you
to
contribute,
as
an
eip
editor
in
turn,
to
be
working
closely
with
the
eip
editors
and
help
provide
the
support
that
is
needed
to
come
up
with
a
good
standard,
the
better
standard
for
ethereum
blockchain
from
the
cathedrals
team.
William
sharp,
has
been
helping
a
lot
on
eip
editing.
C
D
F
G
Yeah
hi
my
name's
chris
and
I
got
into
ethereum
or
just
became
interested
in
it,
beginning
of
2021,
and
now
it's
like
all
I
think
about.
So
I
would
love
to
get
involved
with
eip
editing
and
I'm
an
economics
student
right
now,
but
I
think
that
this
would
be
becoming
an
eip.
Editor
would
be
a
great
way
to
enter
into
the
space
and
kind
of
like
my
first
role
like
technical
role.
So
thanks.
D
A
H
Can
jump
in
hey
everyone?
I'm
john!
I
got
into
ethereum
around
when
cryptokitties
launched,
because
a
friend
of
mine
was
on
that
team.
I
didn't
actually
read
the
nft
spec
until
like
january,
and
then
I
just
fell
in
love
quit
my
consulting
job
started,
making
nfts
full
time,
and
I
heard
the
call
from
I
think
it
was
maybe
tim
on
twitter
because
we
follow
each
other.
That
eips
needs
some
some
nft
specific
love
in
particular,
and
I
hadn't
even
realized.
I
All
right,
I
think
I
can
go
next
hi,
I'm
everyone,
I'm
chi.
I
love
to
contribute
to
the
ethereum
community
in
a
way,
but
in
some
way
and
also
love
to
learn
more
from
it.
So
I
think,
being
an
eip
editor
gives
me
the
chance
to
do
both
at
the
same
time,
I'm
a
software
developer
full-time.
So
hopefully,
I'm
able
to
help
out
in.
J
A
K
All
right
so
I'll
go
next.
My
name's
mike
I
became
re-interested
in
crypto
earlier
this
year,
probably
january
february,
really
interested
in
on-chain
data
really
interested
in
on-chain
automation
and
basically,
how
we
can
democratize
d5,
make
it
kind
of
a
safer
space
for
everybody
being
playing
around
a
lot
with
nfts
and
like
trying
to
figure
out
like
how
we
can
make
things
more
gas
efficient
by
storing
on
like
decentralized
storage,
because
obviously
unchained
storage
is
really
really
expensive,
so
yeah.
K
I
think
this
is
a
great
thing
for
me
to
be
involved
with
and
just
kind
of
see
like
how
the
ethereum
community
is
evolving,
and
I
went
to
the
lisbon
conference.
I
went
to
eat
lisbon
a
couple
weeks
ago
after
taking
part
in
the
etho
online
hackathon-
and
I
know
like
ethereum
is,
is
where
the
evolution
is
is
happening
in.
In
my
opinion,
where
there's
a
sense
of.
L
I
guess
it's
yeah,
so
I
guess
so
hello,
everyone.
Let
me
turn
on
my
camera.
If
that's
possible
hello,
everyone,
this
is
shashank.
I
come
from
india
same
same
country,
puja
lives
in,
so
I
currently
work
as
a
vp
of
engineering
in
a
smart
home
company.
We
develop
smarter
products,
so
I
do
most
of
the
low
level
embedded
stuff
and
also
work
on
the
cloud
and
the
on
the
on
the
app
end.
So
I
basically
handle
all
these
software
efforts
that
is
happening
inside
our
company
similar
to
alpha.
L
Things
are
pretty
bad
at
that
point
because
they're
not
too
many
developer
resources,
but
yeah
things
are
looking
good
right
now,
so
I
just
wanted
to
hop
back
in
and
see
how
I
can
provide
my
experience
in
the
low
low
level,
stuff
and
understanding
the
architectural
level
distance.
In
the
ethereum
project,
that's
support
me.
A
So
about
the
ethereum
categories,
we
are
a
decentralized
project,
management
and
process
improvement
group
for
ethereum
blockchain.
We
are
trying
to
provide
any
and
all
help
that
can
be
provided
to
the
developers
and
the
client
team,
so
they
can
continue
working
without
bothering
about
how
how
to
be
communicated
with
the
rest
of
the
community.
Today
we
are
going
to
see
a
bit
about
the
eips.
A
I
used
to
call
it
a
building
block
of
ethereum.
It's
a
ethereum
improvement
proposals,
it's
a
design
document
that
describes
new
feature
process
and
information
and
based
on
this,
it
is
divided
into
further
categories,
a
little
bit
of
history.
So
it's
actually
coming
up
from
python
enhancement.
Proposals
which
were
pps
and
pips
were
inspired
by
these
peps
and
our
eip
ethereum
improvement
proposals
are
also
kind
of
inspired
by
peps
and
then
bes.
A
There
are
three
types:
standard,
meta
and
information.
A
standard
track
has
four
categories:
core
erc,
networking
and
interface.
Generally,
people
get
confused
about
erc
to
be
different
than
eip,
but
it's
not
erc
is
a
part
of
standard
track
eip.
So
it's
nothing
different.
It's
an
eip!
That's
what
we
need
to
know
these
information
are
provided
in
eip1.
A
A
A
The
quilt
team
is
also
working
on
maintaining
a
python
library
for
ethereum
execution
specs.
This
is
something
new
that
team
is
working
on.
As
I
mentioned
erc.
This
is
a
standard
type
eap.
These
are
ethereum
requests
for
comments,
so
these
are
application
level
standards.
So,
of
course,
nfts
are
part
of
them.
So
I
I
understand
someone
is
there
to
help
out
with
that
that
that's
going
to
be
really
great.
We
are
looking
a
lot
of
help
in
this
particular
category
of
eips.
A
Similarly,
on
networking
sites,
it
includes
improvement
around
deaf,
p2p
and
lifeline
protocols.
They
generally
follow
the
same
process
for
standardization
as
core
eips.
However,
these
are
disassociated
with
upgrades.
I
mean
they
don't
have
to
wait
for
an
upgrade
to
become
a
final
standard.
I've
added
an
example,
eap,
2124
that
is
fourth
identify
for
chain
compatibility.
This
is
like
one
of
the
most
active
in
discussion,
networking
eip
and
for
rest
of
the
proposals
you
can
visit.
The
link
provided
here,
meta
eip
is
by
the
name.
A
A
Earlier
we
used
to
keep
all
upgrade
related
information
in
meta
e,
but
recently
we
have
moved
all
these
information
in
execution,
specs
repo
as
upgrade
dot
md.
So
if
you're
trying
to
follow
any
upgrade,
you
can
find
the
information
on
that
particular
upgrade
name:
dot,
md
file,
informational
eips.
As
my
name,
these
are
just
to
describe
an
ethereum
design
or
information
about
anything
that
is
changing.
That
does
not
have
to
go
for
a
hard
fork
and
it's
just
a
community
guideline.
There's
no
mandate
that
it
needs
to
be
followed.
A
A
You
need
to
create
a
pull
request
at
ethereum
eip's
github
repository
matt
connect,
who
is
here
with
us.
He
he
shared
a
lot
of
valuable
information
on
one
of
the
episode
of
p
penny.
Actually,
that
was
the
very
first
episode
of
people,
an
educational
video
series
that
cat
had
us
run
to
describe
how
an
eip
should
be
documented.
A
A
A
A
A
A
If
everything
goes
well,
a
proposal
is
considered
to
be
an
ethereum
standard
that
is
available
on
the
repository
for
a
rest
of
the
community
to
follow.
If
adapt
developer
wants
to
develop
a
project
on
top
of
that
you're
more
than
welcome,
so
the
process
is
described
in
one
of
the
categories:
medium
block,
the
new
ethereum
improvement
process.
A
A
A
Definite
phases
is
the
phase
when
it
is
approved
by
client
team
and
they
have
put
it
into
a
developer's
test
net
and
then
comes
the
main
net
phase
where
it
goes
to
public
test
net
and
finally,
on
the
main
net.
But
these
this
network
upgrade
process
is
only
followed
by
one
category
of
eip,
which
is
called
as
a
core
eip.
A
K
C
Sure
I
think,
there's
like
a
pretty
big
discrepancy
right
now
between
the
amount
of
reviews
that
ercs
get
and
the
core
eips
get
so
for
corey
ip.
That's
going
to
be
reviewed
by
you
know,
editors
like
myself
and
micah
and
alex
and
we'll
make
sure
that
it
conforms
to
all
of
the
eip1
rules
and
everything.
C
And
then
you
also
have
a
lot
of
other
core
developers
who
are
reviewing
the
actual
content
of
the
eap
and
they'll,
bring
it
to
all
core
devs
meetings
and
have
people
discuss
it,
and
so
it
goes
through
like
quite
a
bit
of
review,
not
just
on
conformance
tip1,
but
also
is
this
a
good
idea?
Is
this
something
we
should
do?
C
I
tend
to
just
allow
them
to
do
that
as
long
as
there's,
nothing
like
egregious
happening,
but
the
quality
of
the
ercs
tend
to
be
like
a
lot
lower.
Because
of
that,
I
don't
have
the
time
to
like
really
go
through
and
depth
and
get
it
to
a
place
where
I
think
that
it
would
be
like
really
high
quality,
and
when
I
started
editing
that
was
kind
of
like
what
I
hoped
the
editor
position
would
be
in.
C
It
would
help
curate
like
a
really
strong
set
of
standards
for
ethereum,
and
I
think
that,
because
we've
been
like
understaffed,
it's
been
difficult
for
us
to
like
actually
do
that
kind
of
curation
it's
more
just
like
somebody
is
here
now
wants
to
make
a
standard.
Okay,
we'll
try
and
help
them
make
a
standard
in
a
way,
that's
readable
for
everyone
else,
but
we're
not
going
to
spend
much
time.
Thinking
about
like
does
that
erc
if
it
makes
sense.
C
K
Forth
yeah,
that
makes
sense
and
actually
what
I've
seen
aligns
pretty
well
with
what
you
said,
which
is
that
some
of
the
erc
standards,
like
you
actually
talk
to
people
in
the
community
you're,
like
you,
think,
having
no
knowledge
of
this
process
like
oh,
it's
an
erc
standard
like
this
must
be
something
that's
like
heavily
used
and
then
you
go
and
talk
to
people
and
they're
like
actually.
No,
that
is
not
really
the
most
optimal
way
to
do
it
or
something
like
that.
So
that
kind
of
aligns
with
what
I've
conversations
have
had.
C
Totally
it's
unfortunate
when
we
get
some
of
these
bigger
ercs
and
we
can't
get
consensus
from
the
community
on
the
right
way
to
do
it,
and
so
you
end
up
having
different
versions
of
basically
the
same
erc
where
you
have
like
different
prepended,
byte
values
or
like
slightly
different
things
in
the
signature.
And
so
now
you
have
people
implementing
essentially
the
same
thing,
but
they
just
couldn't
come
to
consensus
at
that
time.
H
C
C
Let's
do
that
and
they
don't
want
to
wait
around
for
something
to
get
standardized
and
so
they'll
just
take
it,
and
I
mean
that
even
happened
in
ethereum
like
we
chose
some
hash
function,
that
was
almost
standardized
and
then
we
freaking
changed
it,
and
now
everyone
uses
a
different
sha-3
than
we
use.
So
it's
like
really
easy
for
it
to
happen.
I
think
like
having
more
people
editing
would
help
avoid
these
situations
where
things
get
stuck
and
people
just
want
to
use
it.
L
Doesn't
eip
editor
also
involved
with
the
author
in
mentioning
that
the
technical
specs
are
not
meeting
to
certain
criteria
or
something
like
that,
or
can
they
add
their
own
input
as
to
how
it
can
be
improved,
or
is
the
eip
editor
just
making
sure
that
documentation
is
in
the
best
format
as
possible?
So
the
community
can
then
start
looking
into
that.
C
You
know,
is
it
the
kind
of
a
weird
balance,
because
it
tends
to
be
that
the
eip
editors
are
the
only
people
who
read
some
of
the
eaps
and
the
ap
editors
also
tend
to
be
really
knowledgeable
about
these
things,
and
so
they
tend
to
also
give
advice
on.
What's
good
and
what's
not
good,
I
think
like
number
one
job
is
make
sure
that
it's
readable
and
something
that
people
can
understand
and
communicate
about
and
then
secondary
is
you
know
hey.
This
is
technically
not
sound
for
some
reason,
or
this
is
potentially
a
better
solution.
H
A
C
Which
he
does
sometimes
he
does
sometimes
yeah
if
he
sees
that,
I
haven't
responded
in
a
week
or
so
he
might
like
go
in
and
say
something,
but
it
tends
to
be
I'm
the
only
one
who
edits
erc's
and
then
core
eips.
He
tends
to
get
there
before.
I
do,
but
you
know
normally,
when
we
have
had
like
multiple
people
actively
editing.
A
A
So
whatever
is
needed
to
make
it
as
a
very
good
standard
should
be
met
before
we
reach
to
the
last
call
generally,
what
happens
like
proposals
keeps
on
getting
passed
from
one
status
to
another
status
and
by
the
time
it
reaches
to
the
last
call
many
people
jump
up
suddenly
and
say
that
no,
this
is
not
right.
We
want
these
changes
so
yeah.
You
are
free
to
comment
anytime.
You
find
that
you
can
help
improve.
F
L
You
know,
I
think
it
was
a.
It
was
sam
wilson's,
p
penny
where
he
mentioned
that,
for
I
think
it
was
for
execution
specs,
so
it
would
fall
on
the
core
eip.
I
I
assume
right
am
I
correct
yeah,
so
I
think
samuelson
mentioned
that
some
changes
around
the
way
the
eip
has
to
be
written
and
the
code
has
to
be
added.
Regarding
that
and
elita
asked
in
the
follow-up
questions
that
will
the
eip
editors
require
any
programming
knowledge.
C
M
C
Yeah,
so
let
me
write
a
couple
in
here.
I
know
that
I
think
1559
is
a
great
like
a
good
eip
example.
I
think
that
2718
is
a
good
example.
I
think
3074
is.
These
are
three
that
I
think
are
like
pretty
well
written
and
if
you
like
also
follow
some
of
the
other
like
meta
information
about
the
eeps
like
via
the
discussion
link.
D
D
C
B
M
C
C
I've
like
left
some
reviews
for
the
the
author,
and
it's
just
at
some
point.
I
I
can't
like
force
them
to
write
it
in
a
different
way
and
like
the
unfortunate
thing
is,
is
that
ethereum
is
very
like
english
centric
and
I
think
it's
fairly
clear.
This
is
not
their
first
language
and
so
they've
been
like
struggling
to
get
it
into
a
place
where
I
think
that
it's
like
very
readable
for
community
members
and
I've
tried
to
like
leave
feedback
on
this,
and
I
there's
also
like
they
have
citation
here.
C
This
is
like
not
a
valid
thing.
I've
like
left
a
lot
of
feedback
and
we've
gone
through
a
couple
rounds
of
reviews
and
it
hasn't
progressed,
and
so
now
I've,
essentially
just
I'm,
I'm
just
kind
of
letting
it
sit
here
to
stagnate
until
the
bot
responds
if
they
continue
to
request
to
continue
to
push
like
we'll
have
to
see
what
happens
but
like
I've
done
a
fair
amount
of
reviewing,
and
it's
still
not
in
a
place
where
I
I
am
like
comfortable
merging
it.
A
I
think
an
erp
can
be
improved.
Like
you
know,
when
someone
is
trying
to
document
there
is
a
template
available
with
us.
It
is
the
link
is
available
in
eip1.
They
can
follow
that.
The
important
thing
here
is
to
follow
up
with
the
author
to
and
get
that
changes
implemented.
Whatever
are
the
suggestions
coming
up
from
eip
editing
team,
so
that
is
one
of
the
key
rules,
so
I
think
that
would
be
helpful
as
as
a
contributor
here.
C
So
josh
is
asking
if
editors
are
encouraged
to
help
technical
writing
circumstances
like
that.
Of
course,
we
have
infinite
time,
it's
great
and
especially
if
it's
like
a
higher
quality.
So
I
I
think
the
like
original
idea
of
that
is
kind
of
a
bit
of
the
duplicate
of
like
several
different
ercs,
that
sort
of
exist.
C
L
C
So
yeah
each
of
those
situations
would
be
different
if
it
was
final,
then
like
of
course
we
should.
You
know
shuttle
them
towards
that
eap
and
just
be
like
look
you're
proposing
something.
That's
already
been
proposed,
it's
been
finalized.
Can
you
use
this
or
not?
And
if
they
can't,
then
maybe
that's
a
reason
for
them
to
have
a
new
eap
if
it's
stagnant?
This
is
a
good
reason
for
them
to
create
the
eap
someone
like
had
the
idea,
but
they're
actually
going
to
champion
and
try
and
bring
it
to
finalization.
That's
totally
good.
C
If
there's
another
eip
and
review-
and
this
is
where
it's
like
really
valuable
for
editors
to
try
and
you
know
corral
those
two
authors
together:
hey
you
want
to
do
this
with
nft.
They
want
to
do
that
with
nft
they're.
Almost
the
same
thing
like.
Can
you
guys
just
work
together
on
the
same
eap,
erc
power
numbers
there,
and
hopefully
you
can
come
to
like
some
sort
of
agreement
where
you
can
both
use.
That
and
now
more
people
are
reviewing
and
looking
at
that,
and
that
tends
to
increase
the
quality.
H
C
We're
editing
yeah
totally.
I
think
so.
I
mean
the
way
that
I
did
it
was.
I
just
turned
on
notifications
to
the
github
repository
I
read
eip1
and
then
I
just
started
pretending
like
I
was
an
eip
editor.
I
would
put
a
review
in.
I
would
say
hello.
This
is
your
number
like
the
people
who
open
the
prs.
They
have
no
idea
who
the
editors
are.
They're,
like
this
person
responded
to
my
pr.
C
That's
an
editor,
and
you
know
when
an
editor
comes
in,
they
say:
okay,
look
like
client
has
responded
and
they've
made
some
good
points.
The
editor
will
continue
to
review
it
and
it
kind
of
just
like
reduces
the
amount
of
work
the
editor
needs
to
do.
They
can
sort
of
like
already
get
this
first
pass
that
this
other
person
has
gone
through
it,
and
now
they
can
like
focus
on
some
different
things.
C
So
if
like
you,
guys,
can
start
doing
that
right
now,
obviously
eip1
is
the
most
important
thing
to
have
a
good
understanding
of
these
calls
tend
to
be
like
me,
just
editing
together
with
people,
and
we
like
start
to
see
how
I
edit
and
that's
like
not.
You
know
the
absolute
canonical
way
mike
at
it's
differently
than
I
do,
but
it's
just
like
a
good
to
see
someone
who,
like
is
doing
it,
how
they
do
and
like
what
we
think
through,
and
so.
K
Oh,
I
was
about
to
say
that
I
was
actually
going
to
ask
the
question
of
well.
How
do
you
figure
out
if
there's
already
like
a
similar
proposal
and
then,
of
course,
there's
tags?
If
you
go
to
the
issues,
so
I
looked
for
like
erc,
and
then
I
found
this
really
interesting
token
standard
that
is
supposed
to
present
prevent
the
problem
of
like
contracts
receiving
tokens
that
they're
not
supposed
to.
I
think
it's
pretty
interesting,
but
yeah
I
was.
I
was
going
to
ask
that
question
like
do.
K
C
It
tends
to
be
more
built
up
knowledge
of
what
exists
in
the
eap
erc,
prs
and
finalized,
and
like
kind
of
where
they
are,
after
doing
this,
for
a
little
while
you'll
start
to
get
a
feeling
of
like
what
other
things
exist.
If
you
just
go
onto
eeps.com
eeps.ethereum.org
website
that
has
all
the
eeps
and
you
kind
of
start
to
like
see
something
and
you're
like
I've
reviewed
something
like
this
before
or
like.
This
reminds
me
of
this
other
thing.
It
doesn't
really
happen
that
much.
C
C
I
tend
to
ask
like
hey:
this
looks
a
lot
like
this
one
and
they
tend
to
say
it's
not
like
that
one
and
then
I
say
it
looks
like
that
one
and
then
they
say
no
and
then
I
merged
their
pr,
because
I
don't
have
time
to
like
also
hurt
all
the
nft
ercs
but
like
in
the
ideal
world,
with
some
sort
of
like
this
nft
working
group.
It
would
be
great
if
there
was
an
an
editor
who
was
also
part
of
that
group
who
was
able
to
like
bridge
those
two
worlds
and
say.
C
C
B
C
Yeah,
the
so
the
ci
what
the
ci
tool
does
currently
is.
It
checks
some
conformance
to
eip1.
So
there's
like
this
preamble
at
the
beginning
of
the
eip,
that
has
the
title
and
the
author
and
the
description,
the
discussion,
link
and
eaps
requires,
and
so
there's
a
validator
that
will
like
go
through
that
and
validate
to
make
sure
that
these,
like
all
conform
to
how
they
should
because
these
things
are
used
to
populate
some
of
the
web
page
on
the
eeps.ethereum.worksite.
C
So
that
validates
that
and
there's
another
eip
bot
that
elita
moore
has
worked
on.
That
does
a
little
bit
more
checking
and
it
actually
will
merge
things
depending
on
like
the
exact
situation.
So,
if
you're
like
creating
a
new
eip,
it
will
review
it,
but
it
won't
merge
because
an
editor
has
to
merge
the
initial
eap,
but
once
you
have
it
as
draft
and
you
put
a
pr
to
update
your
eap,
that
bot
will
actually
emerge
if
it
passes,
like
the
conformance
checks
that
it
does.
C
But
it
doesn't
do
like
more
intricate
things
like
it
would
be
great
if
we
could
go
through
and
we
can
make
sure
that
all
of
the
required
subheadings
of
the
eips
are
included.
Like
you
have
the
abstract,
you
have
the
motivation,
the
spec,
the
rationale,
the
backwards.
If
you
have
all
those
things,
it'd
be
great.
If
I
bought
check
that
and
then
like
you
said,
if
we
could
check
if
the
code
compiled,
that
would
be
another
thing.
It's
just.
C
A
A
L
C
C
C
Okay,
so
I
use
github
notifications.
Some
people
use
email,
just
like
whatever
you
feel
more
comfortable
with.
Neither
is
like
perfect
solution,
but
I
have
it
turned
on.
So
I
get
notifications
of
every
single
pull
request
that
happens
in
each
repository.
You
can
turn
it
on
also
for
issues,
but
I
find
that
just
as
long
as
I'm
reviewing
the
pull
request,
then
that's
what's
important.
There
was
an
important
one
that
I
need
to
review
and
let
me
see
if
I
can
figure
out
which
one
it
is
I'll,
also
just
throw.
B
C
C
C
Okay,
so
this
was
august
26th
when
it
opened
micah
reviewed
it,
and
then
I
reviewed
it
and
now
they're
planning
to
launch
it.
So
this
is
like
a
situation
where
he
opened
in
august
as
a
specification
and
now
they're
wanting
to
launch
an
implementation
of
the
eep,
and
the
problem
would
be.
Is
that,
like
we
haven't,
been
able
to
get
it
to
a
final
status?
C
And
I
I
don't
even
know
if
we've
gotten
this,
like
initially
merged,
like
three
seven,
seven:
zero,
we
haven't
even
got
it
merged,
and
so
this
is
like
probably
more
on
the
fault
of
the
eip
editors,
but
also,
probably
because
we've
left
feedback
and
it's
just
taking
like
longer
for
them
to
respond
and
get
it
done
so
now
like.
We
should
try
and
get
it
accepted
before
they
release
something,
because
then
you
get
into
the
situation
that
we
talked
about
where
they
release
something,
and
somebody
else
is
like.
C
C
C
Should
also
kind
of
review,
okay,
there
introducing
a
new
address
standard,
and
so
this
is
like
another
thing
that
frustrates
me.
I
don't
know
what
the
proper
way
of
spelling
dap
is,
but
I
feel
like
that's
not
it,
but
we
don't
really.
I
don't
think,
there's
a
style
guide
on
each
one.
That
explains
how
to
spell
that.
C
No,
we
do
have
a
style
guide,
but
it
refers
to
eap
numbers
and
this.
So
this
is
like
another
thing.
That
would
be
great
if
we
had,
but
we
don't
anyways.
They
have
that
this
emerges
from
increasing
adoption
and
non-maintenance
ethereum
change.
Yes,
so
they're
linking
to
these
chain
agnostic
caips,
I
don't
even
know
how
one
would
pronounce
that
this
is.
C
C
C
C
C
C
We
also
want
to
make
sure
there's
no
unresolved
complaints
about
the
vip,
because
it's
going
to
drop
is
like
less
serious
but
generally
sometimes
when
people
are
moving
things
to
last
call
and
the
final
there
might
be
outstanding
complaints
and
it's
important
to
make
sure
that
you're
not
finalizing
something
where
someone
in
the
community
was
saying
hey.
This
is
a
problem.
C
C
C
The
problem
is,
is
that
sometimes,
when
you
put
in
when
you
have
files
yeah,
so
it
says,
eap
must
be
named
like
that,
so
that's
probably
because
they're
adding
an
image
and
the
eip
bot
still
does
not
understand
image
formats.
So
we'll
just
like
look
and
we'll
just
visually
check.
Okay,
adding
all
these
things
that's
correct,
so
I'm
probably
going
to
have
to
force
merge
this
just
because
the
bots
are
not
doing
the
correct
job,
but
I
just
want
to
make
sure
that
that's
like
the
only
reason
it's
not
failing,
there's
not
a
misspelling
somewhere.
C
C
So
we
should
take
a
look
and
see
why
that's
happening
okay,
so
he
says
authors
here.
This
is
supposed
to
be
only
author.
So
that's
why
that's
failing
and
there's
a
trailing
space
right
there.
It
looks
like
so
I'm
going
to
review
that.
I'm
just
going
to
force
push
this
myself
because
this
has
been
sitting
for
a
while,
and
this
is
like
this
is
not
really
changing
the
meaning
of
the
epis
just
getting
it
to
it's,
just
getting
it
to
conform
with
the
eip1.
C
C
H
H
C
Oh
yeah,
I
mean
yeah.
I
wish
they
wouldn't
do
that,
but
I
also
you
know
I
kind
of
think
of
this
like
folders
their
little
sandbox.
They
can
trade,
however
they
want
and
if
they
want
to
double
up
on
their
ei
like.
I
don't
think
that
you
should
put
the
eip
name
in
the
name
of
the
file
in
the
folder.
It's
already
in.
C
A
Yeah
right,
I
would
first
like
just
kind
of
briefly
summarize
this.
I
understand
that
most
of
us
who
are
in
this
call
have
pretty
good
idea
what
we
are
expecting
with
this
position,
maybe
and
what
we
are
looking
forward
to.
So
we
are
just
trying
to
invite
more
participation,
to
maybe
add,
review
comments
and
improvement
suggestions
to
this
open,
pull
request
which
can
actually
help
us.
A
You
know
get
it
started
before
we
actually
at
the
last
call
and
communication
is
like
really
important,
like
lightline
mention
when
he
was
sharing
his
screen,
that
we
need
to
let
arthur
know
what
needs
to
be
done.
As
an
eip
editor.
I
think
it
is
very
important
that
they
should
know
what
we
are
expecting
because
many
of
the
people
who
actually
submitted
their
proposals.
They
are
new
and
they
don't
even
know
the
exact
format
they.
We
recommend
to
read
eap
one,
but
there
are
chances
that
they
might
miss
out
on.
A
So
it's
not
that
we
have
to
be
like
technically
skilled.
To
like
there
was
one
question
like
you
need
to
be
a
developer
to
be
able
to
review.
That's
an
added
bonus
point,
but
if
you
think
that
you're
going
to
help
make
it
better
or
you
have
interacted
with
people
who
are
trying
to
implement
this,
your
comment,
your
suggestions
are
going
to
be
helpful
and
we
have
planned
a
peep
meeting
with
matt
ganette
to
kind
of
list.
A
All
these
secrets
of
eip
editing
on
december
14th,
so
stay
tuned
for
more
information
coming
out
on
ethereum
cathode
is
discard
for
this
particular
meeting,
and
if
people
are
interested,
we
can
have
an
another
meeting
in
like
two
weeks
and
in
the
meantime,
you
guys
please
feel
free
to
post
your
questions
in
eap,
editor's
channel
at
the
ech
github.
We
hope
that
that
would
be
answered
before
the
next
meeting
and
yeah.