Filecoin Core Devs 82 Meeting Agenda

[Tanisha-fil]

🧠 Core Devs Call #82 — Community Agenda
📅 Thursday, August 7, 2025
🕗 7:00–8:00 PM GST
🔗 Zoom Link: Join Meeting
👩‍💼 Moderator: Tanisha Katara

Core Devs 82 Presentation: Click Here

🌍 Timezones
🕗 GST (UAE): 7:00 PM – 8:00 PM

🕓 CEST (Europe): 5:00 PM – 6:00 PM

🕘 IST (India): 8:30 PM – 9:30 PM

🕛 UTC: 3:00 PM – 4:00 PM

🕙 ET (New York): 11:00 PM – 12:00 PM

🕘 PT (California): 8:00 AM – 9:00 AM

📌 Agenda Overview

1. 🎉 Welcome Back to Core Devs
   Meet the new Head of Governance, Michael Madoff

Moderation by Tanisha Katara

2. 📢 Latest Status on FIPs
   ✅ FIPs in Last Call:

FIP-0105: Add Support for EIP-2537 in the FEVM

FIP-0103: Remove ExtendSectorExpiration Method

FIP-0106: Remove ProveReplicaUpdates Method

FIP-0107: Implicit Messages in Block Receipts

FIP-0077: Add Cost Opportunity for New Miner Creation (Last Call completed)

📦 FIPs Backlog Cleanup:

FIP-0016: Pack Arbitrary Data in CC Sectors — Rejected

FIP-0039: Message Replay Protection — Rejected

📣 Pending Core Devs Discussion:

FIP-0064: Add Parameters to Base Fee Mechanism

3. 🚀 NV’27 Network Upgrade Planning
   🧊 Code Freeze by end of August

🧵 Queued FIPs for Upgrade:

FIP-0105

FIP-0103

FIP-0106

FIP-0077

FIP-0107

FIP-0101

FRC-0108: Support for F3-Aware Snapshots

4. 📊 FIP-100 Committee: Progress & Metrics
   Review of FIP-100 rollout via new data KPIs

Deep dive into sector economics, fee modeling, gas usage, and renewal behavior

Early signal indicators on token economics and grace period behavior

💬 Why You Should Attend
Contribute feedback on high-impact protocol upgrades

Hear directly from governance and engineering leaders

Stay in the loop on what's coming with NV’27

Shape how FIP-100 evolves through community input

📣 If you want to discuss specific agenda points, please mention them in this thread. See you all soon!

[BigLep]

@Tanisha-fil : a couple of thoughts when quickly looking at this:

1. For https://github.com/filecoin-project/core-devs/blob/master/Core%20Dev%20Meetings/Meeting%200082, can we add the .md suffix like the other docs in that folder. That will cause it to render nice in github too.
2. Rather than directly push, maybe create a PR? That way it can accumulate any comments / corrections over a day or two including getting the recording link? The PR being merged would also allow the automatic closing of this issue.
3. After the meeting, can the issue for the next meeting get opened so additional topics (or action items from the last meeting) can be copied in? For example, totally minor I want to propose in next meeting that Add Aryan to Core devs list + fix ordering #198 get handled (which may just mean discarding).

[Tanisha-fil]

1. Resolved. Thanks for pointing that out
2. Just so that I understand this well, are you suggesting that I use the “Edit” button on the file but select “Create a new branch for this commit” instead of “Commit directly to the master branch"?
3. For the next Core Devs meeting, I generally share an open agenda thread in #core-devs and #fil-fips slack channels. In that, anyone can recommend agenda items for the next meeting. Would that help?

[BigLep]

are you suggesting that I use the “Edit” button on the file but select “Create a new branch for this commit” instead of “Commit directly to the master branch"?

Yeah, that's right. Creating a PR like you did for #200 I think is a good prtactice.

For the next Core Devs meeting, I generally share an open agenda thread in #core-devs and #fil-fips slack channels. In that, anyone can recommend agenda items for the next meeting. Would that help?

Sure, that works. Ideally that would be documented (e.g., FAQ entry on "how to propose a topic for next core dev"). Given a github issue is going to get created anyways though for the meeting, I think it's probalby easier just to create it right after the last meeting and it's a natural place for parties to find or augment the agenda. Your call though.