►
From YouTube: Eth2.0 Call #29 [2019/12/5]
Description
A
A
One
is
the
removal
of
signing
earth
which
proto
on
the
last
call
said
he
was
going
to
execute
and
we
were
gonna
get
consensus
by
this
call
and
weather
change.
Great
I
have
had
some
conversations
with
a
handful
of
you
that
are
overwhelmingly
all
those
were
overwhelmingly
positive
and
that
it
is
much
cleaner
and
it
cleans
up
some
issues
around
caching
and
cleans
up
some
issues
around
not
having
to
provide
zero
signatures.
Zero
doubt
signatures
and
consensus,
which
had
some
typing
issues
and
in
general
positive
but
I
will
not
speak
for
everyone.
Are
there?
A
Looking
for
winter
right
now,
so
I'm
sure
that
you,
the
plan,
will
be
to
probably
merge
it
in
three
hours.
So
speak
speak
now
on
that
issue
here
on
that
issue.
Here,
if
you
have
initiative
in
general,
I'm
I've,
it's
very
nice,
it's
very
clean
makes
things
a
lot
better,
so
I'm
I'm
acutely
that's
issue,
1491,
sorry,
four
plus
four
fourteen.
Ninety
one.
A
A
You
can
check
out
the
issue,
but
we
have
a
fix
for
it,
but
we
have
it's
actually.
Pork
choice.
Stuff
is
increasingly
difficult
to
test
and
kind
of
specify
scenarios,
so
we
will
probably
Murchison
soon
but
we're
working
on
a
better
way
to
more
generically
specify
complex
for
choice
scenarios.
This
would
also
be
in
conjunction
with
some
of
the
intended
for
choice.
A
Tests,
release
had
a
couple
of
conversations
I'm
a
little
behind
on
these
conversations
on
what
that
test
format
might
look
like
there's
it's
kind
of
between
unit
testing,
some
of
these
functions
that
are
in
the
spec
versus
more
just
integration
tests,
throwing
a
bunch
of
blocks
and
add
two
stations
at
a
client
and
getting
a
result
in
head.
So
that's
a
priority
that
we're
working
on
we'll
probably
get
this
released
without
additional
work
choice
s
very
soon,
with
the
removed
sending
group
but
poor
traces.
B
Are
still
suffering
one
thing
that
could
be
done:
I'm
just
thinking
for
multi-threading
testing,
it's
very
hard
also
because
we
have
to
like
test
interleaving
of
four
or
five
phrases
in
different
order,
and
there
are
ways
to
do
that.
So
maybe
we
can
reuse
the
same.
I
can
put
some
blog
posts
on
how
it's
done.
We
can
use
the
same
technique
because
sometimes
you
will
receive
an
a
decision
just
before
the
photo
is
just
after
so
it's
the
same
scenario:
interleaving
of
various
inputs.
A
A
B
B
A
A
So
again,
those
two
pr's
need
to
be
merged.
Before
we
release
a
major
release
very
soon.
I
know
some
initial
test
nets
will
be
on
the
Uni
to
which
I
think
it's
totally
fine.
From
my
perspective,
just
make
sure
that
we
specify
when
you're,
specifying
your
tests
at
which,
which
it
is
there
are
some
the
integration
of
the
modified
bill
aspect
with
respect
to
the
standard.
There's
a
couple
of
pr's
out
those
are
also
a
priori
to
get
merged
and
to
get
out
to
be
built
and
tested.
A
I
think
the
intention
is
to
likely
do
a
release
right
after
New
Year's.
That
includes
the
BLS
modifications
such
that
test
nets
during
December
will
have
the
old
BLS,
but
maybe
during
December
people
begin
to
work
on
the
integration.
The
new
BLS
and
then
come
to
your
test.
Nets
will
have
the
new
BLS
implementations,
the
any
any
tests
net
that
is
long
running
and
gives
us
signals
to
move
to
main
net
would
have
to
have
the
correct
signature
scheme.
So
I
don't
have
I,
haven't
taken
a
look
at
these
I
know.
A
D
D
So
you,
if
you
are
handed
a
sort
of
black
box,
you're,
less
library
that
implements
the
ITF,
the
ITF
spec,
then
these
are
sort
of
the
wrapper
functions
you
need
to
make
them
compatible
with
with
the
PI's
that
the
each
suspects,
so
it
should
be
classic
clean
and
nothing
expected
already
needed
there
I'm
in
the
process
of
changing
PI
ECC.
So
we
can
get
all
our
test.
Vectors
updated
for
this
and
then
hopefully,
in
the
next
day
or
two
one
of
those
should
be,
should
be
really
cool
for
merchants.
A
A
E
C
B
A
B
B
We're
gonna
use
a
cross
Peck,
we
finished
sir
last
SSE
bugs
last
week.
So
now
you
can
use
n
CLI
again
to
compare
Adams
against
yours.
Regarding
optimizations,
we
removed
the
last
vestige
of
our
quadratic
behaviour.
Now
we
reduced
OCI
time
for
over
50
minutes
to
less
than
20
minutes
and
the
last
bottlenecks
that
we
have
are
sha-256
and
brss,
but
it's
not
really
blocking
for
having
the
state
transitions
under
6.
B
Second,
on
test
net,
we
are
debugging
syncing,
it
works,
but
we
have
some
edge
cases
and
we
met
a
lot
of
polish
on
the
instructions
so
and
it
has
been
tested
from
first
start
and
from
restarting
so
it
should
work
much
better
than
the
previous
week
on
tests
and
CI.
We
are
in
the
process
of
setting
up
our
Jenkins,
so
the
goal
is
to
be
testing
members
on
control
hardware,
especially
on
Draenor,
on
our
phones,
and
we
are
no
auto
tracking
on
tests,
especially
state
transitions,
to
make
sure
we
don't
have
any
regression.
B
We
now
have
something
similar
to
NCL
I
called
NFS,
fuzzing
endpoint,
and
we
have
PR
pending
on
CPE,
become
phase
repo,
with
shuffling
as
a
proof
of
concept
and
for
networking.
We
are
now
ready
to
integrate
people,
so
it
does
all
the
building
blocks
are
ready,
so
it
can't
aggression
can
be
done
in
the
coming
weeks
to
remove
the
p2p
demon,
so
I
guess
next
purchase.
Is
this
v5.
E
Everyone
yeah
generally
a
lot
of
work
to
get
up
to
spec
0
9.
So
it's
a
lot
of
fork:
choice
updates
and
some
refactoring.
On
our
end,
we
have
an
open
PR.
That
I
believe
is
pretty,
give
us
better
sort
of
currency
handling
overall
and
then
a
bunch
of
various
bug
fixes
stability
work
as
we
propose.
We
talked
about
that.
A
F
Hey,
so
we
swapped
out
our
pls
implementation
in
the
past
few
weeks
with
a
Wasson
build
of
Hermes,
BLS
and
great
great
results.
Things
like
40
X,
roughly
speed-up
across
the
board.
Well
yeah,
we
implemented
the
the
BLS
vips
to
333
through
to
335,
just
as
some
utility
libraries
not
immediately
used,
but
will
probably
be
useful
soon.
F
A
G
Yeah,
so
we're
up
to
date
with
zero
point
I'm
going
to
including
naive
aggregation
implementation
in
chat
with
gem.
About
that
request.
Responses
done,
we've
been
testing
against
prism
on
lighthouse
and
I
think
there
might
be
a
few
little
corner
cases
we
like
house,
but
our
Adrian
will
reach
out
that
team
to
discuss
our
main
focus
for
this
sprint
remains
jawed
being
able
to
join
public
test
nets.
So
it's
a
lot
of
work
on
syncing
importing
deposit
receipts
and
and
that
bread-and-butter
staff,
and
also
finishing
off
the
disk
v5
integration
I
think
that's
it.
H
Yeah,
hey
guys,
our
single
clan
tester
has
been
running
smoothie,
although
we
saw
a
few
instants
of
finality
regression
and
thanks
to
Danny
for
helping
us
with
a
debugger
on
that.
That
was
super
helpful
and
we
all
will
have
a
pig
in
Chains,
plural,
Ronnie
and
thanks
to
Peter
from
b-fly
are
making
that
happen.
So
with
that
there
was
lots
of
faces
and
hardening
in
our
RPC
server,
so
we
can
serve
people
that
want
to
build
that
became
chains
blower
or
like
any
cool
stuff
with
it.
H
We're
primary
focus
on
this
0.92
relaunch
so
and
then
remaining
ward
of
aggregation
protocol
and
then
the
equal
one
data
majority
voting
and
I'm
Raul
spend
all
time
optimizing
SSC
by
creating
a
functional
cash
for
the
cost
for
a
costume
state
SSC.
With
that
we
sell
about
like
50
times,
performance
improvement
during
doing
syncing
and
yeah.
That's
about
it.
I
I
We
look
like
we're
gonna
be
on
track
for
that,
but
was
still
kind
of
squashing
bugs
and
doing
a
number
of
different
optimizations
a
lot
of
optimizations
over
the
last
two
weeks
to
being
hopefully
kind
of
like
database
focused,
we've
implemented
a
schema
where
we
don't
duplicate
any
state
and
we
now
kind
of
have
these
checkpoints
so
that
our
database
is
pretty
small
when
we,
when
we
had
an
original
in
our
original
test,
that
was
kind
of
growing
way.
Too
far,
so
it's
been
a
real
time.
I
I
I
Now,
with
a
lot
of,
we
found
that
there's
a
bit
of
lag
and
some
issues
when
you're
trying
to
pull
out
a
large
amount
of
blocks
from
a
single
node,
we've
tied
up
with
our
logging
to
make
it
a
bit
more
user
friendly
for
when
people
come
and
join
this
thing
our
validator
onboarding
Doc's
are
all
written.
It's
in
a
PR
we're
waiting
to
merge
that
we've
got
metrics
and
monitoring
for
the
tests
and
all
up
and
running
so
that
kind
of
set.
I
That's
that's
all
good,
and
just
as
a
PSA,
we
pulled
our
testing
it
down
today
because
one
of
our
major
boot
nodes
or
some
of
the
nodes
booted
the
up
boot
or
the
other
nodes,
often
ban
them.
We
were
being
fairly
strict
with
nodes
on
the
network
that,
if
anyone
gives
us
anything
incorrect
or
invalid,
we
kicked
them
forever.
So
we've
made
up
here,
though,
that
would
just
need
to
get
most
down.
That
I
is
a
little
bit
more
lenient.
I
I
B
A
J
Yeah
we
have
updated
two
hours
back
implementation
to
0.9
and
point
to
not
including
aggregation
stuff,
as
this
update
was
done
as
a
part
of
our
work
on
the
focus
tests
we
have
like
and
alex
is
working
on
integration
tests
for
the
pulp
choice,
and
we
are
almost
finished
with
them
and
ready
to
push
work
on
that
community
dispute
and
for
choice.
Yeah
hope
it
will
happen
next
week.
J
K
Yes,
so
for
us
so
updating
the
subject,
the
Casper
consists
of
the
engineering
is
subject.
It
was
thought
that
there
would
be
a
vulnerability
in
how
that
consider
the
injury
interact
with
rent
I'm,
a
quick
module
later
I
figure
out
it's
just
a
config
issue,
but
India.
We
need
to
probe
for
the
wording
somewhere
senior
shouldn't
configure
Chen
this
way
so
yeah.
That's
that's
for
the
second
part,
but-
and
we
are
also
we're
still
and
spike
0.9.0.
K
So
we
are
trying
to
join
the
currents,
public
prismatic,
test
net,
disarmed,
updating
the
networking
module,
but
currently
I'm
still
facing
an
issue
in
the
pr
I--'s
verification
which
is
slightly
weird
but
I'm
saying
what
might
be
the
issue.
So
we
pass
over
there
for
nigh
on
zero
spec
types,
including
the
BI
signature
verification,
but
we
seems,
cannot
verify
the
signature
on
the
prismatic
test
net,
so
yeah.
So
there's
our
current
progress.
A
L
I
didn't
expect
to
be
I
called
out,
but
yeah,
so
we
started
being
from
implementing
the
thing,
so
we
would
be
kind
of
this
back
but
hopefully
should
have
the
spec
implementation
because
you're
annoying
to
in
a
month
or
so
so
we
have
like
all
the
basics.
This
is
that
being
recognized,
ation
BLS
is
working
fine,
so
you
passing
the
bill.
This
is
that
all
the
container
casts.
L
We
have
all
the
containers,
so
we'll
continue
now
at
the
fork,
choice
and
and
all
the
become
change
specification
we
also
merged
with
we,
the
team
with
a
guy
from
Australia
called
swine
yeah,
so
Santa
may
be
a
request
for
invitation
here,
he's
been
working
on
the
bacon
chain
implementation
already,
so
we
have
some
code
that
passes
some
of
that.
We
can
chain
tests
and
we
just
merge
these
two
code
bases,
since
we
sure
had
some
conversations
with
the
guys
from
security
team
about
discovery.
L
F
F
On
top
and
there's
this,
and
if
challenge
of
figuring
out
like
exactly
how
much
it
should
include
yeah
so
right
up
coming
up
soon
on
that,
do
that
and
I
did
have
a
write-up
on
one
way
to
do
the
appearance
get
cross
charting
on.
You
know
the
write-up
coming
soon
on
how
to
I
mean
to
accomplish
the
things
that
I
was
trying
to
achieve
without
needing
to
do
that.
M
I'm,
going
really
really
deep
on
the
snark
stuff
and
actually
I
I
recently
did
zero
knowledge
study,
club
presentation
on
the
polynomial
commitment
schemes,
which
should
be
very
accessible,
so
I'm
posting
the
link
in
the
chat
and
I've.
Only
I
only
went
through
I
think,
roughly
one-third
of
my
slides.
So
there
will
be
more
our
presentations
in
the
coming
weeks,
I
guess
where
I
talk
about
polynomial
commitment
schemes
and
there's
like
this
fundamental
central
thing
and
snarks,
and
once
you
understand
the
role
they
play
and
this
bigger
framework,
like
everything,
becomes
so
much
simpler.
M
If
you
want
to
actually
understand
how
stocks
work
and
yeah
now
that
I
understand
stocks
better,
you
know,
as
the
tag
was
saying,
there's
kind
of
some
some
new
ideas
that
came
out.
You
know
from
multiple
people
and
and
yeah,
potentially
like
really
or
pretty
significant
break
for
snark
world.
So
hopefully
a
write-up
will
be
available
very
soon.
M
There's
also
been
you
know,
a
pretty
significant
breakthrough
in
MPC
the
MPC,
so
my
DD,
the
MPC,
has
successfully
has
now
successfully
invested
with
10,000
participants.
So
you
know
that's
kind
of
that's
awesome
openly
on
bias.
You
know
couple
orders
of
magnitude
and
it
shows
that
yeah,
so
the
new
hero
team
has
done
an
amazing
job
there
I
know
we
only
need
a
thousand
people
and
I
think
that's
sufficient
decentralization.
A
C
C
C
N
We
we
just
kicked
off
the
the
new,
the
next
phase
of
the
project,
which
is
about
building
abstractions
of
the
the
big
chain
model
that
we
developed
over
the
last
few
months
and,
of
course,
the
objective
of
all
of
this
is
to
to
show
how
safety
and
lightness
can
be
proved
on
the
change
specification,
so
so
yeah.
So
we
just
started
this
week
and
I
am
personally
going
through
the
details
of
the
gasper.
A
Great
thanks
and
the
area
also
prevent
that
verification
is
doing
the
last
bit
of
work
on
the
deposit
contract
and
working
on
a
write-up
for
public
review
to
be
released
within
the
month.
I
know
many
of
you
out
there
potentially
listening
or
anxious
to
see
that
deployed,
and
this
is
getting
that
out
for
public
review
is,
is
that
last
requisite
stuff?
O
I'll
we
quilt
help
chaperone
the
first
base
to
it.
You're
gonna
be
call
this
week,
and
that
was
a
lot
of
fun.
We
had
some
interesting
conversations
and
we're
trying
to
target
the
next
one
for
a
mid
January.
So
hopefully
we'll
see
a
lot
of
people
from
this
call
there.
You
can
see
some
of
those
conversations
regarding
to
phase
two
will
is
aggregated
some
questions
regarding
stateless
protocols
and
put
it
on
each
research.
O
Oh,
that
link
here
and
then
I'm
working
on
some
tools
to
improve
the
process
of
building
and
testing
execution
environments,
which
has
been
one
of
the
big
pain
point
for
both
of
us
explore
in
that
area,
and
our
new
hires
are
still
working
on
the
simulation
they've
been
on
board.
It's
the
simulation.
It's
progressing
pretty
well,.
A
Okay
next
I
had
networking
and
then
realized
that
we
had
to
call
it
up
by
yesterday.
I
dropped
two
very
good
links
from
then
and
mommy.
There
are
notes
from
the
call
that
you
can,
if
you
were
not
a
part
of
that
call,
you
can
check
out
in
general,
it
was
a
survey
of
what
is
going
on
all
the
various
problems
at
hand.
A
The
maybe
more
interesting
component
was
trying
to
figure
out
the
problems
that
aren't
getting
enough
resources
currently
in
terms
of
research,
and
so
we
are
likely
going
to
do
a
follow-up
follow-up
call
in
about
two
weeks
and
I'll
post.
That
soon
are
there
any
just
general
updates
that
people
want
to
share
about
networking
here.
A
A
Mikail
added
an
agenda
item
about
discussion
of
ways
to
reduce
persisted
state
database.
Size
I
know
that
this
is
kind
of
independently
being
explored
by
a
number
of
teams.
I
know,
specifically
Adrienne
lighthouse
y'all
seems
been
working
on
it.
Do
you
want
to
give
us
a
critically
synopsis
on
what
y'all
are
doing.
A
I
Yeah,
so
we
there's
two
parts
throughout
well:
I.
Guess
three
bucks
point
is
the
the
hot
cold,
as
you
said,
so
hot
is
pretty
much
anything
after
finalized
things
that
move
so
once
things
are
finalized.
That
kind
of
goes
in
into
the
cold
database,
so
in
in
the
cold
database,
which
are
which
are
things
that
shouldn't
be
changing
or
moved,
we
can.
We
can
kind
of
streamline
where
they're
actually
stored
on
the
disk.
I
I
guess
the
the
main
gains
that
we
had
is
doing
an
a
Nimbus
style
approach,
which
we
store
state
snapshots
instead
of
every
state
and
then,
if
you,
if
some,
if
we
need
to
read
the
state
for
any
reason
in
the
cold
database
at
some
stage,
you
rebuild
a
state
or
replace
that
or
you
buy
the
state
from
the
blocks
that
we
that
we
have
in
the
diary.
So
you
keep
the
blocks
and
checkpoint
states
we've
also
added
a
essentially
we
don't
duplicate
any
of
the
states.
A
I
It's
configurable
at
the
moment.
Michael
was
playing
around
exactly
when
to
do
it,
so
it's
obviously
a
trade-off
between.
If
you
need
to
pull
data
and
you've
got
massively
long
snapshots,
then
it
takes
time
to
actually
build
the
particular
state.
You
need
to
pull
I
think
there
was.
There
were
some
some
metrics
I
can't
actually
remember
the
distance
between
the
states,
but
we're
measuring
the
time
it
would
take
to
fill
32
gig
on
a
hard
drive
and
we
worked
there
for
like
a
decent
gap.
J
Ago,
yeah
and
I
have
a
question
and
in
the
hot
storage
you
have
all
states
for
all
box
imported
since
finalized
one
right,
yeah
I
ablation,
because
it
could
be
huge
even
bit,
not
big
number.
While
the
daters
I
mean
hundreds
of
megabytes
for
to
represent
an
epoch
and
yeah
it
it.
It
requires
some
reduction
as
well.
From
my
opinion,.
I
J
C
Well,
the
tree
said:
I
did
write
up
about
a
few
days
ago.
Comes
recipe
close.
We
only
really
started
changes
to
the
Merkle
tree
of
the
state,
and
this
is
something
you
choose
for
the
of
our
two
states
right
and
you
have
lots
of
parking.
It's
a
very
short
amount
of
history.
Rest
for
the
part.
Instead,
I
think
approach
from
lighthouse
is
really
do.
I
just
said:
listen
outside
just
make
it
fly
off
world.
P
See
yeah
I
just
wanted
to
mention
that
the
problem
is
somewhat
linked
to
which
states
we
want
to
keep
available
for
syncing
later
on.
If
we
ever
want
to
do
state
sync
across
the
network,
any
protocol
so
to
speak,
it's
probably
useful
to
times
agree
a
little
bit
on
which
states
they
sort
of
keep
available
to
others
and
whether
that
should
be
like
lost,
finalized
or
or
some
particular
week,
subjectivity,
parent
state
or
or
whatever
that
ties
in
a
little
bit
to
which
states
really
worth
keeping
in
mind
when
this,
when,
when
designing.
A
A
P
A
Yeah,
but
even
then
you
can
still
do
block
sync.
You
have
to
like
show
up
with
a
state
route,
get
a
proof
about
a
block
from
that
state
route
and
then
state
sync
to
that
block
and
and
then
block
synced
to
us
block
synced
to
that
block
and
then
show
that
it's
the
state
route
that
you
cared
about.
So
there
are,
there
is
a
technique
in
which
we
don't
eat
it,
but
it
would
be
come
increasingly
useful.
P
P
J
A
A
A
A
F
I
guess
I
would
feel
like
doing
it.
At
least
this
I
gotta
pro
mean
like
at
least
nestled
in
the
kind
of
the
scaffold
or
phase.
One
is
importance
to
get
out
there.
Just
so
people
can
start
building
the
thing
and
testing
the
thing.
Yeah
yeah
I
think
there
is
the
fraud
proofs
part
as
well,
but
the
fraud
groups
part
is
like
like.
If
we
assume
notes
are
honest
and
it
literally
doesn't
matter
so
I
guess
the
foot.
F
A
F
Thing
to
think
about
is
given
that
we're
not
doing
a
explicit
fee
market
and
face-blind,
like
basically
a
figure
out
like
what
mechanism
will
you
will
use
the
suggest
that
people
used
to
pay
for
getting
data
included
and,
if
is
one
blocks
or
vary
and
option
would
be
it's
like.
So
as
I
see
it,
the
meet
the
primary
users,
their
phase,
one
are
gonna,
be
like
cat
pictures
and
optimistic
roll-up
yeah.
F
It
turns
I,
don't
think
we
need
to
make
anything
more
to
make
a
phase,
one
optimistic
or
friendly,
because
well,
oh
yeah,
the
thing
that
all
right,
sorry,
the
thing
that
we
do
need
is:
we
need
some
way
for
the
youth
one
chain
to
learn
about
the
contents
of
the
youth
through
chain
right.
So
basically,
this
stuff
we're
gonna
do
anyway
to
build
a
bridge.