►
From YouTube: Eth2.0 Implementers Call #16 [2019/4/18]
Description
A
A
A
Cool
okay,
great
the
stringers
transferred
over
let's
get
started,
so
we
have
a
number
of
things
needed
today
and,
as
we
have
in
the
past
few
weeks,
we're
going
to
start
with
testing
updates.
Diedrich
has
been
spending
a
lot
of
time,
restructuring,
getting
everything
really
clean
and
working
on
some
tests.
Diedrich.
Do
you
wanna
give
us
an
update.
C
Was
to
get
the
tests
integrated
into
the
inspection
poster
ii,
so
it
could
trigger
it
on
the
CI.
We
want
the
prospect
to
be
this
common
core
between
tests
that
do
the
sanity
tests
for
the
aspects
of
the
test,
generators
and
in
the
future,
we'll
also
have
invariance
testing.
So
we
know
a
certain
output
is
valid
and,
together
with
some
new
tooling,
we
get
to
write
new
testing
writers.
We
have
an
example:
state
transition
test
generator
now
for
deficits.
We
have
lots
of
theaters
and
here's
a
few
others
that
are
backward
ported
student.
You
wouldn't.
A
Cool,
hey
Greg.
Can
you
mute?
Please
sorry,
no
problem,
thanks
Berto.
So
there
is
there's
increasing
number
of
tests
and
good
examples
on
how
to
use
the
new
test
generator
functionality.
If
you
want
to
get
your
hands
dirty
and
write
some
tests,
I
recommend
opening
it
up
cool.
Next,
we
will
go
to
client
updates.
D
Hey,
can
you
hear
me:
okay,
yep,
okay,
so
we're
pretty
close
to
being
up
to
date
with
the
zero
point,
five
point,
one
spec
we've
been
doing
a
bunch
of
network
debugging.
We
integrated
Antoine's
implementation
of
the
plum
tree
algorithm
and
we're
also
planning
that
road
dinner
up
workshop.
So
if
y'all
are
gonna,
be
in
New
York
during
blockchain
week,
I
think
it's
like
the
15th
or
16th.
Maybe
someone
can
jump
in
if
they
remember
the
exact
date.
D
D
E
E
All
right
yeah,
so
we
we've
just
were
doing
a
couple
things.
We've
got
a
branch
tracking
v6
because
we
thought
it
was
going
live
last
week,
so
we
just
had
that
continue
updating
and
we
pretty
much
wired
up
everything
and
we're
getting
ready
to
actually
test
like
a
single
node
kind
of
block,
processing
and
processing
some
empty
blocks
and
we're
getting
ready
to
integrate
a
couple.
E
If
we've
got
lid
PDP
actually
on
its
way
pretty
well
and
we're
working
on
hobbits
as
well,
so
we
can
get
closer
to
testing
syncing
up
with
Artemis
and
whoever
else
wants
to
join
and
well,
and
we
have
a
like
POC
MVP
of
our
validator
client.
It's
like
stateless
at
this
point,
but
it
looks
like
it
should
be
working
soon.
A
G
G
We
didn't
work
much
on
Windows
testing
because
we
had
some
issues
in
the
past,
but
now
it's
it's
working,
but
we
don't
advertise
yet
because
the
build
system
is
a
bit
complex.
Regarding
networking,
we
had
some
discovery
issues
that
we
fixed.
We
improved
sync
efficiency
so
right
now
we
have
both
backward
sink
like
a
client
request
missing
blocks
and
we
also
have
4
watt
sync.
So
someone
request
blocks
and
the
reply
err
will
send
the
block
requested
and
every
following
blocks
both
have
merits.
G
If
I
am
one,
we've
been
working
on
whisperer
a
bit
regarding
testing,
so
we
can
now
pass
state
tests,
though
we
don't
pass
them
and
we
open
the
two
issues
on
the
test.
Repo
on
the
improvements
that
we
would
like
to
see.
We
are
eagerly
waiting
for
the
SSD
tests,
because
caching
is
needed
to
pass
the
state
tests
and
that's
where
we
we
are
failing.
H
H
A
F
Hello,
so
last
week,
most
most
of
us
or
in
at
car
last
two
weeks
so
still
feel
in
Australia,
respectful
the
people
who,
in
Australia
really
and
the
test
a
is
under
construction
and
now
we're
testing
how
to
proposing
the
box
between
the
meditators
and
the
knowledge
thing
is
that
we
are
interpreting.
The
common
test
is
to
put
all
test
version,
0.5
one
two,
the
Trinity
heist
ID,
that's
our
updates!
Thank
you.
Thank.
J
Yep,
so
we
are
now
passing
five
one
state
transition
tests,
Paul's
implemented
the
tree
hash,
cashing
in
isolation
I
think
next
week,
we'll
probably
implement
into
our
run
time.
We've
been
assisting
with
the
BLS
standardization
by
benchmarking,
a
new
hash
to
curve
method.
We've
been
improving
networking
and
doing
some
bug
fixes
like
everyone
else,
particularly
in
Discovery
and
started
doing
some
peer
management
for
a
lighthouse
and
we're
improving.
Our
logging
in
freaking
out
started
building
some
debugging
tools
to
do
some
proper,
large-scale
network
tests.
That's
it
from
us
great.
K
Hey
guys,
as
many
of
you
seen
from
our
Cortana
dashboard,
most
of
our
resources
are
going
to
improving
and
15-time
parks.
So
what
may
be
incremental
steps
we
right
now
the
current
update
is
we're
able
to
run
128
validators
with
post
and
restart
with
tests
on
for
scenario
and
120
ml.
Did
this
work
so
we're
now
we're
trying
to
ramp
up
to
1024
validators?
We
reign
through
a
few
issues
where
we're
trying
to
figure
out
what
type
of
bad
blocks
wish
you
save?
What
about
four
o'clock?
K
We
should
be
saving
and
I
will
ask
them
later,
so
we
don't
spam
the
step
status
update
on
top
of
that
we
are.
We
are
optimizing
LMD
for
tourists,
we
add
caching
to
community
shuffle
means,
and
we
implemented
where
a
single
validator
can
act
us
multiple
validators
by
giving
them
many
different
public
and
private
keys
and
shout
out
to
our
team
and
we
shape
for
that
and
that's
it.
L
Yeah
so
I
can
I
can
just
say
that,
basically,
there
is
some
work
on
Heath
to
stuff
in
in
the
gut
team
is
mostly
me
working
on
the
discovery,
and
then
we
have
one
guy,
just
like
exploring
different
parts
of
it
too
and
I
trying
to
implement
some
stuff,
but
we're
not
at
a
point
where
we
can
actually
like
you
know,
follow
the
spec
or
anything
so
I
guess
like
at
that
point.
Someone
and
someone
who's
actually
working
that
stuff's
gonna
join
the
call.
L
M
A
Okay
thanks
and
we
will
get
to
network
updates
in
a
little
bit,
I
think
Keith
I,
don't
think
we
have
anyone
from
eath.
Is
that
correct
cool?
Okay?
Thank
you
I.
So
we
had
a
workshop
in
Sydney.
Thank
you,
everyone
that
was
able
to
attend
and
thank
you
single
crime,
guys
for
helping
us
find
location
and
just
general
hospitality
and
have
one
out
there.
I
wanted
to
give
a
little
bit
of
time
for
brief
updates.
A
The
expectation,
I
think,
is
to
write
up
some
notes
from
each
of
these
sessions,
and
we
also
have
some
videos
of
most
of
the
sessions
that
I
will
I'm
hoping
to
get
soon
and
release.
But
if
any
one
that
was
leading
her
in
her
session
that
once
you
have
just
a
quick
refund,
look
what
happened
again,
quick,
but
how
about
it?.
N
Sure,
sir
mine
was
a
client
architecture,
so
he
spent
the
first
part
sort
of
talking
about
I
think
it
was
I.
Don't
have
the
notes
in
front
of
me,
but
it
was.
It
was
API
so
talking
about,
like
I'm
trying
to
find
maybe
some
minimal
interface
between
beacon,
road
and
a
Ballard,
a
client
and
what
that's
like.
We
try
a
little
bit
about
whether
we
should
use
JSON
or
G
RPC
I.
N
Think
Luke
from
Sigma
prime
is
going
to
create
some
issues
to
deal
with
that,
and
then
we
just
kind
of
had
a
bit
of
open
discussion
about
caching
and
optimizations,
and
things
like
this
yeah,
not
a
huge
amount
of
takeaways,
but
once
I
have
those
issues.
I'll
link
them
in
mostly
just
us
kind
of
trying
to
like
learn
from
each
other
cool.
O
Austin,
so
we
covered
a
variety
Thanks
first
thing
that
we
covered
was
Lippe
to
be
just
issues
and
things
that
we
might
like
to
change.
The
gardening
with
p2p,
so
I
have
a
big
list
of
those
things
we
might
go
over
this
later
during
this
call,
I'm,
otherwise
all
sort
of
aggregate.
Then
we
can
discuss
them
offline.
We
discussed
briefly
some
problems
with
serialization,
which
I'll
be
writing
up.
Spec
changes
for
in
order
to
support
and
potentially
also
discussing
with
some
of
the
sse
team
in
just
a
few
minutes
regarding
propagation.
O
So
one
of
the
big
things
we
walked
away
from
was
that
we're
going
to
resurrect
some
of
the
efforts
that
white
block
was
doing
in
order
to
test
out
gossip,
some
performed
under
load.
So
I'm
really
looking
forward
to
that,
since
that's
sort
of
the
biggest
blocker
right
now
to
full
adoption
of
gossip
sub,
but
nevertheless
I'll
be
creating
the
specification
for
what
we
are
going
to
be
gossip
subbing
over
the
next
couple
of
days
to
check
and
then
finally
for
peer
discovery.
O
It's
still
a
pretty
early
discussion
there,
but
the
main
thing
that
sort
of
we
came
together
as
a
group
was
that
we
need
to
just
spend
some
time
to
talk
to
Felix
or
some
other
expert
on
Discovery
v5
to
understand
how
it
needs
to
change
as
it
relates
to
e2.
So
if
he
looks
like,
if
you
have
a
chance
in
the
next
like
week
or
two
I'm,
just
have
a
great
call
with
me
to
go
over
those
things.
I'd
really
appreciate
it.
Oh.
A
G
So
secession
started
with
a
reminder
of
the
goal
of
EVM
at
the
start
and
wasn't
so
for
was
a
mix
was
more
like
a
Java
for
the
web,
something
built
from
the
web
from
the
very
start,
compact,
with
security,
property
and
close
to
native
performance,
and
it
was
an
is
the
goal-
is
to
abstract
the
execution
layer.
So
the
two
main
challenges
for
it
wasn't
that
I
noted
was
mattering
and
bounding
execution.
G
So
we
had
a
very
long
review
by
CAHSEE
on
it
was
a
performance
and
some
special
cases
also
where
the
EVM
was
actually
faster
than
it
wasn't.
We
talked
a
lot
about
was
E,
which
is
Mozilla
web
assembly
system
interface
and
comparing
it
to
a
forum,
environment
interface
and
some
questions
about.
Does
it
fit
with
V
frame
or
not?
G
A
Very
much
so
those
are
the
morning
sessions.
Then
after
lunch
Vitalik
let
a
whiteboard
session
on
light
clients,
which
is
awesome
just
pretty
much
going
over
the
specs,
the
rationale
and
the
design
there.
There
is
a
video
and
we
will
be
sharing
so
I.
Don't
think
we
nearly
need
to
go
over
that
right
now
and
the
afternoon
we
had
a
session
on
just
test
nets.
Roadmap
kind
of
we
ended
up
just
talking
about
lots
of
things
that
need
to
happen
and
generally
trying
to
figure
out
what
happened
needs
to
happen
in
Q,
2,
3,
etc.
A
A
few
notes
I
have
for
some
conditions
necessary
for
having
a
long-standing
multi
client
s
net,
we're
all
clients,
pass
tests,
consensus
tests,
speaking
sand,
networking
protocol,
building
out
and
networking
monitoring
output
tools.
We're
definitely
interested
in
doing
some
sort
of
structured
test
nets,
as
may
be
similar
to
type
of
game
of
state
stuff,
xenon
cosmos.
So
we're
looking
into
organizing
that
and
maybe
what
some
of
the
goals
there
would
be
obvious.
Some,
let's
see
general
tooling,
on
visualizers
Bach
explorers
some
functions
for
injecting
bad
data
into
the
test,
nuts
and
then
stuff.
A
Those
notes
in
a
little
bit
more
formal
way
to
share
and
the
other
afternoon
session
was
just
phase
two
outside
of
the
VM
I
believe
this
ended
up
being
I
wasn't
a
part
of
it,
but
I
ended
up
being
kind
of
like
a
whiteboard
session
that
italic
let
of
italic.
You
have
any
notes
or
comments
on
what
happened
during
that
event,
yeah.
B
And
we
basically
went
through
the
end
of
different
parts
of
what
we
expect
to
be
faced
to
so
webassembly
crossed
short
communication,
rent
state
merkel,
proofs,
like
abstraction,
and
I
guess
it
seems
that
the
that
all
of
the
kind
of
big
parts
of
phase
two
were
kind
of
rough
are
kind
of
roughly
figure
it
out,
at
least
in
their
general
form,
and
and
I
got
the
improv,
the
impression
that
people
seemed
and
if
fine
I'm
fine
with
it.
But
then
there's
obviously
I
bunch
of
small
details
still
to
be
figured
out.
A
Thanks
and
so
we
do
have
videos
of
all
of
these
sessions
that
SEP
for
the
client
architecture,
because
we
only
had
two
recordings.
That
was
because
of
the
way
the
space
is
set
up
and
so
I
will
get
those
out
as
soon
as
possible
and
to
my
company
notes
again
thanks
everyone
that
can
make
it
and
thanks
Sigma
prime
for
doing
some
of
the
hard
work
getting
us.
The
space
and
stuff
cool
next
up
on
the
agenda
is
research
updates.
Are
there
any
research
updates.
P
P
Quite
a
bit
quite
a
bit
of
engagement
there
we
also
are
looking
into
constant
time
hash
functions
for
hash
g2
and,
in
addition
to
the
traditional
method,
which
is
called
the
fook
Taguchi,
apparently
there's
a
new
curve.
That's
just
came
out
by
Dan
Bonet
and
Ryan
Bobby,
so
I
guess
we'll
be
discussing
that
one
thing
that
I
think
this
rough
consensus
around
is
moving
transfers
to
phase
one.
So
no
transfers
in
phase
zero,
I
guess
part
of
the
rationale.
P
There's
to
take
a
slow
and
steady
approach
like
transfers
would
be
the
main
you
know
economically
meaningful
type
of
action
on
phase
zero.
So
if
we
remove
them,
we
are
kind
of
signaling
that
it's
mobile
test
net
and
if
there
is
some
sort
of
network
disruption
that
we
can
do
a
large
rollbacks
without
having
to
worry
about
these.
P
Guess
thinking
forever
down
the
line
for
Phase
two
and
that's
kind
of
a
one
of
the
outcomes
of
the
workshop
and
is
a
kind
of
transaction
abstraction.
So
the
idea
that
in
in
DBM
to
puno,
we
may
not
have
a
notion
of
transaction
where,
basically,
everything
is
just
a
contract
in
the
contract
call,
which
is
an
idea
that's
to
to
be
quite
quite
nice
and
powerful.
With
a
few
downsides.
B
B
From
one
shard
into
another
shard
before
the
second
shard
kind
of
formally
learns
about
the
receipt
from
the
first
shard
and
then
what
happens
is
that
inside
of
the
second
chart,
you
store
a
conditional
state
object.
So
you
have
a
process
that
kind
of
runs
behind
behind
an
epoch
and
resolves
all
of
the
conditional
objects.
But
that's
just
a
kind
of
very
big
category
of
ideas
and
within
that,
there's
the
challenges
of
how
to
avoid
exponential
blow-ups,
how
to
actually
store
state.
B
How
to
just
make
the
whole
thing
work
sanely
in
in
a
reasonably
simple
in
general
way,
so
I've
been
I'm
still
in
of
early
stages
of
mentally
trying
to
figure
out
the
best
of
the
best
model.
For
this
sort
of
thing.
So,
like
the
general
approach
that
I'm
thinking
about
is
that
you
can
have
state
objects
in
one
shard
that
store
and
a
dependent
that
store
dependencies.
B
And
so
you
would
have
potentially
multiple
copies
of
a
state
object
and
you
would
have
some
data
structure,
and
that
basically
says
this
is
the
state
objects
that
I
kind
know
is
most
likely
to
be
to
turn
out
to
be
correct,
and
so
this
is.
This
is
the
one
that
means
that
a
transaction
can
work
off
of
and
the
rest
of
the
objects
are
just
there
and
if
in
case
the
first
one
through
turns
out
not
to
work,
and
so
what
this
gives.
B
You
is
the
ability
to
do
this
kind
of
optimistic,
fast
path,
and
it
almost
looks
like
you're
at
you're
getting
actual
state
transitions
cross
shard
within
a
couple
of
seconds,
but
then
actually
it's
done.
On
top
of
this
thing,
where
they're
real
state
transitions
only
happen
after
a
couple
of
a
couple
of
minutes,
and
the
challenge
is
basically
just
making
and
making
that
whole
thing
kind
of
lorca
maximum
just
and
feel
maximally
elegance
to
a
use
and
work
with
so
realistically.
B
The
way
I
see
this
happening
is
that
there
would
be
one
contract
that
you
could
call
a
kind
of
hypervisor,
and
transactions
might
actually
might
end
up
actually
just
being
calls
to
the
hypervisor,
and
then
the
hypervisor
would.
And
if
do
logic,
that
says
that
basically
just
manages
these
different
state
objects.
A
Great.
Thank
you.
Another
comment
on
the
transfers,
so
I
think.
The
intention
here
is
to
launch
with
the
max
transfers
per
block
constant
at
zero
and
I'm,
actually
in
favor
of
before
phase
one
to
coordinate
a
fork
on
enabling
transfers
simply
to
kind
of
practice
a
hard
fork
before
we
with
the
fork
any
mechanism
before
we
hard
for
phase
one.
But
that's
up
for
debate
and
discussion
for
that
online.
A
Q
So
this
is
from
BSC.
This
is
more
of
an
academic
update,
perhaps
rather
than
a
Sunday,
because
it
was
important.
I
just
mentioned
that
I
have
give
a
couple
of
classes
on
the
last
few
weeks,
master
that
is
focus
on
project
energy
and
I,
more
or
less
explain
the
concept
of
a
chart
in
material
and
I
have
presented
the
simulator
to
France
and
a
supercomputer
to
the
students,
and
so
they
have
been
playing
with
this
simulator
a
little
bit
so
yeah.
A
L
Nice
so
I
posted
it.
The
link
on
the
agenda
to
the
call
so
I
think
we
have
the
discovery
before
expect
95%.
So
there
are
still
some
tiny
things
to
figure
out,
but
basically
I
think
almost
everything's
come
together.
Now
I
have
a
go
implementation
of
it.
It's
not
as
completely
suspect.
So
at
some
point
it
was
ahead
of
the
spec.
L
Now
it's
behind
again
I
was
sick
this
week,
so
I
couldn't
actually
do
anything
but
I'm
guessing
that
we'll
be
able
to
actually
I,
don't
know
like
test
it
out
in
like
one
two
weeks
time.
So
what
we
need
right
now
on
the
on
the
Discovery
v5
is
just
you
know
extra
eyes
on
this
back
and
just
you
know
to
see
if
the,
if
the
Crypt
is
okay,
so
we
changed
from
the
last
update,
which
was
I
think
three
weeks
ago
and
they
call
change
quite
a
few
things.
So
there
was
like
it's
it's
encrypted.
F
L
So
there's
like
a
key
agreement,
handshake
and
some
of
the
actual
messages
in
the
protocol
and
simplified
and
there's
a
lot
more
documentation
in
general
like
about
the
protocol.
So
we
have
a
dis
packet
and
it
is
a
spec
is
in
three
parts
now
so
we
have
a.
We
have
the
actual
wire
protocol,
spec,
which
is
really
short.
So
it's
like
1,500
words
approximately.
Then
we
have
a
sort
of
theory
document.
L
It
explains
how
to
implement
it
in
terms
of
algorithms
and
data
structures,
and
then
we
have
a
rational
document,
but
this
one
is
outdated
at
the
moment.
So,
just
probably
like
the
next
update
to
the
spec,
is
probably
going
to
be
to
just
update
the
rationale
to
explain
some
of
the
design
choices
better.
L
So
this
is
where
we
are
at
the
moment
and
I'm
actually
really
excited,
because
because
there's
just
not
so
much
to
do
anymore
in
terms
of
figuring
out
some
of
the
problems,
so
I
guess
the
the
the
big
next
step
is
just
going
to
be,
like
you
know,
having
it
audited
and
seeing
how
the
implementation
behaves.
And
then
you
know
maybe
having
a
second
implementation
or
test
against
before
we
can
like
launch.
L
There
is
definitely
you
know
we
have
a
voltage
in
in
in
Goya
theorem,
because
we
we've
had.
You
know
for
the
for
the
topic
advertisement
stuff.
We
basically
already
had
the
implementation
from
the
from
the
two-year-old
prototype
that
we've
actually
been
using
for
two
years.
So
we
can
already
know
that
you
know
it's
not
obviously
broken
in
in
in
in
those
parts,
but
but
the
wire
protocol
is
like
brand
new,
so
it's
that's.
Actually
most
of
the
work
was,
which
is
you
know,
making
the
wire
protocol
work,
so
they
actually
did
a
structure.
L
I
just
used
the
same
thing
that
we
already
had
for
the
v4
and
from
the
from
the
earlier
prototype.
So
it's
not
not
changed
all
that
much
in
general,
I.
Just
think
you
know
it
would
be
best
if,
like
some
people,
whoever's
like
really
internet
working
who
just
check
out
the
spec-
and
you
know
tell
me
if
there's
anything
obvious
is
wrong
or
they
think
something's
wrong.
Maybe
something
needs
like
to
be
explained
and
to
be
explained
better.
L
A
Thanks
cool
yeah:
to
reiterate
this
is
definitely
one
of
the
big,
not
a
blocker,
but
just
kind
of
one
of
these
unknowns
that
we
need
to
resolve.
So
if
the
networking
person
from
your
team
can
take
a
look
at
it
and
provide
feedback
as
soon
as
possible,
that
would
be
awesome,
and
if
you,
if
somebody
does
want
to
take
a
whack
at
an
implantation,
let
me
and
Felix
know
cool
anything
else.
Felix
on
your
side,
no.
A
S
So
one
big
change
on
our
end,
something
that
has
been
Hey
for
a
long
time:
entry,
consolidating
and
basically
pulling
together
all
of
the
instructions
that
make
up
will
it
be
to
be
into
a
single
place
so
that
it's
you
know
it's
easy
to
reason
about
the
system
to
understand
how
things
are
wired
together
and
so
on.
This
is
taking
place
already
in
the
current
gravitation.
We
are
basically
deprecating
around
fifteen
records,
which
is
a
very
huge
number
that
I'm
very
happy
about
and
and
yeah.
S
This
is
I
posted,
a
few
links
on
the
meeting
agenda
for
today
with
a
few,
but
the
forum,
discussion
and
the
issues
and
so
on.
So
you
can
participate,
take
a
look
at
how
it's
shaping
up
in
the
in
the
branch
where
this
work
is
taking
place
and
so
on
and
and
just
just
take
a
look
around
and
poke
around.
That
is
the
main
update
update
from
my
end,
but
I
just
want
to
say
that,
and
you've
probably
already
seen
this,
because
I
noticed
it
in
several
places
that
we
have
opened
up
our
forums.
S
They
are
now
GA,
finally,
so
feel
free
to
to
create
an
account
there
and
start
a
discussion.
I
don't
want
to
be
a
bottleneck
for
you
guys
to
indeed
here
in
community,
to
interact
with
them
at
the
TP
community.
So
that's
pretty
rich.
These
two
communities
together
and
have
a
free
flow
of
conversations
there.
A
O
Hello,
can
you
hear
me
yep,
yes,
cool,
so
there's
a
bag
of
updates
that
I
have
coming
that
I
should
have
ready
by
like
Tuesday
next
week.
So
specifically,
these
are
changes
based
on
feedback
serialization,
the
contents
of
the
gossip
sub
or
not
gossip
sub,
but
the
like
the
block,
propagation
api's
and
then
a
couple
more
that
I'll
aggregate
from
the
notes.
So
you
can
expect
those
to
be
open
on
Tuesday
and
ready
for
discussions.
A
O
O
O
So
there
are
two
pieces
that
are
inside
that
porpoise
there's
the
introduction
of
a
null
and
the
introduction
of
a
union
type
which
will
allow
us
to
have
richer
data
structures
for
structures
that
we
do
serialize
using
ssz,
but
for
the
actual,
like
request
response,
payloads
I'm,
just
not
going
to
use
SSE
and
just
use
a
sequence
of
bytes
just
because
it's
massively
easier
and
expresses
the
data
inside
those
request/response
wrapper
objects
simply
enough
without
having
to
introduce
big
changes
to
these
serialization.
So
that's
the
sort
of
story
there.
G
A
I
just
shared
eight
six
one
and
eight
seven
one
in
the
chat
which
I
believe
are
both
related
and
then
I
shared
the
PR
related,
the
Union
type
and
Melo
type
in
SS.
So
discussion
can
definitely
happen
there
and
it
looks
like
Matt
is
going
to
be
releasing
some
of
these
updates
next
week,
and
so
discussion
can
happen
on
that
PR
as
well.
Okay,.
A
O
A
T
No
I
I
just
started
a
new
repo
for
it
and
I
just
repurposed
everything
from
our
work
last
year
with
III
search,
I'm
gonna,
be
writing
out
the
test
library
and
sharing
it
all
in
that
repo,
so
feel
free
to
check
it
out.
Any
feedback
or
collaboration
on
defining
the
test
test
plan
would
be
appreciated,
but
I'm
gonna
start
already
started
on
this
week.
So
great,
can
you
share
the
repo
please
yeah
I
added
it
to
the
big
get
for
the
call?
Okay,
great
thanks.
S
So
when
I
wanted
to
say
that's
that
can
I
have
been
in
touch
regarding
saluting
them,
for
this
and
I
put
them
in
touch
as
well
with
the
lead
developer
of
concepts
table.
So
we
can
help
you
refine
that
test
plan
and
support
to
you
whenever
you
find
roadblocks
or
whatever
thanks
thanks
a
lot
appreciate
it
and.
S
A
Cool
general
spec
discussion
I
want
to
highlight
okay,
so
we're
we
have
this.
This
looming,
0
6
I
kind
of
want
to
get
it
out
tomorrow,
because
it
has
a
number
of
testing
updates
that
I'd
like
to
get
out,
but
there
are
a
few
things
still
pending,
so
we're
debating
on
whether
to
wait
on
getting
it
out
for
next
week.
So
I'm
gonna
pull
up
a
draft
PR
today,
I
like
to
take
a
look
at
the
complexity
and
things
going
on
and
make
a
judgment
call
so
that
to
be
released
in
the
next
seven
days.
A
K
K
So
one
scenario
is
that
you
could
receive
a
backlog
and
the
backlog
to
just
be
a
passing
issue,
and
then
we
could
receive
a
block
that's
from
a
for
chain
and
then
the
third
scenario
is
that
we
can
receive
a
block
that
is
from
the
canonical
chain
right.
So
let's
say:
if
we
receive
a
block,
that's
bad,
which
has
a
bad
signature.
K
I
think
we
should
just
drop
the
block,
discard
it,
and
then,
if
we
receive
a
block
that's
from
a
fortune,
we
should
probably
save
it
and
then
update
the
registrations
with
the
latest
stasia
targets,
because
that
block
could
be
the
head
sometime
again.
So
because
of
that,
we
want
to
save
it
and
then,
if
we
receive
a
block
from
economical
chain,
would
you
just
process
it
normally?
Do
you
guys
agree
with
this
type
of
approach.
A
Yeah
that
all
sounds
sane
when
you
are
processing
a
block
I
suppose
you
eat
either
building
on
what
you
see
is
the
head
or
not,
but
regardless
of
whether
it's
building
on
the
head
of
its
building
on
something
that's
in
your
block
tree,
you
should
certainly
process
it
and
see
if
it
is
the
head
and
save
it
for
later
use,
so
I
think
we're
definitely
in
agreement.
They're
bad
blocks
should
should
be
dropped.
A
K
One
question
that
I
had
was
that
safe,
we
receive
a
block,
but
then
it's
from
a
different
proposer
and
that's
it.
We
ignore
that
block
is
from
different
proposer
and
later
there's
two
reorg
and
in
the
reorg
caused
a
reshuffling
and
then
and
then
turns
out
that
blood
is
actually
from
the
right
proposer
because
of
the
shuffling.
So
what
do
we
do
in
that
case?
So.
A
The
only
way
that
a
so
that
say,
you
have
a
block
from
an
unexpected
proposer
if
it
was
built,
if
it.
If
it's
in
your
tree,
you
can
still
tell
if
it's
a
valid
proposer,
given
so
say
it
built
off
something
prior
to
the
previous
reshuffling,
then
that
proposer
would
be
valid
in
the
context
of
the
branch
of
the
tree,
and
so
you
could
always
process
it.
A
A
You
always
have
a
heuristic
of
attestations,
so
if
you
have
a
block,
come
in
and
there's
literally
no
authorization
for
it
and
it's
going
to
cause
you
to
have
to
download
a
bunch
of
other
blocks
to
figure
out
where
it
goes
or
an
unexpected
proposer.
There's.
Definitely
if
it's
gonna
cause
you
to
do
unto
work
and
there's
no
attestations
for
it.
You
might
put
it
in
a
queue
and
deal
with
it
later.
Mm-Hmm.
A
A
K
A
N
We
have
a,
we
have
a
queue
like
a
queue
that
we
we
build
up
like
as
we
sink.
We
build
this
queue
and
then
we
try
and
process
the
queue.
So
we
have
to
do
just
like
a
little
bit
of
extra
logic.
On
top
of
that
to
be
like
is
it
is
it
should
we
discard
it
from
the
queue
or
should
we
leave
it
in
the
queue
and
try
and
process
it
later?
N
So
if
it's,
if
it's
like
the
case
where
we
don't
know
its
parent,
but
it's
not
necessarily
invalid,
then
we
keep
it
and
maybe
try
and
process
it
later
same
deal
if
it's
from
like
it's
the
future
slot,
that's
like
ever-so-slightly,
maybe
the
next
or
something
like
that.
So
that's
just
something
that
we've
come
across.
That.
G
Do
the
same
thing:
in
Nimbus
we
have
a
block
pool
which
run
in
a
separate
process
so
during
the
block
processing,
if
we
receive
a
block
with
that,
we
don't
know
about,
we
put
it
in
that
pool
and
we
have
a
separate
process
that
just
checks
and
ask
the
network.
Well,
I,
don't
know
about
this
block,
give
me
information
and
if
something
is
is
missing,
because
we
are
missing
that
block
and
a
lot
of
block
in
the
middle
we
ask
for
all
of
those
as
well.
G
A
N
A
A
Sorry
I
destroyed
Greg's
comment:
okay,
I
guess
we
can
move
on
from
spec
discussion
as
always
head
up
the
getter
get
in
touch
with
me
or
you
know.
Actually,
at
this
point
the
clients
there,
your
Co
clients,
can
answer
lots
of
questions,
cuz
they're,
seeing
a
lot
of
these
problems
in
the
law
as
well
cool,
so
open
discussion.
U
I
just
want
to
reiterate
what
Johnny
was
talking
about
this
workshop,
we're
gonna
do
May
16th
in
New
York,
it's
kind
of
in
between
consensus,
I
assume.
Nobody
here
is
going
to
that
and
in
between
consensus
and
East
New
York,
it's
just
a
day
in
between
we'd
love
to
have
everybody
come
out.
I
think
there's
been
like
a
decent
amount
of
commitments
from
the
various
implementation
team,
so
we
hope
either
yeah.