<aside> ‼️
The FIL implementer call notes are public, unpublisized security issues shall not be disclosed in this doc.
</aside>
| Team/Area | Section Owner | ⬅️Updates Since Last Meeting | ➡️Upcoming Plans |
|---|---|---|---|
| 🐈 FilOz | @Anonymous | • Released v1.38.3 with the Go fix for the publicly disclosed certificate issue. Release notes | |
| • builtin-actors: Merged reward-stream recipient validation to prevent payouts becoming stranded in singleton builtin actors. Awaiting a future network upgrade. #1805 | |||
| • FIPs: FIP-0119’s 10-year sector-lifetime draft merged with security analysis and implementation guidance. | • Roll out wasmtime 48 (inn progress - tracking issue) | ||
| • Finishg closing out nv29/solstice (removing old code, operationalizing watchtower) | |||
| • Looking at sate cleanup and migration time cleanup improvements. Will have a tracking issue/update next wek. | |||
| 🌳 Forest | [email protected] | • peer visibility & connectivity improvements | |
| • continuing work on block producer tests | |||
| • see here for latest monthly update https://github.com/ChainSafe/forest/discussions/7818 | |||
| 🪚ChainSafe Infra | [email protected] | ||
| 🌞 Venus | [email protected] | ||
| 🤔 Curio | [email protected] | ||
| StorSwift (lotus-miner, Boost) | |||
| ⚖️ Governance | [email protected] | https://thatguyllc.github.io/fips-dashboard/ | |
| 🔐 FF Security | [email protected] | refining red team agent with console UI. |
Working closely with filone team for doing more runs.
fixing issues found by Red Team Agent in Implementations.
Bug bounty reports coverage. | 1. Launching red team agent to dev teams. 2. Duplicate handling via bounty triage agent |
Add agenda items here
https://github.com/filecoin-project/core-devs/discussions/228#discussioncomment-19073165
| FIP/FRC | Link | FIP Stage | T-shirt Size | Priority | Notes |
|---|---|---|---|---|---|
| 🟡 FIP-0119: Increase maximum sector lifetime to 10 years | FIP-0119 · Discussion #1291 | Draft · New; candidate for NV30 (no deferrals) | S | Needs agreement on the FIP-0067 policy points | |
| 🟡 FIP-0117: Repeated SnapDeals with Piece-Level Integrity | PR #1269 · Discussion #538 | Draft (PR open) · New; candidate for NV30 (no deferrals) | L (Jennifer’s estimate) | Utility TBD | |
| 🟡 FIP-XXXX: Remove payment channel actor | Discussion #1290 | Discussion Forum · Not yet scoped to an upgrade | TBD | Author: rvagg. Settlement path for any live channels | |
| 🟡 FIP-XXXX: Clear State Simply | Discussion #1266 | Discussion Forum · New; candidate for NV30 (no deferrals) | S (AJ +1) | ||
| 🟡 FIP-XXXX: Fault fees and other reward-derived charges after Solstice | PR #1303 · Discussion #1302 | Draft (PR open) · New; not yet scoped | TBD | Author: lucaniz. Scales fault fee, invalid-WindowPoSt penalty and consensus-fault penalty by the FIP-0118 consensus weight, floored at 0.5. Open: move consensus-fault penalty together or separately; reporter reward drops from ~1 to 0.5 FIL; is 0.5 the right floor | |
| ⚪ FRC-0120: Filecoin Encryption Envelope | PR #1294 · Discussion #1253 | Draft (PR open) · Not tied to an upgrade | TBD | Open: scheme 1 test vectors, shared 1 MiB prefix-read cap | |
| 🔴 FIP-0107: Implicit messages in block receipts | FIP-0107 · Discussion #1149 | Accepted · Deferred NV29 → NV30 | M | Decide: commit to NV30 with named Forest/Venus owners, or defer again | |
| 🔴 Fork Signaling Repurposing | Discussion #1221 | Discussion Forum · Deferred NV29 → NV30 (can ship without an upgrade) | S | Not consensus-critical; likely an FRC | |
| 🔴 Sealer ID | PR #993 | Draft (PR open since Apr 2024, stalled) · Deferred NV28 → NV29 → NV30 | TBD | Decide: re-scope, defer again, or withdraw | |
| 🔴 F3 Calibration Smart Contract Activation | go-f3 #1054 | Not a FIP (implementation issue) · Deferred NV28 → NV29 → NV30 | L | Decide: still needed for NV30 testing, or close | |
| Remove the Fil+ actors (f06, f07, f080) | Discussion #1300 | Discussion Forum · New; not yet scoped | TBD | Started by rvagg |