►
From YouTube: Eth2.0 Call #28 [2019/11/21]
Description
A
A
A
We'll
get
started,
testing
and
release
updates,
as
for
testing
I
think
generally
staple.
Although
I
think
Maddie
will
give
us
an
update
in
a
moment
on
some
work
that
he's
been
leading
as
for
release,
I
do
have
a
pending
release
on
github,
with
some
minor
clarifications
and
changes.
I
think
specifically
clarify
some
things
in
the
last
update
about
subnets
and
stuff
I'm
looking
to
get
that
out
as
soon
as
possible.
I,
don't
think
that
changes
might
change
one
test
version,
but
I'll,
let
y'all
know
that's
coming
other
than
that.
B
Thanks
hi
everyone,
so,
as
some
of
you
may
have
seen,
Danny's
update
suma
Prime
has
been
awarded
a
grant
from
the
you
theorem
foundation.
We
do
welcome
because
professor
I'm
very
excited
to
keep
contributing
to
the
issue
security
ecosystem
beyond
I.
Guess
our
work
on
the
lighthouse
so
we'll
be
ramping
up
our
efforts
on
first
starting
from
next
week
getting
more
time
and
resources.
B
So
far
since
the
last
update
we've
managed
to
clean
up
the
buzzing
targets,
there
are
no
longer
relevant,
so
we've
just
basically
got
rid
of
the
function
of
the
fuzzing
targets
that
are
no
longer
endure
in
spec.
We've
also
added
a
couple:
more
block
state
transitions
to
our
fuzzers,
so
in
fact
good
news.
All
the
block
state
transitions
are
now
included
in
which
is
cool
and
we've
also
added
to
Hawk
state
transition
functions
that
are
running
locally
on
my
machine
at
the
moment.
B
So
looking
at
process
rewards
and
penalties
and
process
slashings,
we
have
been
working
on
integrating
other
implementations
as
well,
so
we've
reached
out
to
a
couple
of
you
folks.
So
as
a
reminder
currently
beacon.
First
works
fully
supports
high
spec
guarantee
on
lighthouse.
We've
reached
out
to
prism
the
build
process,
not
you
know
very
straightforward,
but
we
got
there
at
the
end
happy
to
say
that
prism
is
now
integrated,
but
unfortunately
we're
facing
issue
issues
since
we're
having
now
to
go
implementations
so
we're
facing
a
bunch
of
namespace
classes.
B
So
we've
reached
dr.
proto
who's,
providing
this
with
a
bunch
of
different
I
guess
avenues
and
up
shows
that
we
can
explore
but
I'm
fairly
confident
that
will
we
get
there
very
very
soon.
We
reached
out
to
name
this
as
well,
so
we
are
I,
guess
trying
to
see
how
we
could
reduce
the
static
sea
library.
Then
we
could
simply
link
to
our
differential
fuzzer
and
we
started
integrating
Trinity
as
well,
which
should
be
very,
very
straightforward.
B
So
we
started
working
on
prison
thinking
that,
since
we
had
the
rnc
up
and
running
with
the
very
I
guess
trivial
to
add
another
go
implementation
turned
out
to
be
quite
the
opposite,
because
we
already
have
a
go
pigmentation.
It's
it's
actually,
not
not
as
simple
as
as
expected.
Next
steps
will
be
to
finalize
all
the
epochs
their
transitions,
so
that
should
be
done
next
week.
B
We'll
also
bump
all
the
current
fuzzers
to
the
latest
version
of
the
spec,
not
just
sure
exactly
what
the
progress
is
from
the
implementers
on
being
compatible
with
zero
point
nine
point
one
but
I
guess
we're
an
update
from
everyone
today
and
will
also
continue
integrating
eternity
so
hoping
to
have
prism,
Trinity
and
Nimbus
up
and
running
on
beacon,
flowers
by
the
next
update.
Thank
you
thanks.
A
A
C
There
are
currently
55
years
right
now
and
when
we
count
them
ours,
so
it's
deafening
great
to
see
that
users
training
now
also
with
that.
It
also
comes
with
other
questions,
support
and
great
feedback
on
the
community.
So
we
have
been
improving
upon
those
feedback
and
then
also
improving
upon
or
testability.
C
Your
opponents
we're
making
SSD
performance
improvements
right
now,
because
with
one
of
our
bigger
bottleneck,
hearing
I'm
seeking
also
where
we
REM
him,
they
eat
one
data,
implementation,
I'll
trade,
a
precedent
had
a
few
questions
on
that.
So
do
you
see
that
happening
and
then
we
also
resume
finish
our
foodie
end-to-end
tests
from
depositing
the
deposit
contract
and
then
from
the
audience
of
submitting
a
deposit
concession
and
the
finalizing
epoch,
so
so
drive
him
on
that
and
yeah?
That's
that's
about
it.
A
D
D
Where
we
have
a
test
that
running
on
running
in
the
cloud,
the
orchestration
and
monitoring
we're
just
not
quite
ready
to
push
it
to
the
public.
Yet
because
we
want
to
finish
our
documentation
and
we
really
came
to
get
the
hot/cold
database
in
there
before
we
make
it
public
just
so
we're
not
filling
up
people's
machines.
D
We're
also
working
on
refactoring
I
validate
a
client
would
be
quite
a
big
refactor
of
it.
We're
focusing
on
acing
corporations
and
we're
putting
in
some
new
slashing
protection
stuff
and
we're
also
doing
some
aggregation
in
the
validator
client.
So
if
you
are
running
very
large
numbers,
like
tens,
hundreds
of
thousands
in
one
machine,
this
should
make
it
much
easier
for
your
bacon
node
to
handle
it.
Some
might
say
they
were
just
trying
to
beaten
him
in
the
next
round
or
tweaking
around
the
most
validators.
But
I
wouldn't
say
that
we're
also
working
with
Harumi.
D
Implementation,
we're
still
gonna
keep
working
on
ours,
just
the
sake
of
diversity.
I
think
we
might
kind
of
put
them
behind
compiled
flags
and
kind
of
see
how
they
go,
because
own
room
is
fast
and
extremely
impressive,
but
it
is
night
assembly.
So
it's
a
tiny
bit
scary,
but
very,
very,
very
much
cool
for
the
networking
side.
We've
started
working
on
noise,
handshaking
lead,
p2p,
we've
added
civil
resistance
to
the
DHT
and
we're
focusing
on
a
testing
effort
to
test
all
Network
components
which
is
not
trivial,
but
something
we
definitely
have
to
do.
E
We
also
made
a
huge
progress
on
this
cui
v
in
javascript
and
our
0.9
spec
is
pretty
much
done,
they're
just
waiting
the
next
release
of
jelly
p2p
because
it
introduces
daesik,
iterate,
iterators
and
stuff,
which
is
kind
of
needed
for
that
spec
version
and
that's
pretty
much
working
that
I
can
remember.
I
want
to
really
expect
this
to
be
delivering
the
update.
Oh.
A
F
G
G
G
So
it
was
twenty
one
millisecond
for
pairing
otherwise,
on
next
to
do
is
working
with
Sigma
Prime
on
be
confessed,
so
probably
will
add
some
books
to
n
CLI
so
that
it's
easy
to
call
or
to
maybe
produce
capi
for
phasing
on
the
networking
front.
We're
working
well
always
on
this
three
five,
an
active
one
and
side
note
on
f-14,
so
Nimbus.
If
one
we
finished
Istanbul
at
fork,
implementation
and
we
started
working
on
a
Grove
wrapper
to
switch
part
of
the
status
client
to
Nimbus
if
one
instead
of
gifts
and
that's
all
fun.
A
A
G
H
Year
so
software
for
party,
we
are
mostly
doing
some
mob
foundation,
work
for
beacon,
Chen
and
the
beacon
beacon
from
state
transition,
implementation
and
mostly
I,
think
the
conference
is
try
to
revive
the
subject
run
time,
which
was
unfortunately
removing
the
pastor
who
the
suspect,
changing
completely
and
also
subject
anything
too
quickly.
So
I
do
catch
every
the
schedule
by
removing
that,
but
I
think
right
now
is
very
important.
We
revive
that
and
the
goal
is
to
hopefully
first
make
a
breach
and
second,
hopefully
make
some
of
the
components
like
this
time.
H
I
Everyone
so
mainly
working
on
spec,
updates
and
performance
to
various
bits,
so
that'd
be
like
the
version:
zero
nine
one
updates,
which
are
mostly
all
together,
there's
really
just
some
refactoring.
We
had
to
do
on
the
fork
choice.
That's
blocking
being
fully
up-to-date
there,
although
I,
do
believe
we're
passing
all
of
the
fixtures,
the
the
spec
test.
That
is
some
other
things
updates
to
pilot
p2p
stability.
We
merged
in
our
eighth
one
monitor
some
great
performance.
Work
on
passes
said,
which
had
been
a
big
bottleneck
for
us,
and
then
we've
started
work
on
attestation,
aggregation.
J
Were
were
split
into
two
teams.
Now,
we're
working
in
one
team
were
calling
Advanced
Research,
which
is
what
we're
kind
of
like
combining
it
Armony
we're
going
to
be
working,
client
not
been
working
offline,
and
we
have
another
team
working
on
Artemis
this
for
being
a
kind
of
like
production,
readiness
and
and
they're
kind
of
making
changes
and
implementing
sync
right
now.
K
Hey,
so
on
the
Artemis
side,
we've
finished
0.9,
oh
and
we
are
just
finalized
that
finalizing
the
naive
aggregation
stuff
and
then
we'll
take
a
look
at
nine
point.
One
right
after
certain
point
nine
point:
one
we've
got
all
the
request
response
methods
done
to
at
least
basic
functionality,
we're
just
finalizing
a
review
and
then
we're
also
starting
a
round
of
in
drop
testing
with
other
clients.
If
there
are
clients
that
have
donker
and
they
just
published.
K
A
Great
thanks,
Johan
and
Meredith
I
saw
your
question
in
the
chat
I'll
get
to
detail
there,
but
the
it
is
a
function
of
the
size
of
the
validators
that
I
don't
know
if
that
is
explicitly
written
down
anywhere,
but
we
can
both
specifically
sorry.
This
is
the
the
weeks
of
heavy
duty
period
how
it's
dynamic
for
many
use
cases
of
a
big
city
period.
We
would
instead
just
rely
upon
some
sort
of
upper
bound
rather
than
using,
even
if
it
even
or
drops
lower
for
the
safety,
health
and
network.
A
L
Yeah
sure
we
we
probably
can
use
our
code
to
generate
some
may
generate
some
basic
vectors.
Also
there
is
a
work.
Yes,
you
have
to
be
finished
with
just
by
5.
It's
now
been
testing
with
the
gap
and
some
like
reach
Interop
stuff.
The
dimitri
is
working
on.
I
guess
it's
going
to
finish
it
this
week.
Also
I've
made
the
write-up
about
station
condition,
detection
it's
compiled
from
the
ideas
that
previously
being
posted
by
by
proto
and
by
Danny
and
some
other
stuff
that
I've
been
thinking
about
around
and
yeah.
L
It's
like
contains
some
also
estimation
of
sizes,
so
the
indexes
and
could
useful
for
those
who
are
design
in
this
part
of
of
the
client
I'll
post
it
like
tomorrow,
I
guess,
I
need
some
to
do
some
polishing
and
there
there
is
no
much
progress
on
our
side.
These
two
weeks
s,
we
spent
some
cycles
on
merchants
teams
yeah
the
next
two
weeks
next
couple
of
weeks,
gonna
be
more
productive
thanks.
Everyone
great.
M
M
I,
don't
think
there
has
been
kind
of
too
many
changes
mostly
and
a
lot
of
kind
of
fairly
small
tweaks.
The
one
and
the
one
thing
that
continues
to
kind
of
not
be
done
not
be
done
in
fraud
groups
and
for
me,
that's
basically
just
kind
of
waiting
on
that
Israel,
the
the
phase
one
design
and
it
is
being
accepted
by
more
people.
M
One
thing
that
we
did
talk
about
is
a
blocks
containing
multiple
chunks
versus
the
ability,
the
ability
to
and
have
created,
multiple
blocks
and
once
a
lot
and
then
like.
Basically,
the
idea
there
is
to
just
collapse
the
two-dimensional
array
into
one
and
like
that's
simpler
in
some
ways,
but
it's
also
more
complex
animal,
s8a,
efficient
and
and
in
other
ways,
but
so,
but
I
think
it
does
still
look.
M
I've
been
getting
the
feeling
from
kind
of
conversations
with
other
people
in
these
two
groups
that
I
think
people
believe
more
and
more
that
data
availability
of
proofs.
Actually
they
are
something
important
and
are
not
just
a
kind
of
optional
extra
to
throw
on
and
to
throw
on
at
some
point,
like
people
are
basically
actually
afraid
of
the
possibility
that
committees
will
break
them.
That
committees
will
break
if
great
gift
rating,
maybe
skin
break,
can
cause
the
entire
chain
to
finalize
something
invalid
and
phase.
M
One
has
been
designed
to
kind
of
from
the
from
the
start,
with
phase
two
and
or
with
the
data
availability
proofs
in
mind.
So
one
of
the
reasons
well,
the
main
reason
why
blocks
have
multiple
chunks
instead
of
one
root,
is
so
that
it'd
be
that
way
it
makes
it
easier
to
and
if
combined
all
of
those
pieces
together
into
a
single
big
root,.
M
But
the
main
challenge
there
is:
we
need
to
just
make
sure
we
have
a
decent
stark
start,
friendly
hash
function
and
four
on
the
hash
function
side.
There
is
also
one
other
new
ones
which
is
basically
do
we
go
with
a
binary
field
based
hash
or
a
prime
field
based
hash,
and
if
we
go
with
a
binary
field
based
hash,
then
like
there's
no
problems
but
on
the
other
hands
they
start.
M
People
have
been
mostly
focusing
on
prime
fields
rather
rather
than
buying
a
binary
field,
so
we
risk
kind
of
being
left
out
of
infrastructure
and
on
the
prime
field
base
side.
The
challenge
is
basically
that
the
256
sides
of
a
chunk
it
doesn't
perfectly
match
up
with
any
particular
prime
modulus.
The
the
one
trick
I
came
up
with
to
try
to
alleviate
that
is
that
blocks
would
basically
come
with
a
tag
that
just
says
like
what
number
you
you
should
offset
everything
by
and
if
you
do
that.
What's.
J
M
With
high
probabilities,
you
will
be
able
to
always
find
the
tag
that
works
and
it
will
have
probability.
The
first
tag
you
randomly
choose
will
be:
it
will
be
a
tag
that
works,
so
the
idea
there
would
be
to
just
kind
of
rotate
every
week
so
that
no
no
none
of
the
weaves
fall
into
like
that
tiny
small
range.
That's
not
not
covered
by
whatever's
prime
right
slightly
blow
to
little
bitty
six
futures.
M
So
I
think
next
steps
would
be
to
kind
I
mean
one
of
them.
I
know
is
that
the
Incred
wants
the
protocol
who
wants
to
prototype
this
dark
based,
stuff
and
kind
of
see
how
actually
viable
it
is,
and
I'm
in
Asia,
bytes
per
second
sense
and
otherwise
there's
the
option
of
just
like
figuring
out
how
to
kind
of
swatting,
but
whatever
version
of
the
proof,
videos
sense
what
how
doesn't
want
to
be
it
incorrectly.
Oh.
A
M
Mean
this
is
basically
like
the
entire
reason
why
you
like,
however,
I'm
stark
friendly
hash
function
and
our
grant
thus
dark.
Where
and
all
of
these
other
kind
of
things
that
have
been
in
motion
for
over
a
year
exist
and
they've,
provided
some
where
I
know,
candidates
that
we
can
use
with
medium
confidence
right
now,
but
in
in
general,
people
like
there's
also
desire
to
be
conservative.
A
N
Yesterday
morning,
Chris
Wood
presented
the
hash
to
curve
idea
meeting.
It
was
mostly
sort
of
just
update,
I
guess
or
for
those
people
explaining
the
changes
that
have
gone
in
since
the
last
meeting,
which
I
believe
was
at
three
three,
so
that
was
people
won't
be
five.
That
explained,
and
then
some
questions
around
where
to
go
from
here
and
all
of
all
looks
very
good.
No
one
raised
any
issues
which
was
sort
of
precondition
on
making
this
a
blockchain
standard,
so
in
terms
of
the
the
hash
to
curve
it.
N
So
the
next
things
are
happening
is
the
sage
proof
of
concept
which
is
for
the
be
master,
the
most
implementation,
that's
being
used
to
generate
the
test
vectors
which
were
removed
for
B
fives
of
a
during
the
test,
vectors
back
in
making
sure
all
the
canonical
implementations
of
hash
to
curve
or
good
again,
which
are
the
ones
in
go
Russ,
let's
see
I've
ever
written,
which
should
all
happen
in
the
next
two
weeks
or
so.
But
those
aside,
there
should
be
no
surprises
there.
N
So
it's
pretty
like
we
need
to
wait
for
anything,
and
so
that
means
that
they're
going
to
move
this
on
to
gloss,
call
status
on
the
an
ITF
standpoint
and
will
be
submitted
to
the
CFO
G
for
input
on
the
cryptography.
But
again
nothing
expected
there.
That's
more
formality,
I
think
for
my
understanding
how.
A
A
N
So
much
longer,
so
that's
all
waiting
for
this
to
be
a
proper,
a
proper
standard
in
in,
in
my
view,
that's
six
months
off
or
something
okay.
So
it's
not
something
we
should
be
waiting
for
and
as
a
blockchain
standard,
these
sort
of
agreement
we
beach
from
the
he
lost
all
we
had
was
a
much
shorter
time
scale.
N
So,
basically,
after
this
meeting,
if
one
raised
anything
which
Cohen
did
so
the
with
with
the
reservation
that
nothing's
being
said,
we
haven't
had
proper
discussions
about
this
since
the
ITF
meeting
and
you
don't
have
any
like
formal
written
agreement
surface
is
a
standard
I'm
pretty
happy
to
reasonably
happy
to
declare
those
to
be
the
easier
less
not
going
going
forward
and
don't
really
expect
anything
too
change.
There's
an
additional
set
more
test
vectors,
which
is
always
a
good
thing,
so
yeah
I
think
for
the
most
cases.
N
Then
it's
fair
to
say
that
the
peer
list
thing
is
not
really
holding
us
back.
That's
for
coming
to
proper
treatment.
That's
us
in
the
standard,
but
only
no
more
after
our
next
internal
meeting,
which
is
happening,
but
even
about
two
weeks
time,
but
for
now
I
think
we
can
basically
think
of
it
as
a
standard.
N
N
There's
a
purview
and
I've
been
through
it
that
looks
that
looks
pretty
good
for
the
Trudeau's
updating
the
hash,
the
curve
to
be
five.
It
needs
some
of
the
definitions.
The
specifications
of
the
in
the
RFC
specifications
I,
don't
know
whether
we
want
to
take
those
off
and
sort
of
explain
them
again
in
pseudocode
or
Python
in
be
in
the
specs
or
not.
N
N
D
O
Have
a
few
updates,
so
zero
I
guess
is
the
different
foundation
is
kind
of
looking
for.
Someone
to
you
know
manage
the
validators
that
we're
gonna
write.
So
part
of
the
plan
is
for
part
of
the
if
the
different
foundation
holes
to
be
validating
so
we're
looking
for
someone
to
you
know,
we
will
develop
skills
with
operational
security
skills
to
help
set
up
high
high
uptime
high
resiliency
high
security
kind
of
set
up.
You
know,
potentially
multi-client
multi-cloud
essentially
been
using
the
threshold
BLS
signatures
and
provide
all
this
infrastructure
as
as
open
source.
O
O
O
Relevant
for
potentially
phase
one
I
I've
been
spending
quite
a
bit
of
my
spare
time
on
on
zero
knowledge,
proof
and
one
of
the
cool
things
that
Dan
Boneh
came
up
with
a
really
neat
secretly
their
election
mechanism
and
he
he
wrote
a
paper
and
his
paper
got
accepted,
so
he
will
be
published
very
soon
and
it
it
turns
out
that
kind
of
the
the
circuit
is
and
very
simple.
So
you
could
do
it
either
large
proof
or
you
could
do
it
as
a
foolproof
kind
of
very
similar
to
the
date
availability
situation.
O
So
there's
been
one
of
the
candidate
hash
functions
in
the
competition
that
was
broken,
the
GMC,
so
there's
kind
of
two
of
the
more
experimental
ones
that
remain
rescue
and
facade.
On
but
kind
of
the
bad
news
is
that
the
the
Crypt
analyst
in
the
in
in
the
committee,
so
there
was
a
committee
that
reviewed
these
hash
functions.
They
still
think
that
it
will
take
years
for
these
functions
to
be
very
far
away
vetted
and
for
for
us
to
have
very
high
confidence,
so
actually
won.
O
One
of
the
hash
functions
which
we
do
have
available
is
the
the
pieces
and
hash
which
is
kind
of
provably
secure
under
well
under
trusted
trust
assumptions.
So
one
of
the
things
that
would
also
be
worthwhile
is
looking
at
the
performances
both
in
the
plaintext,
because
it
is
significantly
slower
than
judge
56,
but
also
also
in
the
context
of
another.
M
Alternatives,
you
were
kind
of
hashing
backstops.
By
the
way
it
is
kind
of
bring
back
template,
multi
hashing,
so
basically
like
at
least
for
shard
blocks.
They
would
provide
both
the
regular
hash
Rouge
and
the
MC
hash
root,
or
whatever
hash
function,
route
that
we
have
and
then
you
would
have
a
fraud
proof
to
show
like
basically
that
one
doesn't
actually
doesn't
actually
lead
to
the
other
and
and
so
that
way
we
can
kind
of
benefit
from
the
data
availability
checking
keep
the
conditional
and
that
has
that
hash
function
working.
M
You
won't
be
able
to
trick
white
clients,
because
white
clients
would
ask
for
branches
that
goes
through
with
the
routes
that
go
through
the
traditional
hash.
Like
you
know,
if
the
hash
function
is
broken,
the
only
thing
you'd
be
able
to
do
I
think
is
get
away
with
unavailable
data.
If
you
can
get
a
committee
to
sign
off
on
it.
M
A
Q
Hey
what's
up
everyone,
so
we're
starting
a
phase.
Two
community
called
December
3rd,
so
I've
been
an
issue
in
the
and
the
PM
repo
and
recently
released
a
update
on
everything
up
until
this
point,
so
you
guys
are
all
interested
in
progress
and
what's
been
going
on,
definitely
recommend
you.
You
read
through
the
article.
Q
We
had
an
implementation
this
this
last
week
of
basically
a
runtime
api.
So
this
is
the
sandboxing
api
for
calling
calling
new,
wise
runtimes
and
those
functions
to
support
this
and
run
them
in
a
a
protective
manner.
So
now
we're
prototyping
a
smart
contract,
execution
environment
and
we'll
go
ahead
and
get
some
basic
smart
contracts
running
for
that
we've
been
expecting
scout
to
test
across
multiple
shards.
So
this
is.
Q
This
is
perfect
in
tandem
with
the
smart
contract
yi
and
we'll
be
able
to
start
testing
contracts
that
that
are
sharda,
where
we're
continuing
to
optimize
the
toes
knees
and
again
and
the
the
update
we
I
think
it
talked
about.
Like
six
token
EE
implementations
that
were
going
on
in
in
parallel
and
also
continuing
to
work
on
making
the
some
of
the
accumulator
implementations
more
more
performant
performance
as
well.
Q
Q
G
Yes,
if
we
can
find
the
contract
original
one
we're
a
source
on
this
script,
we
can
just
replicate
it
in
name,
see
that
we
generate
something
executable.
That
is
almost
the
same
on
this
way
we
kind
of
well,
it
would
be
a
bit
like
Viper
in
terms
of
interface
and
that
we
can
use
it
for
fish
for
testing.
Also
awesome.
Q
A
Okay,
moving
on
I
want
to
announce
them.
Let's
shall
be
aware
of.
There
are
some
new
domain
specific
calls.
I
think
the
particular
cadence
of
these
calls
is
still
TBD
likely
once
a
month
to
start,
but
might
depending
on
progress,
and
things
might
might
swap
to
be
quicker.
So
there's
the
East
one
X
there's
a
research
call
they're,
primarily
organizing
on
the
e3
search
forum.
A
So
if
you're
interested
check
that
out,
it's
pretty
much
a
provided
revitalization
of
an
effort
to
push
forward
on
some
of
the
research
on
the
existing
etherion
chain,
with
a
focus
on
getting
one
improving
theorem
today
and
also
staging
ethereum
for
the
future
upgrade
of
moving
hearing
into
to
moving
more
towards
stateless
model
and
other
things.
So,
if
you're
interested
check
that
out,
like
I,
said
they're
organizing
a
lot
on
on
the
research
forum,
we'll
announce
a
soup,
oh
I
drop
the
link
of
the
chat
and.
A
In
addition
to
that,
we're
going
to
start,
and
at
least
monthly
networking
call
where
a
member
or
two
from
each
team
I
hope
that
it
has
been
focused
primarily
on
networking.
We're
going
to
gather,
gather,
enumerate
the
problems
more
explicitly
and
work
on
driving
that
effort
a
little
bit
more
to
sleep
I'm
going
to
leave
that
call
to
start,
but
certainly
I'm
open
to
not
leaving
that
call
depending
on
who
steps
up
and
is
available.
I
will
drop
a
an
agenda
item
on
the
8th
p.m.
repo,
an
issue
that
will
set
up
this
call.
A
A
A
A
A
R
F
R
A
A
P
One
thing
that
might
be
of
interest
to
the
historic
team
is
that
we
just
converted
key
going
to
use
four
modules,
which
means
it's
actually
much
easier
to.
It
should
be
much
easier
to
actually
consume
Goethe
immersive,
tenants
now
and
I'm
looking
to
include
the
disc
if
I
code
on
the
quartermaster
branch
as
soon
as
possible,
so
I
think
that's
gonna
be
a
big
help
to
anyone
using
gold,
because
then
you
can
just
report
it.
There
are
key
from
the
upstream.
P
So
you
can
actually
set
us
up
and
then
I
guess
we'll
have
something
to
announce
there
right
after
the
after
the
for
process
and
I
think
this
is
gonna,
be
a
pretty
good
test.
Run
of
this
like
DNS
infrastructure
and
I,
think
is
probably
gonna,
be
really
nice
for
it
to
as
well
once
it
launches
possibly.
A
P
P
It's
just
that,
like
I'm,
not
really
in
contact
with
anyone,
so
it
just
all
seems
to
like
work
without
my
involvement,
which
is
very
nice,
but
at
the
same
time
there
are
research
challenges
left
for
this
protocol
and
I
also
be
really
happy
to
like
get
more
help
on
that.
Like
shouldn't.
Just
be
me,
I
think
so.
P
Yeah
I
mean
it's
nice
that
everyone
is
implementing
and
I'm
really
happy
about
that.
I
can
really
say
that,
but
it's
just
like
I
would
be
nice.
It's
like
there
was
more
involvement
in
me
on
the
open
research
questions
there.
It's
not.
There
are
not
that
many
questions
left
actually
and
they're
all
on
the
on
the
track.
First,
one
I'm
also
happy
to
have
calls
about
the
city
anytime,
yeah.
A
S
It's
like
kind
of
closely
connected
lifelines
work,
but
also
if
as
the
equation,
work
and
reduction
of
state
representation,
so
you
can
store
the
state
in
some
kind
of
miracle
store
to
serve
light
client.
So,
for
example,
all
these
kinds
of
things,
they're
blogs,
are
very
inconvenient
because
of
the
way
you
have
these
two
different
kinds
of
routes.
Let
map
to
different
tree
structures
and
a
outlined
this
in
more
detail
in
the
issue
and
I
should
are
even
more
like
edge
cases
and
things
to
consider
here.
T
Hey
also,
when
I
add
on
to
this
row
from
prismatic
labs
here,
sending
Roo
there's
a
name
is
also
can
be
a
little
bit
confusing
like
to
somebody.
That's
not
deeply
familiar
with
its
purpose
or
the
EQ
spec.
So
yeah
I
agree
that
it's
worth
revisiting
also,
it
doesn't
make
sense
that
only
something
like
to
an
external
implementer
like
why
sometimes
some
types
types,
tiny
rude
and
some
others
don't
so
there's
a
lot
that
can
be
done
to
explore
alternatives.
T
I
like
photos,
alternative
of
having
like
a
sign
block
container
and
like
also
regular
block
container-
and
he
mentioned
the
point
that
it
could
just
really
remove,
remove
a
lot
of
complexity
that
exists
regarding
like
dealing
with
latest
block
headers
and
things
like
that
in
the
state.
So
that
could
be
very
helpful.
K
S
G
S
A
Okay,
I
have
the
next
item
in
there
was
general
discussion
of
test
nuts
I
think
the
status
is
very
similar
to
two
weeks
ago.
There
is
a
the
prime
focus
for
most
clients
is
getting
public
versions
of
the
test,
nuts
out
and
or
joining
other
public
test
nuts
there's.
Obviously,
some
really
good
movement
on
that
with
prismatic
relaunched
in
their
test
net
and
with
I
know
a
couple
of
other
clients
very
near
that
oh
and
Nimbus
doing
their
weekly
builds.
A
A
M
M
M
M
M
A
M
A
Okay
I
know:
y'all
are
all
pretty
heads
down
working
on
these
things.
I
think
this
we're
also
entering
into
a
period
where
it's
very
important
to
communicate
with
the
community,
so
that
I
started
doing
those
quick
updates
but
updates,
and
your
individual
teams
on
how
to
better
understand
your
clients
again.
Vulva
test
nets
are
always
extremely
appreciated
by
the
community,
so
don't
forget
to
write.