►
From YouTube: Eth2.0 Call #25 [2019/9/19]
Description
A
B
B
Great
so
many
of
you
were
there,
then
if
you
saw
the
fanfare
on
Twitter
as
we
were,
hitting
different
milestones,
accomplishments
have
to
interrupt
retreat
and
we
just
did
publish
a
quick
follow-up
to
kind
of
celebrate
some
successes
and
set
the
stage
for
things
to
come
on
the
EF
blog,
which
seen
it.
It
is.
B
Today
I
know
we
could
probably
talk
in
the
client
updates
about
all
the
exciting
things
that
happened.
Instead,
we
will
save
that
the
Twitter
save
that
for
individual
blog
updates
and
for
this
blog
post
we
posted
you
know
you
can
mention
a
little
bit
about
what
happened
to
everybody.
I
need
to
get
into
the
nitty-gritty
about
all
of
things
great,
so
we
will
get
started
with
testing.
B
So
I
enter
up.
We
had,
as
you
know,
three
or
four
consensus.
Arrows
showed
up
primarily,
interestingly
enough.
I
guess
isn't
that
surprising
and
respect,
but
they
happen
too
often
on
the
epoch
transition
between
one
and
two,
which
is
the
first
time
you're
doing
you
have
enough
information
to
do
updates
with
respect
to
the
account
policies.
B
B
A
lot
of
the
cross,
links
and
rewards
done,
which
is
good
so
on
the
list,
is
to
take
those
scenarios
in
that
repo
and
create
some
handwritten
tests.
That's
on
my
agenda
today
that,
along
with
updates
the
network
spec,
which
worked
out
at
interrupts
and
a
number
of
che
I,
don't
know
how
much
is
that
I
think
it's,
it's
actually
very
small
things
to
be
released
likely
in
the
next
few
days
would
be
that
Oh
8
for
the
updated
networks
back
in
some
additional
tests,
cool,
grody
or
anything
else.
C
Anyone
else
yes,
so
during
interrupt,
we
made
use
of
this
tooling
to
do
the
state
transition
without
running
the
fill
clients,
and
it's
really
sped
up
progress
and
the
time
we
needed
to
fight
these
books,
and
so
I
want
to
automate
this
and
I
started
to
come.
Writing
this
tool
to
trigger,
at
the
stage
of
session
upload
it
to
the
clouds
register,
its
fire
offence,
distributed
and
then
have
each
clients
or
some
sort
of
CLI
to
we're
in
the
staging
session
and
upload
the
results.
C
So
you
can
automate
the
testing
and
get
a
real
first
result
on
the
all
these
different
clients,
from
certain
state
position,
and
hopefully
with
the
next
step,
would
be
to
not
manually
trigger
this.
That's
attached
it
to
the
test
not
and
I.
Go
off
of
this
is
to
automate
the
effort
we
have
it
put
in
interrupt.
B
Right,
the
expectation
is,
as
we
make
more
tests,
add
some
more
tests
for
different
clients
in
different
scenarios.
We
expect
to
still
find
some
of
these
instances
airs,
and
so
thanks
for
on
the
buzzing
front,
we
do
plan
on
in
the
next
couple
of
weeks,
open
up
reopen
the
differential,
fuzzer
Mehdi
from
Sigma
prime
is
going
to
be
helping
out.
B
D
D
So
the
rusticity
five
that
we've
built
we're
going
to
start
testing
out
with
they
go
one
which
is
inside
prism
and
also
we're
finishing
some
of
the
updates
for
the
latest
network
specs,
so
that
we
can
start
syncing
and
hopefully
have
some
longer-lasting
multi-client
test
nets.
That's
it
from
us
thanks.
E
Yeah
so
pretty
much
the
same
of
Diaz
Adrienne.
Our
top
priorities
are
working
on
just
st.
resilience.
We
currently
don't
handle
missing
parts
very
well
and
also
what
he
has
going
on
validate
account
to
2024,
and
we
found
a
few
BOS
having
issues
and
there
at
the
station
handling
box
issues
and
then,
as
well
as
updating
to
the
latest
network
spec
PR,
which
astronomers
are
a
few
days
ago,
and
then
we're
also
working
on
SSC
resilience.
So
we
don't
have
made
through
some
false
testing
on
there
and
stuff
working
on
test
coverage,
improvement.
E
F
H
Yeah
this
week,
we've
been
working
on
emerging
in
our
Interop
changes,
master
fixing
those
up
we're
also
working
on
some
roadmaps
for
the
next
few
months,
so
that
we
kind
of
have
a
better
sense
of
our
priorities
and
we're
working
on.
You
started
also
developing
a
roadmap
specifically
for
like
light
client
or
light
client
work,
so
we're
just
wanting
to
flesh
out
flesh
that
out
and
get
started
with
it.
B
I
Yeah
yeah,
so
so
we
learned
about
many
new
issues
during
Interop
that
could
be
summarized
into
two
things.
The
first
one
is
the
stability
that
we
are
now
focusing
on,
make
hinder
internal
tests.
They
could
be
more
and
more
stable
and
to
organize
the
logs
to
people
structural
eyes
and
also
make
a
clear
go
to
monitor
it.
And
the
second
thing
is
the
ability
of
distribute
the
software
and
set
up
the
client
that
Alex
and
Brian
had
made
a
TOC
file
during
the
on
top
decided.
J
B
Thanks
Miguel
and
right
so
nimbus
most
of
them
are
on
a
flight
I
believe
so
from
mommy
great
interrupt.
Thank
you
all
socially
to
just
DeLongpre
organization,
they're,
slowly
merging
fact,
the
interrupt
branch
and
to
master
they've
gathered
a
bunch
of
start
scripts
to
startle
the
clients
that
currently
live
in
there
we
go.
Although
we're
talking
about
living,
something
like
this
into
the
PM
repo,
which
that
was
the
next
sentence,
they
propose
cake
a
common
repo
for
this.
B
B
Jasper
parody
was
not
able
to
attend,
but
I
know
that
way
has
been
working
through
some
pairwise
ability
tests
last
I
heard
I
knew
he
did
some
work
with
lighthouse
and
had,
but
was
only
on.
Oh
wait.
One
at
the
graduates
in
sir
so
then
was
updating
the
client
to
Oh
a
tree,
but
way
will
be
with
us
in
Dhaka
great
day.
Miss
anyone.
B
Research
updates,
italic
and
Justin
are
not
here.
I
know,
there's
some
busyness
with
Def
Con
coming
up
and
I
know:
we've
been
interrupts
and
something's
going
on
in
Tel
Aviv,
the
specter
ego
has
been
a
little
bit
slow,
there's
some
big
PR
submerge,
some
last
updates
to
get
in
a
lot
of
the
focus
has
been
on
ensuring
that
the
phase
one
short
day
to
change
spec
is
clean
and
to
begin
to
revisit
a
lot
of
the
custody
games.
K
Outside
normally
changes
but
we're
looking
the
integration
of
and
learning
after
needs,
so
we
I
implemented
kind
of
proof
of
concept
in
vintage,
Time,
Protocol,
simulator
and
I
will
be
working
with
the
afternoons
team
inside
conferences,
especially
on
how
to
attend
details
unlikely
to
work
on
this
as
well.
We've
recruited
team
in
psychosis,
but
it's
more
on
implementation
point
of
view
were
not
changing
the
protocol
itself.
B
K
G
L
All
the
tests
pass,
which
serve
as
a
very
nice
validation
of
the
model
and
right
now
we
are
doing
coverage
analysis
it's.
This
is
specific
to
the
to
the
K
tune
we
are
using
and
we
are
hoping
that
we
get
some
kind
of
evaluation
of
of
the
test
suite
and
maybe
suggest
some
some
other
tests
to
increase
coverage,
and
once
this
is
done,
which
we
hope
is
going
to
be
very
sometime
soon.
We
will
be
hopefully
able
to
share
this
with
everyone,
so
we
are
very
excited
to
have
this
done
when
once
once.
B
C
B
L
L
J
M
Have
really
better
reception
right
yeah
if
anybody's
interested
I
can
give
some
update
regarding
face
to
you
yeah
stop.
Some
of
you
may
have
seen
that
the
kilt
and
he
wasn't
in
some
members
of
the
teams,
also
attended
the
intro,
but
we
actually
did
a
mini
sprint
prior
to
the
intro
and
then
I
think
had
some
discussions
at
the
intro
of
itself.
Now,
in
the
past
couple
of
months,
the
the
main
focus
for
both
teams
were
just
to
prove
the
feasibility
of
the
idea,
and
that
really
was
focusing
on
two
different
efforts.
M
Having
good
schemes
for
marker
proofs
and
all
the
witnesses,
and
obviously
we
have
looked
into
sse
partials
and
we
also
looked
into
Alexei's
multi
proof,
which
is
in
interval,
guess
if
you
guys
have
heard
about
that
before,
and
there
were
also
a
couple
of
other
new
initiatives
to
you
to
have
some.
You
know
different
schemes
for
marketers
and
businesses.
M
M
We
need
to
look
at
it
more
in
an
integrated
manner
because
they
design
so
I
think
that's
the
next
step
for
the
two
teams
to
you
to
work
on
this
more
closely
and
the
very
last
thing
what
happened
at
the
in
truck
was
Vitaly
came
up
with
a
new
proposal
for
Phase
two,
and
we
spent
quite
a
bit
of
time
and
discussing
it
with
him,
trying
to
understand
it
and
comparing
it
to
the
current
proposal
so
yeah.
It
was
quite
a
busy
period
and
sorry
for
the
long
update.
Thank
you.
No.
B
Great
on
to
networking,
there
was
much
work
done
on
the
networks
back
at
Inter
up
a
lot
of
this
primarily
had
to
do
with
the
structure
of
the
request,
response
messages
or
sync
and
all
the
related
kind
of
sync
messages,
rather
than
the
gossip
and
some
of
the
other
structures
so
age
or
someone
that
was
in
the
weeds
working
on
that.
Would
you
like
to
give
us
a
quick
on
what
happened
there.
D
Yep
sure
so
it
was
proposed
that
it
would
be
more
efficient
and
a
little
bit
more
general
that,
when
we're
requesting
large
amounts
of
blocks
that
we
previously,
the
spec
required,
like
matched
amounts
of
block.
So
we
for
a
long
range
thinking
we
had
blocks
blocks
by
blocks
by
range
is
the
new
name
of
the
RPC
request,
which
you
can
request.
Let's
say
a
hundred
blocks
and
previously
the
requests
would
you
would
have
to
buffer
this
and
get
the
whole
number
of
blocks
in
one
hit.
D
Now
you
can
effectively
stream
them
through
the
network,
so
you
send
one
you
send
one
block
wrapped
in
a
in
an
RPC
response
and
then
another
one
and
then
another
one
and
then
until
either
you've
completed
the
entire
request
or
an
error
has
happened.
So
this
allows
implementations
to
you,
know,
read
a
single
block
from
the
database,
send
it
across
the
network
and
and
do
this
as
opposed
to
having
to
buffer
large
amounts
of
blocks.
So
that's
the
main
change
in
the
two
RPC
request
that
required
large
amounts
of
blocks.
D
B
D
B
Thanks
yeah
any
other
questions
regarding
that,
as
I
mentioned
on
the
discord,
this
spec
parent
lives
in
the
b08
X
branch
and
it's
released
into
master
and
a
minor
release
in
the
next
few
days.
But
if
you're
working
on
that
work,
sync,
please
check
that
out,
rather
than
the
current
one
and
with
me,
zero.
Eight
three.
N
Here,
Rose
on
vacation
this
week,
so
I
thought,
let's
step
it
in
Phyllis
place,
but
we
didn't
really
have
it
a
much
of
an
update.
I
know
some
of
the
teams
have
been
the
language
teams.
We've
been
making
progress,
which
is
great
but
I,
don't
know
they
can
speak
to
that
if
they
want
the
jvm
folks,
for
example,
but
we
didn't
really
have
a
update
for
Limpy
to
feed
like
overall
yeah.
B
A
J
It
probably
could
be
released
already,
I'm
not
sure
need
to
reach
Anton
again,
but
the
things
is
about
to
publish
artifacts
and
do
some
documentation
collapse.
Maybe
maybe
I
missing
something
else.
Also
Shahana
is
working
on
the
noise
implementation,
which
is
not
required
by
this
version,
so
it
could
release
it
like
in
the
next
one
yep,
so
yeah,
thanks
or
tennis
for
being
the
second
users
for
the
GBM
with
p2p
yeah.
That's,
what's
very
exciting
to
see
that
it
really
works
method.
O
Danny
yeah
I
can
give
a
quick
update.
I
wasn't
at
interrupts,
so
I'll
just
keep
it
short.
This
is
coming
from
the
team
that
was
there,
as
most
of
you
know,
it
went
very
well,
is
super
productive.
We
had
Antoine
Renee
and
Daniel
there.
They
spent
most
of
the
week
adapting
the
e
to
clients
to
work
in
Genesis
white
black
Genesis,
which
is
for
those
of
you.
That
don't
know,
is
what
we're
gonna
be
testing.
O
The
network
and
scale
on
like
I,
said:
I'm
super
productive
and
but
one
of
the
things
that
or
two
of
the
things
that
we
weren't
able
to
complete
were
prep
for
testing
gossip
sub
for
a
client
like
what
variables
we
can
change
and
also
how
to
optimize
gossip
soap.
So
these
are
two
big
things
that
were
gonna,
be
attacking
in
the
next
few
weeks,
we'll
be
refining
the
test
cases
that
were
already
developed
to
interrupt
from
here
on
out
and
actually
starting
to
see
how
we
can
test
them
at
scale.
O
P
Or
move
on
I
should
add
Anton
here
for
my
luck
separately
from
this,
we
also
study
on
network
with
li
p2p
and
gossip
table.
So
we
have
people
from
protocol
ABS
we
TV
spot
too,
as
well.
This
week,
we're
going
to
get
started
on
implementing
a
go
based,
client,
the
authorities
open
source
is
under
the
white
block,
critical
or
gossip
testing.
P
The
idea
is
to
take
up
the
work
that
we
had
done
there
early
this
year
and
really
poor
ties
it
using
a
specific
implementation
going
to
pay
for
it
that
we
can
really
stretch
and
test
at
scale.
So
in
terms
of
testing
the
variables
for
the
sub
testing
the
behaviors.
This
is
something
that,
for
each
attack
not
more
than
four.
B
B
Public
test
networks
and
some
incentivize
test
networks-
we're
not
quite
there,
as
you
all
know,
there's
a
lot
of
work
to
do
to
stabilize
clients
get
sync
in
place
and
things
like
that.
But
before
we
get
there
start
thinking
about
manual
test
nuts,
so
also
something
that
we
need
to
be
looking
into
the
next
level
piece.
P
And
yeah
I'd
like
to
throw
my
hat
in
the
ring
before
to
help
you
see
a
city
from
the
my
book
perspective.
So
we
can.
We
can
coat
the
shoe
many
you
built
coming
in
and
we
can
have
about
to
be
attest
to
that.
So
I
think
we'd
be
happy
to
be
involved
in
help
the
community
in
terms
of
metric
English,
centric.
Q
Q
No
I
was
just
thinking,
you
know,
def
cons
three
weeks
away
and
we
just
all
walked
away
from
from
the
Interop
with
you
know,
a
lot
of
really
good
miles
and
I
was
wondering
you
know
if
we're
had
anything
specific
in
mind
for
what
we
wanted
to
target
in
the
next
three
weeks
and
then
and
of
course
like
in
q4,
is
coming
so
I
prismatic
we're
just
planning
out
the
rest
of
our
quarter.
I
wanted
to
hear
from
from
you
or
anybody
who's
interested.
What
the
specific
goals
for
coming
up.
Yeah.
B
I
mean
on
my
end,
it's
CI
Network,
informants
mapping
out
a
plan
for
public
test
nuts
and
incentivises
hats
on
client
side.
I,
expect
kind
of
continual
stability.
I
know
we
some
of
them
post
vention.
We
had
a
big
sprint
to
get
to
interrupt,
but
now
we
have
a
lot
of
things
to
clean
up
around
that
and
then
I
guess
going
into
DEFCON.
A
lot
have
a
lot
of
contra
conversations
there
about
things
coming
up
the
next
couple
of
months.
B
B
B
Cool
and
general
open
discussion,
anything
that
would
not
address
that
is
worth
one
I
do
not
understand.
I
do
not
have
anything
organized
primarily
because
we
just
have
this
huge
Meetup
and
it
seemed
a
little
bit
like
overkill.
There
is
so
day
one
of
four
day.
One
is
relatively
light
at
Def
Con
with
respect
to
some
of
the
content,
but
there
is
a
room:
that's
dedicated
to
I
think
the
magicians
are
organizing
at
this
time,
dedicated
to
working
through
a
bunch
of
stuff
and
I.
B
B
J
B
A
B
The
people
are
still
working
on
early
implementations
and
test
vectors,
and
so
from
the
perspective
of
the
deposit
contract,
we
can't
we
can't
reasonably
deploy
that
until
we
have
the
standard
in
case
anything
related
to
public
keys
and
the
required
signature.
Initial
signature
changed
so
the
current
almost
certainly
it
will
not
be
the
plate
that
come
because
of
this
Walker
and
we're
kind
of
in
a,
although
it
is
moving
fast
for
a
standard,
because
there's
a
lot
of
demand
from
another
block
chains
that
are
involved.
It's
quite
simply
not
gonna,
be
ready
by
October
time.
B
F
Interop,
if
people
who
were
there
or
like
to
join
I,
think
maybe
give
some
feedback.
So
when
we
do
it
next
time,
you
know
things
like,
maybe
not
make
it
seven
days
kind
of
thing
yeah,
so
that's
TBD
I'll
send
out
an
invite.
I'll,
probably
drop
it
into
the
Interop
Channel
and
into
the
sharding
getter.