Core Devs 46 Meeting Agenda

[kaitlin-beegle]

Filecoin Core Devs Meeting 46 Agenda

• Meeting 1 Date & Time: Thursday, June 30, 2022 @ [16:00 UTC] (https://www.timeanddate.com/worldclock/converter.html?iso=20210903T180000&p1=1440)
• Meeting 2 Date & Time: Friday, July 1, 2022 @ [00:00 UTC] (https://www.timeanddate.com/worldclock/converter.html?iso=20210903T180000&p1=1440)
• Meeting will be recorded.

Agenda

• Discussing updates, hurdles, questions, and challenges from Filecoin implementations:
  • Lotus
  • Forest
  • Venus
• Updates from Filecoin Foundation
• Core Devs Discussion of v16 Skyr Network Upgrade Timeline
• Core Devs Discussion of v17 Network Upgrade Timeline https://github.com/filecoin-project/tpm/discussions/91
• FIP Presentation: Sector Duration Extension Multiplier
• Q&A

[arajasek]

Lotus updates:

• Shipped v1.16.0 which supports network v16!
• Fleshed out our H2 roadmap, which includes:
  • Supporting new FIPs in future network upgrades
  • Bringing major improvements to the Lotus miner
  • Shipping splitstore, which brings a major boost to performance and online Garbage Collection

[arajasek]

I'd also like to discuss whether we can organize a collective call to function as a virtual war room during the M1 upgrade. It'll be great to have a diverse group of folks online, given that this upgrade relies on new code from the Forest team, FVM team, proofs team, as well as all the impls themselves. We might need different folks to troubleshoot in case things go wrong.

(and if everything goes well, we can pat each other on the back)

[steven004]

Venus updates:

• Shipped Venus suite to support Network v16!
• Venus-market update to support all storage and retrieval function
• Venus STM work in progress
• go-fvm-sdk: completed code generation tool to support user quick-start of actor programming.

[steven004]

One thing to mention, there is one API name change again: BeaconGetEntry=>StateGetBeaconEntry . It is understandable there must be a reason. At the same time, an API change might result in some tools or other modules in the ecosystem to change.

I would suggest we set up a mechanism for API change discussion/notification, and this might be needed be in the release notes.