►
From YouTube: Filecoin Core Devs #43 (Meeting 2)
Description
Recording for: https://github.com/filecoin-project/t...
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
Get
started
all
right
and
welcome
everyone
to
this
call.
This
is
falcon
core
devs
number
43
meeting
number
two
and
today
is
thursday,
the
19th
of
may
2022..
A
So
we
do
have
a
smaller
agenda
today,
I'm
just
going
to
go
through
implementation
updates
and
then
share
sort
of
the
latest
planning
around
the
v16
network
upgrade
and
the
fbm,
and
if
either
of
you
want
to
bring
up
any
additional
topics
to
chat
just
sort
of
openly
about
or
raise
questions
for
some
of
the
other
implementers.
You
can
do
that
as
well.
A
So
I
think,
in
terms
of
updates
for
both
the
forest
and
the
lotus
team
this
week,
they
both
have
been
working
really
closely
together.
Some
of
these
updates
from
the
forest
team
are
a
little
bit
old,
just
based
on
their
latest
community
updates,
but
really
what
both
teams
have
been
really
focused
on
is
testing
for
the
ref
built-in
actors
and
also
planning
for
the
fbm.
Obviously,
so
there
are
hundreds
of
tests
that
have
been
queued
to
be
performed
or
have
already
been
performed.
A
B
Okay,
yeah
for
vsteam
we're
almost
focusing
on
the
various
market,
part
for
the
zero
data
and
storage
energy,
so
yeah
in
last
two
weeks
we
have
done
the
various
max
and
high
availability
and
deployment
yeah.
The
coding
is
completed
and
we're
working
on
the
testing
right
now
and
also
we
have.
The
velocity
supports,
object,
storage,
yeah
so
that
yeah
for
our.
Therefore,
for
the
storage
providers
they
use
in
the
best
package,
they
can
use
different
kind
of
storage
type
and
yeah.
B
Generally,
the
file
consist
the
file
system
or
objects,
storage
and
some
others
will
support
the
drug,
and
we
are
also
on
the
progress
to
use
with
us
clusters
to
to
replace
the
yeah
stainless
we
used
before
and
now,
whereas
back
yeah,
breast
cluster
and
just
suppose
a
separate
winning
poster
and
window
post
so
that
we
could
have
user
post
outsourcing
and
we'll
have
some
I'm
going
past
yeah,
especially
it's
on
the
afm
and
the
next
version
and
yeah
16,
and
running
some
testing
and
we're
still
working
on
the
google
f3m
sdk
integration
with
rdf
fm
tester
for
unit
testing
and
which
is
also
very
important
part
for
us
to
continue
develop
the
google
ffm
sdk.
A
Yeah
thanks
for
your
overview,
it's
also
really
helpful
for
making
sure
that
we
have
really
complete
meeting
notes
for
all
of
the
cordex
calls.
So
this
is
great
on
the
foundation
side.
We
have
no
security
updates
at
the
moment,
parth
is
continuing
to
work
with
jennifer
and
molly
mcinlay
to
make
sure
all
security
needs
and
audits
are
covered
and
also
to
run
the
file
queen
bug
bounty
program.
A
So
if
you
have
any
questions
about
that,
I
can
put
you
in
touch
and
on
the
governance
side,
we
have
a
lot
going
on,
but
slowly
so
obviously,
two
accepted
fips,
fifth
27
and
29,
as
well
as
the
three
fvm
flips,
which
are
currently
in
last
call
through
next
monday.
Fortunately-
and
as
we've
kind
of
hoped,
these
tips
have
been
really
quiet.
A
A
Additionally,
the
crypto
econ
lab
did
go
and
review
some
of
the
new
gas
parameters
that
were
introduced
in
fifth
32
and
noted
that
they
would
sort
of
monitor
changes
to
the
batch
balancer,
also
to
make
sure
they
remain
sustainable,
but
that
there
were
no
concerns
that
they
had
at
face
value
about
this
step
moving
forward,
so
nothing
was
introduced
which
would
change
that
last
call
period
and
again.
A
This
is
one
of
sort
of
those
final
hurdles
to
making
sure
that
we're
ready
to
go
for
the
v16
network
upgrade
other
than
this
alex
decided
to
merge.
One
of
your
drafts-
it
was,
you
know,
mostly
complete
in
terms
of
like
initial
review.
Lots
of
work
still
to
do
but
made
sense,
and
on
top
of
my
list,
is
putting
for
together
some
documentation
on
what
we
ought
to
do
with
new
proposed
standards,
so
potentially
the
ask
v2
protocol,
but
also
the
indexer
advertisement
protocol.
A
C
No
thanks
sounds
great.
We
can
update
the
the
fib
number
in
this
slide
for
next
time,
because
you
get
you
get
me
a
fit
number.
I
think
34
for
set
pre-commit
deposit
when
you
merge
the
draft.
C
Yeah
I
expect
to
have
more
of
the
like
the
frc
type
things
coming
as
well,
so
I'm
looking
forward
to
sort
of
the
discussion
about
that.
That's
been
prompted
by
the
the
indexer
advertisement.
Protocol
I'll
have
some
of
the
traditional
sort
of
erc
types
for
token
standards
and
things
that
will
happen
within
the
vm.
A
Yeah,
I
want
to
kind
of
look
up
to
some
of
the
yeah,
so
there's
going
to
be
two
things
that
we're
going
to
need
to
broadly
decide
as
a
group.
One
is
obviously
the
governance
of
these,
these
new
types
of
type,
these
new
types
of
fip
types
right.
So
how
do
we
actually
approve
what
a
standard
is
and
how
do
we
document
it?
But
the
other
thing
is
deciding
at
what
level
we
decide.
Something
ought
to
be
codified
as
an
official's
network
standard.
A
So
we
discussed
a
little
bit
this
morning
about
sort
of
what
it
would
mean
to
do
this
at
the
application
level
and
if
you
have
questions
or
want
to
sort
of
see
how
that
discussion
went
it'll,
be
reflected
in
the
documentation
that
I
post,
which
will
obviously
be
for
everyone
to
provide
their
feedback
and
ideas
about.
A
All
right
so
otherwise
the
only
other
discussion
we
had
really
had
to
do
with
network
version.
16.
raul
was
able
to
join
us
this
morning
and
had
some
really
great
feedback
about
some
of
the
progress
to
date
and
some
of
the
ongoing
work
that
their
team
is
really
focused
on
right
now.
So
do
again
take
a
look
at
the
meeting
notes
if
you
want
to
sort
of
understand
how
they're
thinking
about
the
next
couple
of
weeks.
A
But
again
the
fdm
code
freeze
happened
just
this
morning
in
the
united
states,
and
so
the
lotus
team
said
that
they're
going
to
release
butterfly
net
sometime
in
the
next
two
weeks.
So
right
now
for
the
tentative
timeline
we
have
june
june
2nd.
This
is
the
latest
date
by
which
butterfly
net
would
become
available
to
internal
testers.
A
But
really
jennifer
said
that
sometime
next
week
is
probably
when
it
would
become
available
for
the
first
time,
so
we're
still
looking
at
the
same
upgrade
timeline
tentatively
scheduled
for
the
end
of
june,
but
we're
really
kind
of
holding
back
an
exact
date.
Yet,
since
there
are
some
sort
of
moving
pieces
that
may
still
change
that
by
a
day
or
two.
B
So
yeah
about
okay,
two
weeks
for
the
butterfly
and
about
two
weeks
for
the
calibration
and
at
the
end
of
july
june,
okay,.
B
A
Good,
we
want
to
make
sure
too
that
even
as
I
mean,
I
know
that
your
sort
of
dependencies
on
the
fvm
are
not
nearly
as
intensive
as
some
of
the
other
teams
steven.
We
want
to
make
sure
that,
even
as
they
tend
to
drive
a
lot
of
the
upgrade
schedule,
this
time,
that
you
still
have
certainty
about
when
you're
going
to
be
expected
to
provide
release,
candidates
or
anything
else,
so
jennifer-
and
I
are
both
working
together
to
quietly-
add
updates
consistently
to
the
thread
in
the
tpm
repo
about
the
latest.
A
Thinking
about
the
exact
dates
again,
they
do
continue
to
change
every
couple
of
days.
But
if
you
ever
feel
like
you
really
need
something
a
little
bit
more
certain.
You
can
find
them
there
or
reach
out
to
either
of
us,
and
we
can
point
you
in
the
right
direction,
but
I
think
for
now
we're
going
to
focus
just
on
getting
the
release
of
the
butterfly
net
and
then
nailing
down
the
exact
calibenet
date
and
hopefully
main
net
update
at
the
next
meeting.
B
Okay,
so
yeah
since
okay,
this
is
a
virtual
machine
changes
and
perhaps
there
yeah,
I
wasn't
okay
one
month
is
enough
for
people
to
upgrade
their
customized
yeah
chain
service
application.
B
For
me,
one
thing
I
could
think
is
about
the
besides
of
the
velas
itself,
and
we
are
also
need
to
upgrade
the
fire
sky
actually
yeah,
because
our
files
came
back
and
actually
had
done,
some
code
change
in
the
chain,
service
level,
yeah
and
also
in
the
virtual
machine
itself,
because
you
want
to
get
more
information
from
the
message.
The
processing
itself.
C
A
Let
us
know
if
you
need
support,
you
may
only
need
you
may
need
more
time,
obviously,
for
this
upgrade
cycle,
because
the
execution
layer
is
changing,
jennifer
proposed
and
we're
going
to
discuss
this,
I
think,
hopefully
with
a
broader
audience
in
two
weeks
time
what
a
version
17
upgrade
might
look
like,
and
it
seems
that
people
feel
pretty
strongly
about
doing
a
smaller
upgrade
sometime
in
july
or
early
august.
A
That
is
a
community
upgrade
such
as
something
smaller,
much
more
lightweight
it'll
give
implementers
an
opportunity
to
take
a
look
at
some
of
the
fips
that
exist
and
sort
of
see
what
the
priority
might
be
and
to
really
sort
of
allow
community
members
to
practice
upgrading
materials.
So
that
might
be
an
opportunity
too,
for
you.
B
Okay,
yeah
yeah,
we
can
discuss
more
offline
and
about
you
know
some
other
path,
perhaps
especially
before
yeah,
and
also,
for
example,
for
the
yeah
for
the
chain
chain-
browser
yeah,
for
example,
the
first
scan.
I
would
think
that
we
need
to
support
more
features,
for
example,
where
we
have
the
user
programmable
actors.
B
So
perhaps
you
need
to
show
the
different
actors
and
their
message
and
we
need
to
have
an
api
to
lead
people
to
use
the
yeah
they
explorer
to
yeah
get
some
information,
something
like
that,
and
so
there
there
could
be
some
new
features
to
debut
yeah
to
be
developed
to
support
this
and
that's
what
we
okay,
I
I
think
we
can
discuss
offline
and
we
can
have
a
proposal
and
say:
okay,
how
could
we
support
and
to
have
this
implemented.
A
That
sounds
great,
so
we'll
coordinate
as
as
we
usually
do
all
right.
Well,
otherwise,
we
had
no
other
discussion
topics
for
this
week.
This
morning's
meeting
was
also
quite
quick.
There
was
some
good
discussion,
though
again
it
will
all
be
in
the
meeting
notes
and
in
the
recordings,
but
is
there
anything
else
that
either
of
you
wanted
to
bring
up
publicly.
C
A
All
right,
well,
I
guess,
as
always,
thank
you
guys
for
taking
the
time.
I
know
it's
still
morning
for
you
both,
but
you
can
have
back
the
rest
of
your
hour
and
we
will
see
you
again
in
two
weeks
time.