►
From YouTube: Eth2.0 Call #38 [2020/4/23]
Description
A
Well,
streams
should
be
transitioning
over
if
there's
anyone
that
is
watching
the
stream.
Let
me
know
yes
cool,
so
there's
the
agenda
generally
similar
structure
most
surprises
here
month,
I
know.
After
talking
with
couple
client
teams,
there
was
some
confusion
here.
I
alluded
to
a
little
bit
in
some
of
these
calls,
but
we
I'll
be
very
clear
right
now,
so.
A
It
is
time
and
a
free
kept
suggesting.
It
is
time
that
our
versions
have
her
a
little
bit
more
meaningful.
So
anything
under
these
0:11
set
for
that
b.
0
11
0,
which
had
a
bug
and
we
fix
very
quickly,
will
be
backwards
compatible.
We
have
a
v
0
11
to
under
final
review
right
now
to
be
released.
Probably
today.
This
is
not
gossip
conditions
to
be
on
her
new
epoch
basis
and
instead
of
up
her
slot
basis.
A
If
two
clients
were
on
kind
of
these
disparate
degenerate
cases,
those
are
still
interoperable,
so
check
it
out.
It's
PR
under
review
that
will
be
released
today.
If
anything
else,
any
minor
things
come
through
that
are
backwards
compatible.
They
can
continue
to
be
released
under
B
0
V
0
12
is
coming.
U
0.
12
is
slotted
slated
for
our.
A
The
user
12
is
slated
for
the
ITF
and
GLS
standard
being
updated
to
the
next
draft.
There's
a
draft
7
of
the
hashed
curve
that
is
supposedly
eminent
along
with
that.
There
is
a
couple
of
type
fixes
which
I
think
would
ultimately
be
non
substitue
to
you
and
are
just
fix
things
not
all
enter,
and
it
looks
like
there
is
a
additional
validation
addition
being
added
to
the
for
choice:
Thank
You,
a
DITA
based
on
some
of
the
old
conversations
and
issues
that
were
picked
up
and
as
a
fix.
A
A
These
0
11
test
Nets
are
still
very
important
today
for
doing
Oliver
Interop
testing
for
potentially
getting
some
users
on
them
like
the
topes,
but
ultimately,
whatever
ends
up
being
a
a
long
term
persisted
multi-client
test
net.
Not
some
of
the
test
sets
that
we're
spending
up
today
will
have
to
target
this
new
ITF
standard.
A
A
Rewards
and
penalties
tests,
so
debugging
lighthouse
and
prison
wee
hours
of
morning.
For
me,
I
wasn't
up
but
normal
hours
for
Australia
there
was
a
another
rewards.
Penalties
bug
found
it's
currently
on
the
towpath
test
net
and
if
you
were
part
of
Interop
of
canada,
this
is
a
surprise.
It's
we're,
like
90%
of
our
bugs
lied
when
we
try
to
get
clients
to
pair.
A
So
in
light
of
that,
proto
and
I
are
working
on
a
proposal
to
reformat
that
function
in
two
different
sub
functions:
to
be
able
to
test
things
a
lot
more
granularly
right
now,
it's
difficult
for
us
to
write
tests
because
there's
a
lot
of
moving
parts
within
that
single
within
that
single
function,
and
so
it's
difficult
to
even
make
sure
that
you're
testing
and
rigging
the
right
things.
Honestly,
the
bug
that
we
saw.
I
was
a
little
bit
surprised
because
I
thought
that
we
had
it
tested,
so
that
is
something
probably
the
next
24
hours.
A
A
A
C
So
we,
you
know,
work
with.
We
think
we're
gonna
run,
topaz
least
for
fern.
For
now
to
consist
out
some
of
these
issues.
We
have
like
with
memory,
usage
and
kind
of
profiling
with
a
lot
of
activity
on
0.11,
and
we
know
already
that
we
have
to
restart
for
0.12
right
because
there's
a
like
a
BLS
change
yeah.
So
so
that
will
be
our
plan
restart
for
topaz.
A
So
it
would
be
a
non
substance,
a
change
and
would
totally
be
backwards
compatible,
and
you
actually
wouldn't
have
to
necessarily
change
any
your
client
other
than
the
the
testing
harness.
So
it
might.
I
did
I
mentioned
that
it
would
certainly
be
out
by
v-0
12,
but
this
might
be
something
we
might
have.
A
testing
update
come
actually
just
next
week
on
the
b
0
11
to
update
that
testing,
harness
cool.
D
A
E
And
I
just
wanted
to
note
that,
although
it's
a
critical
book,
it
doesn't
really
affect
users
directly,
look
I
mean
so
what's
happening
here.
Is
that
if
in
the
attestation
belt,
you
can
get
slightly
different
three
words
right
now.
There's
this
mistake:
where
month,
I
defaults
gets
the
context
of
another
type
of
fault,
and
so,
unless
she
starts
look
really
deep
into
the
finishing
you
know,
moms
really
know
this
is
a
user
and
right
now
it
effectively
means
the
Reavers
aren't
just
slightly
higher
than
they
should
be.
E
A
A
E
I
could
get
the
shorter
plants
so,
along
with
the
spec
changes.
So
if
recognized
along
with
respect
changes,
I
hope
tell
it's
rumored
to
include
these
new
functionalities
as
the
new
RPC
types
and
whatnot.
So
clients
can
start
testing
using
that
functionality
right
now,
but
for
Network
tests
us
like
the
spectres,
we
change
the
direction
there,
a
little
bit,
I've
seen
actively
instrumenting
and
six
seven
eight
different
clients
is
not
going
to
work
short
term.
E
E
Have
a
client
started
the
client
instruments,
the
clients,
if
variety
in
read
private
key
for
the
network
identity.
The
right
feature
sets
at
once
and
then
the
network,
the
script.
So
when
the
actual
test,
so
those
two
big
fighting
tests
and
looking
at
all
this
network,
behavior
enough
that
we
try
and
manage
these
responsibilities
between
clients
and
testing
infrastructure
better.
G
G
Chuckling
proto
has
already
fixed
I'm,
not
sure
this
was
mentioned
last
time
that
we
also
found
the
very,
very
interesting
and
critical
bug
in
our
as
I
said
as
a
visualization
on
my
house.
By
the
way
we
published
a
blog
post.
So
if
you've
got
a
blog
that
cpio
top
post,
it's
got
a
lot
of
details
around
around
that
bug.
G
I
just
want
to
talk
about
the
fact
that
a
lot
of
implementations
out
there
are
treating
beacon,
States,
there's
trusted
structures.
This
is
quite
risky
if
we
are
potentially
moving
to
a
version
of
warp
sync
for
each
two,
so
sinking
by
B
States
and
not
just
block
patches,
so
yeah.
There's
a
lot
of
we've
had
conversation
around
overflow
and
underflow,
so
the
spec
has
been
clarified,
which
is
good.
Now,
state
transiting,
multiple
fuzzing
engines,
including
home
class,
will
be
leveraging
our
structural
fuzzing
effort.
G
We
currently
have
a
PR
in
the
works
to
do
this,
a
lot
house
and
we'll
be
using
the
generated
samples
in
the
differential
differential
processor.
So
we're
going
to
document
all
this
in
a
nice
design
book
that
will
be
shared
with
everyone,
hopefully
sometime
next
week
and
we're
looking
forward
to
community
feedback
and
that's
it
great.
H
Hey
so
past
few
weeks
we've
been
mainly
working
on
getting
to
spec
spec
compliance,
so
we've
were
mostly
up-to-date
with
0.11
we're
passing
the
0.11
spec
tests.
The
two
notable
gaps
are
snappy
compression
request
response
and
a
few
eonar
things.
I,
don't
think
we
have
the
eath
to
DNR
flag.
Yet
so
we're
working
through
that
and
we're
also
gonna,
be
fixing
up
our
CLI
to
make
it
a
little
easier
to
run
lodestar
yeah.
A
A
I
Hey
guys,
parents
from
Chris
Matthew
labs,
so
we
launched
our
hope
as
test.
Ned
attorney
has
21,000
validators
with
3000
Andy
and
right
now
we're
about
40,000
slots
since
Genesis,
which
was
last
Friday.
We
had
to
skip
one
penalty
yet,
except
for
one
incident
and
if
I
am
fixed
and
life
and
and
like
what
was
announced
earlier,
we
were
able
to
sync
with
my
house
until
the
first
epoch,
you'll
find
a
consensus
part
of
our
imitation
due
to
number
due
to
a
number
overflow.
I
D
Okay,
that's
me
so
our
JVM
Lib
p2p
noise
implementation
is
now
interoperable
with
lighthouse
from
what
I
understand
that
go.
Implementation
needs
some
upstream
fixes,
but
then
we
should
be
able
to
fully
interoperate
with
prism.
After
that
using
noise
we've
implemented
some
optimizations,
so
one
is
batch
verification
signatures
within
blocks.
This
gives
a
modest
but
worthwhile
speed
up.
The
proto
array
for
choice
algorithm
is
implemented
and
has
been
tested
using
Alex
Russell's
fork:
choice
tests,
we've
also
reworked
our
hot
state
management
in
order
to
keep
all
of
the
hot
state
completely
in
memory.
D
So
on
restarts
we
regenerate
it
by
replaying
blocks
on
to
the
last
finalized
state.
This
has
improved
our
sync
speed
by
a
factor
of
three
or
so,
and
our
current
focus
in
the
current
sprint
is
finishing
up
all
the
network
changes
for
V
zero
point.
Eleven
the
state
transition
is
up-to-date.
That's
all
from
techie
great
sounds.
J
You
guys
so
not
yet
it
still
requires
some
some
fixing
on,
but
under
the
p2p
side
the
problem
has
to
do
with
simultaneous
handshakes
and
basically
litigated
Peters
and
doesn't
really
handle,
who
should
be
the
initiator
of
the
handshake.
So
that's
still
pending
resolution
we're
still
just
supporting
sekai
o.
Ideally
once
it's
fixed,
we
were
just
update
to
noise
and
allow
the
fallback
to
happen
correctly.
Cool.
A
K
Everyone
steady
progress
on
a
be
0
xi
s
net,
there's
a
lot
of
lateral
change
going
on
with
the
client
right
now
as
this,
whichever
judgment,
concurrency
framework
and
python,
but
still
some
progress
towards
test
nuts
internal
changes
to
the
for
quois.
Some
ops
work
we've
been
doing
on
our
team
for
running
Trinity
test
notes
and
we
also
got
an
updated
BLS
binding
over
Milagro
thanks
to
chain.
B
B
We
have
some
performance
improvements
to
do
in
particular,
or
processing
is
dominated
by
harsh
reroute,
and
we
know
that
we
have
a
lot
of
repeated
harsh
reroute
that
we
can
skip.
So
some
focus
is
on
that
and
we
also
have
stack
overflows,
probably
one
that
was
detected
by
become
first
another
thing,
and
that
is
that
currently
we
use
this
update
and
rewind
rewind
States
to
apply
two
new
blocks.
B
Two
vowels
I
think
lighthouse
uses
that
use
that
at
least
three
months
ago
as
well,
but
we
are
concerned
now
about
it
being
a
potential
dose
vector
if
some
blocks
or
attestation
are
crafted
to
make
us
spend
lots
of
time
processing
those
on
the
networking
site.
We
have
improved
or
syncing
algorithm.
Now
we
have
more
reliable
thinking
and
we
are,
we
spent
the
past
weeks,
also
debugging
discovery
and
the
p2p
in
particular.
We
had
memory
leaks
some
solved
and
we
have
at
least
another
one
to
track
down
to
prepare
for
auditing.
B
We
are
removing
stale
code
and
we
are
improving
the
handling
of
errors
in
all
our
four
libraries,
the
p2p,
cryptography
and
name
become
Jana's
work
and
on
the
interrupt
site
we
fixed
the
bug
that
led
to
different
Genesis
between
Nimbus
and
lighthouse,
something
that
we
talked
about
two
weeks
ago.
We
have
discovery
between
lighthouse
and
Nimbus
working,
but
we
cannot
talk
yet
and
we
also
try
to
run
prism
locally,
and
this
part
is
still
work-in-progress.
F
Just
regarding
money
talking
about
the
database
thing
we
do
do
that
week.
We
call
it's
fast
storage,
so
you
store
it's
kind
of
configurable
you.
You
know
you
store
a
full
state
on,
say
every
epoch
boundary
and
then
you
replay
box
to
get
the
ones
in
the
middle.
Something
we've
done
is
that
we
we
make
the
assumption
that
any
block
in
our
database
has
signatures
verified.
So
when
we're
replaying
blocks,
we
need
to
verify
signatures.
F
So
that
saves
a
little
bit
of
time
a
lot
of
time
really,
but
we
also,
we
flattened
out
the
the
state
routes.
So
it's
another
point
is
we
only
do
it
in
the
cold
section?
So
we
only
do
it
in
the
finalized
area
and
in
the
hot
section
we
keep
all
of
the
states
there
in
the
finalized
section,
because
it's
finalized,
we
flatten
out
all
the
state
routes
into
their
own
kind
of
key.
So
when
we're
replaying
box
onto
there,
where
we're
not
actually
doing
state
routes,
we
already
know
what
the
state
return
to.
F
Getting
into
update
we've
launched
to
test
nets
in
the
last
week,
four
thousand
validated
test
that
and
a
sixteen
thousand
validator
test
that
they're
not
a
hundred
sent
to
be
eleven
spec,
yet
we're
still
kind
of
stress,
testing
and
testing
out
deployment
infrastructure
and
against
bugs
we're
hoping
that
we
can
launch
a
long-lasting
16k
test
that
next
week.
But
we
don't
want
to
do
that
prematurely.
F
We've
motion
this
long-running
be
zero
point,
two
point:
zero
branch,
so
we
had
that
people
are
getting
frustrated
with
ourselves
and
other
people.
So
that's
now
in
master,
so
master
is
now
version.
11.10,
stew,
full
compact
for
version,
zero
point:
one
point:
one
we've
raised
several
PRS
and
the
network
expect
over
the
last
couple
of
weeks
to
kind
of
address
things
in
caches
and
stuff,
like
this
I've
spent
a
fair
bit
of
time
learning
and
using
ansible
to
automate
our
test.
That's
it's
pretty
cool,
so
it's
I
think
it's
like
just
SSH
automation!
There's!
No!
F
You
know
software
to
install
for
it
just
SSH
boxes
and
you
define
what
you
want
to
do
in
yanil.
So
we
can
go
so
three
commands
go
from
nothing
to
deploy
AWS
infra
with
deposit
contract,
and
then
you
know
like
boot,
nodes
distributed
and
F
distributed,
validates
deposited
and
the
test
that
started
so
we've
been
enjoying
that
and
we're
hoping
that
we
can
use
that
it
works
quite
well
for
managing
multiple
disparate
tests,
and
so
we're
looking
forward
to
starting
some
test
ends
with
short
slot
fines
and
other
challenging
kind
of
things.
F
So
that
thing
is
all
fully
open
source,
except
for
hopefully
authentication
secrets
at
seek
PD
forward,
slash
slight
housewife
and
ansible.
If
you
want
to
look
at
it,
Adrian
decided
to
sync
with
prism,
I
managed
to
get
the
RPC
working
in
blocks.
I
downloading,
then
we
hit
the
state
route
thing.
We've
spoken
about
that
we
made
some
progress
on
switching
to
Russ
latest
async
programming,
feature
called
stable
futures,
which
gives
us
an
updated,
execute
async
executors.
So
we
can
avoid
some
locks.
We've
been
having.
F
We
went
and
implemented
safe
arithmetic
through
the
state
transition
logic,
so
we
can
files
with
arbitrary
States,
so
that
goal
is
to
so
that
their
implementation
is
panic.
Free
across
any
arbitrary
state
think
we're
getting
close,
we're
pausing
it,
but
hopefully
we'll
get
that
soon.
Haven't
found
anything
yet
since
that
and
to
do
that,
Michael
wrote
a
rust
linter
that
goes
and
finds
unchecked
arithmetic.
F
We
ran
it
across
the
code
base
already
found
some
interesting
mod
by
zeros
and
stuff,
like
this
we're
doing
some
research
on
suicide
events
to
see
if
it's
conceivable
with
our
HTTP
library.
It's
looking
good
so
far,
we're
looking
forward
to
jumping
on
that
standard,
HTTP
API
when
it's
defined
and
finally
Michael's
revisiting
our
slashing
production
database
and
we're
doing
some
thinking
about
exporting
out
so
like
JSON
or
some
format,
so
that
we
can
transfer
validators
between
my
house
instances
and
hopefully
between
other
clients.
A
A
Ok,
great
generally
I
think
people
gave
their
individual
tests
and
updates.
There
are
there's
a
public
test
sent
out
in
prison.
I
was
working
on
some
tests
on
stuff,
Nimbus
has
their
regular
weekly,
restart
test
nuts
and
some
base
interoperability
stuff
going
on
after
you
have
anything
else
to
update
us
on.
L
Yeah
I
have
some
comments
sure.
So,
two
weeks
ago,
I
dropped
a
dot
ten
test
net
spec
in
favor
of
11,
because
most
of
the
clients
are
working
towards
or
11
I
started
backwards.
As
time
tried
to
bootstrap
in
network
based
on
Teague,
my
main
goal
was
finding
trying
to
find
out
what
yet,
unfortunately,
I
didn't
manage
to
get
this
test.
Net
bootstrap
I
later
added
a
lighthouse
node
to
validate
its
configuration
is
valid
and
that
brought
but
eventually
I
braked
it
and.
L
Then
I
didn't
have
the
time
to
investigate
and
was
a
little
bit
distracted
by
the
tapas
launch
and
also
curious
about
adding
a
lighthouse
node
to
tow
past,
but
I
think
most
observe
things
being
covered
was
called
already
experiences.
Pampy
networking,
yes,
I,
was
just
one
consensus
parks
in
general.
I
would
like
to
emphasize
that
we
would
probably
have
this
single
client
test.
That's
for
why?
Because
they
saw
a
good
purpose,
was
according
client
teams
for
interoperability.
L
I
would
encourage
that
we
have
more
short-lived
test
nets,
so
we
can
pass
evaluate
any
issues
that
occur
at
the
networking
and
synchronization
consensus
or
whatever
comes
up
yeah.
So
if
possibly,
we
could
start
setting
up
very
fast
definites
in
the
future.
That
would
be
nice
but
I
believe
from
from
the
colonization's
on
discourse
as
well.
Everyone
is
going
to
that's
my
update,
yeah.
F
Okay,
well
I
think
so.
I
think
one
thing
might
be:
we've
the
eff
to
test
Nets
repo
is
using
a
config
tamil
file
that
describes
the
test
net.
It
was
modeled
off
the
the
config
directory
in
the
spec,
but
that's
now
kind
of
full
of
phase
one
stuff.
That's
that's
not
really
particularly
interesting
to
phase
zero
clients,
so
I
think
we're
probably
gonna
see
clients
like
we're
missing
a
few
things
from
there,
because
it's
not
obvious
anymore.
F
A
F
M
M
Probability
of
a
cross
card
transaction
and
that
should
be
released
soon,
Johnny
ray,
is
working
on
a
network
monitoring
tool
called
purple.
Sorry
for
anybody,
that's
finished,
I!
Guess
that's
a
curse
word
in
finish,
and
and
so
he's
connected
to
the
total
past
test
net
and
and
he's
able
to
monitor,
peers
and
walk
the
PHP
of
the
Topaz
Network.
M
M
Choice,
tests
for
based
on
PI
specs,
so
he's
wanting
to
make
okay
a
essentially
a
transpiler
that
will
take
the
the
high
spec
and
compile
it
into
the
languages.
You
know
tested
to
the
languages
of
the
clients
rather
than
having
to
manually,
modify
them
and
Dimitri's
continuing
on
with
disc
v5
simulation,
and
that's
many
surprises
he's
got
it
so
you
can
compare
about
14
different
metrics,
let's
just
cool
sure,.
N
Can
talk
about
my
peer
right
all
right,
so
Paul
opened
an
issue
about
the
F
F
G
and
L
n
D
vote
in
attestation
is
not
being
consistent
and
so
I
won't
describe
what
the
issue
is,
but
the
fix
to
it
is
that
when
you
receive
at
the
stations
outside
of
blocks,
you
should
check
that
the
beacon
block
route
and
the
target
for
that
attestation
is
in
the
same
chain.
So
this
introduces
like
some
new
stuff
in
the
for
choice:
speck,
no
removals,
so
it's
still
not
backwards
compatible,
but
it
should
be,
hopefully
minor.
N
N
Right
and
the
full
choice
stuff
so
for
trace
testing,
try
to
get
on
it
as
soon
as
possible.
It
should
be
in
the
next,
with
major
update
to
the
spec.
Fuzzy
testing
seems
fine
for
now,
but
somewhere
down
the
line.
We
also
want
to
test
for
orchestrated
attacks.
So,
let's
see
if
we
can
get
it
in
in
the
next
major
update.
O
Nothing
new
from
the
last
announcement.
We
are
continuing
to
work
towards
account
abstraction
in
the
ether,
1x
endeavor,
and
also
thinking
about
ether,
1
X
64
and
have
been
working
on
just
generally
getting
data.
So
we
can
start
evaluating
how
we
might
partition
properly
current
eath
1
transactions.
If
we
were
to
expand
it
across
multiple
shards.
A
P
P
Apart
from
that,
there
was
just
a
small
post
regarding
the
block
hash
on
a
tree
search
which
was
triggered
by
the
atomic
64
work
and
has
could
have
some
implications
regarding
stateless
deuterium,
but
I
think
it
may
have
more
implications
regarding
the
8
1
e
to
merge.
I
think
these
are
the
only
visible
updates
from
from
our
side.
A
R
A
I
think
especially
probably
I
know
some
of
you
began
to
look
at
that
spec
we're
working
on
a
always
working
on
refining
some
mistake,
cleaning
things
up,
testing
we're,
adding
the
validator
guide,
adding
Network,
spec
and
so
certainly
at
the
beginning
of
May.
If
you
haven't
taken
a
look
at
it
and
want
to
start
digesting,
it
would
be
a
good
time.
A
Great
we
didn't
have
an
API
call,
didn't
mention
that
on
Monday
there
were
some
decisions
made.
There
was
some
discussion
of
kind
of
this
extra
man
proposed
a
little
bit
proto
put
together
for
a
beacon,
API
and
the
formation
of
a
small
working
group
to
refine
that
make
it
as
restful
as
possible
and
get
an
updated
proposal
out.
There's
been
some
work
done
there
I'm,
not
sure.
If
there's
an
update
there
in
do
you
have
anything
for
us
or
we're
gonna
wait
watch
out
next
week
for.
R
A
A
My
house
has
brought
a
number
of
small
networking
changes
primarily
around
these
gossip
validation
conditions,
trying
to
reduce
the
overhead
of
some
of
the
caches
and
stuff.
Is
there
anything
else?
That's
come
up
that
you
all
want
to
discuss
the
glaring
issues
and
problems
we
found
10
cents
with
respect
to
networking.
F
So
yeah
I
just
wanted
to
point
out,
there's
lots
of
different
things
and
we've
had
to
really
pay
attention
to
like
before
we
were
returning
an
error
on
the
HS
state.
If
someone
said
it's
noted
station
in
it,
we've
got
an
error.
Adding
it
to
full
choice
would
declaring
that
to
be
invalid,
but
it
is
actually
valid
for
an
extension
you
get
on
the
eve
gossips
to
not
actually
get
it
to
your
fortress,
which
is
something
to
keep
in
mind
right.
A
Yeah,
the
the
conditions
are,
first
and
foremost
dose
resistant
conditions
in
the
gossip
and
then
like,
for
example,
the
block
ones
very
obvious,
like
we
don't
actually
run
the
state-transition.
You
know
we
see
if
the
signature
checks,
because
that's
a
signal,
a
pretty
strong
signal
that
a
proposer
wouldn't
if
we
see
their
proposal
kind
of
like
someone
doing
the
group
work,
and
so
there
is
certainly
a
difference
between
fully
verifying
these
messages
and
just
verifying
the
dose
resistance
stuff.
So,
yes,
there
are
some
disparities.
There.
A
Great
spec
items-
obviously
we
talked
about
beginning
this
part
and
I
are
working
on
a
modified
proposal
to
break
up
the
mega
rewards
function
into
better
testable
components
so
that
we
can
try
to
nip
some
of
these
rewards
problems
in
the
bud,
but
we'll
have
an
update
on
that
soon.
Any
other
spec
things.
S
Even
if
we
like,
we
think
it's
too
late
to
do
would
add
them
into
phase
zero.
They
seem
like
potentially
good
ideas
for
phase
one,
so
one
of
those
was
Justin's
proposal
to
a
unify
uniqueness,
slashing
for
beacon
blocks
and
shard
blocks
and
potentially
anything
else
that
has
uniqueness
and
the
other
one
was
the
proposal
that
I
had
suggested
that,
basically,
we
tried
to
maintain
an
invariant
that
the
maximum
possible
amount
amount
of
money.
S
S
Mean
fee
in
phase
zero,
it's
slightly
untrue.
The
reason
at
is
proposer,
Awards
right
so
right
now,
I
think
each
of
the
rewards
is
divided
by
it
was
at
five
either
for
and
direct
are
like
5
sec,
five
sections
of
rewards
that
all
add
up
to
be
its
reward,
divided
by
this
Groot
of
the
balance,
but
then
there's
also
the
total
rewards
that
are
like
the
other
reports
divided
by
eight.
So.
T
S
Rewards
per
log
is
for
who
write
the
proposer
award
as
right.
Okay,
so
base
rewards
for
a
park
is
four
and
then
yet.
Base
reward
is
divided
by
a
divided
by
four,
and
then
they
get
base
reward
is
added
for
once
for
matching
source
once
for
matching
target
once
for
matching
head
and
then
there's
the
inclusion,
delay
reward
and
then.
T
S
S
A
S
A
A
A
C
A
A
We
are
in
communication
with
the
spec
maintainer
x'
and
they
say
it's
imminent,
but
they
said
that
week
ago,
so
we're
gonna
continue
knock
on
their
door.
That
would
I
mean
ideally
first
week
in
May
we
can
cut
this
release,
but
I
there's
a
little
bit
of
this
variables
out
of
our
control.
As
for
the
modified
testing
of
the
deposit
and
of
the
rewards
function,
that
is
something
that
will
probably
release
to
be
0
11,
which
would
be
totally
non
substances.
We've
changed
some
of
the
test
harnesses
as
soon
as
possible,
so
essentially
next
week.
A
Following
that,
the
only
thing
that
the
only
breaking
changes
through
that
anybody
would
be
critical
security
fixes
I'm,
not
confident
to
say
that
we
wouldn't
necessarily
find
any
of
those.
There
are
ongoing
audits
of
clients
which
might
uncover
things
and
there's
the
potential
that
we
run
into
some
bugs
on
the
assessments.
Interoperability
testing,
but
barring
critical
bug
fixes
the
plan
is
to
release,
is
to
bring
that
the
v-0
12
to
make
that
okay.
Thank
you
and
the.