►
From YouTube: Eth2.0 Call #44 [2020/7/23]
Description
A
B
People
of
YouTube-
let
me
know
you
can
hear
us.
The
agenda
is
in
the
chat,
nothing
crazy
on
here.
Let's
go
ahead
and
get
started.
Okay,
testing,
release,
updates,
there's
an
ongoing
efforts
by
Lakshmanan
proto
to
turn
rumour
into
chain
tests.
They
can
maybe
give
us
an
update
in
a
minute
in
terms
of
the
lease
I
have
a
pending
release
fees,
zero
12,
to
which
I
said
I'd
get
off
by
yesterday
and
I'm
working
on
getting
out
today.
B
There's
a
couple
of
very
minor
PRS
so
going
into
it,
and
nothing
crazy
backwards,
compatible
generally
some
clarifications
and
fixes
primarily
in
the
gossip
conditions
section
of
the
PGP
spec.
So
we
released
that
apparently
in
v-0
12:1,
there
were
something
like
for
a
test
for
slashing
tests
that
were
not
published
and
I.
Think
funny
enough.
B
C
D
Small
update
for
me
kind
of
prompted
by
I
think
there
was
a
a
recent
case
where
it
was
found.
There's
like
a
a
das
vector
in
gossip.
If
you
proposed
blocks
that
were
not
the
descendants
of
a
known
finalized
block
or
something
like
that,
so
I've
been
kind
of
doing
a
deep
dive
on
other
possible
kind
of
holes
and
gossip
validation
that
we
can
use
to
kind
of
like
prevent
other
defectors
and
hopefully,
I'll
have
have
that
put
together
in
any
issue
or
something
soon.
B
Okay,
we're
gonna
move
on
to
test
nets
as
you've,
hopefully
seen.
There
are
three
very
small
attack.
Next
up,
they're
all
single
client,
they're,
four
notes:
each
their
128th
validators
on
each
of
those
networks,
there's
a
repo
that
we
posted
that
kind
of
shows
the
rules
and
shows
the
bounties
and
things
I
know
Johnny's
been
getting
his
hands
dirty
and
hopefully
others
on.
This
call
are
people
on
listening
on.
B
C
Maybe
something
to
emphasize
that's
right
now,
it's
your
best
chance
to
try
and
find
Ichigo,
specters
I,
think
clients
are
not
as
far
along
yeah,
definitely
small
and
it's
single
client
as
we
go
towards
dish
like
shared
client.
This
night,
it's
much
harder
to
get
the
business
done.
The
same
time
observe
this
new
attack
factor
of
splitting
the
network.
C
B
B
F
F
F
I
used
the
chance
last
week
to
repeat
the
client
benchmarks
and
case
you
didn't
see
yet
I
profiled,
all
three
or
four
Genesis
Valley
clients,
I
tossed
presume,
Kiko
and
Nimbus,
compared
their
high-level
performance,
metrics
and
I
published
a
small
report
on
that
and
the
given
stability
Naitonal.
Let
us
to
conclude
that
we
want
to
do
a
very
similar
test
in
it,
but
this
is
public
launch,
and
this
is
what
we
prepared
the
last
couple
of
days.
F
F
B
I
just
put
out
a
blog
post
this
morning
that
linked
to
some
of
the
relevant
stuff
and
also
linked
to
the
at
least
the
four
clients
that
we
know
will
have
Genesis
validators
and
encourage
people
to
try
them
out.
We
also
have
a
imminent
release
of
The
Associated
validator
launch
pad
just
like
an
educational
deposit
UI
that
expect
you
alive,
essentially
the
next
24
hours,
certainly
by
Monday,
which,
if
people
are
not
familiar
with
this
process
and
haven't
tried
out
Tesla's
before
this
should
be
like
a
good
portal
to
get
started
and
learn
about.
F
B
G
G
So
maybe
one
input
for
this
test
net
I
mean
it
would
be
great
if
we
try
to
track
100%
of
the
slashings
like
to
like
basically
open
an
issue
for
each
slashing
that
happens
and
make
sure
that
we
know
exactly
what
happened
because
I
feel
like
like
when,
when
we
launched
this
is
like
a
catastrophic
failure
for
those
who've
actually
staked.
So
so,
if
we
find
these
issues
now,
we
we
shouldn't
just
sweep
them
under
the
carpet.
G
C
B
H
G
Maybe
maybe
in
the
drip
hole
we
could
have
like
people
could
have
a.
We
could
have
a
table
where
everyone
reports
who
like
which
validators
they
run.
So
that
makes
it
easy
to
then
contact
them
and
ask
them
hey
what
happened?
Can
you
have
a
look
at
the
locks
for
those
who
are
happy
to
have
that
info
public.
B
Y'all
open
up
the
multi
client
repo
and
figure
out
a
good
spot
for
all
that
Thank
You,
dark
red
yeah.
We've
we've
definitely
been
a
little
bit
light
on
the
like,
oh
they're,
slashing,
but
that's
certainly
things
that
we
want
to
very
much
avoid.
I
mean
that
and
I
imagine
99%
are
just
gonna,
be
UX
failures
or
potentially
education
failures.
You
know
running
your
cues
in
multiple
places.
Thinking
that
that's
a
good
idea,
which
is
also
maybe
a
UX
failure,
because
you
should
be
good.
G
I
G
B
H
I
G
B
Doesn't,
though,
that
it
was
for
a
normal
beacon
notice
is
probably
a
very
expensive
query
there.
Is
these,
like
specialized
slashers
being
written,
which
resume
has
one
lighthouse
is
working
on
one
which
creates
an
index
like
a
more
indexed
database
of
the
attestations,
but
at
that
point
also
at
least
for
now,
it
was
pretty
expensive
operation
to
run.
Wait.
B
G
C
C
G
J
Because
it
need
an
API
thing,
though
I
mean
technically
in
the
beacon
note,
the
B
cannot
receive
Quantico
traffic.
So
if
you
have
to
find
running
to
things
on
the
network
anyway
running
one
of
them
receives
an
application.
The
particular
validator
that
you
know
is
connected
to
you
as
soon
as
that
validated
client
creates
the
authorization
will
try
and
even
the
become
out.
B
J
G
G
Saying
is,
if
you
didn't
start
them
exactly
at
the
same
time,
but
you
have
one
running,
you
didn't
remember
that
it's
running
and
you
start
you
think.
Oh
I'm
gonna
start
my
no,
but
now
then
that
new.
You
know
it
would
detect
hey
it
wasn't
at
a
station
six
minutes
ago
and
it
wasn't
me
so
I'm,
better
gonna
shut
down.
That's
I!
Guess
what
I'm
interesting.
B
G
K
B
We
were
thinking
on
those
for
for
clients,
1024
validators,
each,
which
is
ends
up
being
less
than
significantly
less
than
one
third
of
the
validators
and
I'm
leaving
a
chunk
for
maybe
some
of
the
EF
and
a
free
to
run
still
equaling
less
than
one-third
of
the
assumed
16
K,
which
it
might
very
well
be
more
so
somewhere
between.
Probably
one
third
and
one
sixth
of
the
Genesis
validators.
Does
that
seem
reasonable
to
everyone,
a
nice
backbone,
but
not
able
to
finalize
or
really
do
much
other
than
just
be
a
strong
percentage.
L
L
Support
you've
been
trying
to
do
some
bigger
end-to-end
tests
to
I
guess
make
sure
that,
like
our
node
is
stable
and
we
can
transition
between
an
initial
sink
and
a
regular
sink
scenario,
we're
kind
of
all
hands
on
deck,
trying
to
get
ready
for
this
test
net
and
because
we'd
like
to
be
validating,
at
least
in
some
part,
or
you
know,
participating
in
some
part.
But
we
also
don't
want
to
like
break
the
test
net.
L
M
Hey
everyone
yeah
from
prism
we've
been
working
on
the
accounts,
revamp
so
basically
restructuring
everything
about
how
key
management
works,
making
sure
we're
compliant
with
the
with
the
IP
standards
derived
through
our
wallets
and
also
working
on
also
also
finished
up
remote
signing
wallets.
So
people
can
basically
connect
to
a
remote
signing
server.
That's
one
of
the
most
requested
functionalities
in
prism,
and
we
think
that
you
know
our
key
management
was
our
weakest
link
and
then
our
user
experience.
M
So
we've
been
focusing
a
lot
on
making
it
easier
people
to
use
and
making
sure
that
it's
it's
a
it's
up
to
standard.
So
that's
been
mostly
I'm
working
a
lot
on
on
fuzzing
and
finding
bugs
we've
been
using
a
tool
called
cluster
fuzz
has
found
a
lot
of
interesting
bugs
in
the
code
base,
so
we've
been
fixing
on
that
and
Preston
was
the
one
to
pioneered
that
pet
initiative.
M
M
Yeah,
you
should
be
able
to
we'll
have
to
try
it
out.
We
do
implement
the
same.
The
keystore
standard
so
just
need
to
make
sure
there's
no
way
like
the
format's
all
match
up
properly,
and
nothing
is
nothing
is
weird,
so
we'll
give
it
a
little
try
very
soon
it's
updated
right,
so
we
should
be
able
to
try
it
today.
I
N
Yeah,
hey
from
Tico
sites,
we
are
still
working
hard
on
American
sub,
so
well
our
GV,
and
he
is
currently
stable,
small.
We
are
still
experiencing
native
memory
leaks
and
our
main
suspect
is
Rob's,
devine
pylori.
So
we're
currently
trying
different
to
be
options
to
to
eliminate
these
leaks
mixed.
So
there
was
lots
of
fuel
management
improvements,
ensuring
better
subnet
coverage,
some
civil
resistance
from
maintaining
a
minimum
number
of
peers.
N
They
randomly
selected
and
initiated
the
connection
to
also
we
are
almost
complete
supranational
blast,
west
library,
integration
and
it
showed
shown
preliminary
that
we
will
increase
our
import
speed
around
three
times.
Also
tackle
security
assessment.
Rfp
is
out.
Its
closing
date
is
third
of
August,
and
that's
it
from
tech
side.
B
O
After
a
few
days
of
just
optimizing
things
bringing
in
stuff
from
the
f2
Fastback
and
also
speeding
up
database
operations,
we're
sinking
at
13
slots
per
second
there's
still
a
few
issues
that
we
have
to
work
out
at
around
like
epoch,
256
but
yeah,
nothing
too
serious,
and
hopefully
we
can
get
get
that
fixed
up
pretty
soon
and
then
we'll
be
sinking
to
the
head
within
maybe
an
hour.
Oh.
B
O
B
O
B
B
E
Hey
everyone
so
updates
from
us
I
guess.
The
first
thing
is:
we've
got
a
new
team
member
on
board.
His
name's
Benedict,
his
github
handle
is
black
template,
so
Chris
name
say:
hi
I'll
show
you
a
coffee,
see
him
around.
We've
been
working
on
a
number
of
stability
improvements,
we've
also
similar
to
prison,
been
working
on
improving
the
key
management
system.
E
We
have
also
started
security
hardening
our
kind
of
our
networking
infrastructure,
and,
apart
from
that,
we're
kind
of
preparing
for
the
midea
test
net,
setting
up
some
internal
test
nets
and
running
some
code
to
make
sure
everything's
gonna
be
up
and
running
the
test.
Now
let
me
get
in
that's
it
from
us.
B
E
I
The
teams
we
have
three
auditors,
consensus,
divisions,
trade
of
bits
and
NCC,
and
the
idea
was
just
like.
If
two
has
multiple
teams,
we
have
a
fresh
take
on
audit
some
who
have
multiple
titles
in
collaboration,
to
establish
a
long-term
relationship
because
of
the
future
audit
for
phase
1
phase
2,
and
it's
separated
into
three
phases:
two
weeks
of
audits
and
when
two
to
three
weeks
of
fixes
three
phases
being
a
networking.
I
I
I
We
had
several
updates
in
the
past
month,
but
we
were
struggling
with
finalization
issues
that
are
being
fixed
right
now
and
on
the
cryptography
front,
we
updated
to
the
list
latest
AIP
253.
We
have
now
a
wide
extraction
and
withdraw
T's
and
we
can
handle
deposits
from
the
Ephraim
lunch
pad
that
will
be
released
soon.
I
We
also
refuse
Els
patterns
that
we
have
a
VLSC
wrapped
but
not
enabled-
and
we
also
updated
Milagro
to
use
miracle
call
from
Michael
spot,
because
all
the
background
was
more
than
a
year
old
and
miracle
core
arm
has
a
bit
more
optimization
and
sometimes
improvement
science
on
the
documentation
and
cost
front.
We
have
a
new
post
on
the
case
for
running
your
own
validator,
but
you
can
point
your
users
to
that's
it.
For
us.
Ok,.
B
A
Yeah
teets
AREX
you've
been
working
on
some
of
the
attack
that
stuff
and
just
wanted
to
reiterate
what
you're
saying
earlier,
I
think
if
we're
the
only
people
working
on
this,
then
you
know
I,
don't
think
we're
gonna
have
to
love,
love
security,
long
term
right
now.
It's
the
attack
nets
are
kind
of
like
the
softest
pieces,
lid
p2p,
because
they're
really
not
able
to
produce
at
the
stations
because
we're
not
validating
on
it.
P
P
Will
we
don't
know
dit
19
blocks
from
the
kana
blockchain,
we
run
tests
ten
times
for
each
block
or
we
subjecting
the
same
exact
compress
result.
Of
course,
the
compression
time
changes
slightly
so
with
the
average
of
the
turn
bronze
and
so
in.
Overall,
we
get
a
compression
ratio
of
1.6
more
or
less,
and
the
compression
speed
is
about
911
megabytes
per
second.
This
is
on
Intel
i5,
with,
for
course,
in
comparison
to
the
eighth.
One
result
that
I
presented
previously
the
compression
ratio
is
lower.
Compression
ratio
of
f1
was
one
point
eight.
P
P
If
we
we
also
compare
these
results
with
the
standard,
is
not
the
compassion
benchmark
that
come
with
the
with
the
source
code
already
just
to
make
sure
that
you
know
the
numbers
we
work
telling
worth
more
or
less
in
line
with
standard
benchmark,
and
we
got
about
seven
hundred
eighty
nine
megabytes
per
second
of
compression
speed
for
the
standard
benchmark.
So
the
nine
hundred
megabytes
per
second
that
we
are
taking
for
tonight
for
the
two
blocks
is
kind
of
quite
close
to
it.
But
these
do
not.
P
These
were
eyes
from
block
to
block
some
blocks,
get
lower
speed,
depending
on
the
data
the
lowest
we
had
was
476
mega
ways
to
second
and
the
highest
we
had
was
about
1234
5
megabytes
per
second.
So
this
is,
you
know,
there's
a
variation,
a
variance
between
between
blocks.
Do
you
know
the
compression
ratio
nylon,
the.
P
I,
don't
have
the
number
right
now,
I
can
put
it
on
the
disk
or
I
will
put
a
mod
in
a
spreadsheet
link
in
the
chat
so
that
you
can
all
look
at
the
day.
All
the
results.
All
the
data
in
case
somebody
wants
to
check
on
that,
and
one
more
thing
I
want
to
mention
is
that
we
started
validator
not
on
the
kana
network
test
net
and
we're
running
the
lighthouse
client
on
a
Raspberry
Pi,
for
we
will
be
testing
also
other
clients.
B
B
J
C
Not
in
the
immediate
release
to
there
Marcus
observe
changes
that
we're
looking
into
and,
in
particular
the
senior
affiliation
slightly
differs
our
clients
in
easy.
We
do
not
use
the
signature
verification,
but
some
clients
do
validate
it
if
it's
present
or
on
some
other
conditions,
and
then
there
are
some
other
related
fields
in
the
messages
suggest
that
message:
origin
sequence,
number,
public
key.
C
These
things
are
propagated
by
some
clients,
jobs,
best
motor
clients
are
randomized
by
some
clients
and
shut
up
this
motor
clients
and
should
try
and
standardize
this
and
try
and
keep
the
message
minimal.
So
I've
opened
with
a
pull
request
and
go
and
if
it
be
posturing
which
was
I
think
merged
yesterday,
this
is
more
or
less.
There
provides
options
that
backwards.
A
bit
compatibility
for
the
regular
course
of
behavior
would
provide
options
for
if
to
change
their
behavior
and
talk
these
extra
fields
and
it
is
not
compatible.
C
B
Yeah,
the
kind
of
TLDR
on
that
is
that
origin
signatures
on
gossip
sub,
we're
not
using
them
and
so
they're
kind
of
all
over
the
place
and
how
implementations
handle
us
not
using
them
and
better
we're
seeking
to
just
have
like
a
enable/disable
flag.
That
is
becomes
part
of
spec
and
adds
compartments
on
here.
So
we
don't
have
any
sorts
of
edge
cases
there.
But
if
you
want
to
dig
deeper
check
out
the
PR
that
proto
will
probably
share
in
the
chat
thanks
better.
B
My
understanding
right
now
is
that
some
clients
have
done
a
little
bit
of
due
diligence
on
the
spec,
some
at
least
looking
at
it.
Some
doing
some
prototypes
there's
a
prototype
of
Java
that
actually
has
a
full
simulator
and
Terence
has
done
some
work
on
implementing
the
face
once
back
and
push
back
into
the
specs
of
bits
and
then
my
other
understanding
of
the
problem
is
that
you
know
the
heavy
hitting
engineering
resources
are
primarily
on
shipping
phase.
Zero
I
think
at
some
point
in
the
next
couple
of
months.
B
Q
R
A
R
A
B
S
So
I'm
curry,
walking
on
sound
face
once
baked,
apply
patient
and
also
there
were
I,
have
some
notes
about
the
face
once
big,
but
I
personally
feel
like
yourself
could
be
simplified
a
lot
before
that
more
teens
to
join
the
develop,
but
I
mean
just
say
that
I
would
like
to
have
right
up
after
some
simplification
be
done,
and
that
would
be
more
proper.
More
tends
to
join
the
work.
I
think.
B
Q
S
B
Yeah
I
agree
as
soon
as
the
phase
1
testing
test
generation
PR
is
merged.
I
will
create
a
separate
branch,
any
two
aspects-
repo
that
includes
these.
For
anyone
that
wants
them.
I
know
McHale
wanted
to
take
a
look.
Terrence
probably
does
too
so.
I
will
drop
that
in
the
discord
once
that's
available.