►
From YouTube: EIPIP meeting 25
Description
Agenda: https://github.com/ethereum-cat-herders/EIPIP/issues/48
A
So
we
discussed
this
in
the
earlier
meeting
and
as
I
mentioned,
then
that
the
cat
hurdles
were
in
touch
of
epdm
or
people
and
we
were
trying
to
support
them
with
the
network
upgrade
stations
yesterday
and
he
left
some
comments
he
wanted
to
join,
but.
B
On
their
website
and
something
that
we
are
planning
to
have
on
at
one
dot-
oh
spec
repo.
So
if
we
can
just
sort
out
what
things
are
missing,
what
we
would
want
to
have
it
here,
then
they
would
be
happy
to.
You
know
point
at
point
back
to
at
one
or
back
repo,
for
whatever.
B
D
Yeah,
I
think
that
so
this
is
the
stuff
that
sam
talked
about
right.
A
So
there
are
three
sections:
basically
we
are
talking
about
here.
One
section
is
like
ethereum
wiki,
which
is
not
very
well
maintained,
so
they
are
owning
that
they
said
that
they
would
be
taking
json
rpc
from
there
and
try
to
update
that
information
and
have
it
on
ethereum.org
website.
That
is
one
option,
and
if
we
want
that
to
be
on
ethereum
one
dot
or
spec
repo,
they
are
willing
to
help.
A
So
it's
on
us.
How
do
we
want
to
proceed
like
I
believe
in
earlier
meeting,
we
discussed
that
we
would
want
to
have
some
developers
related
doc
on
ethereum,
one
dot
or
spec
repo,
so
that
client,
development
team
or
any
new
person
who
would
like
to
understand
how
what
are
the
specs
for
clients
they
could
find
it
here.
So
we
want
to
have
this
as
a
canonical
resource.
D
I
think
for
the
json
rpc
spec
specifically,
we
need
to
have
a
conversation
with
thomas
from
nethermind,
because
I
think-
and
maybe
micah
saw
this
or
like
client
saw
this
in
the
ethernet
just
discord.
Maybe
even
someone
else
like
james
in
the
chat.
I
think
they're
doing
a
call
on
this
every
other
week
or
something.
F
Yes,
that's
what
they're
planning
on
the
goal
of
that
group
is
tentatively.
This
is
the
first
meeting
the
goal
of
the
group,
so
it
sounds
like
they
want
to
clearly
specify
the
json
rpc
standard
across
the
clients
and
get
them
into
sync
basically,
and
so
that
is
a
project
that
they
are
actively
working
towards.
F
This
is
a
brand
new
group,
so
it's
always
an
unknown.
You
know
how
effective
a
good
new
group
is
going
to
be,
but
that
is
at
least
their.
D
Plan
yeah:
let's
just
ask
them
where
they
want
it,
I'm
gonna,
guess:
they're
gonna
do
github,
because
then
they
can
do
pull
request
more
easily
and
the
one
point
of
specs
repo
just
seems
like
a
better
place
in
my
opinion,
but
yeah.
Let
me
see
adding
a
section
and
then
linking
to
the
one.
Oh,
oh
I
see
so
the
the
I
think
sam
is
wanting
to
have
like
a
section
on
it
like
in
the
ethereum.org
site
that,
but
that's
not
the
canonical
source,
necessarily
it
links
to
github.
B
A
Okay,
is
it
better
now,
I
hope.
C
They'll
point
the
website
ethe.org
site
to
the
specs,
repo
opposite,
the
opposite.
D
B
D
H
B
C
C
Yeah
that'd
be
great,
there's
a
couple
things
that
have
floated
around
that
are
like
this.
Like
the
jason
rpc
spec
like
e365,
I
think
we're
on
or
e67
like
the
networks
specification.
C
D
Okay,
I
think
that
for
the
next
piece
yeah,
we
would
have
to
list
what
we
want
on
the
east.
One
point
of
spec
yeah
page.
That
makes
sense.
D
D
Help
yeah
and
pooja,
since
your
audio's,
cutting
in
and
out,
I
can
take
over
the
next
part.
If
you
want.
D
Sure,
okay,
so
the
next
one
is
network.
Upgrade
information
from
the
comment.
I
think,
because
we're
yeah
we're
doing
all
of
these
okay,
so
sam
spoke
with
puja
about
this
it'd,
be
great
to
collaborate
to
improve
the
ethereum.org
history
page
with
network
upgrade
information
because
there
is
piece
is
missing,
including
a
section
that
says
where
to
look
for
the
latest
stuff
on
that
so
and
where
to
follow
for
updates.
So
like
I
can
see
the
ethereum.org
history
page
having
like.
D
E
D
Of
it
yeah,
the
website
can
have
a
list
of
the
eips
once
it's
final,
but
the
one
point
of
specs
would
be
the
notional
source
and
then
the
ethereum.org
would
both
point
to
it,
but
have
a
list
of
the
summary.
D
That's
like
a
trend,
I
think
we'll
be
seeing
as
long
as
sam's,
okay
with
it
and
then
also
spoke
to
puja
about
eip
information,
so
summaries
list
of
links
and
discussion
resources.
D
D
C
F
There's
definitely
a
a
missing
piece
exactly
as
james
just
said,
where
you've
got
the
spec,
which
is
a
technical
specification,
it's
kind
of
motivation
section,
but
that's
meant
to
be.
You
know
just
like
a
brief
little
thing
just
to
get
people
in
the
mood
sort
of
thing
like
just
to
write
them
up
a
little
bit.
It's
not
meant
to
be
like
an
argumentative
essay.
It's
not
meant
to
be
like
a
an
opinion
piece.
F
It's
the
motivation
section
is
just
like
hey
here's,
some
things
that
this
would
be
useful
for,
like
here's,
a
short
list
of
uses
or
here's
a
few
benefits
we
get
when
playing
this.
Meanwhile,
of
course,
along
with
the
ip
there's,
also
the
opinion
pieces.
There's
the
user
stories,
there's
the
essays
there's.
The
analyses
that
are
being
done.
Eip
is
a
great
1.5,
is
a
great
example
of
this,
because
we
have
a
ton
of
this
stuff
and
there's
currently
no
place
to
put
that
right.
D
Okay,
but
I
think
the
summary
of
what
micah
was
saying
unless
mike
are
you
back.
D
You
were
talking
about
what
was
missing
or
the
the
fact
that
there
were
definitely
some
things
that
were
missing
and
there
were
articles
that
were
written,
that
provided
supplemental
information
that
could
need
to
go
somewhere.
F
D
A
I'm
sorry,
so
that
is
the
thing
that
we
are
proposing
here.
I'm
gonna
share
the
link
in
the
chat,
so
this
is
the
place
I
mean
like
on
the
ethereum
category
cat
header
website.
We
are
trying
to
curate
the
list
of
resources
for
any
eip
under
discussion.
For
example,
right
now
we
have
three
four
eips,
one:
five,
five,
nine,
two,
nine
three,
eight
evm
three,
eighty
four
and
all
the
stuff.
A
So
whatever
resources
like
other
than
the
eip,
the
at
magician
forum,
like
blogs,
published
by
you
and
others,
we
just
kind
of
curate
it
and
keep
it
there,
and
the
idea
here
is
that
that
should
be.
I
mean
if
we
can
make
it
publicly
available
with
the
help
of
ethereum.org
people
so
yeah.
They
are
thinking
in
this
direction
and
looking
for
some
thoughts
like
if
this
is
something
good
that
we
should
be
doing.
D
Moving
the
resources
from
cat
herders
website
to
ethereum.org
makes
sense
to
me,
because
that
consolidates
information
from
one
less
source,
because
no
one
really
goes
to
our
website
or
if
they
do,
they
just
want
to
know
about
the
cat
herders
and
if
we
start
trying
to
make
it
a
an
information
hub.
That's
gonna
be
like
the
seventh
information
hub.
D
So
although
we
should
have
something
on
our
site
about
like
stuff
like
hard
forks
and
where
to
find
information,
it
should
funnel
to
like
the
eip's
website
or
ethereum.org
or
the
ethe
1.0
specs
repo,
in
my
opinion.
So
it's
like
an
index
more
than
a
listing.
A
D
A
Okay,
we
will
bring
it
in
cater
this
meeting
as
well
and
then
see,
but
from
this
meeting
I
believe
that
people
are
having
positive
being
positive
towards
moving
the
entire
thing
to
the
ethereum
data
yeah.
That's
all!
That's
all
three
points
that
we
discussed
yesterday
and
we
wanted
to
mention
it
here.
D
A
Before
we
move
on,
I
just
wanted
to
have
some
clarity
on
the
next
step
like
who.
What,
when
kind
of
thing
as
per
my
understanding
james,
are
listing
the
resources
that
we
would
want
to
have
on
at
one
dot,
os
spec
repo,
and
then,
if
people
think
that
we
should
have
a
meeting
with
ethereum
our
team
to
and
with
nethermine
for
json
rpc
thing
we
can
arrange
for
that
or
how
do
we
want
to
proceed
about
it
like
in
the
next
meeting?
D
My
opinion
is
for
the
json
rpc:
let's
try
to
keep
that
asynchronous
and
text
base
in
the
all
core,
devs
channel
or
with
a
private
conversation
with
thomas
actually
there's
about
to
be
a
discord
channel
created
for
this
rpc
spec.
It's
going
to
be
in
the
eth1
section
of
the
ethernet
discord
likely
and
I'll
be
creating
that
in
the
next
hour.
So
let's
that'll
be
one
of
the
first
discussion
topics
in
there
and
if
we
need
a
call,
we
can
have
one.
D
But
let's
try
to
just
talk
it
out
in
there
first
and
then
what
do
people
think
of
that.
D
C
And,
as
far
as
like
me,
writing
up
a
list
about
what
shouldn't
shouldn't
be
there.
If
I
I
like
this
sort
of
organic
the
stuff
that
should
be,
there
seems
to
be
finding
its
way
and
not
having
to
be
not
having
to
dictate
it.
I
think
we'll
end
up
making
better
participation
from
those
involved.
We
want
to
bring
stuff
to
the
repository.
D
A
A
A
Okay,
okay
sounds
good
to
me
so
moving
on
to
the
next
item.
The
next
item
is
contracting
out
to
someone
to
move
the
bot
to
github
action.
So
it's
it's
a
link
if
you
click
the
link.
It's
coming
up
from
the
discord
conversation
a
few
meetings
ago,
we
discussed
about
looking
into
contracting
out
to
someone
to
move
the
bot
to
github,
but
I'm
not
sure
if
some
something
happened
or
like
we
had
some
decision
on
that.
A
So
on
the
request
of
micro
comment,
I
have
added
it
to
the
agenda
so
yeah.
My
guys
would
like
to
add
things
or
change.
F
Sure,
just
for
anybody
who's
not
aware
we
have
a
auto
merge
bot,
it
goes
up
and
down
has
bugs
needs
fixes,
like
any
other
piece
of
code.
Nick
was
the
original
author
of
it
and
he
it's
very
busy
other
things
and
doesn't
work
on
the
ap
group
really
anymore,
and
so
it
would
be
nice
if
we
had
a
new
owner
and
basically
nick
said
you
know,
this
should
really
be
moved
to
get
up.
Actions
I
agree
can
have
actions.
Are
the
perfect
place
for
it?
F
Github
actions
did
not
exist
when
you
wrote
it
back
in
the
day,
so
it's
a
new
tool
that
we
have.
That
just
makes
this
a
lot
easier
for
group
maintenance,
because
anyone
who
can
see
the
repo
can
see
the
action
and
tune
it
and
play
with
it,
and
it's
obvious
to
anyone
who
uses
github
so
generally,
a
good
thing
to
do
as
far
as
contracting
is
one
of
those
tasks
that
is
really
easy
to
outsource,
because
it
doesn't
require
really
any
null
much
knowledge
of
like
ethereum.
F
D
I
think
this
is
a
good
idea.
I
think
that
there's
a
bigger
issue
around
funding
that'll
be
a
completely
different
topic
and
today's
meeting,
if
we
have
time
or
a
different
one
once
I
have
more
updates
on
that.
But
I
think
this
is
a
important
enough
change
that
we
should
ask
the
cat
herders
for
funding
for
it
now
that
their
treasury
has
gotten
bigger
from
the
price
increase,
especially
if
we're
going
to
be
paying
out
an
eth
or
something
like
that.
D
F
A
Yeah
but
I
believe
getting
an
estimate
of
what
amount
of
funding
or
the
effort
that
we
are
looking
for
here
would
be.
You
know,
help
us.
D
Yeah
that
would
be
helpful
for
a
cat,
herders
decision.
Micah,
do
you
have
any
ideas
or
anybody
else
in
the
call.
F
I
mean
this
is
one
of
those
things
like
it
depends
on
the
skill
level
you
hire
and
whether
the
person
already
has
at
least
some
knowledge
of
how
this
works
like.
If
you
were
to
hire
like
like
client
or
me,
it
would
be
an
easier
job.
They've
hired
someone
stranger,
but
I
think
my
client
and
me
both
are
going
to
be
more
expensive
and
have
a
little
time
available.
C
F
So,
for
me,
I've
used
github
actions
all
of
one
time
and
I
used
an
office,
basically
an
off-the-shelf
action,
and
it
took
me.
You
know
a
few
hours
to
figure
out
how
to
use
github
actions
how
to
make
the
off-the-shelf
action
work
which,
like
pick
from
a
marketplace,
fill
in
my
my
things,
then
a
couple
hours
to
fix
it
because
it
didn't
work
on
the
first
try.
F
Of
course,
this
would
be
a
more
complex,
github
action
in
that
it's
got
custom
code,
but
I
think
github
actions
can
run
basically
any
language,
so
you
can
run
python,
you
can
run
javascript
whatever,
and
so
whoever
you
hire
would
presumably
work
in
a
language
they're
familiar
with,
and
so
if
they
already
know
github
actions-
and
they
already
know
their
language.
D
C
F
F
That
was
in
review
and
that's
like
a
month
or
two
later
and
the
bot
just
broke,
like
you
just
choked
on
that
entirely,
and
so
ideally,
we'd
have
someone
that
you
know
we
can
call
up
and
we
better
on
a
retainer
or
whatever.
That
means,
where
you
say:
hey,
there's
a
bug,
you're
looking
for
some
more
work.
That
being
said
once
in
github
actions,
I
think
it'll
be
easier
for
us
to
swap
out
people
to
work
on
it.
So
if
they're
not
available,
we
can
find
someone
else.
D
The
average
developer
salary,
according
to
the
first
post
page
in
google
for
a
python
developer,
is
110
000
per
year.
Therefore,
if
we
were
to
take
math
and
do
math,
then
that's
hard,
we
would
do
a
hundred
ten
thousand
dollars
per
year,
divided
by
twelve
divided
by
sporty.
F
D
Okay
53
an
hour,
so
it's
53
an
hour
and
let's
say
we
do.
We
can
be
a
little
liberal
with
this
and
say
two
weeks
of
work
so
or
we
can
get
the
hourly
rate.
First,
that's
like
a
good
starting
thing,
so
57
an
hour
and
then
we
could
say
two
weeks
of
work
to
implement
and
write
documentation
for
it
and
then
one
week
of
service
with
the
idea
that
we
can
also
hire
them
again
for
more
larger.
D
D
A
Something
between
six
to
ten
k
would
be
an
ideal
one
for
you
know
if
you
want
to
go
ahead
with
this
thing,
but
I
mean
I
don't
know
it's,
it
would
be
my
personal
preference,
like
people
who
are
already
involved
here,
should
go
ahead
with
that.
But
what
do
people
think
should
we
with
some
kind
of
bitcoin
bounty
or
try
to
reach
out
people
who
are
already
engaged
here.
D
I
like
the
idea
of
setting
a
precedent
for
a
git
coin
bounty
because
that
could
attract
more
people
to
both
eip
stuff
cat
herders
ethereum.
In
general,
I,
like,
I
always
like
the
idea
of
bringing
brand
new
people
in,
especially
if
we're
charging
this
much
for
someone,
that's
more
python
than
aetherium.
D
D
Yeah-
and
this
also
so
me
trying
to
fund
eip
things
for
the
future
from
different
organizations,
if
we
can
set
a
precedent
of,
we
might
make
another
gnosis
say
for
community
fund
for
eip
editors
and
for
related
eip
related
tasks.
We
can
say:
we've
already
done
this
once
and
it
worked.
A
Okay,
moving
on
the
next
item
on
the
agenda
is
a
single
source
of
truth
for
eip.
I
guess
brent
is
working
on
that.
G
Yeah
yeah
I've
haven't
had
a
lot
of
time
to
work
on
this
yet
and
I
think
I've
been
trying
to
educate
myself
around
what
all
the
sources
of
information
are
and
I
think
I'm
getting
out
of
hand
and
getting
lost.
But
so
I
think
what
I'm
the
first
task,
I'm
going
to
focus
on
doing
is
just
there's
two
sources
of
truth.
G
Evidently,
there's
the
eip.etherium.org
and
there's
also
ethereum.org
eip,
and
the
latter
is
only
referenced
by
a
few
people
on
the
internet,
where
the
former
seems
to
be
by
far
who
everyone
points
to,
and
so
I'm
just
going
to
focus
on
getting
the
etherium.org
eips
get
that
to
redirect
to
the
eip.etherium.org
and
that
just
at
least
do
that
first
and
just
focus
on
that
task.
So
does
anyone
else
have
any
other
thoughts
on
that.
A
G
A
A
Okay,
so
moving
on
the
next
item
is
eip
status.
Change
update,
like
the
categories
have
been
working
with
eip
editors,
sorry,
eap,
authors
for
the
proposals
which
are
in
a
draft
status
or
maybe
not
in
the
correct
status,
even
if
it
is
in
like
in
review,
it
is
even
if
it
is
in,
like
last
call
it
is
more
than
a
month
or
so
so
we
are
trying
to
reach
out
to
those
authors
and
asking
them
to
change
their
status.
So
we
made
some
progress.
A
I
think
at
least
three
of
the
eips
we
closed
last
week
I
mean
closed.
By
close,
I
mean
that
it
wasn't
draft
status
now
they
are
in
review
and
for
berlin
eip.
I
I
think
there
are
three
eips
which
are
still
in
draft
and
that
they
that
they
need
to
move
into
review
status.
If
there
is
no
change
done
by
the
author
this
week,
we
will
be
creating
a
pull
request
to
change
it
to
review
the
eips
are
yeah
ip2718,
eip2929
and
eip2315.
A
All
these
three
are
in
draft,
so
we
would
like
to
have
that
in
review
other
than
that,
with
the
help
of
p
penny
series,
we
interacted
with
quite
a
few
authors
and
we
suggested
them
to
make
a
request
to
move
on
their
eip
from
draft
to
review,
but
there
are
quite
a
few
which,
which
hasn't
created
any
pull
request.
Yet
if
they
are
not
done
by
the
end
of
next
week,
cat
headers
will
be
reaching
out
to
them
and
try
to
create
a
pull
request
to
change
the
yeah.
That's
the
update
here.
B
A
Okay
yeah.
Thank
you,
micah.
I
have
seen
that
you
have
already
closed
this
thing.
So
yes,
I'm
happy
to
contribute
here.
I'm
I'm
also
looking
forward
like
many
eips
are
still
draft
status.
When
I
look
at
it,
I
still
get
confused
why
they
are
there,
even
if
they
are
not
active
for
over
two
years.
So
yes,
okay.
Moving
on
to
the
last
item,
that
is
a
review
action
item
from
the
previous
meeting.
A
There
are
one
this
one
decision
and
two
action
items
that
removed
linked
eips
on
eip1
that
are
dead.
I
have
already
created
a
pull
request
to
remove
this
eips,
which
are
not
like
active
right
now.
They
were
just
from
the
pull
request.
They
never
made
it
to
the
eips
dot,
ethereum
dot
com
and
the
pull
request.
A
Number
is
three
two
one,
eight
so
micah
like
client
hudson
all
editors
if
they
would
want
to
give
it
a
look,
and
yes,
we
can
close
that,
if
that
is,
if
there's
nothing
wrong
with
it
and
then
next
two
action
items
where
james
is
collecting
ideas
for
a
single
source
of
truth,
which
he
will
report
on
the
next
meeting
and
james,
would
be
working
on
hard
fork
information
into
at
one
dot,
respect
repo.
A
So
I
think
james
yeah
james
would
be
working
on
this
and
where
you
have.
C
The
berlin
specification
is
on
the
website.
They're,
the
previous
hard
forks
are
not
there
yet,
and
I
think
we
have
a
pretty
good
list
now
of
stuff
that
we're
thinking
about
adding
to
them.
So
I'm
pretty
happy
with
where
that's
progressing.
A
Yeah,
that's
that's
really
good
and
the
next
one
is
adsense
to
work
on
the
eip,
editor's
rules
and
responsibilities
block.
B
A
D
Just
refresh
it
funding
for
eip
editors,
etc,
I'm
starting
to
have
more.
I
have
an
idea
of
how
to
do
this,
based
on
other
models.
We
have
a
few
different
options.
I
think,
as
everyone's
seen
open
grantsio.
D
D
Yes,
but
there's
a
specific
page
that
like
uses
it
dang
it,
why
can't
I
remember
it
all
right
either
way,
it's
a
it's
a
website,
I'll
I'll,
have
to
find
it
later,
where
everybody
pulls
their
ether
together
into
a
contract
that
over
time
gives
out
ether
to
a
set
of
participants
in
a
multi-sig
based
on
milestones.
D
D
F
I
don't
have
preference
on
the
logo
side
of
things.
What
would
be
the
milestones
you
had
in
mind.
D
Oh,
it
wouldn't
be
that
complicated.
It
would
just
be
like
being
an
active
eip,
editor
based
on
consensus
among
x,
number
of
people
or
something
I
don't
know,
I'd
have
to
think
more
about
what
the
milestones
would
be,
but
it
wouldn't
be
anything
like
x,
number
of
pull,
requests
handled
or
anything
like
that.
That
would
have
take
someone
an
extended
amount
of
time
to
actually
calculate
because
yeah,
that's
we
don't
need
to
waste
time.
C
That's
some.
I
don't
some
like
it's
still
not
really
clear
who
gets
to
choose,
who
gets
to
be
vip
editors
or
like
who
would
not
get
funding.
D
C
D
The
eip
editors
who
are
currently
on
there
and
kicking
people
off
who
aren't
active
would
be
step
number
two
one
or
two,
and
then,
if
we
decide
to
go,
that
is
if
we
decide
to
go
that
route,
it
might
be
complicated
to
use
a
brand
new
thing
like
that,
and
then
we
can
go
the
traditional
gnosis
safe
with
companies
who
have
a
voice
in
deciding
where
their
money
goes,
or
they
can
delegate
to
the
eip
editors
themselves
who
to
pick
among
themselves
and
have
like
a
third
neutral
party
like
the
cat
herders.
H
C
D
D
F
D
We're
making
a
new
term
okay,
we're
groundbreaking
again:
okay,
yeah,
so
yeah
I'll!
Think
on
this
more
and
if
you're
interested
I'll,
probably
move
the
discussion
to
eip
editing
and
the
discord.
A
D
A
A
If
not,
thank
you
all
for
joining
us
today.
The
next
meeting
is
in
two
weeks
from
now
that's
on
february
10
at
1500
utc.
Thank
you.
Everyone
for
joining.