This is a plan for implementation of a bunch of network changes that the PL Lotus and Cryptonet teams propose for nv17. Without a concrete plan, we have been lacking ability to make decisions about what to prioritise and when to target completion.
Items below are still subject to network governance process, which will ultimately decide on the upgrade scope. However, most items are dominated by changes to built-in actors or the FVM, so require little effort from node implementation teams.
Preparing for FVM M2
A chief constraint of scope for this upgrade is to get out of the way to provide space for FVM M2-EVM to have a space to deploy in a network upgrade in late 2022. I have assumed this is a reasonable possibility for that team.
If FVM-M2 is not projected to be ready for a 2022 upgrade, then there is a good opportunity to get more into nv17 (as the only remaining upgrade in 2022). In particular, we could pull the programmable storage market architecture into scope, which would greatly expand the scope of user-programmed storage-related actors/contracts after M2.
FRCs
The list below only includes items subject to network governance (i.e. FIPs). However, some of the items also enshrine a calling convention for native actors, which would otherwise be only an FRC. So setting on FRC-0042 is an implicit pre-requisite to those items.
Background
Value: High
Actors effort: Small (implemented, needs tests) – IPFSForce
Node effort: Small (just UI)