►
From YouTube: Ethereum Cat Herders Meeting #43 [2020/10/13]
Description
Agenda:
https://github.com/ethereum-cat-herders/PM/issues/140
A
A
A
A
Let
me
just
pull
up
so.
According
to
the
clients
update
provided
in
the
meeting,
the
hyperledger
leisure
basu
would
stand
up
a
pure
test
net
with
some
changes
like
they
have
accepted.
The
wrapped
transaction
pr
submitted
by
mikka
forget
vulcanized
team
is
trying
to
debug
a
consensus
issue
that
they
were
having
on
the
f
mirror
test
net
poi
test
net
for
nether,
mind
eip1559
is
syncing
and
the
syncing
with
the
test
network,
and
they
will
continue
to
work
with
basu,
get
another
mind
team
together
to
adding
another
mind
validator
soon.
A
A
Where
projects
and
dab
developers
were
excited
to
see
this
proposal,
the
proposal
eip15599
to
be
deployed
on
the
main
net
as
early
as
possible.
The
miners
community
expressed
their
dissatisfaction
and
the
main
benefit
that
was
highlighted
by
the
projects,
was
the
predictability
of
gas
prices
that
is
provided
by
this
proposal.
B
Do
we
want
to
continue
the
outreach
project
even
now
that
the
article's
written
like
there
were
even
sort
of
like
entire
categories
of
stakeholders
who
were
not
reached
so
in
the
interest
of
just
having
the
information,
even
if
it
doesn't
necessarily
lead
to
a
blog
post?
Are
we
interested
in
sort
of
continuing
to
comes
effort,
or
is
this
going
to
be
the
end
of
it?.
A
No,
I
I
assume
that
there
is
going
to
be
a
wave
two
of
the
outreach
efforts.
This
time
we
are
trying
to
target
more
on
wallets
and
exchanges,
because
they
were
low
participation
last
time
and
we
would
also
try
to
reach
out
to
the
service
providers
because
they
would
be
the
projects
where
the
changes
are
expected.
They
are
providers.
They
need
to
do
some
changes
on
their
end,
so
my
assumption
would
be
like
we
would
be
doing
a
wave
two
of
that.
However,
if
people
are
interested,
what.
B
A
A
The
next
item
is
eipip
meeting
update
in
the
last
eipip
meeting.
We
discussed
about
network
upgrade
process
flow.
I
shared
some
concern
with
eip
statuses,
not
getting
changed
even
at
the
time
of
it
being
deployed
on
the
main
net
and
the
general
sentiment
was.
It
will
be
good
to
have
it
updated
for
that.
A
The
agreement
was
to
have
a
twitter
handle,
from
which
the
change
of
the
aip
statuses
can
be
shared
with
the
community.
Thanks
to
light
client,
he
secured
a
handle
at
eip
info
and
I
have
shared
the
credentials
with
james
because
he
mentioned
that
he
would
be
interested
to
you
know
tweet
about
that
and
handle
it.
But
if
any
cat
header
also
wants
to
get
involved,
feel
free
to
get
in
touch
with
james.
A
A
It
will
be
helpful
to
you
know,
set
expectations
for
editors
and
get
more
people
involved
so
that
we
can
iron
out
the
process
of
the
new
process
of
eip
standardization
and
and
like
look
into
more
proposals
and
get
it
faster,
because
now
we
have
only
one
active
editor
that
is
looking
into
it,
and
one
of
the
agenda
item
for
next
meeting
is
from
his
side.
Only
any
comment.
Questions
on
this
part.
B
A
Right
I
mean,
like
I
see
that
cat
headers
are
getting
engaged
more
in
the
eip
ip
meeting
like
in
more
into
the
process
part.
So
if
anybody
would
have
any
suggestion
on
in
the
improvement
park
or
something
that
could
help
improve,
the
current
process
would
be
highly
encouraged,
and
that's
why,
like
we
have
started
creating
agenda
way
in
advance,
so
that
people
can
go
and
add
their
comments
like
what
they
would
like
to
discuss.
B
B
B
Would
probably
make
the
process
significantly
more
efficient
or
even
just
calling
attention
to
eips
that
need
attention
given
to
them.
So
I
mean
hearing
that
as
an
initiative
makes
a
lot
of
sense.
I
can't
say
that
I'm
really
up
for
spearheading
it
right
now
and
it
sounds
like
edson
from
what
you
mentioned
may
be
taking
initiative
on
a
project
like
that.
It
would
be
very
interesting
to
see
where
it
goes.
B
I
mean
to
some
degree
it
could
be
that
the
process
is
fine,
just
that
it
hasn't
scaled,
very
well
with
the
manpower
that
it
has
right.
Now
and
it'd
be
interesting
to
see
if
perhaps
giving
the
like,
you
know,
scaling
the
amount
of
people
working
on.
It
might
be
enough
just
to
make
it
a
much
more
efficient
process.
A
Right
and
now
with
the
new
bot
like
we
have
like
in
process
of
getting
a
pr
close
if
it
is
stagnant
for
a
while,
and
I
myself
have
seen
some
of
the
proposals
getting
close
because
they
weren't
able
to
cut
proper
attention
from
the
editors.
So
it
would
be
better
to
you
know
close
a
proposal
after
making
a
decision
on
certain
proposal,
not
just
because
it's
not
getting
editor's
attention.
A
A
It
seems
like
the
biggest
desire
to
go
with.
That
was
to
avoid
memorable
complexity
of
introducing
past
batch
transaction
that
was
proposed
by
litecoin,
and
there
wasn't
any
consensus
on
the
transaction
time
that
could
be
introduced
in
berlin
so
until
the
next
upgrade
or
until
there
isn't
any
agreement
on
the
best
mechanism
like
client,
would
be
working
into
looking
the
batch
transaction
complexity
and
understanding
the
complexity
of
mempool.
A
A
A
So,
with
the
help
of
this
series,
we
are
trying
to
socialize
the
ethereum
proposal
and
at
present
I'm
not
aware
of
any
other
forum
where
such
discussion
happens.
So
it's
an
opportunity
for
community
to
learn
about
the
core
proposals
and
for
the
developer
community
to
also
share
their
questions
if
they
have
anything
on
the
erc
or
any
or
the
standard
track
proposal.
B
Had
I
had
the
eip
I
ran
into
like
yesterday?
Actually
so
I
just
reached
out
to
the
author
to
see
if
he'd,
if
he'd
respond,
I'd,
have
to
get
the
number
again,
it
might
be
23.80.
No,
it
wasn't
that
far
1837,
maybe
refungible
tokens
sort
of
like
an
idea
for
splitting
nfts
and
trc20s
wait
a
second.
Where
are
we
1634.
A
A
B
So
the
truth
is,
I
really
need
hudson
here
for
that.
The
one
thing
that
I
could
say
is
that
we've
got
there
have
been
two
documents
that
we've
written
internally
so
far
about
protocols.
We
got
them
to
a
point
where
we're
happy
trying
to
start
to
share
them
a
bit
and
get
ready
to
get
feedback
from
the
community.
Hudson
took
point
on
point
on
that,
and
I
I
don't
know
where
it's
holding
right
now,
so
I'd
I'd,
sort
of
need
him
to
figure
out
where
that
next
step
is.
A
B
B
A
The
next
item
is
cat:
head
is
funding,
moloch,
tau
and
esp.
I
do
not
have
updates
on
molok
talk
part
because
again
we
have
to
check
with
him
on
with
hudson
on
that,
but
I
heard
from
some
of
the
esp
people
and
they
are
happy
with
the
work
that
we
are
doing
as
cat
hurt
us,
that
we
are
taking
care
of
supporting
the
network
upgrade
process
and
the
the
newsletter
that
we
publish
the
cad
headers
update
that
we
published
are
really
appreciated.
A
A
Yes,
I
mean
generally,
even
if
people
do
not
read
it
immediately
when
it
is
published.
If
that
is
there
in
the
inbox,
they
get
the
notification
of
that
sometimes
later
they
pull
it
out
and
start
reading
it,
and
because
our
cat
holders
update
are
mostly
covering
the
minute
related
information.
What
is
going
on
in
ethereum
one
chain
and
theorem
two
chain,
and-
and
you
know,
proposals
around
that,
so
it's
helpful
for
people
for
keeping
track
of
a
network
upgrade.
A
B
A
Not
really,
I
don't
know,
maybe
I
came
across.
Maybe
this
is
a
new
feature
of
medium
or
what
I
may
have
to
explore
more
on
that,
but
I
think
medium
also
provide
this
facility
of
you
know
whatever
you
are
publishing
here,
get
it
sent
through
a
newsletter
or
something
I
may
have
to
look
into
that
or,
if
not,
then
maybe.
B
A
D
B
C
A
So
generally,
when
we
publish
this
cat
address
update,
I
tend
to
share
it
in
reddit,
linkedin,
twitter
and
everywhere
else,
so
somebody
reading
it
on
you
know
youtube
or
something
yeah.
That
would
be
interesting,
but
again
that
would
be
something
a
good
amount
of
work
would
be
needed
for
that,
and
we
might
deal
with
somebody.
B
A
Yeah
and
also
like
right
now,
I'm
the
only
one
who
is
writing
these
newsletter.
I
mean
these
chat
editors
update
earlier
a
few
more
people
joined
and
they
were
doing
that
and
we
had
this
feedback
from
the
foundation
that
it
would
be
good
to
engage
more
people
like
you
know.
The
write-up
coming
up
from
different
people
will
give
an
impression
that
everyone
is
like
you
know,
equally
participating,
so
it
would
be
good
for
the
group
as
a
whole.
So
if
anybody
is
interested.
B
I
could
probably
contribute
I
mean
the
basic
the
the
newsletters
in
general
basically
are
just
a
recap
of
the
subjects
that
we
discuss
in
the
calls,
also
just
sort
of
like
the
proof
of
work
if
you'll
forgive
a
pun
of
what
we've
done
over
the
last
two
weeks,
so
I
mean,
if
it's
broken
into,
if
it's
broken
down
into
different
subjects
like,
for
instance
like
if
there's
going
to
be
a
paragraph
on
emergency
comms
or
something
like
that,
I
I
could
contribute
writing
to
that.
That's
not
a
major
investment
on
my
part.
B
I
think
the
easiest
thing
for
me
would
be
if,
when
you're,
I
don't
know
exactly
what
your
method
is
for
writing,
but
if
it's
broken
into
categories
first,
even
before
you
start
writing
it,
and
you
can
give
me
like
a
look
at
the
categories.
It
should
be
easy
for
me
to
see
if
there's
something
there
that
I
can
easily
pick,
because
I
sort
of
know
what's
going
on
with
it
and
maybe
put
in
a
paragraph
or
two
on
it.
B
A
Yeah
I
mean
that
is
generally
the
idea
and,
like
personally,
what
I
do
is
like.
I
focus
on
every
meetings
that
we
have
here:
every
public
meeting,
ethereum
one
meeting,
ethereum
two
meeting
and
all
sort
of
meetings
where
cat
headers
are
engaged.
I
tried
to
pick
up
those
put
highlights
over.
There
share
their
notes,
that
is
done
by
the
cat
holders
itself,
and
there
is
one
section
about
community,
like
whatever
is
going
on
in
other
section
for
one
particular
section,
so
that
is
there
I'm
going
to
share
this.
A
B
Read
and
I
have
read
the
newsletters-
this
is
more
of
a
question
of
your
method
like
it
could
be
something
that
would
really
help
you
with
engagement
would
be.
If-
and
I
don't
know
if
this
is
the
way
you
do
it-
I'm
just
going
to
pull
an
example
from
myself.
Usually
when
I'm
doing
the
notes
for
say
core
devs.
A
B
Then
that
might
help
people
be
able
to
engage
more
easily.
You
would
sort
of
like
be
taking
like
an
editor-in-chief
position
with
it,
but
it
could
be.
The
editor-in-chief
is
still
going
to
be
better
than
being
the
editor-in-chief
and
the
writer
and
the
distributor
and
everything
else
too
like
it
could
be.
You
can
pull
in
some
engagement
that
way.
A
That
that
sounds
like
a
very
interesting
idea,
and
the
good
part
is.
We
already
have
this
channel
for
medium
update
in
the
communication
section
of
the
cad
headers.
Discord
probably
would
want
to
start
utilizing
it
better,
and
the
suggestion
on
doing
that
on
individual
part
is
also
good,
but
when
I
would
like
to
see
more
people
getting
engaged
and
things
going
out
by
their
name,
that
would
be
even
you
know,.
B
A
B
D
A
Yes,
like
I
provided
an
update,
but
now
that
you
have
joined,
if
you
would
have
something
to
add,
I
don't
know
because
you
did
not
hear
about
it
here
when
we
were
discussing
about
it.
So
I
just
provided
the
update
the
highlights
on
what
was
discussed
in
the
previous
meeting
and
how
we
are
doing
on
the
outreach
front,
and
we
decided
that
cat
headers
will
continue
to
reach
projects.
D
A
A
Coming
back
to
the
newsletter,
I
think
the
idea
is
really
interesting,
william,
and
we
should
try
to
work
on
that.
We
have
this
communication
channel.
I
believe
all
the
members
should
have
access
to
it
and
member
and
contributors
should
have
access
to
that
and
yes,
we
can
start
posting
it
and
maybe
plan
out
from
for
the
next
meeting
onwards.
A
A
There
is
one
item:
there
is
one
issue:
104
update,
folkman
and
publish
code
properly.
So
if
I
understand
correct,
martin
has
started
this
folkman
dot
at
devops.io,
and
that
is
up
and
running
again.
So
it
would
be
a
good
time,
but
I
left
it
open
for
others,
others
to
review
it,
and
if
this
is
fine,
we
can
go
ahead
and
close
this
issue
at
least
one
will
be
down.
A
D
D
D
D
D
Okay,
I
think
a
lot
of
I
think
the
if
we
want
to
just
touch
on
highlights,
one
of
the
biggest
highlight
would
be
that
progress
is
still
very
much
underway,
so
the
implementers
aren't
really
ready
to
implement
and
there's
a
bunch
of
like
different
dependencies
from
different
eips
that
aren't
ready
to
be
implemented
in
the
berlin
and
there's
a
couple
changes
that
can
be
made
a
couple
different.
I
think
it's
forgetting
exactly
what
it
was,
but
there
was
some
like.
D
D
A
Right
right,
thank
you
for
the
updates
alita.
So
there
was
one
more
item
that
was
listed
today
and
we
did
not
hear
much
on
that.
It's
in
that
now
that
you
have
joined
about
the
eipip
meeting
update
we
were
discussing
about
the
you
know,
onboarding
of
editors
and
how
important
it
would
be
if
there's
anything
that
you
would
like
to
mention
based
on
your
survey
and
the
document
that
you
are
working
on
or
how
you
would
like
to.
You
know
spearhead
this
initiative.
A
F
A
Yeah,
that
would
be
awesome,
yeah
yeah.
This
is
exactly
what
other
thing
that
I
was
trying
to
mention
here.
We
need
to
reach
out
to
community
in
more
different
ways
like
we
have
to
be
talking
about,
whatever
changes
are
coming
in
picture
or
whatever
we
are
doing
here
as
cat
artists.
So
if
you
have
anything
in
mind-
and
you
won't
want
to
share
it
as
a
form
of
blog,
please,
let's
coordinate
and
talk
on
this
channel
discord,
channel
and
publish
it.
F
F
F
A
So
I
think
the
intermediate
level
could
be
answered
from
you
know
the
triage
information
that
we
are
talking
about.
That
might
be
helpful
there
for
the
time
being,
and
yes,
this
particular
survey
and
the
documentation
that
we're
talking
about
was
more
focused
on
having
a
full-fledged
eap.
Editor
that
would
be,
you
know,
would
be
able
to
look
into
every
aspect
of
all
the
jobs
of
an
editor
and
should
be
able
to
perform
that.
B
F
A
Right
and
it
would
be
great
to
hear
more
about
the
process
part
you
know
like-
I
don't
know
if
you
get
a
chance
to
get
responses
on
this
part
like
what
would
be
the
formal
process
earlier,
it
was
like
three
four
editors
decided
and
they
want
to
put
on
something
they
just
added
it's
a
good
way.
I
mean
if
people
would
want
to
continue
that,
but
if
there
is
also
something
defined
and
documented
would
be
helpful
for
other
people
to
refer
in
future.
A
Great
thank
you
for
that
update.
We
look
forward
to
the
next
eipip
meeting
and
hopefully
we'll
get
some
solution
to
this
thing
and
this
item
how
we
are
moving
for
the
selection
or
maybe
onboarding
of
eip.
It
is
so
I
think
we
have
covered
everything
what
was
listed
for
today's
meeting.
If
there
is
anything
anybody
would
like
to
bring
up.
C
C
A
A
No
problem
sounds
good,
looks
like
we
are
on
time
and
yeah,
okay,
just
one
one
more
one
last
thing
is
this
time
and
a
schedule
works
for
everybody
for
this
catalyst
meeting
or
if
there's
something
that
people
would
like
to
change
or
you
know,
would
be
more
comfortable
for
people
to
join
frequently
we
can
discuss
about
it.
Maybe
in
the
discord
channel,
oh
yeah.
D
So
for
me,
because
I'm
actually
kind
of
I
kind
of
have
a
pretty
messy
schedule,
but
so
maybe
not
take
my
advice
too
much,
but
I'm
thinking
we
push
it
back
an
hour.
So
then
it's
like
the
same
sort
of
schedule
with
the
other
meetings
so
because
yeah
e-I-p-I-p,
for
example,
it's
all
like
10
a.m,
where
it's
all
at
1400
utc,
and
I
think
today
that
might
help
people
like
me
remember
when
the
time
will
be
just
kind
of
like
implicitly
unders
like
know.
A
No,
it
is
so
here's
the
thing
like
I
like
I
present
this
is
at
1400
utc,
like
ethereum,
1.0,
meeting,
all
code
meeting,
ethereum
2.0
meeting
and
most
of
the
meeting.
It
is
at
1400
utc,
but
the
good
point
is
from
next
month
november
onward.
There
would
be
a
change
of
time
for
people
in
u.s,
so
it's
going
to
be
an
hour
earlier.
I
don't
know
what
time
zone
you
are
from,
but
it's
going
to
be
a
hour
earlier.