►
From YouTube: Filecoin Core Devs #43 (Meeting 1)
Description
Recording for: https://github.com/filecoin-project/tpm/issues/101
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
welcome
everyone
today.
This
is
core
devs
meeting
number
43
today
is
thursday.
May
19
2022..
A
We
have
a
relatively
small
agenda
today,
so
plenty
of
time
to
talk
about
any
issues
bugs
whatever
it
is
that
you'd
like
to
bring
up
ad
hoc,
but
as
always,
you
will
go
through
updates
from
each
of
the
implementation
teams,
as
well
as
from
the
file
coin
foundation,
touch
on
the
latest
status
of
the
version,
16
network
upgrade
and
then
again
we'll
move
into
that
open
discussion
in
case
you
have
any
topics
you'd
like
to
bring
to
the
rest
of
the
group
so
to
kick
it
off.
A
C
Sorry,
all
right
yeah,
I'm
not
sure
how
to
share
the
the
updates.
I
think,
like
sometimes
some
of
the
updates
you
get
up
from
from
like
previous
cordless
meetings,
but
anyhow,
so
the
last
two
weeks
we
have
been
working
very
hard
together
with
with
wyatt
from
the
golden
team
or
fm
team
on
on
porting,
the
the
go
actor
test
over
into
rust,
and
we
have
in,
like
hundreds
and
hundreds
of
tests
and
found
a
few
mismatches
between
the
the
rust
actors
and
the
directors.
C
This
is
great
and
that
work
is
still
ongoing.
C
Hopefully,
we
are
like
very
close
to
being
being
like
having
a
complete
port
of
all
the
tests,
and
it
should
be
no
more
than
two
weeks,
hopefully
yeah,
and
that
is
about
all.
We
have
been
writing
lots
of
tests
and
doing
pretty
much
nothing.
A
Good
else
is
a
quick
question
from
me:
you're
right,
these
are
older
updates.
I've
still
been
pulling
them
from
the
forest
team
wiki,
and
I
saw
your
update
this
morning
about
all
of
the
testing
that
you're
doing.
I
guess
lee
do
you
want
me
to
keep
pulling
them
from
the
wiki
or
should
I
just
keep
asking
in
slack
what
what's
easiest
for
you
guys.
B
A
D
Not
a
question,
but
I
just
want
to
say
a
very
big
and
very
public.
Thank
you
to
your
entire
team
for
all
of
these
tests.
I
know
zen
and
me,
to
a
lesser
extent,
have
been
overwhelmed,
but
we've
been
overwhelmed
by
having
to
review
all
of
your
work,
which
is
a
great
problem
to
have
yeah.
I
think
this
is
just
like
a
like.
It's
a
really
really
massive
good
for
the
network
that
you
folks
are
giving
so
much
momentum
to
so.
Thank
you
very
much.
A
Yeah
and
on
the
foundation
side
we're
working
with
your
your
biz
dev
team,
also
to
make
sure
that
we
are
providing
you
as
many
resources
as
we
can
to
help
you
continue
with
this
work.
We
know
that
it's
a
lot
of
asks
all
the
time
and
we
want
to
be
able
to
make
sure
that
you
can
do
these
unencumbered
by
logistical
issues,
capacity
etc.
So,.
D
Yeah,
I
can
give
a
quick
update,
I
think
jennifer.
Obviously
a
lot
as
you
can
imagine.
A
lot
of
our
work
is
kind
of
very
closely
with
the
fem
team,
and
I
know
that
we
have
an
fem
update
coming
up
from
jennifer
but
from
our
end,
just
quick
release
numbers.
As
always,
we
shipped
one
fifteen
two
and
started
testing
one
fifteen
three
right
now.
D
One
thing
that
I
do
wanna
call
out
is:
we
were
experiencing
quite
a
few
reports
of
lotus
notes,
having
sync
issues
just
falling
out
of
sync
or
starting
to
slow
down.
It's
not
clear
what
would
cause
them
to
to
kind
of
start
to
happen
more
frequently
than
before,
because
the
first
issue
dates
back
to,
but
we
did
investigate
and
fix
a
deadlock
in
the
the
message
pool,
which
was
ultimately
bubbling
up
to
causing
sync
issues
itself.
D
D
Apart
from
that
yeah
continuing
to
kind
of
sprint
towards
the
network,
v16
effort,
which
you
know
involves
integrating
the
fbm
testing
built
on
actors
and
reviewing
those
pr's,
some
sort,
some
proofs
work,
I
think,
has
been
happening
as
well,
which
we'll
be
integrating
into
b16.
So.
A
Team
all
right,
thank
you.
It's
for
the
venus
team
as
before
the
venus
team
is
not
quite
so.
Heads
is
down
on
the
fvm,
but
they
are
on
track
to
sink
in
caleb
net
in
the
coming
weeks,
when
we
get
there
for
the
most
part,
they
continue
to
work
on
usability
enhancements
to
venus
market,
mostly
in
venus
cluster.
Additionally,
especially
around
just
simple
marketplace:
operations
as
well
as
the
venus
sealer.
A
A
All
right
any
questions
for
anyone
before
we
move
on.
A
All
right
parth:
do
you
want
to
give
us
a
quick
security
update.
E
Yeah
sure
so,
fortunately,
a
couple
of
reports
were
resolved
and
were
paid
so
and
a
couple
of
reapers
are
also
in
progress
to
get
paid
and
also
like,
as
I
told
last
time,
the
hall
of
fame
pages.
We
have
built
the
hall
of
fame
page,
so
I'm
working
with
ishan
for
design
and
the
content
I'm
yet
to
confirm
that
the
content
with
jennifer
first
so
first
welcome.
E
A
All
right,
thank
you
on
the
fifth
side,
lots
of
things
ongoing
at
the
moment
and
also
thank
you
for
all
of
your
patience.
I
was
out
at
a
conference
and
I
got
covered
so
I've
been
on
sort
of
a
reduced
work
schedule
for
the
past
couple
of
weeks.
But,
most
importantly,
as
we
all
know,
all
three
of
the
fvm
fips
are
currently
in
last
call
status.
So
thank
you
so
much
to
everyone
who
is
not
only
working
very
hard,
but
also
very
communicative.
A
As
final
gas
testing
parameters
were
concluded
as
final
auditions
were
pushed
into
those
documents,
they
look
really
great
and
the
last
call
period
has
been
really
quiet
so
far,
which
is
a
good
thing.
No
one
has
big
concerns
or
questions.
I've
already
spoken
with
storage
provider
groups.
Sometimes
they
arrive
with
some
last
minute
things
that
they'd
like
to
discuss,
and
this
time
it's
been
smooth
sailing.
A
We
also
recently
had,
I
think,
raul
and
jennifer
help
to
coordinate
an
additional
review
on
the
gas
parameter
changes
with
the
crypto
econ
lab,
which
is
great.
They
took
a
look
at
it.
A
couple
of
sort
of
flags
around
the
batch
balance
or
changes
that
we
may
see
but
no
concerns,
and
so
nothing
that
we
would
expect
to
slow
down
that
last
call
process.
So
all
of
this
just
means
that,
as
of
the
end
of
next
monday,
we
expect
these
fips
to
be
completely
accepted.
A
There
are
no
other
outstanding
logistical
or
governance
hurdles
that
would
sort
of
slow
this
down
and
so
really
we're
entering
kind
of
the
final
lap
on
the
fvm
fips
other
than
that.
As
you
all
know,
we
have
two
accepted
fips.
Currently,
hopefully
we
can
sort
of
schedule,
an
interim
sort
of
quieter
upgrade
after
b16,
hopefully
put
those
onto
the
network,
but
you
know
that's
sort
of
a
future
consideration.
A
We
have
a
couple
of
open
drafts,
but
nothing
that
is
new
for
any
of
you
to
take
a
look
at
and
do
know
that
in
the
coming
days,
I'm
going
to
push
some
new
documentation
about
how
we
handle
new
fips
standards,
so
sort
of
like
a
file
coin,
request
for
comment.
That's
probably
how
we're
going
to
handle
the
ask
v2
protocol
that
was
presented
two
meetings
ago,
but
other
than
that.
Any
questions
from
anyone
take
a
look
at
the
chat
too.
A
All
right,
then,
I
think
we're
good.
We
are
good.
We
know
we're
good
we're
doing
great
all
right.
Well
then,
let's
keep
going
and
sort
of
have
an
open
conversation
then
about
our
favorite
topic.
The
skier
skyr
network
v16
upgrade,
and
I
am
just
going
to
open
the
floor
to
you
all.
If
you
have
any
topics,
questions
concerns
flags
or
compliments.
You'd
like
to
deliver
about
the
pending
upgrade.
Now
is
the
time.
F
I
think,
there's
something
a
little
bit
like
off
on
the
tentative
timeline
around
like
a
butterfly
upgrade,
but
basically,
as
the
kitty
was
suggesting
that
all
the
flips
are
in
either
acceptance
or
a
last
call
and
raw
just
announced
the
big
news
this
morning
that
we
are
featuring.
Freeze
our
vm,
I'm
gonna.
F
Let
him
speak
more
on
to
that
like
later
on
give
us
everyone,
an
update
but
giving
that
that
ifvm
is
in
future
freeze
and
we
have
already
implemented
all
the
fibs
into
beauty
actor
with
like
for
from
bosnia
globalism.
Forest
teams,
like
effort,
I
think
it's
very
close
to
say
lotus-
will
be
ready
to
release
the
first
rc
with
a
two
weeks.
F
So
it's
not
like
in
june
the
second,
yes,
actually
we're
expecting
rc
very
soon
and
upgrading
the
butterfly
so
that
the
community
can
join
the
test
day
and
to
to
make
it
better
clear.
Obviously
we
are
saying
today
that
rcy
is
going
to
be
the
feature
freeze
for
all
the
repository
that
including
reference
kind
of
implementation,
lotus,
refvm
and
built-in
actor.
We
are
expecting
to
have
more
rxes
and
changing
code
to
incorporating
all
the
bug
fixes
being
discovered
in
the
next
couple
weeks.
F
As
foreign
is
wrapping
up
on
the
beauty,
actor
tax
coverage
rally,
effort,
they
are
funding
critical,
bugs
consensus,
bugs
we
are
fixing
it
we're
expecting
to
discover
more
so
so
so
so,
like
you're
doing
the
whole
butterfly
testing
process.
So
I
would
say
I
would
you
know
I
think,
I'm
comfortable
to
commit
to
a
butterfly
upgrade
sometime
like
next
week
because,
like
we
can
use
this
week
to
testing
on
caterpillar
before
we
we
we
involved
the
community,
but
sometimes
next
week
we
can
start
testing
and
maybe
based
on
the
testing
results.
F
You're
gonna
take
like
two
to
three
weeks
before
we
upgrade
your
calibration
upgrade.
We
do
want
to
do
code
freeze
before
upgrading
to
calibration
live,
so
we
expect
you
know
external
outdoor
internal
audit,
test
coverage
ready
to
be
wrapping
up
before
we
upgrade
our
calibration
and
that
we
will
be
testing
there
for
like
two
to
three
weeks
before
we
fully
launch
our
mainnet,
so
I
would
say,
starting
on
the
first
butterfly
upgrade.
G
All
right,
so
it's
here!
Finally,
here
we
have
called
development
freeze.
As
of
this
morning,
it
has
been
in
the
making
for
for
quite
some
time.
The
last
minute
changes
that
went
into
this
were
tons
and
tons
and
tons
of
cleanup
in
general
and
a
bunch
of
cisco
final
cisco
changes
that
we
wanna
that
we
wanna
make
because
we're
very
conscious
that
the
the
api
of
the
syscalls
that
we
that
go
into
mainnet
now
are
essentially
gonna
also
find
the
protocol
whatever
so
for
forever.
G
So,
if
anybody
wants
to
in
the
future
sing
the
chain
from
skur
onwards,
they
will
need
to
have
an
fem
that
is
able
to
serve.
That
is
exposing
the
same
api
of
the
syscalls
as
we're
going
as
as
we
have
now.
G
So
we
wanted
to
make
sure
that
those
were
clean
and
any
considerations
that
we
had
around
cleaning
up
kind
of
like
the
way
that
pointers
were
used,
the
way
that
cids
were
addressed
and
how,
like
the
safety
of
memory
addressing
and
a
bunch
of
other
things
and
also
error
numbers
that
says,
calls
were
returning
making
sure
that
those
were
properly
structured
and
that
were
that
would
appear
as
well
and
properly
documented.
G
We
wanted
to
make
sure
I
kind
of
like
do
just
a
sanity
check
on
on
everything
to
make
sure
that
we're
ready
to
ossify,
which
is
a
very
weird
thing,
to
say
right.
So
this
is
basically
much
of
what
went
into
kind
of
like
this.
Last
few
days
of
the
development
freeze,
we
have
released
fem100rc
one
and
the
sdk
one
zero,
zero
rc
one
as
well,
so
these
are
kind
of
like
the
two,
the
two
kinda
like
public
entry
points
to
for
actors
and
for
implementations,
so
we're
there.
G
Finally,
this
also,
I
think
this
version
numbering
also
aligns
with
kind
of
like
the
development
roadmap
of
the
fem,
where
we
have
milestone
one.
So
fem1
is
the
one
that
implements
milestone
one.
So
it's
a
lot
more
consistent
than
what
we
had
before
where
fem
was
was
version
zero
for
milestone,
one
and
and
yeah
right
now
we're
doing
the
work
of
integrating
into
built-in
actors
and
built-in
actors
needs
to
be
integrated
back
into
the
conformance
tests
and
also
integrating
into
into
five
point
ffi.
G
These
are
the
last
two
things
left
from
the
release
process
of
the
development
freeze,
but
we're
there.
Basically,
as
of
this.
As
of
this
point
for
m1
we're
going
into
into
bug
fix
mode,
there
are
still
several
audits
ongoing,
both
internal
and
external,
so
we
do
expect
some
some
findings
to
to
come
out
of
there
and
there
have
been
a
few
finding
small
findings
that
we've
already
been
implemented
from
the
external
audits.
So
anything
that
has
been
found
up
until
now
has
already
been
fixed.
G
So
in
the
last
three
weeks
of
the
external
audit,
if
there
are
any
more
findings
that
will
come
in
as
bug
fixes,
we
expect
that
any
of
these
will
come
before
the
calibration
net
upgrade.
So
any
bug
fixes
so
the
version
that
goes
into
calibration
net
should
be
the
final
version
that
is
the
candidate
for
hitting
for
hidden
mainnet,
unless
we
of
course
encounter
anything
something
else
in
calibration
net
and
and
yeah.
G
Besides
that
there
is
the
back
the
the
the
built-in
actors
testing
effort,
that
is
obviously
continuing
in
the
with
the
chainsafe
guys
and
wyatt,
and
a
bunch
of
others
really
doing
an
amazing
amazing
job
there
and
discovering
things.
So
we
do
expect
that
you
know
any
more
discoveries
will
come
before
calibration
net
and
will
be
integrated
in
that
in
that
final
candidate
release.
G
So
that's
the
update
from
ion
thanks
a
lot
for
bearing
with
this
process
and
for
bearing
with
kind
of
like
the
you
know,
the
the
many
the
many
changes
along
the
way
it
has
been.
It
has
been
super
super
exciting
to
work
on
this
and
and
yeah
we're
we're
hoping
to
to
see
it
soon
in
maynet
and
we're
also
shifting
focus
to
m2
as
of
these
days.
F
G
G
Definitely
thanks
a
lot
for
for
that,
for
that
mention,
but
like
it
heads
up
to
to
all
of
you,
especially
to
steph
who's,
not
in
this
call,
as
well,
has
been
kind
of
like
my
my
partner
in
crime
since
the
beginning
of,
like
you
know,
early
times
of
the
fpm,
and
it's
been
super
super
fun
to
share
this
together.
B
A
All
right
well
also,
thank
you
all
for
joining
this
meeting
once
again
and
giving
what
was
an
excellent
efficient
update.
Also,
does
anyone
have
any
other
questions.
A
I
do
want
to
know
also
a
little
forward-looking,
but
jennifer-
and
I
were
also
talking
about
this
last
night
and
to
reconfirm
this
has
been
such
a
big
network
upgrade
and
it's
required
so
much
of
everyone,
as
we
know
after
this,
of
course,
we're
going
to
do
a
dedicated
retro
session
just
to
sort
of
talk
through
this
experience,
planning
challenges,
etc,
gather
your
feedback.
A
We
can
also
do
this
anonymously
if
you'd
prefer
and
just
want
to
make
sure
that
we've
heard
everybody's
sort
of
needs
prior
to
beginning
to
think
about
that
m2.
So,
as
we
look
to
the
next
milestone,
that's
going
to
need
to
be
implemented.
It's
probably
going
to
be
it's
going
to
be
a
big
lift
in
certain
ways
also,
and
we
want
to
make
sure
that
everyone
is
prepared
and
on
the
same
same
page,
so
look
to
that
in
a
couple
of
weeks.
A
All
right,
otherwise,
we
have
no
other
standing
agenda
items.
Is
there
anything
anyone
would
like
to
discuss
before
we
end
the
meeting
today.
F
Yes,
I
do
want
to
like
post
that
we
start
to
talk
about
like
what
is
the
next
network
outbreak
algorithm
gonna,
be
maybe
in
the
next
core.
That
call
because
I
I
know
that
fcm
team
or
like
the
avm
working
group,
is
gonna
start
to
kick
off
like
planning
on
m2.
However,
for
me
is
this
is
my
personal
opinion.
I
haven't
even
talked
to
the
lotus
team
yet
like
for
me
personally.
I
think
it
may
make
sense
for
us,
as
a
you
know,
imprint
implementers
of
the
file
coin.
F
I
want
to
consider
maybe
before
launching
another
like
huge
upgrade
of
like
if
vm
m2,
maybe
we
can
do
incremental
small
network
upgrades
to
tesla
couples
things
all
like,
including
you
know,
implementing
very
small
fips
like
the
benefit
beneficially.
For
example.
That's
in
the
queue
just
like
to
see
how
we
will
be
because,
like
we're
introducing
if
new
vm
new
actors,
the
upgrade
process
is
changing,
as
everything
is
not
cid.
F
Like
you
know,
content
address,
like
all
those
things,
it
will
be
good
if
we
do
a
small
upgrade
just
to
make
sure
we
have
the
new
upgrade
like
processing
place,
make,
for
example,
whatever
we
have
a
new
proof
release,
we
will
have
to
do
the
trusted
setup
and
making
sure
everyone
fetched
the
new
parameters,
proof
parameters
we
now
have
to
do
the
same.
F
I
don't
know
if
I'll
agree,
maybe
you
can
even
introduce
some
like
you
know
things
that
we
know
that
can
be
really
good
efem,
but
we
don't
think
it's
we're
seeing
the
scope
for
m1,
but
also
it
can
be
pre
pre
m2
thing
is
like
we
can
introduce
some
like
guest,
optimization
things
like
that,
which
also
require
like
a
network
upgrade.
Maybe
you
can
do
a
small
one
that
to
introduce
those
factors
before
we
launch
the
big
network
upgrade
to
refactor
or
the
system
actor
or
we
launching
fvm2.
F
So
that
is
like
what
I
am
thinking
and
because
it's
a
small
network
upgrade.
I
do
expect
that
less
that
resources
is
needed
because,
like
after
we
starting
testing
and
why,
in
the
test
network,
basically
that
implementation
teams
can
start
working
on
next
things
like
in
parallel
right
so,
like
I,
I'm
thinking,
maybe
something
around
late
july
or
like
early
like
mid
august,
like
a
very
small
network,
upgrade
just
to
practice
this.
This
is
what
I
am
thinking
literally
just
like
this
morning.
B
Yeah,
I
think
we
can
definitely
start
discussing.
I
think
it's
a
good
idea
to
get
head
start.
I
think
one
of
the
things
that
I
would
like
to
point
out
is
that,
after
the
network
upgrade
and
the
testing,
I
think
our
forest
focus
should
be
getting
in
sync
with
the
network
upgrade.
So
probably
that's
going
to
be
the
next
immediate
focus
for
us,
and
then
we
can.
We
can
move
towards
other
things.
D
Yeah
I'll
chime
in
not
to
just
to
say
I
broadly
agree
with
with
jennifer.
I
think
yeah
there's
just
a
few,
at
least
in
my
mind,
open
questions
about
m2
in
terms
of
essentially
how
much
work
needs
to
happen,
and
so
when
it
might
be
landing,
but
you
know,
I'm
sure,
there's
lots
of
I've
not
been
paying
attention
to
new
flips
that
have
been
open,
for
instance.
D
So
my
guess
is:
there's
probably
a
lot
of
cool
ideas
that
are
that
we
don't
want
to
block
too
long
on
to
lee's
point
about
yeah
us
needing
to.
Obviously,
you
folks
have
switched
to
focusing
on
this
and
like
kind
of
leaving
forest
itself
behind,
so
there's
some
catch-up
time
to
happen
there.
So
we
one
thing
we
could
do
is
focus
or
almost
exclusively
consider
fips,
where
all
of
the
work
happens
in
the
built-in
access
repo
itself,
so
that
the
actual
client
implementation,
client
side
of
things
is
just
integrate.
D
The
new
actors
and
you're
good
to
go.
That
might
be
one
way
in
which
we
can,
you
know,
have
an
interesting
upgrade
without
putting
too
much
work
on
on
the
various
implementations,
because
yeah
we
have
some
catching
up
to
do
so
yeah.
I
think
it's
a
good
time
to
get
time.
To
start
that
conversation,
we
can
maybe
try
to
scope
it
for
our
next
cortex
call.
G
Something
that
we
can
do,
I
can't
commit
that
we'll
be
able
to
do
it
by
the
next
core.
Devs
call
is
to
to
scope
out
potentially
some
of
those
things
that
are
incrementally
incremental
improvements
to
fvm
that
that
are
would
be
prior
to
enabling
upgradeability,
and
we
can
mark
those
and
we
can
like.
If
there
is
enough
we
if
we
see
there
is
like
a
considerable,
you
know
batch
of
things
that
would
make
sense
to
ship.
G
Then
we
can,
we
can
talk,
we
can
take
it
up
and
decide
if,
like
we
can,
we
want
to
batch
those
into
a
fit
and
consider
it
for
inclusion.
For
that
intermediate
network
release.
I
would
also
suggest
that
you
loop
in
alex
north
into
this
conversation,
because
he
had
done
a
bunch
of
prior
work
on
extending
the
programmability
of
actors,
and
that
is
a
100
percent
candidate
of
stuff
that
we
would
want
to
land
on
the
network
before
programmability
lands.
G
So
maybe
there
is
like
some
some
parts
of
that
that
can
be
scoped
for
this
intermediate
network.
F
Yeah
definitely
agree
so,
like
I
also
wanted
to
access.
Like
reiterate,
it's
like
we
don't
the
network
doesn't
have
to
be
big.
Usually
it's
small
things
like
matters
because,
like
my
my
main
proposal
will
be
my
entire
main
intention
will
be
allowing
the
community
and
just
like
to
practice
how
to
upgrade
in
this
new
setup.
F
I
think
it's
very
important
as
like
any
changes
in
the
actual,
like
you
know,
some
strangers
in
the
fm
will
need
a
network
recovery
from
now
on,
the
community
should
be
expected
to
have
to
be
more
responsive
to
support
changes
so
that
the
network
is
more
resilient
and,
like
you
know,
for
all
those
reasons,
but
yeah.
A
All
right,
so
I
think
what
we'll
do
for
the
next
meeting.
Also,
I
will
capture
or
jennifer,
if
you
want
to,
if
you
figured
out,
we
should
capture
some
of
these
preliminary
thoughts
and
preferences
in
the
v17
async
notes
in
the
tpm
repo
and
for
the
meeting
that
we
have
in
two
weeks,
which
will
be
core
devs
44
in
the
beginning
of
june.
All
of
these
sort
of
stakeholders
who
don't
always
attend
this
meeting.
I
will
proactively
ask
that
they
do
so
alex
north.
A
Of
course,
aside
from
the
fifth
that
raul
mentioned,
he
has
a
couple
of
other
fifths
pending
that
are
quite
large
and
are
not
going
to
be,
I
think,
appropriate
for
the
upgrade
that
we're
discussing,
but
I
think
it's
important
that
he
participates
in
these
conversations.
A
Also,
I
want
a
representative
from
the
crypto
econ
lab
to
come
too,
since
they're
going
to
be
monitoring
some
of
the
gas
changes
as
we
introduce
m1
and
prepare
for
m2,
and
I
also
think
more
broadly,
if
there
are
other
researchers
or
folks
who
regularly
submit
fips
who
want
to
come
and
just
sort
of
share
their
feedback
and
ideas.
It
might
be
helpful.
A
Yeah
jennifer's
question:
if
there's
any
community
fips,
there's
no
drafts
right
now,
except
one
was
pushed
this
morning
and
I
haven't
been
able
to
read
it
yet
we
do
have
sort
of
an
unfinished
draft
from
brenda
on
the
sp2
protocol.
We
also
have
the
indexer
advertisement
protocol.
I
think
both
of
these
might
just
be
standards
which
should
be
a
new
fifth
type
that
we'll
introduce
so
not
a
lot
of
work
to
do
there
and
certainly
not
something
that
we
would
have
to
coordinate
around
a
network
upgrade.
A
But
there
have
been
a
couple
of
questions
around
sort
of
you
know:
lending
opportunities,
collateral
changes,
stuff
for
filecoin,
plus
again,
ideas
that
haven't
been
fully
fleshed
out,
but
they
seem
to
reflect
real
needs.
And
so
again
I
think
if
we
knew
that
we
had
space
to
do
a
couple
of
likes
more
simple
fits
as
part
of
an
upgrade.
We
could
just
put
a
little
bit
of
attention
and
focus
on
actually
drafting
these
into
something
a
little
bit
more
cohesive.
F
For
off
a
very
good
point,
it's
like,
oh,
why
you
mentioned
us
protocol,
so
I
actually
do
want
to
discuss
with
the
rest
of
the
team
here.
It's
like.
Do
you
guys
think
like
market
falcon
market
protocol
should
be
a
part
of
the
standard,
all
of
it
all
like
be
included
in
the
flip
process
because,
like
as
many
of
you
have
maybe
already
noticed,
we
have
a
team
in
pl
and
collect
boost
team.
F
They
have
been
working
really
hard
working
on
this
amazing,
like
software
calling
boost
that
is
like
improving
deal
making
progress
and
we
are
suggesting
lotus
users
to
eventually
switch
into
booths
as
their
go-to
market
software
the
same
with.
Yes,
they
are
actually
developing
a
new
gold
fuel
market
like
a
market
protocol
version
two
as
well
so
right
now
in
the
network,
we
are
running
a
gold
fuel
market
for
both
storage
market
and
retrieval
market.
F
However,
boost
has
been
making
huge
improvements
like
into
storage
protocol
and
like
for
that
gold
data
transfer
as
well,
so
they
are
actually
implementing
a
new
protocol
while
implementing
the
reference
implementation-
and
I
just
don't
know
if
that's
something
probably
should
be
standardized
in
the
in
the
like
in
the
fun
queen
market.
Basically,
it's
not
consensus
breaking
or
anything.
However,
if
we
don't
have
a
good
standard,
it's
possible.
Some
kind
of
implementation
cannot
make
deals
with
some
providers
because
they
are
not
agree
on
the
protocol
they
have.
F
However,
we
don't
have
a
good
idea
like
what
should
we
be
standardizing
here,
so
it
might
be
good
for
us
to
start
like
discussing
about
that.
The
same
goes
to
api
standard
because
I
feel
like
aligning
our
aps.
Doctor
is
like
critical
for
fvm
m2,
so
we
have
the
interface.
We
have
the
same
interface
for
that
developers
to
interact
with
the
powerpoint
chat
and
deploy
their
use,
the
contract
and
building
dabs.
So
I
do
think,
like
all
the
implementations
should
supporting
a
common
standard
of
the
apis
there.
B
Yeah
definitely
agree
on
this
one,
because
I
think
it
will
be
also
a
good
if
we
standardize
this
and
help
foreigners
to
consume
the
storage
and
deal
making
module.
I
think
this
could
be
probably
like
an
application
layer-
standardization
rather
than
a
core
layer.
That's
how
probably
we
could
potentially
do
it.
If
there's
an
agreement
on
this.
G
G
Maybe
sometimes
we
have
the
bias
of
just
thinking
that
material
that
is
eligible
for
a
fit
is
only
that
kind
of
stuff
that
actually
changes,
changes
the
consensus
or
affects
consensus,
but
in
reality
the
file
coin
protocol
is
made
up
of
many
pieces
where
the
chain
is
one
of
them
and
the
actors
are
one
of
them
and
the
execution
environment,
like
everything
that
makes
consensus,
is
one
of
them,
but
really
like.
If
we
weren't
able
to
make
deals
in
the
network,
then
then
the
file
coin
network
would
like
not
be
very
useful.
G
F
So
funny
enough
that,
like
I
don't
think
we
actually
have
market
like
a
up-to-date
market
back
within
the
spec
of
alcohol
io.
So
so
I
think,
like
maybe
right
now,
because
still
making
activities
it's
like
growing
as
crazy
in
the
network
today.
So
maybe
it
makes
sense
for
the
foundation
to
push
like.
F
You
know:
marquee
implementation
teams
to
actually
start
to
specking
the
scenes
out
so
that
like
we,
can
actually
work
towards
that
goal
because,
like
I
absolutely
agree
with
you
all
that
it's
critical,
if
we
don't
have
data
in
the
valcoin
network,
what's
the
storage
for
right,
so
so
so
so
that
makes
sense
a
fourth
form
like
pl
inside
of
the
things,
the
team
that
is
working
on
this
year's
boost
a
bad
rock
at
pln
and
they
have
a
public
channel
that
you
can
reach
out
them
to
it's
just
like
boost
so
like
hey
today.
F
If
you
want
to
reach
out
to
their
developers,
it's
dirk
and
anton
who
are
leading
the
project
and
also
hannah
is
also
working.
Hannah
and
archie
is
working
on
the
retrieval
side
of
the
days
and
the
pm
is
brenda.
Brender
lee,
who
created
the
pro
ask
protocol
fifth
and
also
their
em
right
now,
is
jacob.
So
maybe
those
are
the
good
people
to
reach
out
to
you
and
like
coordinate
on
that.
A
Yeah,
that's
really
helpful,
so
thank
you
and
I'm
gonna
follow
up
to
get
their
their
handles
too.
So
I
can
talk
with
them.
I've
spoken
with
the
boost
team
before
but
not
consistently,
and
I
think
this
conversation
is
very
helpful,
but
also
fortuitous,
pushing
some
kind
of
documentation
for
feedback
related
to
how
we
actually
implement
these
any
kind
of
comment,
process
or
standards.
A
There's
like
the
actual
classification
of
what
this
looks
like
and
at
what
level
we're
standardizing,
of
course,
but
then
also,
how
do
we
make
sort
of
decisions
around
standards
and
it
might
actually
be
something
I
think
we
end
up
pushing
to
core
devs,
so
it's
less
of
a
community
review,
even
though
there
will
be
community
participation
and
more
of
something
that
we
confirm
sort
of
the
way
we
have
active
fips.
This
is
something
that
has
been
delayed
because
I've
been
sick.
So
I
do
apologize.
A
We
have
talked
about
this
at
previous
core
dev
schools
also,
so
hopefully
we
can
get
something
soon
and
once
I'm
able
to
push
something,
I
will
circulate
it
with
all
of
you,
because
I
would
love
your
feedback
in
particular,
especially
around
the
specification
of
where
we
actually
draw
the
line
for
what
canon
should
be
standardized.
A
Anything
else
I
think,
we're
near
time.
We
still
have
a
couple
of
minutes.
If
anyone
has
any
other
topics,
I
think
we've
had
some
really
good
conversations
today,
which
is
always
refreshing.
A
Thank
you
guys
so
much
for
participating
raul
thanks
for
coming
and
being
also
helpful,
as
always
josh
thanks
for
joining
welcome
to
the
team,
I
suppose
the
broader
filecoin
ecosystem,
I
think
we're
all
going
to
be
in
touch
quite
a
bit
over
the
next
couple
of
weeks
as
always,
but
if
you
have
any
questions
or
needs,
you're
welcome
to
dm
me
for
help
or
just
flag
them
in
the
fill
implementers
channel,
and
otherwise
I
will
see
all
of
you
again
in
two
weeks
all
right
thanks.
Everyone
bye,
you.