►
From YouTube: Eth2.0 Implementers Call #7 [11/29/2018]
Description
A
You
know
chat
box,
there
cool
so
first
thing
on
jinda
client
updates.
These
can
be
as
long
or
brief.
As
you
want
I
know,
we've
been
fiddling
with
the
spec,
a
lot
which
we
can
talk
about,
so
I,
don't
expect,
suits
much
progress
and
what
people
catching
up.
So
if
anybody
wants
to
start
us
off,
go
ahead,
I.
B
So
we
caught
up
with
latest
spec
changes.
So
now
we
are
at
most
three
days
off.
It's
I,
guess
a
quite
a
feat,
given
all
the
changes
that
were
going
on,
we
have
a
name
wrapper
working
for
Ally
p2p
demon.
So
now
we
tested,
we
can
have
two
team
members
chatting
freely
p2p
demon
with
name
rapper.
We
we
have
mini
target
of
running
kind
of
demo,
become
node
for
December.
B
A
B
C
D
A
F
G
Converting
to
typescript,
so
we've
been
trying
to
create
native
types
for
the
different
types
in
that
Easter
Oh,
like
you
and
patch
32,
and
all
these
different
types,
that's
the
main
thing
that
we've
been
working
on,
we're
slowly,
starting
a
beeline
signature,
aggregation
library
as
well.
So,
if
my
me
later,
if
we
couldn't
talk
about
how
that's
going
for
you,
I'm
that'd
be
great.
Otherwise
we
have
no
other
major
updates.
H
Me
right
so
yeah
I
both
were
helping
the
ruling
of
the
spec
in
these
two
weeks.
Oh
not
much
big
process,
IDs
I,
accept
reworking
on
the
data
structures
and
help
her
functions
and
the
other
side.
We
have
a
internal
consensus
of
the
test
net.
The
help
the
Trinity
test
Nate
just
fortune
at
the
end,
is
with
MVP
and
what
will?
What
are
the
components
of
the
MEP?
Will
contents
so
I
post
the
link
track
and
that's
our
updates,
I
think
or
anyone
else
going
to
better
comment.
I
I
B
F
I'll
start
with
some
of
this
would
be
a
less
given
that's
the
topic
of
this
session,
so
we're
using
the
Hiromi
library,
which
is
you
know,
created
by
xD
Finity
person,
they're
using
an
underlying
cryptographic,
library
called
mcl
which
uses
DMP.
However,
he
actually
just
removed
the
dependency
on
GMP
yesterday,
so
we'll
have
to
do
some
benchmarks
to
figure
out.
F
If
you
know
removing
GMP
is
how
how
slow
that's
gonna
be
a
session
that
he
is
also
working
on
optimizing
a
Miller
loop
so
that
we
can
have
kind
of
signatures
in
g2
and
then
public
keys
in
g1,
so
we'll
be
doing
a
lot
more
work
on
that
kind
of
once
once
he
pushes
those
changes.
Hopefully,
in
next
few
days,
yeah
I
think
we
should
probably
see
a
speed-up
on
the
order
of
like
3x
without
GMP
way,
which
is
unfortunate,
but
that's
still
left.
That's
the
left
to
be
seen.
F
Aside
from
that,
we've
been
refactoring
a
code
base
to
match
having
a
single
beacon
state
that
was
really
nice.
It
cleaned
up
like
it
removed
like
thousands
of
lines
from
our
code
base,
and
we
also
have
a
kubernetes
kind
of
configuration
in
place
for
a
test
net.
We
have
a
basically
a
DHT
discovery,
working
with
a
relay
mode
that
helps
traffic.
That
kind
of
you
know
inbound
connections
to
nodes
in
the
cluster,
and
we
also
have
a
boot
node
for
the
beacon
nodes.
F
So
Preston
from
our
team
has
been
to
putting
a
lot
of
work
on
that
front.
I
said
from
that
we've
mostly
been
focusing
on
aligning
with
respect
there.
Is
there
been
so
many
changes,
a
lot
of
refactor
to
be
done,
but
yeah
I
think
we're
just
cleaning
up
our
repo
fixing
things
up
and
then,
after
that,
we'll
be
ready
to
put
in
new
features
and
work.
F
On
more
of
that,
we
also
have
a
bounty
worker
working
on
a
pure
gold,
VLS
called
3d
one
implementation,
so
he's
he's
basically
basing
it
off
the
rest,
implementation
and
trying
to
get
close
to
the
same
amount
of
performance,
but
yeah
that's
still
kind
of
to
be
seen.
He
has
some
benchmarks,
but
still
a
little
bit
slow.
So
hopefully
we
can
get
more
optimizations
on
that
front,
but
yeah
I
think
that's!
That's
all.
Thank
you
great.
K
Hi
I'm
Jen
long
with
the
Pegasus
team.
In
the
like
past
two
weeks,
we
brought
in
three
new
team
members
to
work
on
that,
so
we
have
about
five
people
working
on
this.
We
started
an
implementation
of
simple
serialization,
but
then
we
put
that
on
hold.
While
we
implement
some
of
the
permanent
types
that
were
laid
out
in
the
spec,
because
you
can't
see
realize
about
having
the
thing.
K
A
K
D
Guess
I
can
start
so
Justin
Danny
as
Yahweh
and
ayah
mostly
have
been
work
working
quite
a
bit
over
the
last
ones.
It's
you
weeks
to
like
basically
get
the
Prague,
get
the
aspect
to
the
point
of
it
kind
of
big
sheets
you're
ready
for
what
we
wants
to
have
for
phase
zero
and
it's
so
the
most
recent
things
that
we
added
include.
D
So
it's
basically
at
the
point
I'm
at
the
point
where
phase
zero
as
I
kind
of
going
through
sort
of
spec,
rewriting
in
spec,
like
basically
Queen
queening
up
making
it
making
it
easier
to
read,
attractor,
I
love,
fixing,
bugs
and
simplify
and
so
forth.
On
the
face
of
one
side,
there's
definitely
still
quite
a
bit
of
work
to
do.
D
It
adds
a
couple
of
Caraway's
significantly
there's
different
ideas
that
I
probably
want
to
try,
try
out
and
think
about
in
terms
of
exactly
how,
like
what
data
roots
get
committed
into
the
beacon
into
the
across
the
data
hash.
That
goes
into
the
crosslink,
but
that's
something
that
we
still
have
quite
a
bit
more
time
for
and.
A
One
of
our
intentions
with
the
phase
zero
first
phase,
one-
is
to
get
all
of
the
data
structures
needed
for
phase
one
all
of
the
beacon
chain.
Related
data
structures
ironed
out
so,
like
the
proof
of
custody,
bits
are
in
phase
zero
so
that
we
don't
have
spaghetti
code
with
respect
to
the
data
structures
when
we
launch
phase
one.
But
you
know
everyone
always
signs
a
zero.
So
that's
kind
of
the
separation
of
concerns
there,
but
why
we're
driving
forward
with
at
least
integrating
those
data
structures.
C
Right
I
mean
I
think
it
is
possible,
even
though
we
will
do
our
best
to
have
a
future
compatibility
that
we
might
have
to
change
the
format
slightly,
there's
something
we
we
find
after
launched.
I'd
agree
with
with
italic
that
we
are
nearing
future
complete,
there's
a
few
things
we
want
to
tweak,
but
at
this
point
I'm
now
in
basically
cleanup
mode
and
finding
bugs
I,
just
the
heads
up
I
think
there's
a
still
a
lot
of
bugs
in
the
spec
I'd
say
at
least
100
bucks.
A
C
Looking
too
closely
at
currently
the
current
spec
one
of
the
things
that
I'm
working
on
and
it's
kind
of,
helping
me
as
well
with
the
the
fine-grain
review-
is
that
I'm
actually
rewriting
the
whole
spec
in
something
that
I'm
calling
the
transparent
paper.
So
it's
meant
to
be
a
little
bit
like
the
yellow
paper
for,
if
you're
in
1.0,
but
instead
of
being
super
formal
and
unreadable,
it's
meant
to
be
designed
for
insight
designed
for
readability,
for
transparency
and
in
addition
to
the
spec.
C
It
has
things
like
definitions
of
every
single
term,
and
it
has
explanations
about
the
sign
decisions
and
things
like
that.
So
I'm
hoping
to
get
that
out
in
January,
probably
ends
up
January.
That's
my
target
and
hopefully
end
up
January.
We
will
also
have
you
know
close
to
finalized
there's
speck
on
github
I.
A
C
Yeah
I
mean,
if
you
do
a
pull
request.
I
think
we'll
try
to
move
fast
on
the
pull
requests,
especially
those
that
are
on
controversial,
so
I
think
every
day,
I'll
just
go
through
the
pull
request
and
just
merge,
what's
low-hanging
fruit
and
on
controversial.
So
we
should
be
moving
faster
on
that
from.
A
Leo
from
the
I
think
Barcelona
BSC,
Barcelona
supercomputing
has
joined
us
today.
He
was
at
the
client
workshop
in
Berlin
and
presented
some
of
his
work,
but
now
that
the
spec
is
getting
into
more
of
a
stable
place,
he's
interested
in
collaborating
again
and
Leo.
If
you
want
to
do
a
quick
intro
talk
about
some
of
your
previous
work
and
some
of
your
potential
intentions
for
future
work.
Sure
so
thank
you.
A
L
L
L
However,
I
did
give
a
talk
about
shardene
in
a
meet-up
in
barcelona
with
the
last.
The
last
aspect
is
changed,
a
couple
of
emails
with
Justin
and
Vitalik,
and
on
that
for
that
talk,
so
I
think
I
have
a
their
vision
of
where
we
are
right
now,
with
respect
and
I
hope
that
in
the
next
couple
of
weeks,
I
would
be
able
to
get
up
to
date
with
a
and
with
respect
on
this
monitor.
L
So,
for
example,
the
kind
of
experiment
that
we
want
to
try
is
like,
maybe
in
different
latencies,
to
different
different
nodes,
different
clients
on
the
on
the
on
the
on
the
net
worth
trying
to
say
that
I
don't
have
to
change
and
put
rate
trying
to
see
different
loading
balance
between
the
number
of
transactions
to
see
how
that
affects.
The
number
of
example,
number
of
cross
card
transactions
and.
L
Basically,
there
is
the
medians
a
wide
set
of
ideas:
that
of
testers.
We
can
run
a
decimal,
editor,
well,
I,
think
initially,
the
idea
is
to
is
to
have
something
that
runs
more
or
less
in
a
in
a
similar
way
on
on
on
what
we'll
have
today,
I
mean
without
shots
of
course,
but
that
we
can
say
that
more,
let
the
simulator
that
we
have
running
in
the
supercomputer
kind
of
really
represents
at
least
a
block
chain
without
charts,
and
then,
after
that
we
can
more
or
less
say
okay.
A
A
M
Yeah,
so
on
one
part,
we
continue
to
work
on
the
Trish
based
aggregation,
so
we've
got
something
working,
but
it's
still
very
basic.
You
can
go
in
the
public
repository
and
we
will
do
mock
test
in
the
next
weeks.
As
a
part
of
this,
we
would
like
to
try
a
quick
photo
curl
in
leap
into
P,
so
it's
something
that
is
currently
under
implementation
and
will
appear
to
be
Tim
and
we've
got
some
packaging
issues.
So
we
will
need
to
wait
so
I
work
for
this.
M
We
will
not
try
quick
I
ever
we
will
find
with
another
library.
So
we
don't
forget
stuff.
Yet
we
need
to
discuss.
We
spent
some
time
on
with
similar
tax
as
web-based
to
peer
level.
So
that's
a
good
issue
and
the
p2p
heater
but
recreated,
and
the
idea
is
that
on
one
we've
got
15,000
node.
So
it's
very
difficult
to
take
a
control
of
a
network.
Why
a
theorem
to
English
sounds:
we've
got
a
few
on
words
of
nodes,
so
you
can
add.
M
You
can
add
two
thousand
three
thousand
three
thousand
nodes
please
to
another,
and
they
can
delay
the
messages
and
it's
quite
important
in
a
time
too,
because
we
know
that,
for
example,
for
blood
producers,
we
have
a
few
seconds
to
send
their
blogs.
So
you
can
clear
it
a
bit
network.
So
it's
it's
small
topic
to
take
into
account,
but
the
big
issue,
but
likely
when
we
need
to
follow
up
on
that
and
the
obvious
solution
is
to
have
a
lot
of
pills
which
way
we
can
avoid
being
a
text.
M
But
it
means
as
well,
but
you
unless
boundaries
available,
because
you're
going
to
speak
to
a
lot
of
people.
So
if
you're
interested
in
this
topic,
we
can
have
a
look
thanks.
They
need
to
keep
originally
I'm
working
as
well,
so
something
but
it's
still
in
the
thinking
process,
applying
like
onion
protocol
at
the
p2p
level
to
increase
anonymity
and
a
little
bit
more
it
done
on
the
network.
So
thinking
about
this
kind
of
stuff
likely
will
create
a
few
issues
in
the
near
future.
M
M
N
I'm
participating
in
order
fishes
three
days,
so,
if
you
can
just
send
me,
the
link
through
the
chat
or
somewhere
else
I
can
make
sure
I
keep
track
of
that
that's
great
and
then
on
the.
On
the
other
hand,
you
mentioned
something
about
the
tour
of
potentially
tour
transfer
and
onion
transport.
Just
wanted
to
point
out
that
we,
this
is
on
the
Libby
to
be
a
road
map
which
is
a
point
in
the
agenda
for
later
as
well.
N
J
M
N
Yeah,
so
from
let
me
to
be
quick
is
definitely
a
priority
for
us.
It
is
true
that
the
spec
is
in
finalized,
yet
I
think
upstream,
so
it
will
be.
We
have
been
closely
following
and
tracking
it
and
we're
working
with
the
Libby
to
be
in
the
Libby
to
be
teamed
as
there's
a
member,
that's
actually
engaging
with
a
working
group
of
the
IETF
working
group
and
keeping
the
implementation
up
to
speed
with
all
the
developments
there.
N
So
we
really-
and
it
is
being
I-
think
the
latest
one
of
the
latest
releases
of
ipfs
has
a
flag
to
enable
quick,
the
quick
transport
as
well,
so
it
is
being
tested
on
an
experimental
basis
out
in
the
open,
I.
Think
it's
good
to
target
or
to
potentially
consider
quick
in
the
long
in
the
medium-term,
so
to
speak,
yeah
but
I,
don't
have
any
say
regarding
specific
dates
or
or
anything,
but
yeah
I
think
it's
definitely
something
to
consider
it
to
keep
on
the
map.
N
Jessica
yeah,
sorry,
so
quick
is
a
UDP
based
transport
that
provides
many
of
the
guarantees
of
TCP
in
terms
of
pack
of
congestion
control
in
terms
of
reliability
and
a
few
other
things.
It
also
implements
multiplexing
protocol
stream
multiplexing,
and
it
also
includes
security
and
encryption
constructs
on
top
of
the
transport
itself.
So
it's
basically
the
best
of
many
worlds
over
UDP.
N
It
allows
us
to
basically
allows
us
to
to
keep
multiple
streams
open
and
an
assembler
ways
HTTP
to
at
the
same
time,
it
implements
TLS
night
security
guarantees
and
all
of
this
with
potential,
with
a
number
of
features
such
as
session
resumption,
zero
round-trip,
bring
negotiation
and
certain
cases,
and
so
on.
So
it's
it's
very.
It's
a
very
promising
protocol
going
forward
and
the
reason
why
quic
is
important
in
this
case
is
because
the
p2p
for
now
is
mostly
a
stream
oriented.
N
It
has
three
more
as
a
as
a
primary
abstraction,
so
implementing
so
using
UDP
constructs.
So
this
is
message.
Oriented
transports
right
now
is
not
feasible
with
the
current
abstractions
we
are.
This
is
on
a
roadmap
we
do
want
to
create
potentially
in
the
future
stream
orientation
on
top
of
UDP.
So
it's
really
it's
really
promising
in
in
many
in
many
directions.
M
That
it's
universal
protocol
and
you
won't
be
able
to
distinguish
between
basically
our
communications
and
standard
HTTP
communication.
So
in
terms
of
this
question
being
a
little
bit
hidden
on
your
network,
it's
useful
and
the
second
reason
is:
hopefully
it's
not
sure
it's
something
that
we
need
to
look
at,
but
hopefully
we
will
be
able
to
use
it
to
connect
to
a
lot
of
peers
without
consuming
too
much
resources.
M
Ok-
and
it
can
be
interesting,
for
example,
for
a
testers
if
a
tester
believes
that
someone
tries
to
Samsung
BAM
it's
interesting
if
it
can
push
we're
at
the
station
to
as
many
nodes
as
possible,
so
without
maybe
being
connected
full-time,
but
they
can
connect
a
lot
of
em,
just
sending
a
very
small
message
with
signature
and
then
the
other.
So
it's
very
interesting
from
this
point
of
view
and
so
on
this
so
format,
but
slightly
difficult.
N
A
N
O
A
A
Topics:
advertising
the
topics
that
you
subscribe
to.
Are
there
any
other
protocols,
any
other
discovery
protocols
that
are
that
do
give
us
this
feature
set
and
that
are
under
consideration?
Is
anybody
know
hi
in
this
site,
so
I'm
looking
into
a
similar
kind
of
a
vertical
where
there
is
a
peer-to-peer
discovery
so
last
week,
I
have
figured.
Q
Okay,
I
think
I'll.
Send
you
the
link
on
the
chat,
so
basically
it
requires
the
Wi-Fi
Bluetooth
or
Bluetooth
classic.
It's
especially
built
for
the
IOT
devices,
and
they
are
working
it,
so
they
basically
the
mode
of
connecting
is
there
are
two
modes
of
connecting
the
system.
First,
one
is
a
proactive
protocol
and
second
was
the
reactive
protocol.
So
the
problem
with
a
proactive
protocol
is
that
it's
good
in
the
finding
the
nearest
devices,
but
it's
difficult
when
it
comes
to
the
scaling.
Q
A
P
B
P
N
Implementation
and
the
behavior
of
the
etherium
1.0
of
the
deputy,
B
DHT
implementation,
and
because
there
are
some
differences
in
behavior
and
these
ultimately
Libby
to
be
intends
to
be
a
stack
that
is
usable
for
a
number
for
any
downstream
user
that
is
intending
to
build
a
peer-to-peer
application.
So
really
these
different
behaviors
should
make
it
as
customization
or
configuration
flags
into
the
let
p2p
getting
the
implementation,
so
I
would
be
happy
to
do
and
to
to
collaborate
with
others
on
this.
N
On
the
short
analysis
identify
those
areas
where
we
defer
and
and
push
tickets
and
purse
changes
on
our
DHT
implementation
to
make
sure
that
we
are
aligned,
or
it
is
possible
to
align
our
behavior
with
that
of
that
p2p.
So
then
you'll
be
able
to
build.
You
know
anything,
that's
necessary
for
discovery
version
5
on
top
of
the
p2p.
This
is
this
is
just
an
idea,
curious
to
know
what
you
think.
N
A
N
J
But
like
that's,
that's
something
that
that
that
I
think
we
should
name
as
a
hard
requirement
for
any
every
protocol.
We
have
that
it
has
this
built-in
capability
of
feature
discovery
of
the
peers,
that
you're
talking
to
that.
That
totally
makes
sense
and
eglantine
the
Libby
to
be
a
road
map.
There
is
one
goal,
one
point
that
speaks
very
loudly
to
this
with
service.
N
Discovery
right,
so
it
is
not
we're
intending
to
build
an
abstraction
for
so
this
discovery
that
can
be
that
can
be
driven
by
khadiyah,
but
can
also
be
driven
by
other
mechanisms
and
other
discovery
protocols
which
might
be
local
or
might
be
connected,
or
it
might
be
over
a
local
network.
They
might
use
different
mechanisms,
and
one
of
one
of
the
one
of
the
protocols
that
came
up
as
well
in
Prague
was
some
research
work
that
had
been
done
in
a
group.
A
D
D
D
A
Suppose
the
design
goal
right
now
is
to
make
the
validator,
as
distinct
from
their
position
in
the
network
as
possible,
such
that
validators
can
create
whatever
node
set
up
or
set
of
nodes
set
up.
That
makes
sense
for
their
security
concerns.
I
know,
that's
slightly
just
kicks
the
can
down
the
curb,
but
I
I
would
err
on
the
side
of
simplicity
on
the
base
protocol.
Unless
we
have
a
very
compelling
solution
to
increase
the
privacy
native
to
the
protocol.
F
We
we
spoke
a
little
bit
offline
about
kind
of
how
perhaps
the
beacon
node
could
be
in
charge
of
syncing
the
shards,
and
then
they
can
hand
off
to
the
edge
of
the
validators.
However,
like
a
prismatic
we've
been
discussing
this
and
we
don't
understand
why
why
this
is
this
sidecar
approach?
Is
that
really
is
that
effective?
A
Entire
blockchain,
the
beacon
chain
and
the
shard
chains,
and
that
the
validator
is
this
special
user
piece
of
software
that
connects
you
and
talks
to
piece
of
software
I.
Think
once
you
put
in
shard
syncing
and
no
peer
management
into
the
validator
piece
of
software,
you
now
have
to
client.
You
have
new
two
nodes
now,
rather
than
you
have
two
node
pieces
of
software
and
you
make
the
barrier
to
entry
to
create
a
validator
piece
of
software.
Very
high
I.
Think
the
distinction
of
the
validator
being
very
thin.
A
The
validator
controlling
keys,
controlling
secrets
and
signing
things
allows
for
incredibly
diverse
setups.
A
validator
could
talk
to
ten
different
nodes,
controlling
them
via
commands.
Sync,
this
shard
sync
that
shard
ask
information
about
the
shards
sign
information
and
broadcast
as
they
please,
but
putting
actual
block,
processing
and
consensus
rules
embedded
into
that
piece
of
software.
I
think
is
not
going
to
give
you
the
diverse
I,
think
it's
optic,
not
the
design
decision
that
gives
us
the
most
optimal
set
of
potential
setups.
A
Another
thing
that
this
does
is
that
the
as
long
as
you
keep
the
validator
secure,
he
can
talk
to
whatever
notes
he
wants
those
nodes.
Don't
I
mean
if
he
has
five
notes
that
he's
communicating
with
and
one
of
those
becomes
hacked
or
one
of
them
is
dosed.
It
has
redundancy
and
talking
to
multiple
ones.
If
it's
instead
in
charge
of
syncing
its
own
of
data
and
connecting
it
appears,
then
it
becomes
a
single
point
of
failure.
I
think
that's.
A
A
J
Discussion
but
but
the
same
thing
was
brought
up
the
centralization
of
all
responsibilities
to
the
beacon
all
including
sinking.
The
shards
is
a
little
bit
odd
in
the
sense
that
the
validator
exists
to
unify,
what's
happening
in
the
shard,
with
what's
happening
in
the
big
new
chain.
Basically,
and
perhaps
a
way
to
address
this
is
that
you
keep
the
to
command
API.
So
a
little
bit
apart,
the
one
that
controls
the
shard
and
the
one
that
controls
the
beacon
or
the
like.
The
API
commands
that
we
don't
conflate
them
into
him.
J
It's
a
single
unit
and
what
that
allows
is
basically
running
a
beacon,
node,
the
validator
and
a
shard
sinker
separately.
If
you
desire
to
do
so,
but
it
also
allows
you
to
implement
the
beacon
mode
sure
the
shard
sinker
cannot
exist
without
a
beacon
without
the
beginning
of
like
a
shard
needs
to
know
information
about
the
system
level
stuff
for
it
to
remain.
In
sync,.
A
E
That
they
need
to
they
need
to
offer
right
on
so
they
need
to
kind
of
they
need
to
gain
from
the
beacon
node.
This
idea
that
there's
like
over
these
periods
over
these
slots,
they're
going
to
have
to
to
create
some
actions
and
there's
like
this
scheduling
system.
So
the
the
solution
that
I
came
to
that
I
thought
was
most
sensible
person
was
that
the
scheduling
is
inside
the
the
validator
client.
E
So
it's
up
to
it
to
retrieve
a
schedule
and
then
to
maintain
it,
and
so
it
should
kind
of
fraud,
the
beacon,
node
and
say:
hey.
You
need
to
sync
these
shards,
hey
I,
want
you
to
produce
a
block
and
I
liked
that,
because
it
means
that
the
validator
can
swap
around
between
nodes
and
something
that
I
thought
would
be
quite
important
for
a
validator
service.
Is
it
needs
to
be
able
to
have
this
idea
of
the
quality
of
service
that
it's
obtaining
from
beacon
node?
E
So
if
it
maintains
your
schedule,
it
can
kind
of
start
to
have
this
idea
that
it's
not
getting
responses
from
the
beacon
node
and
it
can
swap
around.
Whereas
if
that
kind
of
schedule
lives
inside
the
beacon
node,
then
you
know
that,
then,
if
the
beacon
Road
falls
over,
there's
nothing
really
checking
on
it.
So
I
think
my
what
I
was
thinking
seems
to
to
link
in
with
what
Danny
was
saying.
Is
that
right?
Yes,
yes
and
yeah?
A
Of
them,
you
now
can't
run
a
beacon
node.
Without
you
can't
run
like
a
char.
Did
you
can't
run
a
shard
chain
beacon
note
without
a
validator,
because
you
need
that
piece
of
like
middleware
I
I
see
again
I
see
the
validator
as
it's
a
user.
It's
definitely
it's
a
core
user
piece
of
software,
but
it's
a
user
piece
of
software
in
the
same
sense
that,
like
the
commands,
the
validator
has,
as
Paul
said
as
a
schedule.
It
knows
it
got
it's
asking
the
system,
the
beacon
chain.
A
You
know
what
the
current
shuffling
is
and
it
sees
there's
an
update,
and
it
knows
oh
I
need
to
sync
this
shard,
so
issues
a
command
to
the
to
the
node
sync,
this
shard
and
then,
when
the
slot
comes
for
it
to
attest
to
it.
It
says
what
is
my
to
station
candidate
and
the
beacon
node
so
like
for
this
certain
piece
of
data.
The
no
passes
that
it
signs
it
and
passes
it
back.
Yeah
I
definitely
support
the
budget
were
approached
by
the
by
the
way
I
have
to
head
off.
A
O
How
that's
implemented
you
know,
we
also
want
to
kind
of
I
would
think
you
want
to
encourage.
You
know
a
more
decentralized
approach
to
staking
pools,
rather
than
you
know,
some
sort
of
like
monolithic
setup
like
how
mining
pools
work
right
now.
So
maybe
that's
worth
you
know,
just
at
least
keeping
that
in
mind.
Yeah,
absolutely
I,
think
by
exposing
the
minimum
generic
functions
to
operate
and
control
these
things.
O
A
A
N
A
unit
when
defining
together
what
we
want
to
focus
on
in
the
future,
not
just
for
2019
but
even
in
terms
of
vision
and
in
terms
of
where
we
want
to
take
the
technology
and
the
future
of
peer-to-peer
networks
as
well
going
forward
we
are
expecting
to.
We
ideally
want
to
knock
down
kinda
the
wish
list
of
all
the
items
and
right
now
we're
at
a
connection
sort
of
like
a
brainstorm
point.
N
What
week
letting
connecting
input
from
many
communities
and,
of
course,
if
you're
in
being
a
very
good
friend
and
a
primary
primary
straits,
stakeholders
when
and
to
be
I,
think
it's
very
important
for
you
guys
to
to
pitch
in
to
look
at
what
we
have
so
far
thanks.
You
know
for
posting
the
link
and
and
yeah
definitely
point
out
where
we
need
to
pay
more
attention.
What
is
a
priority
for
you,
what
you
know,
different
ideas
or
different
things,
that
we
should
take
into
account
and
really
we
as
a
community
in
general.
N
So,
right
now,
as
I
said,
this
pretty
much
reads
like
like
a
wish
list
so
far
and
yeah.
Basically
the
process
right
now
looks.
We
are
connecting
these
ideas
by
next
week
or
the
two
weeks
after
this.
We
hope
to
have
prioritized
these
ideas
and
in
general,
build
roadmap
and
a
timeline
to
deliver
them
for
2019
and
and
forward,
and
we
really
want
to
we're
also
working
with
what
the
milk'
are
closest
to
keep
us
elves
accountable
and
to
keep
the
community
in
general
accountable
as
well,
so
so
yeah.
We
basically
at
this
point.
N
A
A
G
A
A
That's
the
short
answer.
These
things
depends
on
the
nature
of
the
split.
Why
this?
What
happened?
What
actually
what
people
were
changing
with
the
protocol
and
with
the
code
but
in
general,
there's
kind
of
a
with
the
versioning
mechanism
for
the
signatures?
I
think
it's
kind
of
under
the
the
idea
of
domain
and
version
in
the
in
the
spec.
If
you
want
to
take
a
look
at
that,
there
is
a
built-in
mechanism
to
handle
forking
a
replay
reproduction
in
terms
of
the
shard
data
chains
and
Static,
yueshen
I,
don't
know
I
I.
Imagine
they
obvious.
A
G
A
J
You
know
the
few
places
where,
simply
because
my
son
uses
integers,
you
know
the
order
of
operations
might
not
matter,
whereas
would
sign
types.
You
have
to
consider
these
things.
I,
don't
know
how
much
the
spec
wants
to
deal
with
that
really.
But
it's
something
to
look
out
for
I
guess.
A
broader
issue
is
that
now
that
we
have
you
in
64
everywhere
whether
we
can
get
some
guidance
on
reasonable
values
for
Fergie's
like
take
something
like
a
slot
index,
for
example,
slot
number.
J
J
Another
idea
I
had
was
that
some
of
the
data
in
beacon
in
the
state
is
slightly
redundant
and
I
think
the
biggest
one
would
be
the
shard
committees.
Basically,
this
is
something
that's
derived
from
from
a
different
field
in
in
the
state.
So,
as
far
as
I'm
concerned,
it
would
perhaps
be
more
simple
if
it
wasn't
in
the
state,
but
it
was,
but
rather
that
it
was
fetched
at
the
beginning
of
processing
and
then
what
time
implementers
can
do
is
cash
it
if
they
wish
to
you're
right
I,
that's
an
interesting
one.
J
J
I
After
some
time,
I
realized
that,
for
example,
in
the
fussing
for
in
its
1.0,
you
download
in
the
state-
and
you
have
to
download,
like
256
previous
blocks,
to
serve
to
to
run
to
run
the
VM
correctly
and
that's
what
you
will
have
to
do
after
download
in
the
state
and
if
there
is
no
showers
and
committees
and
recent
walk
hairs
and
all
the
stuff
that
you
could
possibly
calculate
from
some
recent
blocks.
You
will
have
to
download
those
blocks
and
process
them.
I
But
if
you
have
everything
in
the
state,
you
could
download
the
state
and
storage
syncing
from
from
that
point.
Something
like
that.
So
it's
it's
pretty
handy
in
the
in
this
case
right
and
one
of
the
one
of
the
general
goals
has
been
that
the
states
plus
the
previous
state
plus
the
recent
block
you.
A
Once
you
take
that
out,
then
you
put
a
lot
more.
You
make
the
state
encompass,
multiple
blocks
and
kind
of
caching,
and
you
have
the
state
the
states
still
there
and
to
process
everything.
You
still
need
the
state
look,
but
you
just
you've
kind
of
hidden
it
rather
than
making
it
very
explicit
what
this,
what
their
requirements
for
that
pure
function
are.
A
I
J
Repeated
twice
yeah
in
terms
of
numbers
of
items
and
it's
also
trivial
to
sort
of
computed
from
from
the
other
data
in
the
state.
So
it's
more
of
a
question
really
and
and
and
I'm
not
I
suggest
I'm
just
wondering
what
what
the
thinking
is
here.
Yeah
I
agree
we,
but
we
need
some
numbers,
at
least
in
terms
of
how
much
disk
space
we
will
need
for
storing
like
I,
don't
know.
I
A
K
Heard
of
off-
and
you
know
I'm
not
first
enough
on
not
to
speak
to
it,
but
I'd
like
to
kind
of
like
get
some
thoughts,
because
you
know
a
simple
serialization
implementation.
I
think,
regardless
of
what
we
use
on
the
networking
layer.
If
we
move
toward
protobufs
that
we're
going
to
use
simple
serialize
with
the
tree,
hashing
algorithm
for
the
actual
hashing
of
the
state.
A
And
so
I
wouldn't
I
wouldn't
say
that's
a
blocker
on
you
right
now
and
that
you
should
empty
much
simple
serialize.
As
for
the
ongoing
network
serialization
debate
or
is
there
any
I
haven't
been
following
that
one
closely?
Is
there
any
updates
on
that
and
you
new
thoughts?
I
saw
that
some
people
wanted
to
run.
Some
numbers
may
be
on
protobufs
I'm,
not
certain.
I
I
I
I
It
was
not
possible
to
change
the
format.
I
mean
it
wasn't
possible
because
all
clients
had
an
implementation
of
this
format
as
an
rfp
and
call
it
golden
and
yeah.
It
wasn't
possible
just
to
change
format,
I
mean
to
add
some
new
field
to
that,
and
it
had
to
be
encoded
as
with
one
of
signature
parameters
within
one
of
the
signature
parameters.
So
that
could
be
a
good
feature
for
for
serialization
protocol
good
feature
to
have,
but
not
not
not,
requirement.
A
Okay,
thank
you.
It's
incredible
to
see
all
the
progress
going
on
a
super
super
exciting
for
me.
As
we
said
Lots,
we
think
we
got
most
of
the
major
changes
and
additions
to
the
phase
zero
document
done
and
but
over
the
next
probably
five
days,
there's
going
to
be
a
series
of
just
ongoing
edits,
fixing
some
naming
reordering
some
things.