►
From YouTube: Eth2.0 Implementers Call #22 [2019/7/25]
Description
A
Yeah
we're
live.
Okay
agenda
is
shirt.
The
youtubers
and
agenda
is
chaired
to
s
first
thing
on
the
agenda.
As
usual,
is
testing
update.
Proto
has
been
cataloging
some
of
the
issues
that
we've
had
and
testing.
Although
the
system
is
great
and
has
a
lot
of
stuff
where
you
want
to
refine
it
and
make
everyone's
lives
this
year,
so
proto,
do
you
want
to
give
us
an
update.
B
Sure
so
yeah
we
started
looking
into
the
testing
problems.
The
other
clients
now
starts
to
have
I
already
knew
present.
Most
I
think
some
problems
will
be
resolved.
Eventually,
there
are
bigger
problems,
nada
or
like
there's
memory
problems
for
some
clients
simply
can't
handle
the
bigger
minute
tasks,
so
we're
planning
to
split
them
up,
make
them
organize,
organize
them
better,
and
so
I
posted
this
issue
to
describe
the
issues
or
like
the
smaller
problems
and
then
get
a
surfeit
to
see
like
hey.
B
C
D
Yeah,
hey
guys
so
we're
mostly
just
giving
runtime
to
a
lion
with
this
bad
freeze
version,
so
we
have
been
able
to
run
single
client
with
single
beacon,
node
with
CC
form
elevators
pretty
smoothly
and
we're
debugging
a
few
sync
related
issues.
On
top
of
that,
we're
just
optimizing
SSE
and
our
sparse
McCrory
implementation.
We
realized.
E
D
F
F
G
So
a
complete
alert,
0.8
update,
we're
now
patching
to
0.8.1
and
right
now,
we're
working
on
some
reference
tests
were
worrying,
worth
white
block
in
prism
to
make
sure
they're
kind
of
their
eighth
one
mock
RPC
client
is
able
to
generate
deposits
that
can
output
te
amo
and
then
we'll
intake
the
female
deposits
in
so
we
can
generate
a
Genesis
state.
That's
the
same
as
prismatic.
H
We
have
completed.
One
of
the
major
milestones
during
this
week
was
updating
to
zero
points
back.
We
have
completed
that
the
biggest
problem
bought
with
SSC,
especially
with
the
bit
list,
and
between
vectors
and
spar
snorkel
trees.
So
cool
request
is
still
on
the
review,
but
I
guess
it
will
be
merged
likes
tomorrow.
H
Anyway,
we
pass
all
the
tests
now,
so
that's
it
should
be
treated
as
completed.
I.
Think
the
next
we
keep
making
progress
on
the
p2p
stuff
Anton
is
about
to
start
implementing
the
subside
protocol
like
since
next
week.
Also
we
continued
our
research
on
attestation
aggregation
and
a
bit
jumped
off
from
this
particular
problem
to
the
adjustment
topic
like
attestation,
delivery
and.
H
I
High
so
we
implemented
the
most
of
0.8.1
except
SSC,
but
we
are
just
on
the
verge
of
updating
or
SSC,
with
the
latest
scheme
and
also
coming
soon
is
a
unique
testing
coverage
of
most
of
the
state
transition
functions.
We
found
some
issue
with
justification
and
finalization,
so
that's
something
that
we
are
investigating.
I
A
E
J
So
we're
at
0.8
one
for
everything.
At
this
point
we
had
a
small
bug
that
we're
working
through,
but
should
be
fine
in
passing
and
we're
in
the
process
of
splitting
everything
out,
it's
kind
of
prepping
for
moving
forward
with
more
tooling
stuff.
So
hopefully
I
don't
know
it's
wednesday
thursday,
so
like
tomorrow
or
this
weekend,
at
some
point,
you'll
be
able
to
like
npm
install
like
ssz
types.
J
You
know
config
params,
everything
like
that
and
like
individually
import
all
of
the
early
material,
so
I'll
be
really
helpful
for
dev
tooling,
as
we
start
moving
towards
that
and
we're
just
doing,
refactor
is
kind
of
on
our
code
base
to
make
it
a
little
bit
more
modular.
So
it's
easier
to
import
again
because
we're
moving
forward
to
like
light
clients,
endeavour
Toulon.
But
aside
from
that,
that's
kind
of
where
we're
at.
K
Hey
everyone
we're
pretty
much
up
to
date
with
the
0.8.1
tests
and
everything,
except
for
one
one,
we'd
Genesis,
that
we
don't
have
the
runner
for
yet.
But
what
in
playing
with
that
and
Michael
found
I
think
we
may
even
found
an
issue
in
the
spec
today
about
get
start
shard.
So
anyway,
we've
just
posted
an
issue,
one
three
one,
five
about
that
today,
so
that
might
be
an
interesting
one.
We've
introduced
chaos,
monkey
and
we've
seen
some
good
results
on
the
network.
K
There
helps
out
with
lot
of
this
stuff
we're
making
efficiency
gains
in
like
the
way
we
store
data
and
reduce
our
size
memory.
Usage
I
was
fleshed
out
our
API
spec
to
be
sort
of
similar
with
other
clients,
work
towards
interrupts
and
we've
also
been
trying
to
make
sure
that
our
rust
limpidity
implementation
works
well
with
the
gold
implementation,
which
has
been
not
as
straightforward
and
there's
been.
Some
issues
were
working
through
with
that
and
we've
also
about
to
review
quilt
teams,
as
I
said
PR
as
well,
and
that's
it
from
us
great.
A
L
We
yeah,
as
we
discussed
before,
we
are
now
actually
looking
into
specifying
the
metallization
operation
in
K
as
well,
because
it
turns
out
that
we
actually
needed
to
do
that
so,
which
is
not
going
to
be
a
big
problem.
Really
it's
just.
That
will
probably
require
some
sample
time
to
do,
but
nothing
fundamentally
difficult
there
yeah
once
once
we
have
that
I
think,
because
this
is
what
you
have
been
trying
to
do,
at
least
for
the
last
two
weeks,
which
is
to
have
something
that
we
can
actually
run.
L
The
tests
on
run
the
tests
on
without
having
to
make
any
changes
to
the
test
so
run
the
tests
as
they
are,
and
we
are.
We
were
hoping
that
by
doing
that,
we
will,
by
doing
this
process,
we're
going
to
be
able
to
do
that
so
initially
on
a
subset
of
this
specification
and
then
eventually
from
its
specification.
L
A
M
Yeah
the
things
that
we've
been
looking
at
is
just
trying
to
figure
out
some
of
the
details
in
phase
one
one
of
them
is
nailing
down,
and
the
persistent
committee
structure
ends
the
approach
that
we
seem
to
have
settled
on
this,
because
some
this
approach,
where
we
have
a
persistent
committee,
the
entire
persistent
committee
signs
every
blog
and
the
persistence
committee-
has
a
size.
That's
capped
at
128,
and
that
reshuffles.
B
M
M
That's
and
doing
those
things
that
I
worked
on.
You
made
quite
a
lot
of
good
comments
on
yesterday,
so
continuing
to
iron
that
out.
The
next
thing
I'm
working
on
is
updating
the
alight
client
protocol.
So
the
white
client
protocol
was
one
of
the
lineup
goals.
What
we're
making
a
like
line
of
protocol
I
knew
both
efficient
and
secure
and
performance
was
one
of
the
key
goals
of
the
persistence
committee
redesign.
So
basically,
the
approach
now
becomes
much
simpler
because
it
basically
says
you
have
a
blog
header
from
the
blog
header.
M
You
download
one
one,
if
you're
a
period
committee
which
was
more
coal
hashed
into
the
header,
then
you
use
that
period
committee
hands
the
period
committee
from
the
previous
period
to
authenticate
blocks
of
a
particular
shard
during
the
next
period,
a
decided
box
within
that
shard
and
then
those
blocks
contain
pointers
to
beacon
blocks
and
when
you
points
by
doing
that,
you
basically
can
figure
out
what
the
updated
state
is
of
any
particular
shard
or
of
any
particular
ORS.
The
recent
beacon
chain
state.
M
B
M
A
M
M
You
know
basically
a
concerns
that
it
actually
would
have
add
more
couple
of
more
complexity
in
a
budget
in
a
bunch
of
ways
like
the
big,
the
big
one
being
dead.
A
single
object
that
says
add
partials
would
not
kind
of
reduce
to
being
exactly
the
same
as
a
morkul
proof
anymore,
but
it
is
something
I
haven't
thought
enough
about,
and
I
could
think
think
about
it.
More
I.
F
The
the
Marco
Marco
tree
hash
exactly
deterministic.
We
can
have
multiple
tree
result
in
the
same
tree
hash
or
vice
versa,
which
has
needs
the
ice
age,
wait
to
be
deterministic,
so
I
I
just
think
this
might
be
something
worth
thinking
about
and
I
actually
have
a
data
structure,
a
Razzie
minimization
that
can
potentially
do
that.
F
I
M
M
There's
a
lot
of
cases
where,
like
you,
should
not
need
to
be
serializing
the
set
of
indices,
because
the
set
of
indices
can
just
be
calculated
in
real
time.
So
the
biggest
example
of
this
is,
if
you
have
a
partial,
that's
going
down
to
some
object,
but
then
you
wants
to
capture
the
entire
object
so
like,
for
example,
you
want
to
capture
an
entire
validator
record
at
some
index,
then,
really,
all
you
need
is
the
validator
index,
rather
than
the
set
of
generalized
indices.
So.
N
O
A
B
There's
this
little
gap
in
that
face
zero
research,
a
threads
filled
with
surrounds
folks,
I'm
matching,
and
so
a
loss
leak
I
looked
into
it.
That's
so
that
we
post
story
with
explanation,
and
now
we
good,
if
you
just
a
few
fix,
need
to
be
polished,
but
there's
potentially
at
30
times
improvement
there.
H
H
A
N
I've
got
a
couple:
quick
updates
from
quilt
great,
so
John
Adler,
just
posted
a
document,
III
search
compiling
some
of
the
questions
that
we
still
have
regarding
East
2.0
in
areas
that
we
feel
need
to
be
more
thoroughly
researched,
I,
think,
okay,
yeah
John
dropped
a
link
for
that
and
then
yeah.
Like
luke
said
we
just
completed
initial
implementation
of
SN,
c--,
partials
and
rust.
It's
a
pull
request
and
the
white
house
repo
that
I
linked
to
earlier.
N
If
more,
if
some
more
people
could
just
take
a
look
at
that
and
ping
me
with
any
questions
or
comments
that
would
be
really
cool.
We
have
come
up
with
a
plan
for
implementing
a
harness
single
shard
phase,
one
and
two
engine
on
top
of
lighthouse
and
we'll
be
implementing
that
over
the
next
few
weeks,
in
parallel
with
building
a
simple
transfer
execution
environment,
similar
to
what
vitalik
proposed
in
the
phase
two
proposal
and
will
has
been
busy
leading
our
efforts
on
that
test
net.
N
A
P
Yes,
the
basic
idea
here
is
I
will
add
much
to
be
working
on
trying
to
come
up
with
my
standards,
for
that
looks
like
for
just
role.
Rather,
what
the
clients
will
need
is
to
be
able
to
cause
the
keystore
files
we
may
have
will
use
what
exists
in
each
one
right
now,
that
seems
to
work
fairly.
Well,
the
more
complexities
arise
or
how
to
do
the
deterministic
arts
for
which,
which
Aquis
you
get
whatever
the
key
tree.
P
A
A
Q
Q
R
Nothing
major
I've,
been
we've
been
running
around
helping
a
team
since
we've
been
pulled
into
conversations
and
participating
as
well
for
that
Jochen
Road
and
responding
to
that
as
well.
Taking
action
on
our
side
to
become
even
more
helpful
to
the
community,
would
then
we've
approved
a
new
ground
for
negativity
and
also,
if
it's
for
changing
beyond
the
peace
from
just
been
running
around
helping
helping
people
as
we've
been
called
into
action?
Great.
Thank
you.
R
A
A
Okay,
jonbi
one
yes,
aspectus
cushon
any
questions
or
comments
or
issues
that
have
arisen.
I
haven't
I
just
saw
that
issue
that
was
reported
by
Michael
from
lighthouse,
but
I
haven't
actually
post.
It
I
think
that
it's,
if
that
isn't
actually
an
issue,
we
can
really
similar
release,
probably
like
next
week
that
has
a
couple
of
minor
things
and
it's
bug
fix.
A
I
have
a
few,
so
I
have
a
few
things
in
the
Ethiopia
Marie
repo
that
people
have
looked
at
in
there
I
think
we
will
start
just
cataloging
in
like
Interop
slash
standards
or
something
the
little
things
that
will
make
our
lives
easier
and
like
doing
tests
and
tests.
So
groups
and
things
coordinating
on
called,
starts
standardizing
on
key
files
that
kind
of
stuff
so
that
conversation
and
those
mini
specs
will
live
there.
A
So
keep
your
eye
out
for
that
and
I'll
make
a
note
when
there's
stuff
up
for
review
people
on
following
that
Rico
too,
closely
and
I
asked
as
individually,
but
as
you
do,
work
on,
interrupts
tough
with,
say
another
single
client.
There
are
gonna,
be
a
handful
of
like
things
that
pop
up
where
you
have
to
make
decisions
like:
oh
well,
how
we're
going
to
do
this?
How
we
do
that?
A
If
you
push
that
those
concerns
and
your
potential
solutions
upstream
into
the
e
to
OPM
repo
for
conversation,
that
will
help
a
lot
because
I've
tried
it
how
to
log
the
things
that
have
come
to
mind
so
far.
But
there
is
a
lot
of
stuff
that
I'm
not
currently
thinking
abut.
It's
only
gonna
really
fall
out
when
we
have
a
couple
people
trying
to
connect.
G
G
Well,
you
know
now
it
is
an
overwhelmingly
YES
on
proposal
81,
you
know
you
just
never
know
what
can
happen
with
votes
and
so
kind
of
like
voting
YES
is
going
to
ensure
that
lodestar
gets
there
three
months
of
runway,
but
also
kind
of
like
creates
a
mandate,
because
this
is
kind
of
a
three-part
thing.
They
had
broken
up
the
grant
into
three
parts
rather
than
a
single
grant,
based
on
some
recommendations.
So
please
vote
YES
for
that.
If
you
have
shares
in
Moloch.