►
From YouTube: Eth2.0 Implementers Call #23 [2019/8/15]
Description
A
A
The
stream
is
transferring
over
pulling
up
the
chat
box
chat
box
from
the
internet.
Please
let
us
know
when
you
can
hear
us
and
otherwise
we're
gonna
get
started.
This
is
issue
68
on
TM
repo,
the
agenda
I.
Imagine
everyone
seen
it
it's
very
similar
to
it
is
how
it
is
every
week
and
we
will
get
started
with
testing
and
releases.
So
somehow,
before
I
went
on
vacation
last
week,
I
messed
up
the
tests
and
BLS
tests
were
not
included.
A
Subsequently,
they
have
been
pushed
into
master,
but
not
cut
as
a
new
release.
We've
also
added
some
additional
SS.
The
generic
tests,
I
believe
we're
going
to
the
intention
and
we
can
discuss
this
is
to
cut
a
zero
rate.
Three
on
my
NER
Tuesday
release
these
new
tests,
zero.
Eight
three
is
entirely
non-substantive
and
includes
additional
tests
and
includes
some
sse
clarifications
and
maybe
like
a
typo
fix
and
something
else
with
the
intention
that
this
is
the
and
it's
substantive
ly
exactly
the
same
as
zero
two.
A
A
A
A
Yep
and
as
for
other
things
that
are
on
the
horizon
for
releases
the
deposit
contract,
we
run
a
verification,
is
doing
a
buy
to
buy
code
verification
deposit
contract.
They
found
a
VIPRE
compiler
bug
which
I
can
share
it
a
little
bit
that
is
to
in
the
works
of
being
fixed
on
VIPRE
side
and,
in
addition,
we're
going
to
be
adding
a
checksum
that
essentially
you
locally
pre
compute.
A
What
the
sec
root
of
your
data
should
be
and
add
that
as
an
additional
parameter,
these
two
things
will
be
added
to
the
repo
sometime
in
the
next,
probably
two
weeks,
but
I.
Don't
think
we're
gonna
cut
any
releases,
so
it'll
stay
in
dev
until
like
mid
to
late
September
in
mid
to
late
September.
There
are
a
number
of
small
substances
fixes
substance
to
changes
that
might
that
have
come
out
kind
of
an
audits
and
thinking
that
will
probably
come
out
after
interrupts.
A
One
of
the
most
substantial
is
to
remove
the
machinery
that's
currently
in
place
for
light
clients,
as
it
doesn't
quite
do
what
we
wanted
to
do,
and
it
adds
substantial
hashing
overhead.
So
this
would
be
a
deletion
of
like
active
index
routes
and
something
else
so
as
a
pure
deletion
shouldn't
be
too
bad,
but
I
want
to.
Let
you
all
know
that
is
on
the
present
as
well,
but
we
won't
be
cutting
that
out
until
after
our
interrupts
blocking
any
questions
on
that.
A
C
A
Removals
I
believe
so
and
if
somebody
wants
to
dig
around
and
find
any
conversation
about
that
and
Sharaf
that'd
be
great,
because
I'm
gonna
move
on
to
the
client
updates
and
I
can
look
around
yeah,
absolutely
and
I.
Think
I
think
there's
an
issue
around
transfers.
That's
disgusting
like
a
more
elegant
mechanism
to
do
it.
There
might
be
another
issue
around
removing
it.
As
for
the
other
stuff,
I
think
there's
an
issue
as
well
sure
that's
room,
oh
okay!
So
that's
testing
and
releases.
D
A
A
I
read
the
RFP:
it's
not
just
a
GUI
it.
It's
very
flexible
and
I.
Think
that
there's
also
there's
actually
proposal
right
now,
but
there's
probably
room
for
more
it's
very
flexible.
It's
pretty
much
do
some
of
the
things
that
clients
probably
aren't
going
to
be
focusing
on.
So
you
can
pull
out
a
bill
about
your
client.
You
can
add
a
GUI
to
an
existing
client.
You
can
build
out
monitoring
tools.
There's
you
know,
there's
a
lot
of
value.
Add.
G
G
However,
this
PR
is
still
waiting
for
get
nourished,
also
Anton
has
finished
a
gossip
sub
implementation
and,
as
a
part
of
GBM,
the
p2p
work
and
now
testing
that's
implementation.
With,
with
the
demon
from
what
I
know,
ash
hunt
has
finished
noise
implementation
as
well,
and
looks
like
phase
zero
of
a
GBM
implementation
is
close
to
to
to
the
release.
G
All
that
we
need
is
Java
API
and
some
infrastructure
things
to
be
done
to
get
there.
So,
hopefully
we
will
be
able
to
use
this
implementation
for
the
internal
process
that
we
are
having
in
September.
We
have
started
to
work
on
zero,
eight
to
upgrade
of
its
back
implementation.
It
involves
a
lot
of
things
to
be
done
in
terms
of
testing,
so
it's
work
in
progress
and
we
have
started
to
work
on
on
the
QA
started
for
a
little
bit
from
probability,
testing
and
started
work
on
Pfizer.
G
H
H
Recently,
well
mostly
focusing
on
the
requirements
of
the
inter
up.
According
to
the
network,
clean
snake
and
most
work
is
in
the
pilot.
Ptp
module
alex
is
working
on
the
sick,
I
Oh
module
for
the
in
top
usage,
and
there
are
still
some
minor
inconsistency
in
the
pilot
appeal.
We
are
fixing
right
now
for
the
wire
protocol
side.
We
are
also
building
a
beacon
receive
a
server.
H
H
C
Good
morning,
all
my
name
is
Johan
I'm
gonna
do
a
brief
intro,
because
I
just
joined
team
Artemis
few
weeks
ago,
Thanks
so
I'm
very
excited
to
be
working
on
e2.
Now
previously,
if
done,
database
related
blockchain,
stuff
and
sand
castle,
which
was
a
Scala
theorem,
smart
contract
language
anyway,
so
I
switched
off
off
of
those
things
on
to
eat
too,
and
one
of
the
first
things
I
worked
on
was
let
me
to
be
with
Anton,
with
the
noise
integration
and
now
on
to
D.
C
Now,
we've
also
gotten
some
benefits
from
Adrienne
helping
us
Adrienne
Sutton
is
working
with
Pantheon
and
he's
given
us
some
of
his
cycles
to
start
production,
izing
it
with
the
metric
side
and
that's
pretty
much
it
nice.
Thank
you.
What
minor?
The
last
thing
if
Joseph
is
online,
if
anybody
has
questions
about
the
upcoming
and
drop,
please
get
in
touch
with
Joseph
DeLong
Thanks
yeah.
A
I
Hey
guys,
I'm
sofa
lighthouse,
we've
got
a
few
points
that
we've
been
working
on
over
the
last
three
weeks:
I
guess.
Firstly,
we've
been
trying
to
optimize
our
database
I
think
we
plan
on
going
down
like
the
the
goth
route,
where
we
have
a
cold
optimized
database
and
a
hot
one
between
finalisation.
Ebooks
we've
been
working
on
our
test:
net
stability,
in
particular,
looking
at
extra
metering
and
doing
some
bug
squashing
and
because
of
the
update
to
the
well.
I
The
latest
aspect
that
we
merged
last
week
we've
been
updating
our
networking
stack
and,
at
the
moment,
we're
at
the
process
of
modifying
and
improving
the
syncing
algorithm
to
match,
with
the
new
RPC
that
we've
got.
So
we
have
to
finish
that
before
we're
completely
up
to
date,
with
that
f2
with
the
new
earth
to
networking
spec,
we've
also
been
working
on
BLS
standardization,
improving
that
and
in
connecting
lighthouse
to
s1
with
the
s-1
deposit
contract
and
finally,
we've
been
improving
our
HTTP
API.
I
J
Yeah
I,
can
you
just
give
me
yep
yeah,
so
there's
a
few
unparallel
efforts
going
on
so
we're
working
on
ramping.
Our
current
sting
and
p2p
service
to
align
with
the
latest
networking
stack,
and
we
also
respect
her
RDP
for
make
you
like
very
easier
to
filter
out
query.
For
example,
I
go
on
Korea
blog
industry.
You
can
just
filter
the
apparent
load
and
above
certain
spot,
and
then
we
also
plug
in
the
new
for
choice,
which
is
we
refer
to
the
for
choice
on
a
finalized,
spec
and.
J
On
benchmarking,
optimization,
so,
hopefully
we
can
see
a
while
on
second
slot,
thanks
to
and
I
will
also
implement
the
various,
obviously
matter.
It's
people
are
scared
stations
and
stuff
like
that
meet
you
at
the
box,
so
people
wanna
call
it
test,
minister,
so
wanna
pewter,
who
you
I'd
you
can
do
that
as
well,
and
they
also
almost
want
to
mention
is
a
POS
improvement,
that's
done
by
using
the
gold
for
library
and
then
test
for
portal.
J
F
We've
migrated
our
code
management
to
a
kind
of
a
model,
repo
style,
it's
all
in
the
lodestar
repository
and
with
that
we've
started
breaking
out
some
of
our
kind
of
sub
modules
or
sub
components,
so
we've
probably
published
SSC
types
on
NPM.
We
published
the
beacon
chain
configurations,
I've
made
that
a
minimal
publish
that
so
people
can
could
use
that
they
wouldn't
like
and
then
kind
of
up.
F
L
L
We
started
about
six
months
ago,
an
equivalent
to
web
Frito
pie
and
web
fridge
is
in
name
and
now
we
are
using
it
to
interact
with
if
one
deposit
contract,
we
also
have
created
a
way
to
bootstrap
if
to
Genesis
from
ganache,
so
everyone
can
use
it.
It's
only
joyous,
it's
not
mean
I
put
the
link
in
the
chat
and
on
the
networking
side
we
implemented
the
new
networking
inspect
and
we
also
have
live
p2p
working
again
on
Windows
and
it
can
be
tested.
We
just
met
one.
A
B
And
so
we're
closely
working
together
on
like
to
book,
and
so
what
they
wanted
to
do
is
really
something
like
toaster
key
to
map
out
exactly
where
from
where
you
want
to
go,
and
since
this
comparison
table
for
all
different
features.
Of
course,
there's
so
many
already
many
different
features.
We
know
there's
also
a
few
features.
B
M
M
B
M
Yes,
so
we'll
be
reaching
out
to
different
client
teams
to
try
to
get
with
a
questionnaire
or
survey
essentially
to
fill
up
and
we'll
probably
put
that
on
my
github
and
share
that
and
also
try
to
like
reach
out
one-on-one
with
everybody.
You
know
we're
gonna
speak
with
some
of
the
other
guys
while
we're
in
town
like
this.
Everyone
else,
that's
here
so
anyways.
A
M
B
N
Danny,
just
to
jump
in
for
a
second
rolls
on
holiday.
It's
a
public
holiday
in
Spain,
but
yeah
I
think
it
would
be
good
good
to
get
in
touch
with
them
about
this.
He
has
a
lot
of
ideas
about
Interop
and
how
we're
gonna
test
interrupts
between
different
limb,
p2p
implementations,
so
I
think
it'll
be
working,
would
be
worth
reaching
out
or
I
can
make
the
intro
or
whatever
yeah.
N
A
O
G
O
P
O
Q
O
Of
the
protocol-
and
we
are
hoping
to
like
the
autumn-
will
still
go
on
for
another
one
or
two
weeks
at
least,
but
right
now
we're
just
at
the
point
where
I
have
to
go
back
and
just
write
about
the
topic
system
more
so
that
they
will
be
able
to
evaluate
better.
So
basically,
it's
a
bit
of
like
what
this
this
first
week
has
shown.
Is
that
the
thing
is
just
not
very
well
explained.
O
You
know
not
so
happy
about
that,
but
I
will
just
explaining
better
and
hope
that
it
will
work
out
and
yeah
on
the
implementation
side.
I
can
say
that
not
much
has
changed
like
my
invitations,
basically
up
to
the
point
where
the
spec
is
and
I'd
be
very
interested
to
actually
see
if
we
can
do
any
kind
of
interesting
on
it
with
any
other
implementation.
Basically,
so
if
there
is,
anyone
is
interested
in
that.
O
O
The
deficit
is
really
minimal,
especially
for
the
wire
for
the
pole,
so
there
was
one
where,
in
the
the
biggest
change
that
that
means
that
was
efficient
for
me,
then
the
goal
was
that
the
tag
prefix
didn't
gone
from
the
who
are
you
response
packet
and
that
basically,
that
was
a
bit
for
me.
That
was
a
bit
weird
like
in
the
goal,
but
it
turned
out
that
they
actually
can.
It
revealed
like
some
other
issue
in
the
implementation.
O
G
O
I,
don't
know
so
basically
right
now,
so
the
text
is
still
there.
We
just
moved
this
part
to
the
rationale,
so
we
did
something
like
there's
actually
just
a
lot
a
lot
of
new
text.
So
when
you
last
check
this
back
what
we
actually
added
quite
a
bit
of
text
before
the
audit
to
explain
some
of
the
security
guarantees,
data
that
exists
and
those
that
don't
exist
in
general,
it
is
not
possible
to
verify
if
you
are
querying
a
single
node
for
publishers
or
good
I'd
like
for
know,
it's
advertising
given
topic.
O
You
cannot
be
sure
that
the
answer
is
correct,
because
there
is
no
way
to
verify
that
you
know
the
notes
you
get
back
actually
do
provide
that
topic.
The
protocol
cannot
give
you
this
fundamental
guarantee,
because
there
is
no
way
to
verify.
But
if
you
carry
a
lot
of
notes
for
providers
of
a
given
topic
and
in
general
the
answer
is
probably
gonna
be:
okay,.
L
O
A
P
O
O
Like
all
of
the
text
so
far
is
at
least
but
it's
part
of
the
report
yeah
most
of
the
now
like
the
big
change
compared
to
a
couple
weeks
ago
now,
is
that
basically
we
updated
the
rationals
and
out
it
matches
the
wire
protocol
specs.
So
before
there
was,
the
rationale
was
like
stuck
in
January
and
the
wire
protocol
was
from
April.
So
now
they
both
up
to
date,
cool.
N
N
N
So
there
will
be
bounties
at
the
hackathon,
the
organizers
of
eath
Berlin.
Why
chose
us
as
keep
like
a
key
project
to
focus
the
bounty
pool
on,
but
some
of
these
some
of
these
projects
were
posting
are
like
too
complex
to
do
in
a
hackathon.
So
you
know
we
would
be
interested
in
other
people
applying
and
we're
also
hoping
that
other
community
members
eventually
might
start
posting
their
own.
You
can
just
post
an
issue
in
this
repo
and
then
that's
about
D,
so
might
start
posting
their
own
and
even
started
offering
burns.
A
C
N
A
A
C
O
O
C
O
Helpful
for
things
like
networks,
also,
because
if
you
can,
you
might
actually
be
able
to
like
punch
a
hole
in
an
app
or
something
with
this
kind
of
message,
or
this
is
not
part
of
the
protocol
just,
but
it's
definitely
something
that
can
be
done
at
any
time.
Like
anyone
yeah
this
aspect
we
can
edit
sounds
good.
A
Anyway,
some
of
the
harmony
guys
have
been
doing
a
dive
into
network
load
with
respect
to
a
cessation
egg
aggregation
after
station
propagation.
You
know
if
there
are
essentially
multiple
agent
chain
blocks
and
multiple
shard
blocks
that
are
up
there
different
network
hues
at
the
time
we
might
actually
have
more
a
station
load
than
expected
and
then
also
investigating
the
pros
and
cons
of
various
strategies,
the
very
structure
strategies,
the
unstructured
strategies,
and
they
have
a
good
write-up
of
some
of
the
problems
at
hand
in
the
github
issue.
A
And
I
guess
the
conclusion
is
that
we
might
need
to
increase
the
max
expectations
for
blocks
if
we're.
If
we
have
difficulties
in
aggregating
such
that
we
have
some
subsets
of
aggregation
of
vegetation
aggregates
that
overlap
with
others,
and
if
we
have
multiple
targets
for
beacon
blocks
and
share
about
decisions,
I
think
that
is
a
possibility.
Certainly
it
comes
at
the
expense
of
larger
beacon,
chain
blocks
and
essentially
at
the
expense
of
computation.
A
A
So,
for
example,
a
committee
split
across
two
shard
subnets
such
that
the
best
effort
aggregate
from
each
can
be
broadcast
and
a
proposer
can
accept
it
and
then
aggregate
it
fully
without
worrying
about
overlap.
So,
there's
there's
a
lot
of
little
trade-offs,
laudable
design
decisions
that
we
need
to
both
think
about
benchmark
and
kind
of
explore.
On
more
real
world
networks,.
G
We
have
started
our
small
research
from
investigating
aggregation
strategies
and
specifically
in
structured
aggregation
strategies,
and
after
some
time
we
realized
that.
Probably
the
aggregation
strategy
is
not
is
not
a
bottleneck
or
for
the
system
and
the
station
delivery
could
be
a
it
could
become
a
bottleneck,
especially
when
we
will
have
big
a
big
number
of
validator
nodes
like
it
could
be
starting
from
phase
one
or
phase
two
or
whatever,
and
what
we
are.
G
These
documents
is
just
draft
which
contains
some
thoughts
and
some
finished
solutions
that
we
want
to
share
with
everybody
and
wanna
put
these
thoughts
and
problematics
into
it,
everybody's
head
and
after
that,
get
a
feedback
and
to
prove
that
assumptions
that
made
during
that
research
are
held,
and
maybe,
after
that,
we
will
have
reasoning
to
continue
to
investigating
that
problem,
to
do
some
modeling,
so
yeah.
The
basic
one
of
the
basic
problem
we
have
thought
about
is
the
DFT
and
the
scalability.
G
If
we
have
a,
for
example,
at
ten
or
fifteen
thousand
nodes
subscribe
to
beacon
attestation
topic,
we
will
probably
have
to
to
to
low
the
degree
of
a
p2p
graph
to
make
dissemination
done
in
a
limited
amount
of
time,
but
reducing
degree
of
the
graph
will
reduce
its
Byzantine
fault
tolerance
property
as
well.
So
you
wanna
read
about
that
in
these
documents
and
just
give
us
some
thoughts
on
that
or
whatever.
G
G
Q
G
G
A
Absolutely
yeah
cool,
so
kind
of,
as
mentioned
before,
the
trade
offs
and
some
of
the
subtleties
here
are
kind
of
one
of
the
big
four
phase:
zero,
the
big
things
that
we
need
to
figure
out
and
also
figure
out
what
strategies
might
be
valuable
to
pursue
in
the
future
as
the
network
size
grows,
cool.
Okay,
thanks,
my
girl.
Is
there
any
any
other
questions
or
comments
on
how
to
stationary
ation.
In
this
general
area
of
research,
the
pp
Network.
A
S
And
so
one
thing
is
that
a
couple
of
cars
got
merged,
so
one
of
them
is
1186,
which
is
modifying
the
way
that
merkel
proofs
work
order
them
working.
The
morkul
proof
your
vacation
works,
and
part
of
that
is
that
it
includes
basically,
instead
of
separately
providing
an
index
and
a
depth
that
it
provides
a
generalized.
H
S
And
there's
a
set
of
methods
for
working
with
a
generalized,
and
this
is
there's
also
Oh
an
unfinished
that
PR,
which
is
I,
think
it's
it's
either
thirteen
sixteen
or
1323
it's
the
beacon
chain
them
updates
work
for
phase
one
where
basically,
we
get.
It
adds
in
the
episode,
persistent
committee
roots
and
then,
after
that
there
is
an
updated
or
a
PR
that
I
started
working
on
the
Justin
recently
made
a
bunch
of
changes,
view
for
making
making
light
clients
or
defining
the
default
light.
Client
a
sinking
algorithm
so.
S
S
D
S
One
thing
I
also
wanted
to
talk
about
in
this
regard
is
just
the
pasta,
the
possibility
of
making
some
kind
of
infrastructure
to
make
it
easier
for
people
to
start
building
in
the
testing
the
roid
clients,
like
basically
the
challenge
being
bed
with
the
way
the
like
clients
back,
is
currently
is
set
up.
It's
not
going
to
be
really
possible
to
make
a
practical
like
client,
until
phase
one
actually
actually
launches,
and
so,
while
we're
learning
out
phase
zero
in.
S
We
wants
to
do
all
of
this
phase,
one
stuff,
also
in
parallel,
trying
to
get
fellow
white
clients
of
running
as
much
as
possible,
so
I
mean
once
did
your
own
suggestion.
I
had
made
is
just
the
possibility
of
making
some
kind
of
minimal
and
of
centralized
test
that
that
has
one
key
one.
Computer
and
friends
runs
one
shard
that
you
can
have
RPC
RPC
against
to
get
to
get
charred
black
roots,
but
would
be
interesting
if
it
think
of
some
different
options.
A
S
S
So
there's
three
kinds
of
API
are
just
to
give
us
a
summary
here.
One
kinds
just
to
get
the
easy
one
is
is
basically
using
trusted
execution
environments.
The
second
kind
is
information-theoretic
PIR
and
the
way
information
theoretic
PIR
works.
Is
you
basically
talk
to
end
server
and
then
you,
you
ask
on
each
of
the
servers
to
evaluate
a
function
on
all
of
the
all
of
the
data
where
in
each
server
gets
a
different
function
and
these
functions
could
just
be
like
a
linear
function,
so
a
vector
that
you
dot
product
the
entire
data
with.
S
But
you
choose
these
functions
in
such
a
way
that
the
sum
of
all
of
the
function
equals
to
the
function
that
just
basically
outputs
the
case.
P
piece
of
data
so
like
zero
times
everything,
but
the
KP
is
plus
one
times
the
capias,
and
then
you
receive
all
of
the
answers
from
the
server's.
You
add
up
the
answers
and
you
get
exactly
what
you
want
and
so
DB
from
an
information.
S
If
you're
writing
point
of
view
and
none
of
the
server's
know,
it's
like
what
you're
actually
accessing
and
the
only
way
they
could
figure
it
out
is,
if
all
of
them
colluded.
So
the
idea
here
would
be
that
this
would
be
based
on
some
kind
of
minority
assumption.
Where
say
you
assume
that
at
least
five
percent
of
registered
servers
are
honest,
you
asked
twenty
of
them
and
then
you
add
up.
The
answer
is:
if
the
answers
from
the
twenty
another
alternative
is,
and
then
the
third
alternative
is
computational
PIR
and
computational.
S
Pir
basically
works
by
sending
the
server
like
some
kind
of
mathematical
objects,
like
could
be
a
prime
number
mod
eats
you
or
some
weird
group
elements
like
there's
a
bunch
of
protocols,
and
then
the
server
applies.
Some
transformation
based
on
the
based
on
every
piece
of
data
and
the
mathematical
structure
has
some
trapdoor
that
you
include
that
basically
has
the
effect
that
without
the
server's
knowledge,
when
you
do
when
you
have
decrypt
the
results
at
the
end,
it
only
includes
information
about
the
specific
piece
of
piece
of
data
that
you
wanted
to
know
about.
S
So
there
there's
different
ways
to
do
this,
but
in
the
basic
like
the
main
drawback,
as
you
can
tell
over,
the
second
and
third
kind
is
basically
the
server
side.
There
is
this
om
n,
computational
overhead
and
in
some
cases,
there's
some
some
data
overhead.
You
can
generally
make
it
be
a
lesson,
though
sure.
A
And
another
update
on
the
white
plants-
stuff
I,
know:
I,
checked
him
with
salts
and
there
he's
moving
forward
with
integrating
Raiden
into
the
Catholic
client
framework
and
is
still
pushing
on
that.
He
said,
stop
buried.
So
hopefully
we
see
some
cool
stuff,
a
lot
of
that
in
the
next
month
or
so
wants
to
have
a
demo
for
Def
Con.
So.
U
I
have
a
few
updates
as
well.
One
is
that
I
guess,
starting
from
right
now
we
have
phase
zero
bounties.
So
any
substance
to
the
phase,
zero
spec
station
isn't
function.
Folk
toys,
rule
or
deposit
contract
will
get
rewarded.
Five
if
or
thousand
died,
so
I
guess
a
thousand
day.
Right
now
is
more
than
five.
If
so,
you
just
need
to
submit
an
issue
or
PR.
You
know
explaining
the
substantive
change
or
the
problem
that
needs
to
be
fixed
and
one
that
once
that
is
merged
in
before
the
e,
through
Genesis
you'll
get
the
bounty.
U
Another
update
is
BLS
standardization.
So
it's
now
kind
of
feature
complete
and
there's
no
known
issues
so
I
guess
we
can
consider
it
frozen
in
a
similar
way
that
phase
zero
is
frozen.
So
I
guess
the
the
plan
is
to
integrate
the
new
BLS
spec
into
dev,
but
not
merging
merged
into
master
too
soon.
In
particular,
we
want.
We
don't
want
to
kind
of
disrupt
the
interoperability
effort,
but
at
the
same
time
we
do
want
to
incur
at
least
some
subset
of
the
implementers
to
start
playing
with
the
new
BLS
standard.
U
U
The
rest
is
very
kind
of
minor
and
and
easy
to
to
implement
if
you
already
have
the
currently
at
a
spec
implemented,
so
just
to
give
it
a
little
bit
of
context
on
the
the
other
standardization,
it's
part
of
the
IETF
standardization
effort
and
actually
it's
spread
across
three
different
standards
and
none
of
these
standards
are
fully
ratified.
So
there
is
the
possibility
that
bugs
kind
of
will
be
seen
and
fixed
I
guess.
U
The
good
news
here
is
that
a
firm
is
going
to
be
the
first
to
launch
I
mean
we
still
have
a
few
months
before
launch,
so
there
is
room
to
fix
bugs
if
necessary.
You
know,
at
least
until
the
deposit
contract
is
launched.
So
how
do
you
find?
Do
you
go
find
these
bugs
I
guess
related
to
their
destination?
There's
also
standardization
around.
You
know
key
related
stuff
that
Carl
has
been
driving
so
checksums
HD
wallets
key
stores.
U
We
kind
of
want
standardization
around
all
these
things
for
sanity
and
I
think
the
approach
that
car
has
been
has
been
taking,
and
it's
one
that
I
quite
like
is
somewhat
minimalist.
Design
is
already
been
discussed,
but
I
kind
of
want
to
share
like
different
viewpoints.
I
think
the
the
new
daikon
design
is
is
totally
awesome,
so
just
I
mean
it's
not
it's
not
like
a
canonical
like
lion
design,
I'd
say
it's
like
a
minimal
one
and
there's
there's
a
whole
design
space
around
like
clients,
but
at
least
the
minimal
one.
It's
extremely
simple.
U
You
know
on
the
order
of
64
lines
of
code,
extremely
low,
go
ahead
for
the
beacon
chain,
because
it's
based
on
these
persistent
committees,
which
don't
change
very
much,
and
it's
also
awesome
because
it
has
lower
bandwidth
requirements
than
in
Bitcoin
ste,
and
you
know
I'm
also
investigating
another
optimization,
which
could
you
know
potentially
in
practice,
need
to
a
10x
reduction
in
bandwidth.
So
you
know
I'm
personally,
quite
excited
about
the
electrons.
U
Once
we
have
these,
these
ultra
light
clients
that
can
be
used
for
more
than
just
you
know,
user
facing
clients
in
mobile
phones.
They
can
also
be
used
built
to
build
these
bridges
between
other
block
chains
where
gas,
gas
cost
optimization
is
critical
and
then
the
final
thing
that
I've
been
looking
into
is
this
idea
of
a
quantum
apocalypse
insurance.
U
So
the
idea
here
is
that
the
validators
can
commit
to
to
two
secrets
so
in
the
context
of
a
lamp
or
signature
which
is
quantum
secure
when
when
they
make
a
deposit-
and
we
we
can
basically
in
in
the
event
that
there's
some
sort
of
quantum
apocalypse,
quantum
computers
break
pls
signatures.
Well,
we
can
basically
disable
and
all
the
BLS
signatures
and
have
a
way
for
for
validators
to
safely
transfer
the
balance
as
validator
onto
you.
U
Whatever
new
platform
comes
next,
which
which
is
quite
insecure,
and
the
nice
thing
here
is
that
we
can
do
it
without
any
substantive
change
to
phase
zero
and
you
can
kind
of
think
of
it
as
a
as
a
validator
level
convention.
So
we
we
will
be,
you
know,
enforcing
at
the
consensus
layer
these
this
this
infrastructure.
But
if
you
want
to
benefit
from
it,
then
you
need
to
kind
of
follow
the
convention.
U
U
E
For
sure,
so
a
few
things
so
we've
been
doing
work
on
benchmarking,
basically,
single
pass,
multi
branch
updates,
multi
normal
proofs
and
a
sparse
normal
tree
implementing
implementing
ssz
within
an
execution
environment
in
the
context
of
simple
transfers.
So
that's
been
working
on
that
and
the
eyz
team
has
been
doing
a
patrician
Merkle
tree
with
rfp
and
so
we're
getting
preliminary
results.
E
Benchmarking
numbers
on
that
so
hope
to
have
Morgan
filled
by
in
Iraq.
Regarding
all
of
that
also,
we
are
continuing
to
build
out
phase
one
to
prepare
basically
being
able
to
plug
in
scout
and
B
capability
and
phase
2
into
to
a
client.
So
that's
that's
in
action
right
now
we're
doing
that
in
White
House.
E
Bugs
as
well,
let's
see
we
started
work
on
a
new
repo
which
wraps
to
some
rapping
on
scout
in
particular,
and
just
basically
gives
you
one
execute
function
with
a
priest,
a
truant
input
and
an
output
and
then
to
basically
extract
away
I
love
it.
The
FFI
functions
they're
set
up,
so
we
plan
on
just
plugging
that
straight
into
into
our
our
node
that
we're
working
on
yeah.
That's
that's
a
big
equal.
K
A
And
the
other
project,
which
is
the
deposit
contract
I,
was
talking
today
June
two
days
ago
and
it's
generally
complete
other
than
the
a
couple
of
negative
conditions
that
he
wanted
to
verify,
along
with
this
Viper
compiler
error,
bug
and
the
checksum
that
we're
going
to
add.
But
it's
exciting,
generally
verified
and
you
ready
to
deploy
when
we're
ready,
pull
any
other
research
updates.
A
T
Yeah
sure
so
III
know
originally
said
kind
of
be
there
at
3:30
and
I
think
what
we're
gonna
wind
up
doing.
It's
kind
of
doing
waves,
so,
like
kind
of
bands
leaving
to
take
us
out
to
the
you
know
the
cult
headquarters
and
so
I
think
I'm
gonna
set
up
or
I'm
gonna.
Add
the
pertinent
people
to
the
there's,
an
interrupt
telegram
channel
and
then
tomorrow,
I'll
do
a
call
like
QA
about
the
sort
of
stuff,
because
this
could
take
a
while.
But
generally
the
idea
is
a
sixth
root
of
13.
T
You
don't
need
to
bring
food
its
cater.
We
have
a
cabin
that
supports.
Like
30
people.
Wasn't
team
has
also
gotten
a
cabin.
That's
ports
like
and
issue
people,
and
so
we
also
happen
with
extra
space.
That's
that's.
What
I
was
talking
to
you
is
talking.
Is
that
the
same
day
II
was
or
he
wasn't,
Kevin
yeah.
T
Great
okay,
so
yeah
so
there's
there's
there
are
those
cabins,
and
so
anyway,
so
will
provide
food.
We
order
food
for
about
45
people,
so
even
if
you're
staying
in
another
cabin
it'd
be
great,
that
I
knew
about
you,
so
you
didn't
starve
to
death,
because
that
would
be
cool
and
so
yeah
Antwan
now
going
to
have
to
the
technical
organization,
because
I'm
kind
of
blocked
down
with
operations
so
he's
going
to
help
kind
of
organize
the
technical
portion
of
what
we're
doing.
T
A
H
B
A
A
B
H
B
U
B
Go
suspect
is
still
over
there
that
already,
that
is,
is
he
going
temptations
to
eat
authority
and
big
smart,
and
so
it's
actually.
The
first
is
even
patient
right
now,
so
every
tuning
for
is
right.
There.
It
just
has
been
like,
like
relatively
quiet
from
Quito,
and
then
there's
no
like
new
developments
in
fishing.