v17 Network Planning

Suggested & Potential FIPs

All of the below represent FIPs that have previously been discussed by Core Devs as priorities for v17. The below list is entirely tentative; any implementation is dependent on Core Dev confirmation of network scope, as well as community acceptance.

Only FIPs indicated with an asterisk () have achieved community acceptance.*

FIP0029 - Beneficiary Address for Storage Providers*

FIP0034 - Fix PreCommit Deposit Independent of Sector Content

FIP0035 - Support Actors as Builtin Storage Market Clients

FIPXXXX - Decoupling FIL+ from Marketplace

FIPXXXX - Forward Compatibility for PreCommit

FIPXXXX - Introducing a Sector Duration Multiple for Longer Term Sector Commitment

FIPXXXX - Signature Domain Separation

Instructions

  1. Review each of the above FIPs.
    1. All FIPs- except for ‘Forward Compatibility for PreCommit’- have already been presented to Core Devs. Please reach out to Kaitlin if you’d like help finding a specific FIP presentation.
  2. Complete your team’s table under v17 Scope & Capacity Planning
    1. Under ‘Implementation Needs’, please add a high-level overview of what your team will need to do to prepare this FIP for inclusion in v17.
    2. Under ‘Team Capacity’ please list any notes or concerns you have incorporating this into your team’s current development roadmap.
    3. Under ‘Prioritization’, please indicate on a scale of 1-5 (1 being not interested, 5 being necessary/critical to include) whether or not this FIP ought to be included for v17.

v17 Scope & Capacity Planning

Venus

FIP Implementation Needs Team Capacity Prioritization?
FIP0029 - Beneficiary Address for Storage Providers buildin-actors change, some UX addition Implemented in go by Venus. Porting to buildin-actors in rust. In progress 3
FIP0034 - Fix PreCommit Deposit Independent of Sector Content pure actor change, will PR and review 4
FIP0035 - Support Actors as Builtin Storage Market Clients actor changes and related change in Venus 1 eng. * 1 mo. 4
FIPXXXX - Decoupling FIL+ from Marketplace to follow lotus change on actors, ad Venus-Market will change accordingly 1 eng. 1 mo. 4
FIP0041 - Forward Compatibility for PreCommit actor change and client support 1 eng. 3 weeks. 4
FIPXXXX - Introducing a Sector Duration Multiple for Longer Term Sector Commitment Implementation is not complicated, but may impact other changes above, and there are too many arguments there 1
FIPXXXX - Signature Domain Separation not difficult, not urgent 2

Lotus

FIP Implementation Needs Team Capacity Prioritization?
FIP0029 - Beneficiary Address for Storage Providers can use client impl ux suggestions / PR if the FIP is accepted & actor code is implemented by other teams, we can support the feature in lotus 2
FIP0034 - Fix PreCommit Deposit Independent of Sector Content pure actor change = CNL will PR, we will review 5
FIP0035 - Support Actors as Builtin Storage Market Clients 1 eng - (Details see here) 5
FIPXXXX - Decoupling FIL+ from Marketplace close review feedback loop with protocol devs across prototyping & work toward finalizing the FIP 1 eng 1-1.5mo - (Details see here) 5
FIPXXXX - Forward Compatibility for PreCommit need actor implementation, and client support suggestion 5
FIPXXXX - Introducing a Sector Duration Multiple for Longer Term Sector Commitment 1-2 (not in lotus h2-q3 backlog atm. so very low priority for us - also seems like “what does it bring to Filecoin network, & impact to existing Filecoin security & participants” is unclear yet, so not sure if this is an FIP that we’d accept before nv17 even
FIPXXXX - Signature Domain Separation 3-4

Forest🌲

FIP Implementation Needs Team Capacity Prioritization?
FIP0029 - Beneficiary Address for Storage Providers Change actor interface inside Forest Same as Lotus - If other teams implement it, we can support on the feature on Forest 4
FIP0034 - Fix PreCommit Deposit Independent of Sector Content Change actor interface inside Forest If other teams implement it, we can support on the feature on Forest 4
FIP0035 - Support Actors as Builtin Storage Market Clients May require changes to logic in Forest regarding the new actor methods. If other teams can implement the new actor, it will be easier for Forest to support it 4
FIP0041 - Forward Compatibility for PreCommit May require minor logic changes on Forest end 90% of the logic change is outside on the Forest 3
FIPXXXX - Decoupling FIL+ from Marketplace The FIPs don’t seem ready 2
FIPXXXX - Introducing a Sector Duration Multiple for Longer Term Sector Commitment The FIPs don’t seem ready 1
FIPXXXX - Signature Domain Separation The FIPs don’t seem ready 2

Other FIPs

These FIPs are those that 1) have not been formally discussed by/with Core Devs, or which 2) are in earlier stages of development. Nevertheless, implementers should be familiar with these proposals and should consider whether these topics deserve additional resources and/or should be considered for v17.

Priority review for these FIP topics will also be added on a 1-5 scale, as above

FIPXXXX - New API for Built-In Actors Accessible to User-Programmed Actors