►
From YouTube: Filecoin Core Devs #42
Description
Recording for: https://github.com/filecoin-project/tpm/issues/99
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
All
right
good
morning
to
those
of
you
in
the
americas
and
wherever
else
you
may
be-
this
is
file
coin.
Core
devs
number
42.
today
is
thursday
may
5th
2022.,
and
this
week
this
is
meeting
one.
It's
also
the
only
meeting
we're
going
to
be
hosting
as
just
discussed
in
slack.
We
thought
it
best
to
have
everybody
in
one
call
today,
so
that
we
could
have
sort
of
an
open
conversation
about
current
timeline
planning
for
network
v16
in
particular,
so
oops.
A
I
forgot
to
update
the
agenda
on
this
slide,
but
I
think
today
we're
going
to
go
through
the
updates
from
all
the
teams
updates
from
the
file
coin
foundation
as
well,
and
then
again
we're
really
going
to
focus
on
talking
about
the
upcoming
network,
just
to
make
sure
everyone's
in
alignment
and
so
that
we
can,
as
a
group,
begin
to
answer
any
questions
which
may
exist
so
with
that
the
forest
team.
Do
you
want
to
jump
in
with
your
updates.
B
D
B
D
So
we've
been
working
hard
on
on
increasing
the
test
coverage
for
the
building
actors
and
we
have
finished
or
almost
finished,
like
95
percent
finished
with
four
of
the
actors,
and
we
have
now
started
with
the
minor
actor,
which
is
the
only
one
left
I
believe,
and
when
that
is
done,
then
the
testing
should
be
at
least
as
good
as
it
was
with
the
going
implementation
and
yeah.
That's
all
I
have
for
for
the
forest
team.
A
Great
and
again,
we'll
have
plenty
of
time
today
to
talk
about
status
of
fbm
integration,
all
the
testing
that's
going
on
and
anything
else,
but
any
additional
questions
for
the
forest
team
right
now.
A
All
right
sounds
good,
then,
let's
jump
over
to
the
lotus
team.
Are
you
sure
jennifer.
E
Lotus
has
released
the
rc
for
115.2,
which
is
all
we're
like
in
the
future
release.
As
the
monthly
release
has.
We
know,
post
worker
schedule,
enhancement
and
all
those
all
sorts
of
things,
but
then
again
we
are
working
on.
E
The
upcoming
network
upgrades,
including
zhang,
is
still
working
closely
with
forest
on
the
test
coverage
rally
scene
and
the
rest
of
the
team
is
supporting
the
fbm
team
to
finalize
the
fvm
implementation
for
the
upcoming
upgrade
and
the
ayush
has
been
working
on
the
migration
side
of
the
cities
and
working
with
viso
to
figure
out
how
we
get
the
new
actor
bundle
published
for
everyone
and
make
sure
the
state
transition
can
go
as
well
around
the
upgrades.
E
One
quick
mentioning
is,
we
are
gonna,
have
a
new
proof
like
release
as
well,
like
gonna,
be
included
in
this
mandatory
release
of
lotus.
There's
no
network
expected
for
the
rest
of
the
implementation
team.
We
will
be
sharing
like
the
lotus
pr
later
in
the
tpm
repository,
but
that's
that's
our
update.
So
far.
A
All
right,
stephen:
do
you
want
to
give
the
update
for
venus.
C
C
So
we
keep
a
close
eye
on
fm
and
building
actors
in
placing
and
you
know,
chat
base
to
integrate
and
incorporate
all
the
changes
so
currently,
after
vedas
supporters,
a
film
m0
and
well
yeah,
following
on
that,
and
also
currently
west
support,
there's
a
test
on
the
caterpillar
and
can
penetrate
yeah
for
testing
and
some
others.
Caster
now
support
the
windowpost
and
win
imposed
separation
as
yeah,
so
that
you
could
you
use
different
different
machines
to
do
this
and
and
which
can
be
configured
via
craig.
C
We
had
a
demo
in
the
yeah
m,
a
meeting
which
is
good
some
others,
I'm
going
right
now,
for
example,
in
vedas
market
and
we're
supporting
post,
to
support
the
http
api
and
actually
and
we're
supporting
on
on1,
and
we
went
back
merchant
for
the
common
proportion,
yeah
and
components
so
that
for
developers
who
could
use
the
oem
one
to
deploy
the
test,
yeah
the
test
environment
and
for,
for
example,
to
ease
our
installation
and
test
it
yeah.
A
All
right,
thank
you,
steven
and
so
for
the
fujan
team,
the
updates
coming
from
me
this
week
as
much
as
I
loathe
to
the
the
bearer
of
bad
news.
I
would
like
to
let
you
all
know
that,
as
of
last
week,
the
foundation
has
ended
its
support
for
the
fujon
implementation,
so
the
team
was
having
a
hard
time
keeping
pace
with
the
rate
of
network
changes
and
sort
of
the
demands
of
providing
community
support.
A
So
we
let
them
know.
Last
week
we
had
been
working
with
them
for
several
months
to
try
and
add
some
additional
capacity,
but
mutually
it
wasn't
something
that
we
were
able
to
make
work
so
going
forward.
The
ecosystem
is
only
going
to
be
maintaining
three
implementations.
Obviously,
forest
lotus
and
venus.
The
repositories
all
of
the
code
is
going
to
remain
open
and
accessible,
of
course,
but
the
plan
is
for
none
of
those
repos
to
be
maintained
now
or
in
the
future.
B
Yeah
I
have
one
caitlyn
yeah
yeah
is:
is
there
going
to
be
another
team
that
does
maintain
like
a
c
plus
implementation
for
the
network,
or
at
this
moment
we
are
unknown
on
that.
A
So
at
this
moment
we
are
no
on
that
we're
open
to
it,
but
it
would
be
very,
very
difficult.
The
thinking
is
for
another
team
to
come
in
and
continue
that
development
so
for
right
now
again
we
will
leave
the
repos
open.
I've
already
put
in
a
request
for
the
filecoin
spec
to
be
updated,
so
it
will
draw
a
reference
to
the
fact
that
there
are
these
c
plus
repos,
but
that
again
they're
not
being
maintained.
A
A
All
right,
and
so
again
so
maxim
will
not
be
joining
us
in
the
core.
Devs
call,
of
course,
going
further
or
going
forward,
but
of
course
he
is
still
an
active
part
of
the
falcon
community.
So
you
are
able
to
reach
out
to
him
on
slack
and
we
do
hope
to
see
him
in
weighing
into
developer
topics
going
forward,
also
so
be
on
the
lookout
so
then
jumping
into
updates
from
the
file
queen
foundation.
On
a
lighter
note,
I
think
congratulations
to
stephen
who
authored
the
beneficiary
address
fifth
of
29.
A
This
was
accepted,
which
is
great
and
really
exciting.
So
hopefully
we
can
get
the
scheduled
for
implementation.
In
one
of
the
upcoming
network
upgrades
and
just
yesterday,
fifth
32
was
finalized
by
the
fdm
team
for
the
most
part
to
the
point
at
which
we're
able
to
enter
all
three
of
those
until
last
call.
A
I
am
currently
technically
supposed
to
be
a
conference,
so
I'm
a
little
behind
schedule,
but
hoping
to
get
all
of
the
community
communications
out
about
the
last
call
status
going
this
afternoon
so
that
we
can
officially
start
that
period
and,
of
course,
we'll
have
a
conversation
about
the
v16
timeline.
But
we
expect
there
should
be
no
real
slowdowns
with
getting
those
approved
and
ready
to
go
by
the
time.
We're
ready
for
the
calibration
at
sync
other
than
that.
The
same
number
of
flip
drafts
exist.
A
Editors
should
continue
to
edit
and
review
what's
there
and
for
the
index
or
advertisement
protocol,
which
was
presented
two
weeks
ago,
we're
trying
to
figure
out
a
way
to
introduce
potentially
a
new
fifth
type
for
standard
for
standards.
Potentially
a
file
coin
request
for
comment,
but
we're
not
quite
sure
what
the
structure
of
this
will
look
like
yet
so
be
on
the
lookout
for
an
upcoming
conversation
topic.
So
we
can
discuss
this
in
greater
detail.
A
All
right
and
parth
do
you
have
any
updates
on
security.
F
Not
much
particularly
working
on
some
bugs
and
also
like
working
on
the
hall
of
fame
page,
which
I
talked
with
jennifer
as
well
like
I
started,
building
the
hall
of
fame
page
and
it
should
be
like
done
by
this
week
or
end
of
next
week
and
I'm
ready
to
make
a
pull
request
as
well.
A
Cool
the
is
the
hall
of
fame
page
for
the
the
bounty
board.
F
F
Yeah
yeah,
it's
just
like
to
add
the
researchers
to
a
hall
of
fame
page,
so
they
also
feel
motivated
to
report
more
in
the
future
as
well
as
they
have
a
proof
of
their
work,
because
you
know
like
they
right
now.
Don't
have
a
proof
that
they
reported
some
vulnerabilities
to
fico
foundation.
A
All
right,
then,
let's
have
a
sort
of
an
open
conversation
then
and
switch
gears
a
little
bit
towards
the
network,
v16
timeline
and
schedule.
I
was
hoping
someone
would
want
to
kick
off
sort
of
your
current
thinking
and
needs,
as
it
relates
to
upcoming
work
or
if
we
want
to
talk
specifically
about
the
timeline.
A
E
Maybe
I
can
kick
us
off
a
little
bit
so,
as
we
all
know,
like
the,
we
have
been
updating
the
timeline
according
to
the
development
progress
and
like
discoveries
a
couple
of
times
now,
so
I
think
right
now,
the
if
vm
team
is
very
confident
that,
like
we
are
super
super
close
to
say
it's
like
consensus,
future
freeze
for
the
fdm
like
the
m1
implementation.
At
this
point,
this
is
like
the
decision
has
been
made
on
top
of
the
fact
we
have
been
going
through
a
couple
rounds
of
internal
outlet.
E
E
However,
we
want
to
simplify
that
a
little
bit,
the
reason
being
we
actually
have
been
testing
more
activities
than
we
saw
in
the
past
like
months,
and
we
think
we
are
confident
enough
to
say
if
we're
confident
enough
to
say
once
the
code
freeze
is
ready
for
fem.
I'm
currently
targeted
at
some
time
the
end
of
next
week,
I
believe,
and
then
we
can
deploy
that
to
butterfly
directly
instead
of
doing
three
weeks
of
testing
in
a
private
developer.
E
E
So
that
being
said,
we
are
looking
at
butterfly
net
sometime
around
like
the
third
week
of
may,
and
we
can
do
all
the
testing
there
for
like
two
weeks
and
in
that
two
weeks
we
probably
will
be
wrapping
up
the
built-in
actor
test
coverage
rally
as
well,
and
we
can
use
those
two
weeks
to
fix
any
bug
that
is
discovered
by
the
tests
by
the
test
that
forwards,
team
and
zen
has
been
writing
and
then,
after
two
weeks
it
depends
on
how
many
discovery
we
have,
if
advocacy,
is
good.
E
We
can
deploy
everything
to
calibration
by
the
end
of,
like,
hopefully
may
early
june,
living
there
for,
like
three
weeks
before
like
midnight
launch,
so
we
are
still
looking
at
the
midnight
upgrade
around
sometimes
like
june,
around
early
mid-june.
Accordingly,
so
I
don't
know
that
that's
the
current,
like
sinking
the
lotus
and
if
fvm
team
has
and
we're
happy
to
hear
what
everyone
else
is
thinking
or
have
any
concerns.
Regarding
that,
oh
and
also
like
I
want
to
be
be
aligned
on
wednesday.
E
Yes,
for
this
upgrade
thanks
again
for
the
forest
team
for
like
supporting
the
whole
test
coverage
like
effort,
but
I
think
only
venus
and
lotus
will
be
joining
all
the
network
upgrades
for
lmv-16.
As
far
as
my
understanding
goes,
but
yeah.
B
Yeah
something
about
the
timeline
so
looks
like
the
butterfly
we're
planning
for
like
in
may
right,
and
I
think
if
everything
goes
well
with
butterfly,
we
will
transition
to
california
by
in
a
couple
of
weeks
after
that,
right.
What's
what
how
many
weeks
you
said,
I
forgot
on
that
one
or
just
different
butterfly.
F
F
E
B
Okay,
okay
yeah,
so
I
guess
like
when
we
migrate
to
butterfly.
We
can
like
keep
the
discovery,
discussion
open
and
you
know,
and
based
on
that
we
will
know
the
timeline
for
calipnet
and
then
again,
based
on
the
open
discoveries.
We
know
for
the
main
maintenance.
So
I
guess
at
this
point
you
know
we
don't
have
very
strict
timelines,
but
based
on
the
discoveries,
we
can
go
there.
Okay,
make
sense.
C
Yeah
so
jennifer,
as
you
mentioned,
it
looks
like
yeah.
The
timeline
is
almost,
as
you
mentioned
in
last
meeting
right
yeah.
As
a
last
meeting,
we
may
target
to
june
the
10th
for
the
main
name
and
upgrade.
E
I
think
last
time
we
said
sometime
june,
we
didn't
see
a
date
because,
like
development
was
unknown,
I
think
the
tense
was
from
the
very
first
proposal
of
like
may,
the
10th,
I'm
not
sure.
Maybe
I
missed
and
I
miss.
I
forgot
something:
okay,.
C
Yeah
so
so
yeah
and
I
got
something
in
my
mind:
okay
yeah,
so
it's
almost
the
same
I
mean
yeah.
I
just
want
to
say
that
and
okay
yeah,
if
there
is
no
change,
that
is
very
good
yeah.
It's
no
problem,
for
you
know,
forbidden
to
to
to
catch
up
is
because
we
are
really
keep
a
very
close
eye
on
the
yeah
fm
and
the
building
actors,
development
and
we're
doing
your
chat
base
to
keep
the
pace
and
that.
A
I
actually
have
a
question
for
you:
jennifer
the
testing
plan,
change
that
you
want
to
incorporate
in
fib
31.
I
I
think
I
missed
what
you
said
about
the
like
certainty
of
this
new
plan.
Has
this
already
been?
It
hasn't
been
added
to
the
31
correct.
E
Not
yet
we're
gonna
get
so
we're
gonna
submit
a
pr
later
next
monday
to
up
to
reflect
a
new,
simplified
testbed.
A
Okay,
that
sounds
good
given
like
the
current
timeline,
we're
discussing.
Also,
it
makes
sense
to
then
wait
for
that
last
call
period
until
next
week.
So
we'll
do
that.
Yep.
G
Yes,
yes,
I
did
just
our
usual
as
we
approach
the
network
upgrade.
Obviously
this
is
this.
One
is
very
fvm
focused,
but
a
couple
of
other
smaller,
potentially
bug
fixes
protocol
level
bug
fixes
that
I'd
like
to
include
really
just
one,
which
is
there's
a
lotus
implemented
a
bug
a
long
while
ago
in
which
in
which
dram
ground
is
used.
G
G
We
wanted
to
test
it
a
bit
more
thoroughly
and
then
just
forgot
about
it,
for
the
snapdeals
upgrade
honestly
I'd
like
to
get
that
into
the
m1
upgrade
just
to
get
it
out
of
the
way
and
yeah
right
right
right
now,
we're
just
using
the
wrong
d-ram
beacon
in
in
fall
point
just
an
off
by
one
and
it'd
be
good
to
clean
that
up.
G
So
I,
if
I
can
lick
the
lotus
pr
in
here,
but
basically
the
change
is
just
to
catch
up
by
one
network
after
the
network
upgrade
yeah
that
and
as
jennifer
mentioned,
the
proof
steam
was
a
new
proofs
release.
I
think
they
were
gonna,
be
changing,
probably
the
the
aggregation
proof
type
so
we'll
have
a
version
1.1
of
smartpak.
I
can
get
them
to
share
more
details
when
they
have.
Those
are
the
two
things
I'd
like
to
add
to
the.
E
And
the
other
one
is
the
one
we
all
know
already.
The
proof
upgrade
updates
bug
fixes
like
the
batch
message
fix,
has
been
landed
in
both
goals
by
catcher
and
future
actor.
So
these
are
the
three
non-trivial
changes.
We're
introducing
in
this
upgrade.
G
We'll
add
them
to
the
tpl
doc,
keeping
it
in
our
heads
for
now.
I
can
do
that
right
now.
A
Going
once
all
right,
then
it
sounds
like
everyone
is
mostly
on
the
same
page.
Everything
is
continuing
as
sort
of
previously
discussed
any
additional
questions,
items
or
anything.
Anyone
would
like
to
bring
up.
A
All
right,
then,
a
relatively
quick
and
easy
meeting
this
week
as
always
feel
free
to
connect
async.
I
think
we're
trying
to
use
the
phil
implementers
channel
on
slack
to
coordinate
core
devs
topics
so
feel
free
to
post
their
ask
questions
or
just
continue
asking
them
directly
on
other
channels
as
well.
Otherwise
we
will
see
everyone
in
two
weeks
and
looking
forward
to
it.