►
From YouTube: Eth2.0 Call #27 [2019/11/7]
Description
A
A
As
usual,
we'll
get
started
with
test
net
and
release
updates
easier.
9
o
is
out
I.
Think
with
us.
What
we
were
discussing
in
the
last
call
came
out
about
a
week
and
a
half
you
know.
I
know
a
number
of
you
are
working
towards
getting
that
cleaned
up
and
ready
to
go,
and
we
have
a
few
more
PRS
that
are
gonna,
be
really
so.
Nine
releases
that
I'm
very
very
actually
working
on
getting
done
and
expect
to
release
this
weekend.
A
There
are
an
additional
cleanup
of
pulling
the
custody
bits
out
of
a
two
stations
and
a
few
for
choice,
fixes
that
are
kind
of
post-audit
fixes.
Booyah
a
Japanese
researcher
has
been
doing
some
work
and
the
past
few
months
on
III
search
has
found
a
couple
of
attacks
on
fg+
ghost
and
a
couple
of
pretty
simple
fixes,
so
those
are
gonna
be
integrated,
again
I'm
working
on
getting
these
out
as
soon
as
possible.
To
note
that's
really
the
delaying
component
on
living
towards
larger
distance
I
have
a
on
our
agenda
today.
A
A
I
want
to
make
a
clarification
on
the
tests,
so
we
did
have
a
number
of
these,
like
ad
hoc
Interop
test
cases
that
we
found
debugging
multi-client
test
nets
on
the
wire.
These
were
408
three
and
I.
Think
some
of
you
had
integrated
them
into
your
test
set
testing
flows.
We
have
since
then
built
out
handwritten
tests
that
hit
these
test
cases.
B
Itself
up
website
this
life
problem
is
the
V
now
needs
worker
notes
or
these
clients
to
run
on
the
sides
and
consume
these
inputs
and
I'm
in
the
process
of
deploying
the
specification
during
these
transitions
and
then
next
up,
I
spec,
maybe
n
COI
and
now
nci's,
working
well
and
absolutely
nice
during
interim,
so
I'll
try
and
apply
it
as
well.
Ooh.
A
B
So
the
main
goal
of
Muskoka
is
to
we're
in
the
same
transition
of
all
these
different
clients
and
make
it
except
us,
XS
boss,
possible
for
someone
to
try
and
win
their
test
case
all
the
different
clients
about,
like
downloading
the
clients,
installing
winning
it
themselves.
And
then
we
publish
the
results,
and
so
it
can
track
what's
happening.
And
if
there
is
any
case
where
the
results
are
different.
Yeah.
A
A
C
Okay,
so
what
I
said
about
consensus
with
moon?
This
is
actually
not
true,
because
this
week
we
are
moving
from
zero
point.
Eight
point
three
to
zero.
So,
depending
on
the
funding
that
you
use,
the
genesis
state
might
change
due
to
the
change
in
the
become
state.
So
Nimbus
is
not
a
consensus
with
Nimbus.
C
Otherwise
we
updated
abducts.
So
we
have
no
build
instruction
for
building
Nimbus
on
the
raspberry
pi
for
the
public
test.
Max
sorry,
I've
created
new
repo
on
the.
If
two
clients
come
on,
which
was
attorney
for
everyone,
I
I
put
the
link
in
the
chat
and
guidelines
on
I
mean
everyone
can
other
is
own
questions
or
change.
Man
just
use
common
sense
on
how
to
share
the
metadata
needed
by
your
client
on
if
another
client
wants
to
connect
to
it
and
regarding
public
test
net.
C
C
That
also
means
that
we
implement
both
specs
is
repond
8.3
at
this
and
report
9.0
at
the
same
time,
and
you
shouldn't
rely
on
States
during
the
immigration
because
sometimes
it
would
be
zero
point,
eight
point:
three
that
you
gets
realized
I
was
reported
at
9.0
regarding
testing
over
the
past
two
weeks.
We
struggled
with
time
outs
in
OCI,
so
we
solve
that.
C
C
We
used
caching
for
the
LFS
EF
files
in
the
past,
but
now,
even
if
someone
does
a
bit
clone
and
FS
something
it
will
not
use
for
sure
the
NFS
quota
of
the
foundation,
we
finished
also
are
running
out
the
bugs
and
grating
to
name
one
point
O,
which
was
released
last
September
and
on
the
to
be
front,
we
had
some
updates
on,
observe
and
go
sub
implementation,
and
now
we
are
starting
to.
We
will
start
to
integrate
the
natively
p2p
into
a
code
base
and
replace
the
gold
p2p
demon.
D
E
E
We
are
almost
done
with
a
more
robust
and
official
syncing
we're
in
the
process
of
moving
from
80.8
inspect
0.9,
pretty
close
to
finishing
on
that
we
are
refactoring
our
gossip
sub,
because
J
s,
Lib
p2p,
is
going
through
a
very
large
refactor
from
like
an
older
style
of
JavaScript,
using
callbacks
to
the
newer
style
using
async
await
it
promises,
and
so
someone
from
the
lib
p2p
team
is
helping
us
with
that
migration
and
hope
that
that
can
be
promoted
soon
and
I.
Believe
that's
it
for
now.
A
Cool
thanks
and
yeah
if
y'all
didn't
see,
there's
a
number
of
these
two
related
bounties
at
Pete's
Waterloo
coming
up
and
if
you
have
any
ideas
for
these
I
think
we're
gonna
run
them
generally
at
the
youth
global
hackathons.
If
you
have
any
ideas
for
little
experiments
or
tools
or
things,
you
think
that
would
be
good
targets,
please
let
me
know,
and
I
can
get
them
on
the
list
great.
F
G
G
We
had
a
really
crazy
performance
improvement
in
pajas
has
said
so
moving
basically
to
have
backing
persistent
data
structures,
so
we
don't
have
to
like
do
well
crazy
copy
and
we
were
doing
it
had
something
like
several
orders
of
magnitude
increase
the
performance,
so
that
was
pretty
awesome
and
then
some
work
on
separating
out
our
about
our
client
has
a
distinct
binary
and
very
much
looking
forward
to
all
these
product
tests.
That's
happening
as
soon
as
possible.
H
Hey
everyone
same
as
everybody
else's
that
we're
working
towards
doing
public
test
nets,
so
in
that
regard,
we've
been
focusing
on
our
s1
connectivity,
which
is
kind
of
helped
us
clear
up
some
of
the
issues
with
one
voting
speck,
we're
making
changes
to
our
CLI
to
like
make
it
more
organ
amah,
so
that
it's
easy
to
use.
When
enjoying
some
of
these
test
notes,
we've
been
ramping
up
a
bit
of
our
testing
as
well
and
most
of
the
aspects
of
white
house
going
for
actually
getting
public
use.
H
We
also
don't
we've
implemented
encryption
for
BL
s
keys,
so
we
have
like
a
key
store
forever.
Dk's
we're
passing
the
test.
Spect
is
for
0.9.0,
but
we
still
need
to
kind
of
finish
the
update,
which
will
probably
be
doing
next
week.
Early
next
week,
we've
also
been
implementing
slashing
protection.
We
have
actually
a
PR
fashion,
protection
for
the
validator
client
and
we're
looking
to
use
SQLite
for
the
database
inside
that
I
think
that's
mainly
the
main
stuff
from
us.
Thanks.Thanks.
A
I
Hey
guys
and
it's
pretty
much
the
same
all
day,
plus
everyone
else
we
face
if
you
are
PC
related
parts
after
users
have
been
before
the
team
name
so,
which
is
nice
that
today
we
have
users
querying
our
testing
information
and
the
our
single
client
testing
is
currently
done
right
now,
since
were
lining
rushing
through
0.9
to
our
database.
So
we
finished,
which
means
during
on
a
few
days
ago,
and
it
will
cause
people
to
spread
test
for
both
stations
to
Sherry
and
si
si.
I
So
those
look
good
so
far
and
we're
planning
to
relaunch
our
test
name
by
the
end
of
the
week
and
in
the
process
we're
also
working
on
aggregation,
but
that's
not
really
passive
party.
We
can
run
in
the
newer
aggregations
batch
as
a
teacher
and
and
was
always
you
know,
splashing
on
both
protection
and
then
and
then
the
policing,
forefront
and
yeah
I
think
that's
many.
It.
J
Know
so
for
something
a
little
different.
We've
got
some
teen
changes,
removing
Ultimates
internally
from
incubation
to
the
product
side
of
Pegasus,
though
it'll
still
be
some
familiar
faces,
but
there
are
one
or
two
new
ones:
I'd
like
to
introduce
Meredith
things
on
the
call
she
did
a
lot
of
the
heavy
lifting
on
our
theory,
one
client
and
we're
very
glad
to
have
her
joining
the
Artemis
team
as
far
as
development,
where
it
goes
similar
to
everyone
else.
J
A
F
K
A
E
Don't
know
I'm
gonna
yesterday
we
start
had
our
first
meeting
with
light
client
friendly
folks.
The
light
client
task
force
soon
directly.
I
guess
you
know
nothing
new
presented,
but
we
had
a
great
Q&A
with
the
Schultz
all
foldy
on
the
like
line
and
sanitization
lies
client-server
and
sanitization
framework
that
he's
come
up
with.
We
have
a
recording
online,
it's
an
hour
long,
so
I'm
gonna
see
if
we
can
get
a
grant
or
not
a
grant,
a
little
bounty
together
to
get
a
transcript,
but
it's
great
to
just
get
get
this.
E
L
Yeah
so
we've
we've
made
some
progress
on
the
Els
civilization,
there's
a
new
hash
to
curve
draft
which
is
out-
and
this
is
the
one
you
know-
that
I'm
expecting
we
will
go
in
production,
wave
boy,
theorem,
there's
also
kind
of
updated
test
Suites
and
he
Rumi,
so
they
make
the
maintain
of
her
room
either.
The
really
fast
GLS
implementation
has
accepted.
L
L
L
The
the
cryptography
seems
to
be
blossoming
because
we
have
these
these
new
constructions
for
snarks
for
accumulators
and
there's
also
new
groups
of
unknown
order
that
are
rumored.
So
beyond
the
RSA
groups
and
the
class
groups
there's
kind
of
a
rumor,
the
yet
another
one
which
has
some
very
nice
properties,
so
yeah.
This
is
exciting
stuff,
that's
happening
that
will
be
relevant
in
Phase
two
and
also
at
the
application
layer.
L
D
L
M
So
we
now
have
a
central
entry
point
challenges
that
we
framed
at
all
and
yeah
I
mean
we're
like
expanding
our
programs
there,
because
we've
seen
like
some
very
good
work
come
out
of
it
and
so,
and
it
seems
like
those
bounties,
are
a
good
way
of
like
getting
our
cryptography
and
we're
doing
some
very
new
cryptography
here
at
the
moment,
yeah
better
validated
so
yeah.
If
you
have
any
people
who
are
interested
in
that,
you
want
to
share
those
with
like
challengers
33m.
N
A
N
O
A
O
That
should
come
to
subdue
you
nicely
and
then
be
compatible
with
everything.
But
yeah
I've
had
a
lot
of
people
in
contact
with
me,
because
some
teams
already
implementing
that
full
ounce
of
bugs
in
my
implementation
and
unplugs,
all
that
go
all
the
way
back
to
test
vectors
for
the
one
key
source
which
is
being
little
uninteresting,
but
yeah
good.
A
A
K
A
A
A
A
It's
largely
subtractive,
be
straightforward:
okay,
good
next
up
tests,
not
discussion.
My
general
read
on
the
past
two
weeks
is
that
people
are
working
on.
Oh
nine
people
are
also
working
on
getting
some
teams
working
on
getting
some
continued
single
client
test
set
stuff
out
there
and
there's
a
lot
of
general
intention
to
experiment
with
some
multi
client
behavior
on
different
teams.
Single
client
test
sets
in
the
coming
foxman
two
weeks
like
I,
said
at
the
beginning
the
call
a
more
orchestrated
test
net.
A
A
That
is
just
a
list
of
tooling
and
things
that
we
want
for
test
nuts
and
also
the
Associated
people
that
are
have
either
mentioned,
that
they're
working
on
it
or
or
not.
I
just
share
that
there
please
add
some
items
that
list
and
we
can
figure
out
how
to
we'll
prioritize
things
and
also
bring
in
some
external
resources
if
we
did
decide
cool.
So
that's
the
at
least
from
my
perspective.
The
Leyland
on
test
nuts
is
pretty
much.
A
E
A
Right
we
had
discussed
at
least
isolating
the
I,
think
some
of
the
signature
domains
or
the
versioning,
so
that
might
be
desirable,
I
think
at
least
from
in
terms
of
shark
counts,
and
things
like
that.
The
intention
is
generally
to
do
minimal
and
then
to
step
up
to
the
main
net.
Do
you
have
any?
Did
you
have
any
other
anything
else
in
mind
for
altering
the
configurations
for
test
nuts
I.
I
A
A
Yeah,
let's
I
saw
that
Justin
had
made
at
least
thrown
up
some
counter-arguments
for
discussion
so
long
ago,
the
number
of
validators
to
start
the
chain
was
specified
as
think
about
half
a
million.
This
was
probably
about
a
year
ago
and
then
Alexei
doing
some
just
kind
of
getting
away
land
and
doing
some
reading.
When
he
too
was
concerned
about
a
gate
keeper
attack
in
which
a
someone
with
around
1/2
million
he
quickly
deposits
triggers
the
chain
to
start
and
then
prevents
new
deposits
from
being
processed.
A
This
was
this
attack
was,
in
the
context
of
there,
only
being
an
amount
of
depositors
to
trigger
the
chain
start
rather
than
also
a
time.
So,
given
that
there's
there's
a
Genesis
time
and
given
that
so
that
it
gives
other
people
other
than
attacker
a
chance
to
make
deposits.
If
that
was
the
case,
that
mitigates
a
lot
of
the
attack
potential
and
also
if
a
gatekeeper
attack
happened.
A
A
A
More
recently,
we've
discussed
that
maybe
it
makes
sense
to
reduce
the
amount
of
minimum
beef
to
start
the
chain,
primarily
in
light
of
this,
like
potentially
long
an
unknown
lockup
period.
It
allows
for,
if
there's,
if
there's
not
enough,
alligators
that
are
encouraged
to
to
validate,
allows
for
a
smaller
number
of
alligators
to
join
at
a
at
a
higher
game
in
those
kind
of
early
days.
A
A
G
A
A
Okay,
short
and
sweet
meeting
I
know
we're
all
pretty
heads
down
trying
to
get
stuff
done
so
I'll.
Let
you
get
back
to
it.
I
believe
we're
planning
on
meeting
in
two
weeks.
I,
don't
think.
That's
us
Thanksgiving,
so
I
think
I
think
we're
gonna
miss
that
which
is
good
cool
thanks.
Everyone
talk
to
you
soon.