►
From YouTube: Eth2.0 Call #30 [2019/12/19]
Description
A
A
This
ends
up
being
backwards,
compatible
with
the
previous
method
of
guess
in
check
and
fully
connecting
the
peers
to
see
if
they're
on
a
subnet.
So
I
am
going
to
release
this.
Probably
today
in
a
p09
for
the
BLS
standards,
integration
has
gone
through
a
couple
of
iterations.
There
is
a
good
PR
or
viewed.
It
looks
like
that's
going
to
be
merged
in
very
soon
into
doubt,
at
which
point
we
will
release
that
probably
first
week
of
this
I'm
not
really
waiting
on
anything,
but
certainly
by
the
first
week
of
January.
A
We
are
undergoing
pretty
comprehensive
auditor
phase
0
with
least
authority
I'll.
Do
an
official
announcement,
probably
at
some
points
a
day
and
we're
going
to
use
that
be
0.
1
0
well
be
0
10
as
the
target
for
that.
So
that's.
What's
coming
up
there,
the
I
have
continued
to
fail
to
deliver
for
choice
s
I
know
there
is
some
work,
so
go
on
my
harmony
on
that
the
guile
or
anyone
from
a
harmony
I
want
to
give
us
an
update,
ok
sure.
B
B
We
have
finished
like
become
dative
accessory
limitation
that
is
very
close
to
the
spec
and
it
handles
things
like
delay.
Data
stations,
which
were
just
queued
and
applied
later
on.
All
this
is
to
could
be
useful
for
generating
comprehensive
scenarios
for
the
fork
choice,
and
we
think
that
integration
test
approach
for
the
four
choices
very
important
thing,
because
it
could
like
find
some
issues
with
that
with
the
integration
of
the
four
choice
that
are
not
covered
by
the
spec
and
could
lead
to
slight.
B
In
different
client
implementation,
so
we
will
alexis
working
on
the
generator
is
so
far
and
when,
once
we
have
this
format
approved,
we
can
just
like
generate
more
test
vectors
and
probably
integrate
them
with
the
ice
pack
later
on
so
yeah
the
work
is
in
progress
and
we
have
some.
Some
vector
is
already
generated.
That's
that's
great
yeah.
So
that's
awesome.
Working
on
that.
Thank.
C
B
D
Absolutely
hey
everyone:
lots
of
cool
progress
the
last
few
weeks
on,
because
so
all
our
buzzers
are
now
matching
version.
9.1,
open
spec
will
be
upgrading
to
three
or
nine
point
four,
once
at
least
three
clients
have
implemented
it,
I
know
we
and
by
we
I
mean
the
lighthouse
crew
will
be
incrementally
until
to
us
or
second
week
with
Jen
I'm,
not
sure
about
the
other
genes.
D
In
other
news,
we've
integrated
pipe
and
sub
interpreters
to
allow
us
to
have
multiple,
pipe
and
interpreters
per
process,
so
we're
using
them
to
basically
keep
the
different
pipe
and
implementations
isolated
with
respect
to
their
dependencies
and
global
states,
and
it
allowed
us
to
have
trainings
on
be
competitive
in
future
to
enable
and
disable
high
spec
entry.
We've
also
integrated
Nimbus
to
a
bunch
of
different
buzzers.
D
So
a
big
thank
you
livin
in
this
crew
who
exposed
a
nice
ITC
library
for
us
to
plug
our
test
harness
to
so
we've
been
helping
out
a
few
logging
and
error
handling
purposes,
but
yeah
happy
to
announce
that
Nimbus
is
on
board
now.
So
you
can
check
out
the
add,
Nimbus
branch,
beacon
files,
repo
for
more
details
and
we're
currently
fussing
with
inverse
lighthouse
in
CR,
NT,
shuffling
the
block
processing
and
the
attestation
process
and
in
fact,
be
confessor
has
potentially
most
likely
identified.
D
Its
first
crash
in
the
cube
should
committee
help
a
function
yeah
by
the
process
attestation
for
the
in
target
due
to
failed
assertion.
So
that's
quite
exciting.
We'll
just
raise
this
with
the
Nimbus
team.
We
provided
traces,
but
we
should
be
able
to
provide
a
lot
more
relevant
information,
mostly
SSA
blobs
tomorrow.
D
We've
also
published
a
couple
of
fuzzers
on
posit,
which
is
a
cloud-based
fuzzing
as
a
service
platform.
So
mostly
doing
this
as
a
proof
of
concept
to
learn
more
about
the
platform
which
looks
quite
promising.
The
first
couple
of
fuzzers
are
essentially
free,
and
then
you
have
to
pay
a
recurring
fee.
We
did
have
to
adjust
our
build.
That
was
quite
painful,
but
we
got
there
in
the
end
and
I
get.
D
D
On
a
completely
before
front,
we've
started
looking
at
little
box
mutaters,
which
is
it's
basically
a
library
that
allows
your
lending
you
type
for
the
batteries.
So
we
can
even
use
that
in
conjunction
with
guided
buzzing
engines
such
as
elite
rasa,
that's
the
classic
engine
we're
using
for
BT
post
and
you
basically
define
our
a
probe
description
files
with
beacon,
state
and
instructive
causal
mutate,
the
specific
fields
prior
to
any
SSS
realization
or
any
hoc
state
transition.
D
So
for
those
of
you
familiar
of
how
solidity
compilers
being
fussed,
it's
extremely
similar,
not
very
identical
approach,
and
it's
a
very
much
working
work
in
progress.
So
you
can
check
out
the
LPN
branch
if
you're
interested,
but
we're
making
good
progress
on
that
front
as
well
happy
to
announce
that
personick,
also
known
as
Krypton
mental
has
joined
the
because
team
you'll
be
working
with
us,
primarily
onboarding
prism,
while
having
guarantee.
D
So
if
you
guys
recall
last
time,
I
provided
an
update,
I
shared,
so
the
challenges
we
were
facing
with
some
namespace
clashes
for
compiling
down
to
pausing
targets.
So
fresh
anak
comes
from
the
f1
fizzling
team,
so
he
had
to
deal
with
a
lot
of
similar
issues,
so
we're
very
much
looking
forward
to
his
input.
He'll
also
be
helping
this
with
closing
coverage
and
optimization
they'll.
D
Do
these
next
row
this
after
solving
namespace
questions,
they
will
have
a
blog
post
next
week
for
everyone
to
consume
that
will
detail
all
the
technical
challenges
we
face
and
the
progress
we've
made
on
beacon,
first
and
I
guess,
independently
of
beacon
trials.
We've
also
implemented
an
RPC
puzzle
for
lighthouse,
which
has
been
running
for
about
seven
eight
days
now
with
no
crashes.
So
we
can't
integrate
that
to
beacon
files,
but
I
would
definitely
encourage
all
clients
to
do
something
similar
so
feel
free
to
hit
me
up
if
you
want
the
fuzzing
target.
D
A
C
Yes,
no,
yes,
and
no
so
miss
Coco's,
built
I
can
like
deploy
as
many
different
coins
as
possible
just
running
on
a
see
if
these
stating
boots
get
fat
into
the
system.
Where
am
I
free
client,
every
consensus
machine?
You
get
all
the
looks
out
goods
registered
so
for
this
kind
of
processing.
It's
another
sense
beats
yes,
I
met,
I
met
with
the
good
gets
writer,
go
for
it,
your
clients,
with
the
failure.
A
A
C
E
Everyone
yeah
so
again
just
working
towards
test
nets,
specific
features,
so
we
merged
in
this
PR
for
our
initial
pass
at
attestation,
aggregation,
which
is
shall
ways
here
she
can
speak
more
to,
but
that
was
exciting.
A
big
one
was
merging
and
updates
to
Pius
instead,
so
essentially
how
we
handle
hash
sure
calculation
and
we
did
some
small
benchmarks,
at
least
I'll,
say
micro
benchmarks
and
saw
like
crazy
performance
speed.
So
that's
really
exciting
a
bunch
of
other
laundry
list
of
things
so,
except
for
about
our
client.
E
A
F
So
we've
been
working
to
get
minimum
viable
sync
algorithm
up
and
running
I've
been
making
good
progress
there,
we're
hoping
to
be
able
to
join
a
testament
soon
and
as
part
of
that,
we've
also
been
doing
some
refactoring
of
our
storage
layer
to
make
that
more
reliable
and
to
make
sure
that
we
can
support
the
queries.
We
need
at
the
key
layer
and
we've
also
been
continuing
to
work
on
integrating
harmonies
discovery,
v5
implementation
and
cardless.
F
G
Guys
Terence
from
Kris
Matic,
so
love
our
biggest
achievement.
Last
two
weeks
was
able
to
run
a
magnetic
config,
which
was
16,000
validators,
our
single
beacon
node
in
a
local
setup.
So
a
lot
of
optimization
was
involved,
such
as
we
optimize
our
it
one
service,
depository,
faster
assignment
from
our
PC
and
CoreLogic.
G
H
Yes,
so
on
the
core
part,
we
started
on
the
attestation
aggregation
and
we
have
PR
bursts.
We
started
working
also
on
benchmarking
tool
in
the
same
vein
as
this
year,
I
pass
it
SSE
arbitrary
SSE
state,
and
you
can
have
a
report
on
number
of
calls
or
the
time
it
took
so.
Hopefully
it
will
help
finding
potential
slowness,
even
at
suspect
level
on
the
inside.
H
We
are
starting
to
get
interested
into
how
to
manage
a
fleet
of
Nimbus
nodes
and
have
like
you
switch
reporting
and
such
looking
into
having
stack
traces
with
less
overhead,
because
it's
slowing
down
the
processing
by
a
lot
on
the
limb,
p2p
and
networking
front.
So
we
had
le
p2p
this
week
we
are
still
a
leaning
back
and
starting
from
next
week
we
will
have
mixed
liquid
to
be
demon
and
Li
p2p
pure
name
test
net.
We
had
some
UPnP
fixes
and
the
only
blocker
right
now
to
join
/
test
net
is
disc
v5.
H
We
are
now
on
zero
point.
Nine
point:
three:
mostly:
we
are
waiting
for
the
CCI
or
I
suspect
energy
states
to
make
sure
that
we
are
in
line
on
Phase
two
part.
We
have
track
who
was
working
on
Viper
in
the
past
that
is
currently
looking
into
Phase
two
for
the
e
and
maybe
on
the
language,
art
and
generating
was
on
and
side
note
on
f1.
H
So
currently
we
are
trying
to
see
if
we
can
sync
with
gas
parity
the
normal.
If
one
chain,
we
have
a
bottleneck
in
storage
and
sync
at
the
moment,
but
we
are
looking
into
it
and
we
are
started.
We
started
also
looking
to
EVM
C,
which
is
an
abstract
back-end
proposed
by
the
LF
team,
and
to
see
if
we
could
add
Nimbus
as
an
alternative.
I
came
to
EVM
C
for
the
holiday
break.
We
will
have
a
couple
of
team
members
of.
I
J
Y'all,
so
we're
still
think
some
final
touches
are
0.9
point
to
branch.
They
should
have
emerged
the
next
few
days
because
with
that
one
also
have
like
a
minimal
at
the
station
ideation
we're
working
on
SSD,
caching,
I
think,
similarly
to
which
Randy
is
doing
and
hoping
that
I
think
that's
going
to
be
really
helpful
for
us
knowing
for
our
beacon
chain,
but
I
think
it's
gonna
help
us
start
prototyping
out
like
like
client
server.
J
My
client
proof
servers
a
little
bit
better
because
our
just
our
hash
tree
root
has
been
really
slow
in
the
past.
So
we're
looking
forward
to
that
and
we
will
be
upgrading
our
lip
p2p
soon
and
refactoring
based
on
this
newer
version,
and
that
should
help
us
with
like
validating
incoming
messages,
which
we
have
not
been
doing
up
until
now.
J
It
just
like
it
took
a
pretty
major
refactor
I.
Think
I
mentioned
it
maybe
a
few
meetings
ago,
but
they
just
kind
of
moved
from,
like
the
old,
an
older
style
of
JavaScript
to
a
newer
style
and
a
lot
of
the
api's
changed,
and
it's
just
a
little
more
a
little
more
friendly
to
use
and
we're
gonna
be
there's
gonna,
be
using
it
a
little
bit
differently.
So
cool.
K
Hello,
so
we
started
I
guess
last
week,
a
week
before
we
started
I
made
that
16k
validated
test
that
it
ran
for
about
a
week.
It
had
four
nodes
on
it.
It's
quite
small
nodes
on
AWS
each
running,
4k,
validators
totem
ended
up
in
a
loop
with
it.
It's
a
station
publishing
receiving
over
gossip
sub
loop.
This
race
exhausted
the
resources
of
two
of
them
which
took
50%
evaluators
out,
and
then
we
stopped
seeing
finality.
K
So
we
managed
to
recover
it
after
the
first
outage
of
100
epochs,
without
finality
by
just
doubling
the
disks
and
basically
control-c
and
up
enter
again
and
even
some
nodes
that
had
larger
disk
managers
survived
through
the
down
time.
We
come
out
the
other
side
following
the
head,
which
was
pretty
cool,
and
so
after
that,
a
couple
of
days
later
it
got
into
the
same
thing
and
went
down.
So
we
just
kind
of
let
it
die
because
we
figure
we
should
probably
fix
the
bugs,
as
opposed
to
just
this
I've
been
around
them.
K
K
We
also
learn
an
interesting
lesson
which
might
be
useful
for
other
people
that
we
were
storing
our
state's
before
our
blocks,
which
meant
that
if
you
kill
mind
it
when
it
was
storing
the
state,
you
would
have
this
dangling
pointer
of
the
blocked
State
Route,
pointing
to
a
state-
that's
not
stored.
So
this
made
us
realize
that
database
wasn't
consistent.
So
we
just
swapped
them
around.
We've
added
a
fix
to
our
f1
cases,
because
we
previously
relied
upon
an
archive
node.
K
So
now
we
get
all
our
deposit
route
deposit
counts
from
the
logs,
not
from
the
contract
calls
because
I
think
those
will
prune
away
old
contract
state.
We
made
some
API
upgrades
that
allowed
the
fo
chain,
beacon
ji
n
bit
flight
team
I'm
to
launch
a
POC
Explorer
for
lighthouse.
We've
also
added
a
bunch
of
stuff
that
you
know
the
community
suggested
ages
been
busy
in
the
networking
side.
K
He's
updated,
rust,
gossip
sub
for
content,
content,
addressed
messages
he's
in
the
process
of
merging
bosses
up
down
into
the
main
roster
p2p
library,
and
he
started
implementing
the
naive
attestation
aggregation
strategy.
So
I
think
we're
gonna
launched
a
new
test
net
tomorrow
and
make
it
public
next
week.
If
all
goes
well,
this
time
we're
gonna
have
more
validator
nose
and
dedicated
boot
nodes
so
that
we
can
maybe
a
little
bit
more
resilient
and
we're
also
hiring
Ross
developers
so
check
out
at
Twitter.
If
you
want
to
link
to
that.
A
K
I'm
not
sure
that
age
was
able
to
fully
identify
what
the
the
cause
of
the
loop
was.
We
can
add
some
more
logging,
so
hopefully,
then
we'll
know
exactly
what
it
was.
We
basically
put
in
a
bunch
of
fixes
to
stop
it
from
happening.
I
think
the
content
address
matter
just
helps,
but
yeah
that's
kind
of
ages.
Domain
I
haven't
been
in
there,
so
I'd
be
speaking
out
of
turn.
A
K
K
A
L
Yes,
oh
so,
for
also,
we
are
mostly
still
testing
against
a
test
net
against
first
magic,
so
trying
to
fix
some
syncing
issues
like
is
currently
a
little
bit
slow.
So
we
try
to
make
sure
the
connection
doesn't
drop
that
often
so
we
can
sink
faster
and
trying
to
get
into
the
discovery
protocol
with
horse
Matic
using
the
cat
cat
Malia
yeah.
So
that's,
basically
what
we're
doing
and
I
think
the
go
is
to
try
to
catch
into
as
many
ties
net
as
possible.
So
we
can
have
some
yeah.
N
N
N
Good
question,
though,
so,
with
with
one
option,
is
some
sort
of
interrupt
with
the
lib
p2p
existing
integration.
The
averages
are
I,
don't
know
which
parts
are
being
used,
but
there's
a
library
appear
talk
which
is
another
like
library
of
different
p2p,
algorithms,
same
sort
of
Heritage's
as
Lib
PDP
and
the
guy.
N
I
Can
add
here
so
I
was
I
was
analyzing
different
approaches,
I
think
the
main
thing
will
be
a
possibility
to
look
at
the
and
the
existing
IPF
fast.
Are
they
p2p
implementation
in
doctor,
but
it's
more
like
4050
percent
done
and
it
was
developed
probably
like
actively
one
or
two
years
ago.
So
this
is
something
to
explore
for
us.
I
H
I
Great
news
so
I
think
we
can
track
the
message,
messages
roll,
maybe
unless
they
encrypted
probably
encrypted.
But
then
it
will
be
this
thing
that
we'll
start
with
for
sure.
So
the
first
first
stages
phase
zero
will
be
on
this
go
demon
and,
in
the
meantime,
we'll
be
implementing
quickly
to
pay
for
Delta,
but
it
all
depends
on
like
whether
we
were
if
the
resources
or
the
Gogi
moon
will
be
enough.
A
A
B
Yeah
we
are
currently
working
on
these
for
choice
staff.
Also
anton
made
a
couple
more
of
simulations
and
yeah.
You
can
find
his
write-up
in
the
notes
to
networking
call
to
the
yesterday's
call.
Also
mitri
is
working
on
basically
five
simulation.
He
tried
to
evaluate
it,
dentistry
simulator
and
it's
like
it's
been
announced
in
the
documentation
of
NS
three
that
it
supports
python,
but
it
it
doesn't
support.
B
It
doesn't
have
a
good
support
for
fight
and,
for
example,
you
can
just
create
your
own
application
like
I,
know,
disco
fire
stack
and
evaluate
it
within
industry,
and
probably
you
will
fall
back
to
Anton's
too
similar
as
a
dental
health
as
grafted,
and
also
why
else
I've
been
accidentally
reviewing
navy
corrugation
attestation
found
a
couple
of
issues
filed
them.
So
that's
that's
it
so
far.
A
O
Sure
so
we
did
some
people
from
Artemis
and
the
harmony
team
are
emerging
and
focusing
on
phase
two
phase.
One
research
now
we're
starting
January
6
will
be
all
together,
but
we're
kind
of
starting
now
a
little
bit.
I
think
and
Anton
is
working
on
disc
v5
simulation,
no
real
updates
yet
and
I
think
the
real
premise
of
what
we're
doing
is
trying
to
increase
the
amount
of
people
who
were
working
on
the
research.
After
that.
J
It
feels
in
the
main
kind
of
to
research
areas.
Right
now
it
seemed
to
be
a
new
one
is
just
figuring
out
the
right
short-term
data
availability
scheme.
I
think
the
main
update
from
the
kind
of
chats
we've
had
with
starter
and
other
people
recently
is
that
the
idea
of
starting
a
merkel
root.
It
does
seem
like
the
best,
a
long-term
approach,
but
it
depends
on
having
us
dark
friendly,
a
hash
function
that
we
can
fully
rely
on,
and
that's
not
going
to
come
for
some
amount
of
time.
J
J
The
problem
set
up
is
basically
that
the
with
the
kind
of
minimalistic
structure
for
how
the
east
to
begin
chain
will
work.
The
like
cross,
shard
messages
are
under
purely
a
higher
level
concept.
Right,
like
the
base
protocol
doesn't
know
about
them.
It's
just
a
bunch
of
moral
proofs
and
code,
verifying
other
merkel
proofs,
and
if
the
base
protocol
doesn't
really
even
know
that
any
of
this
stuff
is
happening.
J
It's
just
entirely
this
higher-level
thing,
but
the
problem
is
that
keep
like
ether
the
currency
can't
be
an
entirely
higher
level,
because
people
need
to
be
able
to
use
ether.
The
currency
to
pay
transaction
fees
and
transaction
fees
have
to
be
legible
by
block
producers,
and
people
want
the
ability
to
be
able
to
and
have
transfer
use
from,
one
shard
to
another
chart,
and
this
these
transfers
need
to
be
ideally
and
have
complete
about
within
once
a
lot,
because
that's
what
we
wants
to
be
want
to
be
able
to
achieve
anyway
and
the
challenge.
J
So
the
challenge,
basically,
is
that
we
need
some
means
of
transferring
if
it's
meeting
execution,
environments
and
I
have
between
one
shard
and
another
shard
such
that
this
mechanism
is
also
understandable
by
block
producers.
So
it's
kind
of
at
least
semi
enshrined
in
some
sense
and
there's
two
major
categories
of
solution
to
this.
J
Can
you
send
a
and
of
crush
our
message
to
shard
via
and
then
the
protocol
itself
kind
of
guarantee
is
in
some
way
that
the
that
cross,
shard
message
gets
received
by
shard
B
and
then
gets
X
and
then
gets
executed
by
ship,
but
by
shard,
B
and
there's
kind
of
key
and
gas
mechanics
figure
it
out
to
to
make
sure
that
this
kind
of
thing
doesn't
kind
of
add
protocol
level
to
make
sure
that
this
doesn't
lead
to
like
DOS
or
attack
vectors.
Anything
like
that.
Q
J
So
if
we
go
that
route,
then
basically,
and
though
there
needs
to
be
so-
let's
say:
I
have
a
transaction
in
some
other
X
in
some
random
execution.
Environments
and
I
have
some
each
from
that
execution
environment
which
basically
meet
so
and
we'll
just
call
these
execution
environments
with
name
starting
with
E
I,
don't
know.
I'd,
say:
I
have
some
ethnic
in
execution,
environment,
Eddie
and
I
once
to
send
it.
J
And
so
and
potentially
it
gets
hard
to
verify
how
many
of
these
execution
vibrates
we
trustworthy,
whether
or
not
their
ethos
kind
of
backed
by
actual
years.
So
the
challenge
would
be
so.
The
way
to
do
it
would
be
that
that
each
kind
of
actually
gets
held
in
some
under
lot.
Some
special
execution
environments
that
block
through
we'll
call
it
the
the
ether
environment
that
block
producers
are
required
to
understand.
J
You
know,
at
the
same
time,
there
would
be
kind
of
one
other
receipt
that
includes
in
all
of
these
different
eath
transfers
and
that
other
receipt
would
be
that
other
receipt
would
kind
of
go
over
a
shard
B
and
that
receipt
would
prove
that
the
actual
underlying
ether
got
moved
from
Sharon
a
to
shard
B
and
then
that
and
then
on
shard
B.
When
you
have
a
transaction
get
executed,
then
that
eath
would
actually
need
to
get
mu
transferred
to
the
Block
proposer
as
part
of
the
execution
so
like.
J
Q
A
P
Ok
cool,
so
these
two
call
coming
mid-january,
we'll
give
a
date
here
and
bet
that
one
will
most
likely
focus
on
discussions
around
crush
our
transactions.
Some
of
the
things
that
our
Luck's
been
talking
about
and
likely
the
fee
market
I
think
are
probably
the
the
two
hot
topics.
So
the
goal
during
that
call
is
to
really
hyper
focus
and
use
it
as
the
brainstorming
productive
session.
P
Some
stuff
that
quill
has
been
up
to.
We
are
continued,
doing
continue
to
work
on
tooling
for
the
contract
EE
to
run
so
we
can
have
that
running
and
and-
and
we
can
play
with
that
across
shards-
so
we're
trying
to
set
up
a
kind
of
a
clan
to
make
the
tooling
to
build
these
E's
more
kind
of
truffle
like
so
it's
a
lot
easier
for
other
people
to
dive
in.
P
So
that's
some
things
that
we've
been
doing
and
then
we
also
need
to
make
it
quicker,
because
there
are
a
lot
of
right
now,
things
that
are
slow
to
even
you
know,
run
this
contract
ee,
so
we're
kind
of
bottlenecked
by
our
tooling
right
now.
So
we're
working
on
that
we
are
releasing
a
first
chapter,
this
e
to
resource
or
book.
So
super
excited
about
this.
The
draft
is
done.
We
have
an
outline.
P
The
first
chapter,
I,
think,
is
really
really
good
actually,
and
so
the
whole
point
of
this
I
think
actually,
maybe
just
wait-
will
likely
release
it
next
week
or
maybe
the
week
after,
since
that's
holidays
and
I.
Think
people
are
gonna,
be
really
excited
about
this.
So,
let's
all
say:
for
now,
we
have
stepped
up
involvement
on
some
of
the
state
provider,
relayer
questions.
So
one
of
the
things
that
I've
been
talking
about,
one
of
the
big
differences
in
the
two
is
that
block
producers
don't
have
the
state.
Where
is
the
eath?
P
One
X
group
is
doing
research
around
the
premise
that
block
producers
are
minors
and
youth.
One
have
states
that's
a
huge
difference
between
some
of
the
challenges
that
we
have,
and
so,
when
we
look
at
the
fee
market,
everything
unto
end
that
actually
has
a
significant
impact
on
everything,
so
Sam
and
on
Skaar
are
putting
up
a
write
up
soon
of
different
directions
that
we
think
that
this
can
go
in
we're
hoping
that
people,
you
know
Danny
guitar,
like
other
people,
will
kind
of
help
but
help
make
a
decision
on
direction.
P
So
there's
kind
of
different
routes
that
we're
thinking
there
so
stay
tuned.
There
should
be
right
up
underneath
research
there
soon,
let's
see
cross
our
transaction,
so
I've
started
going
in
on
this
I'm,
specifically
starting
off
by
looking
at
eath
one
data
right
now
trying
to
bloat
that
evaluate
that
kind
of
hyper
focus
on
four
of
the
main
contracts,
and
one
of
the
goals
is
to
look
at
what
can
be
parallelized
right
now.
You
know
what
practices
for
writing
contracts
needs,
one.
P
How,
though,
that
wouldn't
necessarily
work
in
the
eath
2
world
and
then
see
how?
How
would
we
write
those
differently?
How
would
we
make
that
work?
How
can
we
reduce
pressure,
overhead,
etc,
etc?
So
I'm,
hoping
to
me
this
is
kind
of
a
three-month
style
project
that
should
result
in
a
really
really
good
write-up
on.
So
that's
that's
been
started.
P
Let's
see
also
figured
out
collaboration
with
tx/rx,
so
super
excited
that
you
know
these
guys
are
joining
it
on
research
efforts,
oh
yeah,
and
pretty
excited
to
club
with
these
with
this
group
as
well.
So
I
think
this
will
move
things
quicker
and
I
think
overall,
this
is
just
really
good
for
youth
to
that's
all
from
quote.
J
A
R
D
J
O
This
is
quick
update
for
pxrx
all
say:
we're
we're
starting
to
kind
of
like
narrow
or
research
topics
that
happens
to
be
one
of
them
and
we're
gonna
do
a
workshop
outside
Stanford
blockchain
conference.
If
people
are
around
for
that,
just
like
we
did
last
year
this
time
in
particular,
focusing
on
phase
two.
S
Just
a
quick,
not
from
my
site,
we
are
organizing
an
event
next
year
in
May
is
ETH.
Barcelona
is
a
short
event.
The
first
time
organized
this
one.
So
it's
short
event
is
a
one-day
event
and
we
hope
to
have
it
would
be
good
to
have
some
of
the
teams
working
on
eight-point
2.0
may
be
presenting
some
of
their
updates
at
this
audit
event.
So
are
we
having
the
link
the
current
website?
S
R
R
So
you
can,
you
can
do
polynomial
commitments
without
any
FFTs,
and
this
is
what
makes
the
this
Knox
suboptimal
for
the
approver.
But
then
you
still
have
you
still
to
come
up
with
a
new
way
to
design
and
IOP
without
the
50s
and
I
think
that
I
have
an
IEP
now
that
has
an
optimal
prover,
but
the
trade-off
is
that
the
verifier
is
no
longer
optimal.
So
basically,
we
flipped
the
optimality
on
the
program.
Verifier
health.
R
J
Yeah
I
just
wanted
to
kind
of
throw
in
there
is
this
kind
of
general
question
I
keep
having
on
general
is
your
knowledge
groups,
which
is
that
I
just
keep
failing
to
get
a
good
answer
for?
Why,
like
any
sub
linear
scheme,
cants
just
become
a
become
a
constant
verifier
ski
invited
by
just
like
we're,
basically
rehearsing
it
over
itself
and
like
I
people,
tell
me
things
about
kind
of
soundness.
Breaking
because
of
this,
like
intuitively.
J
That
doesn't
make
sense
to
me
right,
because
a
proof
that
says
either
statement
X
is
true,
or
these
assumptions
are
broken,
is
the
same
thing
as
a
proof
that
says
either
either
a
proof
of
access
true
or
these
assumptions
of
bookid,
where
these
assumptions
are
broken
like
from
a
first-order
or
even
a
logic,
point
of
view.
They
just
collapse
into
the
same
thing.
So
you.
A
T
R
Impression
is
that
it's
not
the
soundness.
That
is
the
issue.
It's
the
knowledge
soundness,
so
the
extract
ability
of
the
of
the
witnesses
and
apparently
I
think
it's
like.
The
argument
is
basically
that
the
extract
ability
kind
of
the
difficulty
to
extract
kind
of
grows
exponentially
with
every
layer
of
recursion,
and
so
you
need
to
be
very
careful
in
the
safety
proofs.
That's
my
understanding,
but
there's
another
problem
with
this
recursion
is
that
it,
but
you
need
to
really
happy
handed
machinery
like
cycles
of
elliptic,
curves
and
right.
T
A
Great
I
have
an
item
here
highlights
from
the
client
survey.
I
haven't
had
a
chance
to
go
through
these.
Thank
you
all
for
submitting
them.
One
of
the
things
that
I
did
see
in
a
very
cursory
look
is
that
we
still
need
to
get
noise
of
TPP
and
plantations
going
I
think
some
of
this
is
due
to
some
uncertainty
and
it's
just
probably
prioritizing
so
what
other
than
that
I,
really
myself
proto
and
he
smothers
we
got
to
dig
out
and
see
see.
What's
there,
it's
just
for
mating
a
planning.
A
This
is
for
aiding
and
like
figuring
out
where
maybe
we
can
help
or
others
from
helping
resources.
If
there's
some
clear
bottlenecks
and
things
like
that,
I
really
appreciate
it.
The
initial
look:
it's
a
lot
of
bloody
good
time
for
their
other
thoughts
on
this
things
that
came
up
that
we're
concerning
about.
It
thinks
that
I
miss
things
that
we
miss.
A
Okay,
networking,
the
bulk
of
this
conversation,
has
moved
to
a
networking
call
which
we've
done
to
this
month.
They've
been
very
productive.
We'll
probably
do
one
in
the
second
week
of
January
dens
notes
are
posted
in
the
agenda.
The
other
questions,
thoughts
updates
on
networking
that
weren't
necessarily
covered
in
that
call,
or
we
were
into
this.
A
K
K
K
Even
if
you,
if
you
like
that,
there
are
points
like
at
the
start
of
the
voting
period,
where,
if
you
don't
have
an
immediate
connection
to
the
f1
chain,
your
ability
to
vote
is
impaired,
not
massively
but
somewhat,
but
with
the
thing
that
I
proposed,
you
can
basically
not
talk
to
an
f1
node
for
less
than
the
follow
distance
and
you'll
be
fine.
I
think
clients
will
find
this
is
much
much
easier
to
implement.
A
K
A
K
So
the
next
thing
I
wanted
to
talk
about
was
how
we
have
to
wait
for
Genesis.
So
when
your
the
deposit
contracts
launch,
we
have
this
period
where
we're
waiting
for
either
me
in
Genesis
time
or
the
right
number
of
validators
to
start.
So
this
is
critical.
We've
implemented
it,
but
it's
kind
of
it's
annoying.
A
few
aspects.
One
is
that
it
adds
a
whole
new
application
states,
your
beacon
to
your
beacon
node.
So
you
have
to
have
this
period.
Where
you
don't
know
what
Genesis
is
you?
Don't
you
can't
have
a
beacon
chain?
K
K
K
A
K
Well,
I
guess:
the
action
item
would
be
that
I
get
that.
So
the
clients
would
perhaps
think
about
this
and
then
all
agree
that
you
know
we
don't.
We
don't
want
to
implement
this,
it's
waiting
for
Genesis
thing
and
then
we
would
perhaps
agree
that
I,
like
the
if
you're
in
foundation,
is
going
to
do
it
or
maybe
like
one
or
two
clients
are
going
to
do
it.
Yeah
I'm,
not
sure
it's
it's
like
it's
not
imperative,
but
it's
one
less
thing
that
we
have
to
do
before.
K
A
U
K
Yeah,
that's
right
like
it's.
It's
mainly
like
a
kind
of
an
agreement
that
it's
not
expected
of
the
earth
to
clients
to
have
to
implement
this
thing
that
there
is
going
to
be
like
it
I
think
ultimately
like
if
all
the
clients
won't
agree
that
they're
going
to
do
it
it.
It
probably
has
to
be
someone
like
the
etherion
foundation
that
produces
the
script
that
produces
the
genesis
state,
otherwise
it
together
it
we
like,
if
only
one
client
you
know,
writes
this
script
and
we're
kind
of
just
trusting
one
client
with
it.
I'm.