►
From YouTube: Filecoin Core Devs Biweekly #22
Description
Recording for: https://github.com/filecoin-project/tpm/issues/52
For more information on Filecoin
- visit the project website: https://filecoin.io/
- or follow Filecoin on Twitter: https://twitter.com/Filecoin
Get Filecoin community news and announcements in your inbox, monthly: http://eepurl.com/gbfn1n
A
I
suppose,
all
right
good
morning,
good
afternoon,
everyone
welcome
to
the
22nd
falcon
bible
core
devs
meeting
on
thursday
july
15th.
I'm
gonna
drop
the
agenda
in
the
chat.
A
We've
got
a
few
things
that
we'll
be
that
we
should
talk
about
after
after
we
go
through
our
updates,
another
another
fifth,
that's
where
or
we
need
to
revisit
fib
16,
which
we
talked
about
in
a
few
a
few
meetings
ago
and
then
there's
a
few
lotus
side
issues
that
we've
noticed
that
are
somewhat
consensus,
critical
they're,
all
fairly
fairly
minor,
fairly
inconsequential,
but
is
relevant
for
this
group
and
stuff
that
we'd
like
to
slightly
improve
on
and
change
in.
The
next
network
upgrade
so
we'll
go
into
this.
A
But
let's
start
off
with
updates
the
forest.
Do
you
wanna
go
first.
B
Sure,
yes
updates
from
us.
We
got
prometheus
metrics
now,
so
that's
pretty
cool.
We
got
some
dashboards
up
and
going
we're
continuing
to
finish
up.
You
know
more
of
the
cli
functionality,
so
we
can
have
a
better
user
experience
when
we
launch
we're
gonna
start
making
a
push
on
documentation
sometime
next
week,
probably
after
we
wrap
up
the
cli
stuff.
So
we
have.
We
have
a
bunch
more
stuff
to
document
and
yeah
in
terms
of
v13.
B
We
have
pretty
much
everything
implemented,
I'm
just
trying
to
iron
out
some
consensus,
mismatching
right
now,
so
you
know
doing
state
diffs,
analyzing,
the
state
and
that
kind
of
stuff
so
yeah.
We
should
probably
be
back
on
wayne
that
in
a
couple
days
or
something
yeah,
I
think
that's
it
from
us.
A
Cool
regarding
audit
stuff
have
have
everything
that
was
flagged
been
resolved
or
flagged
like
won't.
We.
B
Yeah,
so
pretty
much
most
of
the
remediation
stuff
is
done.
We
just,
I
think
we
have
like
one
more
thing,
that
we
need
to
patch
up
a
couple
more
things,
I'm
not
sure,
but
most
of
the
major
ones
have
been
fixed
and
then
some
of
the
other
ones
are.
B
I
guess
things
that
it's
that
that
will
require,
like
a
network
network,
hard
fork
to
fix,
for
example,
like
us,
accepting
non-utf-8
strings
that
kind
of
stuff,
so
yeah,
probably
gonna.
You
know,
do
all
that
once
that
gets
fixed
in
the
active
v6
or
whatever
version
is
next,
that's
good.
Let's.
A
Try
another
numbers.
Yes,
yeah.
No
sorry
sounds
good.
I
think
there's
been
some
kind
of
crosstalk
about
some
of
those
issues,
but
if
there
are
kind
of
protocol
sensitive
ones,
maybe
useful
in
maybe
the
next
core
devs
meeting,
we
can
kind
of
go
over
the
ones
that
are
that
would
require
network
upgrade
to
fix
and
kind
of
talk
about
whether
we
want
to
fix
them
in
the
next.
The
next
upgrade
yeah,
that's
great
thanks.
Yeah
sounds
good.
Go
any
questions
for
first
cool.
C
Can
and
hello
everyone
you
forbid
us,
as
in
last
few
weeks,
we
achieved
a
very
good
event.
We
passed
the
spread.
C
A
Okay,
maybe
we'll
we'll
try
again
or
get
an
ethic
update
from
stephen.
I
think
he
may
have
dropped
for
now.
But
if
you
want
to
move
on
to
fuchan
we'll
see
if
we
can
revisit
him
later.
D
Yeah
sure,
good
evening,
everyone
good
morning
a
day
for
other
people,
so
for
fujon
we
are
currently
working
on
preparing
documentation
for
the
security
audit.
We
are
working
on
preparing
the
codework
and
policing
the
stuff
that
we
need
to
well
that
we
want
to
do
before
the
code
freeze.
D
The
other
thing
we
are
currently
working
is
is
testing
our
well
our
node
with
lotus
miner
on
interrupt
net.
We
have
several
incompatibilities
here
and
there
and
we
are
currently
working
on
figuring
them
out,
nothing
major
so
far,
but
yeah
well.
Currently
they
we
have
an
issue
where
we
are
well.
A
lot
of
smiler
is
not
receiving
notification
about
the
message
status
for
some
reason
and
we're
currently
figuring
it
out.
D
So
probably
the
problem
is
now
site
and
somewhere
in
the
notification
channel,
but
we
will
have
to
check
so
this
is
something
we
are
currently
debugging
and
figuring
out
the
issue.
Otherwise
we
are
currently
well.
We
have
also
faced
an
issue
on
the
main
net
node
and
it's
quite
strange
one.
So
we
can't
we've
been
testing
our
main
net
node
on
the
virtual
machine,
which
has
well
obviously
virtual
memory,
but.
D
Recently
we
have
faced
an
issue
where
there
was
a
part
of
memory
was
corrupted
and
our
dependency
in
it.
Well,
something
in
libsy
has
broken
and
it
was
not
able
to
access
memory,
which
is
usually
not
the
issue
and
the
ellipse
use
quite
widespread
library.
D
So
it's
quite
low
probability
that
the
problem
is
in
the
software,
so
we'll
have
to
what
we
did
was
we
have
moved
to
our
testing
maintenance
to
the
dedicated
server
with
our
shared
memory,
and
we
will
see
if
it
will,
it
will
resolve
the
issue
so
yeah,
that's
the
status
for
the
for
for
the
foothold.
A
Interesting,
okay,
yeah,
I
don't
know
what's
going
on
with
the
with
that,
let
us
know
if
we
can
help
investigate
it,
but
otherwise
otherwise
sounds
good.
Regarding
interrupt
yeah,
sorry
that
it
it
took
a
while
to
get
you
for
some
some
funds
on
drop
net
to
to
test
and
we'll
we'll
discuss
the
stats
been
dropping
out
a
bit
later.
I
think
it'll
probably
need
a
reset
because
of
one
of
the
lotus
bugs
that
we're
going
to
be
talking
about,
but
yeah.
That
sounds
good.
A
I
think
stephen
was
having
a
hard
time
with
his
internet
connection,
so
he
provided
an
update
async
and
in
the
zoom
chat
just
reading
it
out
for
the
benefit
of
anyone
viewing
later.
The
main
achievement
of
venus
is
that
we
have
the
security
audit
done
and
got
the
final
report
published
that's
great
and
the
v1
has
been
released,
which
is
very
exciting.
Now
working
on
incubation
launch
preparation,
that's
cool!
Always
nice!
A
When
you
have
a
one
in
front
of
your
release,
number
perfect
cool
load
aside,
what's
going
on
in
lotusland.
For
the
most
part,
a
lot
lots
of
exciting
things
actually
so
we're
in
terms
of
releases
we're
testing
our
v1.11
release,
which
is
about
three
months
worth
of
dev
work,
because
a
bunch
of
network
upgrades
kept
jumping
ahead
of
the
queue,
and
so
we
kind
of
had
like
a
bunch
of
like
new
features
and
bug
fixes
sitting
in
stasis
for
a
while.
A
So
that's
on
rc2
and
we're
kind
of
like
putting
it
through
the
testing
measures
right
now
hoping
to
cut
the
release
itself
next
week.
Apart
from
that,
a
bunch
of
exciting
stuff
has
landed
at
master.
One
of
the
important
ones
is
so
we're
what
we're
calling
split
store
and
there's
a
bunch
of
documentation
that
I
can
share,
I
think,
has
been,
has
been
in
lotus
for
a
while
and
it's
gonna
it's
getting
more
and
more
important
and
then
we're
hoping
to
get
a
production
ready.
A
One
of
the
important
features
that
it
enables
is
online
garbage
collection
so
that,
if
you
only
want
to
like
validate
the
node
but
not
keep
old
chain
history,
which
is
what
most
people
running
on
filecoin
are
doing
these
days,
it
enables
that
to
happen
automatically.
So
you
throw
away
old
state
once
you're
once
you
don't
need
it
anymore
for
consensus
purposes.
A
We
also
have
a
fairly
the
major
refactor
of
the
the
way
the
lotus
binder
interacts
with
the
markets
module
and
how
and
how
the
deal
making
happens
around
that
I'll
drop.
I'll
drop,
a
link
to
that
as
well,
so
both
of
these
have
landed
in
master
they'll,
probably
be
going
out
into
a
release
later
this
month
and
then
yeah.
Those
are
kind
of
the
chief
updates
on
the
lotus
dev
patch,
also
kind
of
a
kind
of
focus
on
testing.
A
Right
now
we
refactored
how
tests
we
basically
refactor
the
entire
lotus
integration
test,
suite
to
make
it
much
more
reliable,
easier
to
write
tests,
and
just
generally,
we
also
had
a
big
problem
with
test
flickiness.
So
that's
been
resolved.
So
there's
a
bit
of
a
testing
push
going
on,
which
you
know
always
a
good
thing
and
obviously
a
lot
of
monitoring,
hyperdrive
and
making
sure
things
are
going
well
there.
So
far,
so
far
things
have
been
good.
A
We
shipped
a
110
one
hotfix
release
that
just
had
a
few
minor
improvements
on
top
of
on
top
of
the
hyperdrive
release,
but
there
was
nothing
nothing
too
too
significant
in
there,
which
is
good
cool.
The
photos
from
the
foundation
have
an
update.
I
don't
have
sonia
dudley
and
if
you
have
things
you
want
to
share.
E
Sure,
I
think,
from
the
foundation
side,
we're
excited
by
the
half
drive
launch
and
all
the
buzz
that's
been
in
the
community
by
that
so
awesome
job
on
that
and,
like
steven
mentioned
the
incubation
center,
I
think
it's
launching
soon
and
there's
been
several
conversations
about
what
it
means
to
be
a
storage
miner
far
coin.
So
it
would
be
great
to
get
this
group's
view
on
what
we
can
really
how
we
can
leave
that
conversation
with
the
storage
miners
in
the
community
and
then.
Lastly,
the
foundation
is
hiring.
E
A
Very
exciting,
I
will
be
sure
to
drop
a
link
to
to
your
available
positions.
The
dots
of
this,
oh,
that's,
cool
dudley.
Did
you
have
an
update?
You
wanted
to
share.
F
Yep
so
primarily
of
interest
to
the
implementer
series
that
we
will
be
extending
the
bug
bounty
program
to
all
implementations
of
filecoin.
So
I've
already
spoken
with
eric
about
this
a
little
bit,
but
I
will
reach
out
to
maxime
and
steven
about
this,
probably
after
this
meeting
to
arrange
meetings
where
we
kind
of
walk
through
it.
What
your
responsibilities
would
be,
which
we
pretty
much
leave.
F
You
know
up
to
you
guys
as
we're
not
in
control
of
you,
but
also
how
we
will
function
with
like
the
rewarding
process,
and
things
like
that
should
be
fairly
simple.
A
few
kinks
to
work
out,
but
yeah
excited
to
get
it
done.
We'll
probably
do
an
announcement
once
every
implementer
is
on
board.
A
Very
cool
yeah
there's
an
interesting
question
about
when,
when
implementations
want
to
like
kind
of
get
started
with
that
in
terms
of
where
in
your
development
process,
but
it
sounds
like
most
most
folks
are
already
pretty
close
to
productionizing
and
getting
midnet
ready,
so
now's
a
good
time
to
start
to
find
some
of
those
bugs
cool.
Thank
you
all
right,
any
anyone
else
who
had
an
update
they
wanted
to
share
or
any
questions
about
anything.
We
talked
about.
A
Cool
sounds
good
all
right,
maybe
first
up,
let's,
let's
talk
about
some
of
these
some
of
this
lotus
funk.
Let's
talk
about
the
priceless
conversations
and
if
you
want
to,
if
you
want
to
share
our
findings
and
fixings
there
and
how
it
will
impact
the
other
teams.
G
Great,
so
I'm
going
to
share
a
link
to
a
ghost
state
types.
Pr
and
yes,
that's
pr30
and
go
state
types,
and
I'm
also
going
to
share
a
lotus
pr,
it's
pr
6766,
if
you're
watching
the
recording
so
so
yeah.
Basically,
we
were
looking
through
the
price
list
trying
to
clear
up
some
technical
debt.
We
noticed
that
the
price
list
was
indexed
on
epic.
G
Where
there's
a
consensus
difference,
because
the
price
list
indexing
was
off
by
one,
so
calico
upgrade
height
is
actually
the
last
block
before
calico,
but
we
were
using
it
to
price
out
the
gas
parameters
for
the
actual
yeah
for
the
last
epic
before
calico
yeah.
So
the
way
to
get
around
it
there's
none
of
this
version
stuff
is
actually
on
chain.
So
it's
not
a
huge
deal,
but
we
do
want
to
associate
a
version
with
consensus
differences.
G
G
It's
still
not
through
review
or
anything
yet.
But
it's
up
with
the
changes
to
to
fix
this,
so
that
the
price
list
is
based
on
version.
So
for
other
implementations,
I'm
not
sure
how
you
all
are
doing
it,
probably
going
versus
yeah.
I
mean
I'm
sure
you,
you
must
be
I'm
guessing.
G
You
must
be
going
by
epic
because
there's
no,
there
was
no
problem
sinking
calico
or
I
guess
if
there
was
no
problem
sinking
calico,
if
that's
the
case,
but
I
guess,
as
a
heads
up,
it
probably
makes
sense
to
do
things
based
on
version
and
to
use
this
version
six
and
a
half
for
that.
One:
weird
block
on
mainnet
yeah,
any
questions.
A
Yeah
just
kind
of
thinking
about
the
impact
of
this.
Obviously
things
for
the
most
part
happened.
Fine
were
we
was
the
new
price
list
kicking
into
place
earlier
or
like
one
block
earlier
or
one
block
after
the
apple
version
challenge
itself,.
G
Yeah,
so
from
what
I
gathered
from
trying
to
sync
this
with
the
off
by
one
error,
fixed.
F
A
So
the
biggest
so
this
could
have
been
bad.
Would
it
be
correct?
This
could
have
been
bad
if
between
the
price
list
we
took
away
between
between
as
we
change
from
old
to
new
we
took
away
or
put
in
some
like
incorrect
or
nonsensical
value
for
essentially,
if
we
deprecated
something
that
we
were
charging
for
earlier,
that
could
have
probably
caused
an
issue
if
there
was
a
message
that
actually
triggered
that,
because
we
tried
to
use
the
old
price
list
or
try
to
use
the
new
priceless
too
early
yeah.
G
To
say
it's,
it
seems
like
in
most
cases
priceless
changes
shouldn't
have
a
big
impact
like
based
on
epic,
like,
I
think
the
biggest
risk
here
would
be
that
different
implementation,
like
somebody
actually
implemented
it
correctly
and
then
lotus,
had
it
wrong,
and
then
there
would
be
a
fork.
That's
that's
yeah.
I
guess
what
I
see
is
the
worst
case,
but
thankfully
that
didn't
happen
or
not,
that
we
know.
A
Yep,
that
makes
sense
cool
yeah,
so
yeah
any
any
questions
from
the
other
implementers.
A
This
should
be
a
minimal
change.
It
should
be
the
situation
if
you're
doing
things
correctly,
then
things
stay
the
same,
but
it's
something
we
definitely
want
to
clean
up
and
the
next
time
we
actually
have
a
network
upgrade.
The
price
list
should
change
at
the
right
time,
along
with
the
rest
of
the
network,.
A
Sounds
good
cool
I
also
wanted
to
talk
about.
This
is
lotus
issue
3613,
I'm
dropping
it
in
chat
now.
So
this
is
an
issue
that
we
kind
of
opened
and
closed
and
then
unfortunately
had
to
reopen.
A
So
what
before
the
hyperdrive
upgrade
so
before
network
v13,
what
lotus
was
doing
was,
if
you
had,
if
say,
if
there
was
a
null
tip
set
at
round
at
height
at
epoch,
10,
and
let's
say
that
the
the
file
point
epochs
and
derand
rounds
are
the
same
in
this
case,
then
what
lotus
would
do
when
you
try
to
fetch
the
randomness
at
round
10,
which
gives
you
the
randomness
at
round
nine,
which
is
fine
for
practical
purposes,
but
isn't
correct
from
a
theoretical
perspective?
A
And
it's
not
what
spec
says
so
we
fixed
this
in
hyperdrive
and
I
think
the
other
implementations
also
made
that
fix.
Unfortunately,
we
didn't
fix
it
correctly.
Where
now
what
happens
is
if
there's
an
if
there's
a
null
subset
at
around
10,
we
wind
up
giving
you
the
randomness
from
for
around
11.,
so
we
go
forward
instead
of
just
giving
you
the
randomness
for
round
10.
A
again,
no,
no,
no,
real,
no
real
world
impact
for
the
most
part,
but
it's
still
wrong
so
something,
but
for
the
most
part,
again
kind
of
like
the
priceless
issue.
The
important
thing
is
that
it
runs
the
risk
of
throwing
other
implementations
out
of
sync
when
this
happens
so
definitely
take
a
look
at
that
and
unfortunately,
because
lotus
has
so
much
of
the
mining
power.
A
The
bug
is
just
going
to
stick
on
mainnet,
so
something
we'll
fix
in
the
next
network
upgrade,
but
you
definitely
want
to
take
a
look
at
this
issue.
Anyone
else
influential
point
out
there,
if
you
want
to
think
mainnet
you'll,
probably
have
to
unfortunately
implement
this
bug
and
yeah
a
bit
unfortunate,
there's
also
a
bit
of
an
open
question
around
how
we
can
catch
something
like
this.
Obviously,
this
is
why
you
want
multiple
implementations,
because
in
our
likelihood
some
other
implementation
would
have
got
this.
A
In
this
case,
I
think
venus
said
they
ran
into
it
on
calibration
net
but
like
it
didn't
get
alerted
to
the
to
the
right
level,
and
so
we
didn't
actually
fix
it
so
moving
forward.
I
think
there's
a
bit
of
a
note
that
when
we're
testing
in
that
like
calibrate
but
there's
a
couple
notes,
have
a
longer
testing
window
on
calibration
and
so
that
across
implementations
can
catch
stuff
like
this
and
when
testing
stuff
like
this
on
test
networks.
A
If
we,
if
we
do
notice
issues,
we
really
need
to
like
talk
them
through
and
because,
in
all
likelihood,
some
implementation
has
a
bug
and
we
need
to.
We
need
to
reason
what
the
correct
thing
to
do
there
is.
It
would
have
been
very
nice
if
we'd
cut
this.
If
you've
got
this
on
calibration
and
it
hadn't
followed
our
maintenance.
A
Cool
yeah,
so
it's
not
the
not
the
nicest
thing
to
be
like.
Oh
there
are
these
two
bugs
and
lotus
that
are
kind
of
impacting
mainnet,
but
there
you
have
it
cool.
Last
thing
I
wanted
to
nothing.
I
have
on
the
agenda
at
least
was
to
revisit
flip
16.
A
Let
me
drop
a
link
in
chat.
This
is
packing
arbitrary
data
in
cc
sectors,
so
the
conversation
is
continuing
in
issue
issue.
A
Where
is
this
give
me
a
second
to
find
it
there
we
go
issue,
57
chat
as
well,
so
yeah.
So
we
talked
about
this.
I
think,
like
maybe
a
month
or
a
month
or
over
a
month
ago,
in
cordev's
call
and
those
kind
of
mixed
opinions
on
this.
I
think
I
think
a
lot
of
this
group
thought
it
was
thought
it
was
a
reasonable
proposal
and
good
to
have.
Since
then,
a
few
more
people
have
weighed
in
on
the
fip.
A
I
think
a
north,
juan
and
user
o
z,
h,
t
d,
o
n
g
commented
on
it
as
well.
So
the
objection
that's
kind
of
being
raised
by
a
few
people
is
there's
a
few
aspects
to
it.
Number
one.
A
There's
a
question
around
how
necessary
it
is
because,
as
a
result
of
hyperdrive
and
ongoing
research,
we're
hoping
that
it
just
becomes
cheaper
and
easier
to
publish
deals,
and
so
maybe
maybe
that
albeits
the
need
for
it
a
little
bit
a
north
there's
this
kind
of
this
question
around
economy
and
how
this
impacts
economy,
where,
on
some
level,
we
do
want,
we
kind
of
want
the
file
coin,
the
token
to
be
the
asset,
that's
obviously
securing
the
network
and
the
asset
that
makes
the
network
useful,
and
so
you
kind
of
want
deals
to
be
transacted
in
the
same
asset
in
order
to
kind
of
keep
the
economy
secure.
A
I
have
a
harder
time
reasoning
about
that
kind
of
thing,
but
I
think
that
yeah,
I'm
curious
to
know
what
people
think
about
that
line
of
reasoning.
The
other
thing
that
anarch
flag-
that
I
think
hopefully
folks
read
is
it-
is
nice
to
enforce
that
cc
sectors
have
all
zeroes
sealed
in
them,
because
that
makes
future
kind
of
innovation
and
things
a
little
more
easy
and
he
shared
a
couple
of
proposals
that
would
be
impacted
if
we
didn't,
if
we
hadn't
been
enforcing
this
all
along
so
do
we
have?
A
What
are
people's
thoughts
on
this?
Are
people
still
in
favor
generally?
Do
we
want
to
do
this?
When
would
we
want
to
do
it?
What
do
people
think.
B
Yeah,
I
think
the
concerns
are
quite
valid.
I
think
I
raised
similar
concerns
last
time
with
respect
to
kind
of
like
the
whole
market
structure,
of
having
something
like
this
yeah.
I
think,
if
it's
something
that
we
really
want
definitely
got
to
do
more
research
before
we
can,
you
know,
do
it.
Okay,.
A
Yeah,
this
kind
of
sounds
like
from
a
secure
from
an
engineering
security
perspective.
There's
no
immediate
objections
that
I'm
seeing
except
one
that
I
raised,
which
is
hyperdrive,
is
going
to
be
increasing
the
size
of
the
state
tree
already,
or
at
least
has
the
potential
to
be
doing
so
so
I'm
a
little
wary
of
adopting
proposals
that
add
anything
to
the
state
tree
right
now,
and
this
does
so,
but
that's
more
a
question
of
timing
than
anything
else.
A
A
Yeah
yeah,
I
think
the
other.
The
other
thing
that
will
be
useful
is
to
get
a
sense
of
essentially
how
and
when
we
might
want
to
do
this
like
like
what
the
impact
is
like
do.
A
People
already
have
lots
of
use
cases
out
there
that
are
like
actively
waiting
for
this
proposal
to
be
adopted,
or
is
it
just
a
nice
to
have
that
we
that
we
get,
in
which
case
it
kind
of
lowers
the
priority
a
little
bit
so
there's
kind
of
some
surveying
work
to
be
done
as
well,
but
any
other
thoughts
about
about
16.
A
I
should
mention
that
the
authors
of
the
pr
also
kind
of
fleshed
out
the
implementation
section,
but
a
north
already
reviewed
that
and
raised
some
minor
concerns,
but
generally,
I
think
the
picture
makes
sense.
So
if
we
want
to
review
that
just
to
make
sure
there
are
no
red
flags,
there,
that'd
be
good
yeah,
any
any
other
thoughts
on
on
the
subject.
A
Cool
yeah
I'll
we'll
push
along
some
of
this,
some
of
the
to-dos
that
we
have
here
and
I'm
sure
we'll
revisit
it
a
little
later
cool.
That's
all
I
had
on
the
agenda.
We
do
need
to
start
thinking
about
kind
of
scoping
out.
The
next
network
upgrade
next
version
of
actors
like
what
we
actually
want
in
there,
but
you
know
right
now.
We
don't
have,
apart
from
these
kind
of
very
minor
fixes
that
we
talked
about.
A
There's
not
a
lot,
that's
kind
of
hurtling
down
the
pipeline,
so
I'm
I'm
okay
to
to
move
somewhat
slowly
on
that,
especially
as
we
wait
to
see
how
hyperdrive
plays
out
and
transforms
the
system,
but
but
we
maybe
maybe
in
the
next
call,
we
can
start
just
scoping
out.
If
only
what
what
kind
of
conceptual
struggle
about
fixes.
We
might
want
put
that
as
a
note
for
next
call.
A
Cool,
oh
one.
Other
item
that
I
did
have
on
the
agenda
was
interrupt
net
so
because
of
the
priceless
issue
that
why
it
was
well
as
a
weird
side
effect.
I
should
say
of
the
priceless
issue
and
the
way
we've
set
up.
A
Interop
net
interrupt
is
the
first
network
we
ever
deployed
that
starts
directly
from
v5
actor,
so
it
doesn't
start
from
v0
and
go
through
all
the
upgrades
as
a
result
of
that
interrupt
net
wound
up
using
a
like
a
completely
wrong
price
list
and
it
is
using
it
today,
so
it
so.
The
network
is
usable,
but
you
would
have
to
like
you
know,
intentionally,
go
and
use
the
wrong
price
list.
A
If
other
implementations,
like
the
sync
is
very
much
just
a
lotus
bug,
slash
a
bug
in
how
we're
setting
up
networks,
so
I
think
probably
what
we'll
do
there
is
just
fix
that
within
lotus
and
then
and
then
reset
the
network,
so
that
interrupt
net
is
actually
useful
and
usable
for
testing
out
compatibility,
minor
work
and
so
on.
I
think
the
fujan
team
in
particular,
is
relying
on
it,
so
we'll
definitely
keep
it
to
keep
it
alive.
A
All
right
sounds
good.
We
can
wrap
up
here.
Lots
happening
as
always
it'll
be
exciting
to
see
some
of
our
some
of
the
other
implementations
go
live
on
maintenance
soon.
I
think
that'll
be
that'll,
be
good
and
really
improve
the
security
of
the
network,
so
whatever
we
can
do
to
exploit
that
like.
I
want
that
to
kind
of
be
like
one
of
our
as
a
group
or
one
of
our
top
priorities
for
the
second
half
of
the
year,
so
whatever
whatever
anyone
can
do
to
expedite
that
process,
we'll
do
it.