►
From YouTube: Eth2.0 Call #36 [2020/3/26]
Description
A
A
A
This
has
some
continued
networking
updates
that
we've
been
working
through
the
past
about
10
days.
It
also
has
fixed
virtue,
critical
bugs
one
in
testing
and
one
in
the
rewards
calculations.
A
rewards
was
set
to
equal
instead
of
plus
equal,
so
which
also
highlights
some
both
of
them
highlighted
that
it's
likely
valuable
to
split
the
attestation
Delta's
function
into
some
sub
functions
for
more
granular
testing,
because
it's
very
difficult
to
capture
much
other
than
whether
the
values
are
going
out
there
down.
A
But
if
you
mess
up
a
calculation
in
the
middle
with
respect
to
testing,
it's
easy
to
throw
a
little
function
and
not
really
really
cool.
So
that's
coming
this
release
I'm
because
of
the
critical
bugs
and
the
previous
one.
We're
gonna
go
ahead
and
say:
use
this
as
your
target.
That's
very
especially
respects
the
state
transition.
Very
minor,
I
hope
y'all
are
having
a
good
time
working
through
p0,
11,
I'm
sure
you
let
us
know
in
a
minute
other
updates
on
testing
and
release.
B
Yep,
okay,
so
we've
been
working
on
the
Java
integration,
which
is
pretty
much
done.
We
got
the
shuffling
up
and
running.
We
just
need
a
way
to
disable
signature.
Verification
on
take
you
I'm
sure,
they'll
come
very
very
soon.
We're
revamping
the
architecture
completely
we're
actually
considering
rewriting
the
differential
for
any
rust.
B
Patrick,
wasn't
security,
fuzzing
expert
started
working
with
us,
we'll
have
a
look
into
e2
and
all
the
different
implementations
writing
started
online.
On
Monday,
we
also
found
a
minor
type
error
in
Isis
bed,
which
is
not
exploitable
or
at
least
not
directly
exploitable,
but
we'll
make
sure
to
report
it
and
that's
it.
C
So
stupid
study,
progress
on
network
testing,
a
swimmer
is,
if
all
thing
like,
introduce
more
features.
We
are
starting
to
get
a
good
interface
in
the
Python
repair
room,
so
in
the
interface
and
use
rumor
for
our
sink
last
as
a
proof
of
concept,
we
have
synced
the
first
10,000
blocks
of
light,
as
does
nuts
if
to
inspect
specification,
including,
and
so
mr.
only
studying
synchros.
It's
pretty
swim.
D
So
we
have
optimized
the
American
banking
news
so
that
the
default
transition
is
now
like
four
times
as
fast
is
what
we
have
before
we're
now
sitting
at
about
300
milliseconds,
vertical
transitions,
work
$33,000
with
the
main
tip
pumping
we
added
a
mode
where
prune
finite
state
as
a
quick
fix
to
keep
stars
from
growing
like
crazy.
While
we
test
thinking
and
we
started,
but
not
completing
work
to
replace
mob
TV
with
rock
CD
racks
Libby
is
out
of
the
box
a
bit
faster
than
mob
baby.
D
So
we're
expecting
a
speed-up
and
describes
that
our
discreet
file
implementation
seems
to
be
working
well
and,
like
testified,
and
we're
working
on
putting
out
a
separate
bail,
very
point.
The
rest
ideas
are
continuing
to
and
we're
hearing
that,
like
Senator
standardization
of
API
to
be
really
useful.
So
it
came
to
that
and
we're
hoping
to
find
something
with
time
and
effort
to
like
permit
that
and,
lastly,
we're
working
on
a
standalone
signing
service
which
support
them
live
in
peace
and
the
hardware
security
module.
D
E
F
Hey
guys
Terence
from
Chris
Matthew
labs,
so
we're
basically
just
working
on
version
11
and
with
the
biggest
feature,
which
is
the
dynamic
at
the
station
subnet
that
feature
that
it's
complete
right
now,
so
we
just
need
extensive
testing
and
then
iron
out
a
few
bars
here
and
there
so
so
and
I'm
talking
about
where
we
have
a
slasher
Rodney
in
production,
catching
slash,
turbo
offense
and
we
cut
our
first.
It's
a
novella
dated
double
booked
last
Friday
and
verify
the
external
date
/
/.
So
that
was
pretty
exciting.
We
added
our
continues.
F
First
casting
as
part
of
our
CI
pipeline,
we
have
seven
first
Argos
right
now,
which
are
tested
with
coverage
based
random
inputs.
We
also
made
a
lot
of
radical
improvements
on
on
the
advanced
TB
computation.
So
we
now
we
have
a
rapid
service
on
top
of
our
state
evey,
to
maintain
a
both
of
hot
and
cold,
an
accessible
state,
and
we
will
star
extensive
testing
on
that
later
this
week.
G
The
heart
from
Nimes
team,
we
continued
our
work
on
the
discovery
we
fight
implementation
and
we're
currently
interrupting
well
with
the
go
implementation
and
the
lighthouse
test
net.
Where
I
go
to
discover
130
nodes
there,
we
completely
dropped
the
goal
demon
from
our
development
branches
now
and
we've
launched
finalizing
test
net
based
on
Lippe
to
be,
but
the
stabilization
efforts
are
still
underway.
G
Then
we
are
turning
down
some
resource
leaks,
so
we
are
seeing
in
this
test
net
we've
synched
with
the
latest
spec
dot
11,
but
we
are
still
have
some
pending
words
on
the
networking
changes
like
snappy
or
similar
items
with
reduced
our
the
json-rpc
library.
We
got
one
from
our
theorem
one
client,
an
integrated
team
in
the
beacon.
Oh,
so
it's
now
supports
some
of
the
RPC
endpoints
that
are
supposed
supported
by
the
lighthouse.
G
G
We've
done
some
work
on
syncing
and
currently
sinking
is
working
in
the
p2p
a
snap,
but
there
will
be
more
ongoing
work
in
making
the
algorithm,
smarter
and
both
bouncing
to
the
requesting
more
appropriate
way.
And
finally,
we've
been
upgrading
our
compiler
tuning.
One
point
point
two
which
will
be
out
in
maybe
the
next
few
days.
H
Let's
start
ok,
so
we
just
finishing
up
to
c5
implementation.
You
need
to
integrate
it
and
do
a
few
more
tests,
but
it's
good.
We've
been
spiffing
up
our
two
node
local
test
net,
just
fixing
some
various
things.
We
noticed
we
had
a
bug
in
our
gossip
validation
and
we've
been
just
fixing
up
our
API
for
that
and
we've
been
working
now
on
on
spec
updates
and
we
got
a
new
contributor
recently
who
is
helping
us
out
with
our
like
a
web.
I
Hello,
so
this
one
I
wiII
be
focusing
playing,
expect
version
11,
so
the
majority
of
the
work
has
been
around
during
the
attestation
aggregation
scheme,
working
mainly
from
a
networking
side
stays
Orion
has
been
working
on
that
a
lot
along
with
Hawaiian
and
diva
so
Adrienne.
Those
team
have
those
people
have
put
some
new
search
routines
in
this
V
fire
to
assist
with
peer
discovery
on
the
sped
up.
I
I
I
We've
been
working
with
a
free
who
has
been
playing
with
some
of
our
tests
at
deployment
tools,
just
kind
of
the
first
time
that
we've
had
anyone
use
them
that,
except
for
the
altars.
So
that's
been
really
helpful.
We've
been
submitting
lots
of
really
good
issues.
We
did
some
more
optimization
stuff
around
batch
verification
of
blocks.
J
Everyone
nothing
too
crazy.
Other
than
kind
of
the
stuff
for
one
else
has
been
working
on.
We've
been
working
to
pull
out
a
separate
other
client,
so
that
work
is
pretty
much
on
the
completion
which
is
exciting
to
see
otherwise
just
work
on
node
stability
and
the
b11
spec
updates,
along
with
some
infrastructure
work
for
single
client
test
nuts.
A
C
K
We
have
been
working
on
generalizing,
the
Casper
model
to
to
support
dynamic,
validate,
turns,
and-
and
we
have
done
that
so
we
have.
What
we
have
right
now
is
is
a
model
of
Casper
as
given
in
the
gasper
of
paper,
so
so
the
model
has
books
of
of
accountable
safety
and
possible
likeness
we
use
and
for
assuming
K
finalization
and
dynamic,
validate
cells,
and
what
we
are
working
right
now
on
is
on
showing
the
bound
given
by
the
theorem
and
that
big.
K
This
is
also
in
addition
to
the
the
second
model
in
K,
so
they,
the
K
model,
is
an
abstraction
of
the
beacon
chain,
transition
function,
state
transition
function
and
that
K
model
does
actually
both
fixed.
Very
data
sets
and
anna-marie
datasets,
and
it
also
includes
partial
refinement
proofs
showing
that
essentially
linking
the
two
model
to
the
two
models
together,
showing
that
the
K
model
satisfies
the
assumptions
that
are
made
in
the
in
the
top
level
model
via
the
croc
model.
K
In
addition
to
some
properties
relating
to
the
state
transition
function,
there
are
still
some
some
other
properties
that
I
think
still
need
to
be
proved,
but
we
are
working
on
those
as
well.
So
the
the
point
of
this
effort
is
is
to
show
that
the
the
we
can
change
state
transition
function,
satisfies
accountable
safety
and
possible
lightness
that
level
and
then
the
ultimate
goal
is
to
be
able
to
eventually
show
that
the
implementation
itself
satisfy
satisfies
these
properties.
A
M
L
Quilt
with
the
ease,
research
and
that's
a
II
framework
and
I
think
the
general
direction
now
is
didn't
lose
away
from
these
as
a
design
for
at
the
earn.
No,
no
it's
going
yet,
but
so
I
think
Johnny
ray
is
going
to
move
into
doing
some
sort
of
network
monitor,
and
this
would
be
helpful
for,
say,
zero
being
and
when
I
monitor
the
activity
of
the
network
and
some
better
understanding.
L
What's
going
on
there
and
mikail
just
published
eight
and
some
research
about
and
East
one
to
bridge
finality
gadgets
and
I
think
that
are
his
conclusions
are
coming
closer
to
the
conclusion
that
the
I
think
the
foundation
is
already
at.
That
is
a
bridge
or
a
finality
gadget
is
length
to
finality,
makes
it
kind
of
like
an
in
feasibility
and
so
I
think
we're
gonna
shift
into
working
on
them.
Each
wanting
to
merge
more
likely.
N
Sofra
and
I've
talked
about
this
and
the
other
calls
before,
but
regarding
a
polynomial
commitments
for
stage,
there's
been
an
obviously
that
each
research
purse
that
I
published
a
couple
of
weeks
ago
and
then
since
then,
Dan
cratis,
public
history,
man,
Dallas
Terrace,
comp
with
Miss
diem
and
the
thing
that
I
presented
yesterday
of
this
UK
study.
Quad
was
basically
some
improvements
to
the
version
that
I
came
up
with
that
remove.
A
A
Cool.
The
next
item
is
well
tonight:
multi-client,
test
net
discussion,
largely
there's
two
efforts,
the
first
of
which
is
getting
a
multiplying
test
set
up
the
which
we
might
see
a
few
give
birth
and
die
rebirth
and
then
also
to
do
sort
of
I
sense.
If
you
could
focus
largely
today,
would
be
on
that
first
effort
after
II.
Do
you
want
to
talk
about
what
you've
been
thinking?
We've
been
looking
into
your
thoughts
here.
M
Yes,
thank
you
for
having
this
is
my
first
East
Room
2.0
card
so
to
be
here.
I
previously
were
no
me
yet
parrot
is
not
interested
in
the
serum,
so
I
have
plenty
of
time
now
and
historically,
I've
been
following
assumed
to
point
out
since
early
implementations,
officer,
hi,
Bert,
Casper,
proof
of
motive
of
stake
and
I
believe
Trinity
harmony
and
parity,
and
we've
come
a
long
way,
and
now
that
assume,
2.0
spec
is
more
and
more
stabilizing
and
I
seasoned
needs
that
there
needs
to
be
some
correlation.
M
M
I
have
plenty
of
time.
I
can
have
coordinating
things.
I
used
the
last
two
weeks
to
investigate
clients,
capabilities
tooling
around
creating
chestnuts.
What
does
it
involve
to
create
a
test
net
and
so
on
and
yeah?
So,
yes,
polar
I
said
I
mainly
work
with
lighthouse,
but
I
also
want
to
learn
how
all
the
other
clients
are
capable
of
interoperability.
M
What's
the
status
of
tooling
around
creating
test
nets
in
for
each
of
the
clients
for
ads
I'm,
not
aware
of
and
yeah,
this
is
all
the
things
I
want
to
learn
more
about
I'm
I'm
q9f
on
this
core,
and
you
can
spin
this
out
and
to
having
separate
cause
on
this.
We
can
use
separate
discs
or
shares
of
cases,
but
yeah
any
any
comments
on
that
I'm
happy
to
learn
more
about
what
can
be
done,
how
we
can
contribute
yeah.
A
Cool
yes
thinking
you
and
I
can
either
go
back
and
forth
on
some
of
the
core
requirements
and
things
that
we're
gonna
need
to
standardize
and
then
share
that
more
broadly,
we've
done
surveys
in
the
past
to
kind
of
get
a
handle
on
where
everyone
is
at,
especially
with
respect
to
the
core
items.
So
we
might
do
some
sort
of
limited
survey
again
as
for
organization
beyond
this
call,
that's
likely
warranted
I
think
we'll
probably
at
least
a
couple
weeks
out,
because
I
think
everyone's
a
version
that
would
like
to
target
is
pretty
much.
A
The
hadn't
expected
a
and
people
are
working
to
get
there.
As
discussed
on
the
networking
call.
Yesterday,
some
of
the
complexities
people
are
working
through
some
of
the
complexities
in
this
aggregation
scheme.
I
think
prior
to
very
recently
we're
kind
of
cutting
corners
there,
but
we
expect
to
be
fully
up
to
the
spec
very
soon.
M
A
A
Unfortunately,
also.
Fortunately,
we,
at
least
in
the
past
two
weeks,
have
seen
a
lot
of
conversation
around
networking,
primarily
because
some
people
are
working
through
it,
the
first
time
and
also
hitting
some
the
pain
points
for
the
first
time.
So
we've
seen
more
iteration
on
that
component
of
the
spec,
and
some
of
these
iterations
have
been
breaking
so
it'd,
be
hard
to
unless
we
were
versioning
protocols
within
the
same
protocol
would
be
hard
to
freeze
that
today,
I
think
likely
in
the
next
two
weeks.
A
We're
still
gonna
see
some
some
bumps
on
that,
so
state
transition
freeze
and
targeting
soon
a
networking
freeze,
I,
don't
have
a
good
intuition
on
how
much
how
many
more
changes
we
might
see
there,
because
a
lot
of
us
just
been
led
by
the
kind
of
networking
experts
on
each
team.
Finding
some
of
the
issues
but
I
know
we're
getting
into
a
better
place.
There.
O
O
O
Yeah
I
I
would
almost
recommend
reading
the
Python
instead
of
the
that
nothing's
changed
basically
in
hashed
opposed
sorry,
indeed
via
their
specs
v2.
Basically,
the
old
ones
expired.
So
the
update
was
just
the
version
bump
and
the
past
occurred.
Things
have
changed
the
hash.
The
field
mechanism
has
changed
from
HK
DF,
a
sort
of
custom,
key
extension,
also
accustomed
extension
mechanism.
So
that's
yeah
that
should
be
doable
and
it
was
I
think
a
bit.
Ok,.
A
So
I
think
what
we'll
do
is
this
version
releasing
today
free
state
transition?
Have
it
be
the
tangible
target,
maybe
a
release
of
version
12
when
we
have
this
breaking
signature
scheme
come
in,
knowing
that
the
rest
of
the
items
are
stable
and
as
clients
get
up
to
that
up
to
speed,
you
can
shift
the
effort
towards
that.
A
A
Talked
a
little
bit
about
this
long,
there's
a
blog
post
and
some
of
the
chats.
The
intention
here
is
to
not
allow
the
ITF
standard
to
be
the
blocker
on
living
the
main
net,
and
so
we
will
try
to
implement
their
latest
whatever
the
latest
draft
is
and
ultimately
probably
try
to
shake
hands
with
a
couple
of
other
blockchain
projects
that
are
also
trying
to
move
quickly
and
conform
upon
one
of
the
traps
if
they
have
not
fully
stabilized
but.
A
Right
so
I
think
a
lot
of
this
conversation
is
probably
going
to
be
had
on
some
different
Doc's
will
be
sharing
significant
things
that
will
try
to
standardize
on
and
increasingly
so,
spending
out
test
Nets
testing,
sync
across
clients,
and
things
like
that.
Is
there
anything
else
after
that?
You
want
to
talk
about
today
or
is
any
questions.
People
have
for
just
about
this
process
or
thoughts
or
comments
before
anyone.
M
I
mean
yeah
I
have
a
lot
of
questions,
but
I
will
be
going
from
Senate
Shannon
from
plant
client
and
folks
team.
So
please
be
Rosemere.
If
I
have
a
lot
of
questions,
I
I
just
need
to
learn
more
about
where
each
client
is
and
what
the
tooling
status
isn't,
how
our
chestnuts
can
be
spun
out.
Each
of
the
clients
and
yeah
I
will
take
those
offline
mainly,
but
if
anyone
has
a
comment
now
just
go
ahead.
A
Thanks
al
for
you-
and
you
know,
I
think
it
has
been
valuable
to
lighthouses
after
he's
been
poking
around
and
they
count
having
a
dynamic
conversation
about
this
tooling,
so
help
them
out,
and
that
will
likely
help
you
out
too
after
he
is.
Are
there
others
from
the
Goya
initiative?
Greater
interest
in
this?
Are
you
flying
solo
right
now.
M
A
A
Okay
expect
discussion.
We've
touched
on
probably
the
most
pressing
items,
which
are
that
there
are
a
couple
of
political
bug,
fixes
that
are
coming
out.
Just
keep
your
eye
out
on
that
and
I
recommend
just
immediately
bump
into
that
version.
Instead
of
finishing
honestly,
because
you're
gonna
finish
out
on
zero,
these
are
11.
I
could
be
I'll
pass
the
test
because
test
generations.