Core Dev 50 Meeting Notes

Meeting Date & Time: Time: Oct 6, 2022 12:00 AM UTC

Meeting Recording:

Meeting Slides: https://docs.google.com/presentation/d/1Y7AGA-JWxT0F0Spn-BEfVv_JbZQuRz7UqeXRjb9tDWY/edit#slide=id.g151e8882e4b_0_0

Attendance: Protocol Labs, Filecoin Foundation, Implementation teams, and other representatives.

Core Devs are the researchers, engineers, and others whose expertise and work is central to the long-term success and development of the Filecoin protocol.
- Core Devs are asked to discuss technical topics of interests
- Engage with draft FIPS and FIP Authors
- Weigh in on critical network security issues
- Govern the acceptance of FRCs and emergency FIPs
Rules for Core Dev engagement to be further deliberated and jointly agreed on by Core Devs.
- Core Dev Rules and expectations will be posted in the TPM repo for thoughts and comments.
- Having clear definition of Core Dev and engagement expectations will be helpful for the team.

FIP0036 has failed to achieve majority support across voting groups.
- Different stages of retros are planned
- Currently working through planning an in person retro for internal stewards
- Async feedback surveys and retros possible async and virtually
How do we do deeper dive into the understanding what went into FIP0036 and possible undeerstanding of
- Planned retros are related to governence process and not context analysis and perceived needs
- Seperate feedback process can be planned for a deeper dive into different perspectives various sub-sets of groups had on the proposal. It should be different from the retro planned on the governance process.

v17 mainnet upgrade is tentatively scheduled for November 10.
- Butterfly upgrade has started
- First Lotus nv17 rc scheduled for October 13
- Calibnet upgrade scheduled for October 20

Led by Steven Allen
Discussion post
This FIP adds an extensible address class, f4, to support the creation of new user-defined actor addressing schemes
This FIP adds the ability to send funds to such an address before deploying an actor there. As of today, it's possible to send funds to an account (f1 or f3) that doesn't yet exist on-chain, but there's no way to send funds to a non-account actor (e.g., a multisig actor with an f2 address) that doesn't yet exist on-chain.
Chats in the FIPs repo have been linked to the draft, Core Devs are encouraged to review, add comments, questions etc.