Skip to content

Commit 976cc8a

Browse files
Create Meeting 0078.md
1 parent 8962dfd commit 976cc8a

File tree

1 file changed

+51
-0
lines changed

1 file changed

+51
-0
lines changed

Core Dev Meetings/Meeting 0078.md

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
# Core Dev Meeting #77
2+
3+
**Meeting Date & Time:** Friday 6, March 2025 00:00 UTC
4+
5+
**Meeting Recording:** See README
6+
## Overview
7+
- **FIP-100 Proposal:**
8+
- Removes the **batch balancer** and introduces a **new sector onboarding fee**.
9+
- Aims to **stabilize gas costs** and improve predictability for storage providers.
10+
11+
- **Current Status:**
12+
- FIP-100 is in **Last Call** with an extended deadline until **Tuesday of next week**.
13+
- Some **APAC storage providers** and other stakeholders have raised concerns about the proposed fee structure.
14+
- Governance discussions are ongoing to determine **whether adjustments can be made** to address these concerns.
15+
16+
## Key Discussion Points
17+
- **Community Feedback & Governance Challenges**
18+
- While there is **not universal disagreement**, some storage providers have **raised concerns** in the **Storage Provider Working Group** and GitHub discussions.
19+
- Core governance challenge:
20+
- Determining **when consensus is reached** while balancing **efficiency vs. endless revisions**.
21+
- Ensuring the **final model is fair** and practical for adoption.
22+
23+
- **Proposed Adjustments & Considerations**
24+
- Exploring **minor refinements** to improve acceptability without **significant design changes**.
25+
- Some stakeholders have suggested a **trial period** with ongoing performance monitoring.
26+
27+
- **Historical & Predictive Data Requests**
28+
- Request to **model historical onboarding fees** under the new system to assess impact.
29+
- Discussion around whether **back-testing onboarding fees** could provide additional insights.
30+
31+
- **Governance & FIP Review Process Improvements**
32+
- Proposal to introduce **formal post-implementation reviews** for major FIPs.
33+
- Suggestion to define **clear success metrics** within the FIP itself.
34+
- Encouraging governance **transparency and participation**, including the right to propose **FIP rollbacks** if necessary.
35+
36+
## Next Steps
37+
- **Last Call extended until Tuesday** to allow for additional feedback.
38+
- **Governance team to review** pushback and determine if consensus is met.
39+
- **Potential Core Devs meeting next week** to finalize the decision-making process.
40+
- **Final decision framework:**
41+
- If objections persist, governance may **reject the FIP or make further refinements**.
42+
- If **broad acceptance is reached**, proceed with implementation.
43+
44+
## Call to Action
45+
- **Community members & stakeholders:**
46+
- Continue **engaging in the FIP-100 discussion** on GitHub.
47+
- Provide **data-driven feedback** to help evaluate potential adjustments.
48+
- **Governance team:**
49+
- Prepare a **clear review process** to determine FIP-100’s readiness for approval.
50+
- **Core Devs:**
51+
- Stay engaged for potential **follow-up meeting on Tuesday** to assess final consensus.

0 commit comments

Comments
 (0)