►
From YouTube: Filecoin Core Devs #40 (Meeting 2)
Description
Recording for: https://github.com/filecoin-project/tpm/issues/97
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
Okay,
let's
see
all
right,
and
can
you
all
see
my
screen
all
right.
B
A
Okay,
great,
so
one
welcome
to
meeting
two.
This
is
file
queen
core
devs
number
40..
Today
is
thursday
april
7th
2022.
A
Today
we're
going
to
go
through
standard
updates,
quick
update
items
from
all
of
the
implementation
teams,
as
well
as
the
foundation,
as
well
as
a
reminder
of
sort
of
the
current
status
of
the
v16
network,
upgrade
that
we're
working
towards.
But
there
were
no
open
discussion
points
on
the
agenda
and
none
additionally
were
brought
up
at
this
morning's
meeting
so
happy
to
discuss
anything
that
the
two
of
you
would
like.
But
otherwise
again.
A
I
think
a
quick
meeting
this
week,
because
everyone's
pretty
heads
down
working
on
the
fvm
so
updates
from
the
forest
team
most
of
their
work,
has
been
collaborating
with
the
lotus
team
to
prepare
all
of
the
ref
actors
and
to
be
ready
for
the
fvm
launch.
That's
coming
up
in
the
next
couple
of
weeks.
A
They've
also
really
greatly
improved
their
documentation,
so
they
now
have
a
new
wiki
which
includes
all
of
their
process
materials
as
well
as
their
formal
technical
development
notices
and
links
to
all
of
their
zenhub
accounts.
If
anyone
is
tracking
the
development
work,
they
have
in
coordination
with
others.
A
They're
also
looking
to
join
everyone
on
the
v16
upgrade
as
well,
so
that
should
be
exciting
and,
aside
from
other
bug,
fixes
and
some
additional
calls
that
they're,
adding
into
fujon
currently
they're,
also
going
to
be
presenting
next
week,
a
node
state
compaction
program
that
they're
interested
in
piloting
and
they'll
talk
a
little
bit
more
about
the
research
objectives
and
sort
of
the
technical
specifics
of
that
proposal,
as
well
updates
from
the
lotus
team.
They
did
not
provide
them
in
advance,
but
they
were
relatively
scant.
A
They
have
been
really
heads
down
just
working
on
fvm,
and
that
includes
that
collaboration
with
the
forest
team
to
get
everything
ready
to
go
for
the
upcoming
mainnet
sync
in
early
may
and
for
the
venus
team,
stephen
I'll.
Let
you
tell
us
a
little
bit
more
about
what
you
all
have
been
working
on.
B
Okay,
yeah
and
the
venus
team
is
now
working
on
a
few
things.
West
is
about
to
integrate
the
fm
into
the
venus,
and
we
had
released
optional
version
for
community
to
test,
which
is
the
rc131r1.
B
We
have
two
loads
around
this
yeah
just
release,
which
is
working
very
well,
and
another
big
thing
is
that
velocity
in
hardness
vedas
have
that
io
yeah,
which
is
a
hub
for
resources
for
events
for
programs
to
have
community
to
join
or
their
developers
to
join
us
to
get
together
and
developing
venus
yeah,
and
this
one
is
under
the
help
of
the
falcon
foundation
and
to
do
this,
which
is
very
well
and
and
currently
what
I'm
going
on.
B
The
and
yeah
velas
team
is
also
working
on
the
venus
market,
which
is
and
you're
providing
support
for
multiple
loads
to
store
real
data
and
currently
working
with
a
real
data
service
provider
and
your
file
drive
and
yeah
to
integrate
the
two
parts
and
yeah.
B
More
more
user-friendly
experience
and
default
yeah
for
file
drives
users
yeah,
and
also
we
are
working
on
the
try
to
find
something,
your
first
a
frame
and
early
builder
and
yeah,
because
the
team
have
a
few
people
are
working
on
the
a
film
starting
and
we're
looking
for.
If
we
could
see
the
go
program
could
be
actually
as
a
contract,
and
you
know
to
compile
it
into
the
wasan
and
to
do
something
yeah.
This
is
just
study
just
that,
and
that's
that,
okay
yeah.
That's
all
good
question.
A
No
questions,
but
I
do
have
two
updates
that
you
might
be
curious
about
one
is
that
we
had
discussed
the
venus
as
collaboration
with
the
bloxico
team
and
I've
sent
the
contract
materials
to
the
foundation's
legal
department
to
review.
So
I'll
get
back
to
you
offline
about
that.
The
other
thing
is
that
dragon
mentioned
this
morning
that
in
future,
cordev's
calls
he
is
going
to
provide
updates
about
the
status
of
the
fvm
early
builders
and
foundry
program.
A
A
B
A
Alex
do
you
have
any
questions
for
stephen
or
that
you
want
me
to
relay
to
any
of
the
other
implementation
teams.
C
I
know
I
don't
think
so
that
all
sounds
good.
I
like,
like
of
the
rest
of
the
lotus
team.
I've
been
heads
down
on
fvm
recently.
A
Yeah
sounds
good
all
right,
so
then
no
surprising
updates
from
the
file
coin
foundation
on
the
governance
side,
feb
27th
is
in
last
call,
so
we
expect
it
to
be
accepted
tomorrow.
Fifth,
thirty,
thirty
one
and
thirty
two
are
fvm
fips
we're
watching
very
closely
and
I'm
talking
with
ayush
in
an
ongoing
basis,
so
that
we
can
get
everything
moving
exactly
when
it's
able
to
be
moved
so
waiting
for
gas
parameters
and
may
even
have
them
as
soon
as
the
end
of
this
week.
A
At
least
that
was
the
update
current
as
of
this
morning.
So
best
guess
is
that
we'll
be
able
to
move
into
last
call
for
those
three
sometime
early
next
week.
But
again
this
is
still
tentative,
so
we
will
see
and
just
try
and
stay
on
top
of
it
as
we
move.
A
One
thing
that
has
arisen
is
that
dudley
is
no
longer
with
the
foundation,
so
he
is
no
longer
coordinating
security,
updates,
audits
or
bug
needs.
I
think
alex
you
may
already
have
been
looped
in,
and
I
think
jennifer
mentioned
that
you're
going
to
be
helping
with
some
fvm
audit
requirements,
but
we
have
interim
point
people
at
both.
A
The
foundation
and
harth
shaw
has
joined
us
recently
and
he's
going
to
be
helping
to
cover
for
some
of
dudley's
work
working
alongside
jennifer,
and
then
there
are
a
few
others
in
protocol
labs
also,
who
will
also
be
helping
to
cover
that
work
until
someone
is
hired
to
take
over?
Take
it
over
full
time
again,
so
we're
hoping
there's
no
slow
down,
but
this
is
a
sort
of
a
late-breaking
development.
So
there
will
be
more
information
in
the
coming
weeks
in
coming
days
about
ongoing
audits
so
that
everyone
can
prepare
accordingly.
C
I
have
a
question
while
we're
looking
at
this
slide
about
the
fips.
I
wonder
what
what
do
we
need
to
do
to
get
529
the
beneficiary
address
into
last
fall?
Is
it
still
awaiting
a
final
round
of
technical
review?
I
believe
the
implementation
or
the
prototype
implementation
go,
I
think
is
complete.
A
Sure
I
think
steven
recently
there
was
some
updated
conversation
about
the
complexity
of
either
the
the
approach
or
the
implementation
itself.
Do
you
have
an
update
on
some
of
the
thinking
you
have
around
this
fit
since
it's
yours.
B
Yeah,
okay,
yeah
thanks
alex
yeah
and
okay.
Actually,
this
is
the
question
I
want
to
ask
god:
yeah,
okay,
okay,
great
okay
and
everything
is
done
yeah.
This
one
has
been
discussed
yeah
for
some
time
and
and
alex
and
contributed
yeah
many
ideas
for
this,
and
we
already
have
a
bill
and
yeah
google
implementation
for
this
and
we
yeah.
B
We
can
move
this
to
mastercall
yeah
from
my
point
of
view
and
next
we
will,
which
will
be
in
available
notice
or
other
implementations
after
network
version
16,
I
hope
yeah.
We
will
at
that
time
we
will
and
how
it
implemented
your
last
yeah
but
yeah
for
the
failure
itself.
Yeah.
It's
done.
I
think.
A
Great,
so
I'm
actually
off-site
at
a
conference
all
this
week,
but
I
will
take
a
look
and
if
we
can
move
it
into
last
call
perhaps
on
monday,
then
we
should,
and
so
we
can,
we
can
go
from
there.
Yeah.
A
Yeah
thanks
all
right
and
with
that
we
had
a
few
quick
updates
from
well.
First,
we
have
current
standard
bear
on
network
v16.
These
are
the
sips
are
pretty
confirmed.
We
don't
expect
to
change
these.
Obviously,
however,
the
timeline
is
still
a
little
tentative
because
of
the
status
of
the
audit
and
some
of
the
interim
plans
that
have
been
put
in
place.
So
jennifer
will
be
coordinating
some
of
the
staffing
needs
early
next
week
and
providing
any
update.
A
That
is
a
but
as
always,
the
mainnet
upgrade
in
the
calibenet
sync
may
be
pushed
out
by
a
few
days.
However,
it
will
of
course
not
be
brought
back
so
for
teams
working
on
planning.
Now
you
may
be
given
some
extra
time
and
that
will
be
confirmed
with
you
and
communicated
as
quickly
as
it's
devised.
So
again,
jennifer
will
be
the
point
person
to
provide
those
updates
in
the
next
couple
of
days.
A
And
those
quick
updates
on
some
of
the
fips
that
ayush
gave
us,
as
mentioned
before,
5th
30
and
31,
are
in
final
review.
Fip
fip32
is
very
close
to
having
those
final
gas
parameters,
we're
just
waiting
for
testing
to
be
completed
and
again
as
soon
as
these
are
ready
to
go,
we
will
move
them
to
last
call
so
that
there's
no
delay
or
hesitation
for
the
v16
upgrade
when
it
comes
to
the
governance
process.
C
Thank
you.
I
I
thank
you
caitlyn
for
posting
about
the
you're
clarifying
the
roles
of
core
devs
and
videos.
The
stuff
you
wrote
up.
I
sounded
really
really
good.
It
sort
of
didn't
have
anything
worthy
of
writing.
A
response.
I
sort
of
you
know
it
looked.
C
Need
some
more
time
to
to
bake?
One
observation
that
I
had
is
that
it
seems
to
be,
and
there's
no
judgment,
just
observations
that
we're
so
clear.
C
It
seems
to
be
going
for
a
a
democratic
style
of
community
governance,
in
the
sense
that
there
are
not
some
community
members
who
have
more
authority
or
more
power
than
others.
It
doesn't
explicitly
state
this,
but
it
also
doesn't.
C
It
also
doesn't
doesn't
and
it
doesn't
anoint
any
particular
parties
as
having
more
influence,
and
so,
in
a
sense,
it's
just
my
observation
that
this
is
your.
This
kind
of
governance
thing
everything
is
easy
when,
when
things
are
going
well,
it's
it's
really
about
when
there
are
conflicts,
how
are
they
going
to
be
resolved,
and
so
this
this
this
year,
is
deciding
for
us
how
such
conflicts
are
going
to
going
to
evolve.
C
There's
no
governance
inertia
to
maintain,
maintain
the
influence
of
the
people
who
have
been
involved
in
the
past.
So,
like
I
said,
it's
not
bad
or
good,
it's
very
situational
and,
of
course,
very
subjective
as
to
whether
that's
bad
or
good,
depending
on
you
know
whether,
for
example,
if
you
have
progress
stagnates
and
then
it's
good
that
a
new
guard
come
up
and
take
it
over
and
that
they
there
are
not
many
barriers
to
do
to
do
so.
C
C
Is
you
know,
like
I
say
it's
extremely
subjective
as
to
whether
one
outcome,
or
the
other
is,
is
preferred,
but
by
by
clarifying
these
kind
of
things,
where
setting
the
context
under
which
your
conflict
in
the
future
will
be
determined.
A
Yeah
yeah,
thanks
for
reading
the
like
the
fip
editors
and
core
dev's,
like
role
definition
piece
I'll,
let
it
sit
for
a
few
weeks
and
if
there's
no
other
comments,
we
have
no
new
thoughts
about
it.
Then
we
can
move
it
to
simplified,
more
formal
guidance,
the
resiliency
component
and
like
the
the
balance
between
making
sure
we
have
like
resilient
and
attack
proof
sectors
within
this
governance
framework,
but
that
it
also
maintains
legitimacy
of
decisions
without
having
like
a
codified
group
of
approvers,
etc.
It's
a
really
tough
balance.
A
It's
actually
one
of
the
conversations
that
we've
been
discussing
while
I've
been
at
the
soft
site
with
the
foundation
over
the
last
couple
of
days,
and
it's
one
that
is
one
of
the
more
it's
one
of
the
million
dollar
questions
like.
How
do
we
create
this
balance?
I
think
one
practical
step
forward
and
something
we've
all
sort
of
been
thinking
about.
A
little
bit
is
really
just
what
happens
if
we
get
another
contentious
fip,
so
we
had
one
in
the
fall.
A
A
We
want
to
make
sure
that
if
things
like
this
come
up
again
that
the
voices
of
people
who've
been
here
longer,
who
have
a
lot
of
deep
expertise
in
the
protocol
are
able
to
have
those
voices
heard
and
they
are
able
to
provide
sort
of
a
balancing
agency
over
what
is
being
discussed
versus.
You
know
the
interests
of
community
members
who
may
have
different
vantage
points
happy
to
like
talk
to
you
one-on-one
about
this
too.
A
If
you
have
like
ideas
for
processes,
etc,
but
again
it's
one
of
those
things
that
we
continue
to
think
on
and
work
on
over
time,
and
it
is
on
the
agenda
for
like
clarification
and
thinking,
I'm
already
working
on
a
project
actually
with
the
crypto
econ
lab
about
helping
clarify
and
making
more
resilient
crypto
econ
fips,
because
they
can
be
relatively
sensitive
and
relatively
technical.
But
from
the
vantage
point
of
the
entire
fips
process,
yeah,
it's
it's
tricky.
It's
good.
You
noted
it.
C
I
don't
have
any
significantly
like
better
ideas,
but
yeah
it's
with
us
being
aware
of
how
the
system
is
set
up,
so
that
we
can
work
most
effectively.
A
They
may
not,
because
they're
not
already
familiar
with
the
filecoin
ecosystem,
so
continue
to
write
this
up
so
that
it's
clear
make
it
easier
to
find
update
docs
update
fifth,
one
etc,
but
yeah
think
about
these
macro
structures
a
bit
more
quickly,
yeah
all
right,
there's
nothing
else,
then.
I
think
this
brings
us
to
the
end
of
our
meeting.
A
All
right
well,
then,
thank
you
both
for
joining
I'm
going
to
encourage
the
next
core
devs
call
in
two
weeks,
those
who
are
meeting
one
to
also
join
meeting
two
if
they
can
just
so
there's
more
voices
in
the
room.
If
you
want
to
have
a
technical
discussion,
you're
going
to
need
other
implementers
or
other
core
devs,
so
it's
important
that
they
do
join
if
they
can
so
we'll
see
if
we
can
get
a
better
balance
in
future
meetings.
A
A
Yeah
great
thanks
guys
talk
to
you
next
in
two
weeks.