Filecoin Filecoin governance

Implementers' Calls

Every implementers' call with its recording and notes, tied to the network upgrades and FIPs it discussed.

Updated 2026-11-09 16:04 UTC
Woof!
Calls logged
45
in the implementers' log
Latest call
Nov 3
6 days ago
Last 90 days
7
calls held
Upgrades discussed
5
named or FIPs covered

Latest implementers' call

All calls →
2026-11-03 FIL Implementer Call
Nov 3, 2026

Nv30 Scoping

NV29NV28FIP-0107FIP-0117FIP-0118FIP-0119

Upgrades and FIPs mentioned. Mentions are not decisions.

Meeting notes (5 topics, 11 points)

NV30 Scope: Primary Driver

  • FIP-0119: increase max sector lifetime from 5 to 10 years
    • Main urgency driver for NV30 timing
    • ~118 PiB hard-capped in the affected window; ~76 PiB expiring through Nov 2026, ~87 PiB through March 2027
    • ~42 PiB unextendable without this FIP; ~268 PiB/year resealing required to hold capacity flat
    • Activating in early December preserves ~42 PiB; January ~40 PiB; March ~31 PiB

NV30 Scope: Small Additions

  • Fault fees and reward-derived charges after Solstice (discussion #1302)
    • Default fees tied to full block reward; as rewards decline, fault fees could become ~2x appropriate amount
    • Proposal: carry consensus weight into miner-actor charges using max(w1, 0.5); ~214,000 FIL in fault fees over last year
    • Small parameter change; beneficial for SPs (lower fault fees over time)
    • Wouldn't drive an upgrade, but easy to include if NV30 is happening
  • Removing legacy Fil+ actors (f06, f07, f080)
    • Frozen at NV29 by FIP-0118; state occupies ~11.8 GB across 14M blocks
    • Rod opened a PR; low-lift cleanup candidate
  • FilOz to do a fresh pass on state cleanup and migration speed improvements
    • Light items could opportunistically join NV30; nothing held up for this

NV30 Scope: Deferred or Out

  • FIP-0117 (repeated SnapDeals with piece-level integrity): L-sized, requires heavy SP testing; too large for this upgrade
  • Fork Signaling Repurposing: deferred since NV28; non-consensus-critical, likely an FRC, not worth the lift given other priorities
  • Anything above medium t-shirt size: not targeting for NV30
  • FIP-0107 (implicit messages in block receipts), Sealer ID, F3 Calibration Smart Contract Activation: deferred to NV30 but not discussed as active candidates

Ownership and Decision-Making

  • Business decision on upgrade timing sits outside this meeting; engineering can be reactive given small implementation lift
  • Suggested outreach: identify miner IDs dropping power in Nov/Dec, contact them to gauge willingness to extend sectors if FIP-0119 passes

Next Steps

  • Move FIP-0119 to Last Call No objections raised; opening the PR after this meeting.

From the public notes; attributions removed.

Notes

About the implementers' calls

Filecoin implementation teams meet regularly to coordinate network upgrades: scope, timelines, test vectors, calibration and mainnet readiness, and blockers on accepted FIPs. Core Devs sets priorities; these calls are where implementers work out how and when they ship.

Network upgradesCore Devs meetings

Network upgrade discussions

Implementers' calls that named each upgrade or discussed its FIPs before activation.

NV29Solstice

Live
Mainnet: Oct 19, 202611 implementers' callsAll 15 calls incl. Core Devs →

NV28Fire Horse

Live
Mainnet: May 27, 202613 implementers' callsAll 21 calls incl. Core Devs →

NV27Golden Week

Live
Mainnet: Sep 24, 202512 implementers' callsAll 18 calls incl. Core Devs →

NV26Tock

Live
Mainnet: Jul 9, 20250 implementers' calls1 call incl. Core Devs →

No implementers' calls in the log discussed this upgrade.

All implementers' calls (45)

DateCallUpgrades and FIPsLinks
Nov 17, 20262026-11-17 FIL Implementer Call
Notes
Nov 3, 20262026-11-03 FIL Implementer Call
Nv30 Scoping
Notes (5 topics, 11 points)

NV30 Scope: Primary Driver

  • FIP-0119: increase max sector lifetime from 5 to 10 years
    • Main urgency driver for NV30 timing
    • ~118 PiB hard-capped in the affected window; ~76 PiB expiring through Nov 2026, ~87 PiB through March 2027
    • ~42 PiB unextendable without this FIP; ~268 PiB/year resealing required to hold capacity flat
    • Activating in early December preserves ~42 PiB; January ~40 PiB; March ~31 PiB

NV30 Scope: Small Additions

  • Fault fees and reward-derived charges after Solstice (discussion #1302)
    • Default fees tied to full block reward; as rewards decline, fault fees could become ~2x appropriate amount
    • Proposal: carry consensus weight into miner-actor charges using max(w1, 0.5); ~214,000 FIL in fault fees over last year
    • Small parameter change; beneficial for SPs (lower fault fees over time)
    • Wouldn't drive an upgrade, but easy to include if NV30 is happening
  • Removing legacy Fil+ actors (f06, f07, f080)
    • Frozen at NV29 by FIP-0118; state occupies ~11.8 GB across 14M blocks
    • Rod opened a PR; low-lift cleanup candidate
  • FilOz to do a fresh pass on state cleanup and migration speed improvements
    • Light items could opportunistically join NV30; nothing held up for this

NV30 Scope: Deferred or Out

  • FIP-0117 (repeated SnapDeals with piece-level integrity): L-sized, requires heavy SP testing; too large for this upgrade
  • Fork Signaling Repurposing: deferred since NV28; non-consensus-critical, likely an FRC, not worth the lift given other priorities
  • Anything above medium t-shirt size: not targeting for NV30
  • FIP-0107 (implicit messages in block receipts), Sealer ID, F3 Calibration Smart Contract Activation: deferred to NV30 but not discussed as active candidates

Ownership and Decision-Making

  • Business decision on upgrade timing sits outside this meeting; engineering can be reactive given small implementation lift
  • Suggested outreach: identify miner IDs dropping power in Nov/Dec, contact them to gauge willingness to extend sectors if FIP-0119 passes

Next Steps

  • Move FIP-0119 to Last Call No objections raised; opening the PR after this meeting.

From the public notes; attributions removed.

NV29NV28FIP-0107FIP-0117FIP-0118FIP-0119
Notes
Oct 20, 20262026-10-20 FIL Implementer Call
I’ve had an SP contact me about the FIL+ deprecation. It may be worthwhile to have a blog link about the pros & cons; Any Lessons Learned / observations we want to carry forward?; Increase maximum sec
Notes (7 topics, 27 points)

NV29 / Solstice Upgrade Status

  • Mainnet upgrade completed yesterday; looks successful so far
  • Rod confirmed: miners extending CEC sectors, power bump received as expected, collateral correct
  • Ongoing monitoring continues

FIL+ Deprecation Messaging

  • No canonical talking-points doc exists yet; engineers doing one-off DM explanations
  • Filoz (driving Solstice) to check in later today on what’s being published and surface feedback
  • SP-targeted blog post suggested: one for SPs with strong FIL+ connections explaining why the transition is still positive for them

NV29 Retrospective and Template Improvements

  • Lessons-learned doc open for contributions while context is fresh
  • Key items already captured (from screenshots)
    • Use Google Doc variables for upgrade issue links
    • Record Butterfly host shutdowns and state changes post-testing
    • Document reset prerequisites
    • Capture calibration snapshots within a few hours of upgrade
  • Doc format discussion: Google Doc tables are hard for agent interaction; Notion considered but permissions management is tricky
    • Filoz doing more doc work via agents, so agent-navigability is a real factor

FIP-0119: Increase Maximum Sector Lifetime to 5 → 10 Years

  • Draft FIP (PR #1293, lucaniz) proposes raising max sector lifetime for PoRep v1.1, SyntheticPoRep, and NI-PoRep
  • No state migration, no pledge/fee/proof changes required
  • Motivation: ~42 PiB cannot be extended after December 2026; 58 PiB expiring Nov 1, 76 PiB by month-end
  • Security risks noted: PoRep flaws and cost/latency drift narrowing SDR margins
  • Caveat: market actors still cap at 3.5 years, so archival terms offered to clients may not be binding

Network Upgrade Cadence

  • Historical norm: ~3 upgrades/year; concern raised about exchange exhaustion
  • Coinbase already cautious; every upgrade creates operational burden for exchanges
  • Consensus: no more than 2 major upgrades per year, with a predictable published schedule
    • Analogy: Ubuntu’s fixed release dates give downstream maintainers a reliable target
    • Cardano cited: 1 major upgrade/year due to long dev cycles and on-chain governance
  • Ad hoc upgrades remain possible for emergencies
  • Proposal: bring to Core Devs call to establish 2 official dates per year; FIPs available at that point determine whether the upgrade proceeds

Wasmtime Dependency Update

  • Good time to do dependency updates now that NV29 is out, to let things bake before NV30
  • Wasmtime v47 upgrade brings ~10% speedup for any state computation
  • Filoz planning to spend time on this; Wasmtime update in ref-FVM had been blocked on Rob, who is now re-engaging

Next Steps

  • Check for existing FIL+ deprecation blog post and share link
  • Check in with Filoz team on Solstice SP messaging
    • Confirm what blog content is coming out and surface feedback from today's sync.
  • Incorporate NV29 lessons learned into upgrade template
    • Invite others to add observations to the doc while context is fresh.
  • Raise network upgrade cadence on Core Devs call
    • Propose 2 official upgrade dates per year with ad hoc exceptions for emergencies.
  • Progress Wasmtime v47 upgrade in ref-FVM

From the public notes; attributions removed.

NV29FIP-0119
Recording · Notes
Oct 6, 20262026-10-06 FIL Implementer Call
nv29 update; Ok to move back 30 minutes (e.g., 7am Pacific - 14 UTC)?; F3 on calibnet stuck since Oct 1 - might need (another) reset if it’s not addressed soon
Notes (6 topics, 13 points)

NV29 Network Upgrade: Confirmed Dates

  • Mainnet upgrade: Monday 19th October at 12:59:30 UTC (epoch 6470279)
  • Solstice contracts activate at 13:00:00 UTC (epoch 6470280), one epoch later
  • Lotus 1.37.0 is the required release for NV29
    • Optional 1.37.1 expected later this week with resiliency improvements and community fixes
    • Folks upgrading next week will likely see 1.37.1 and can use it, but 1.37.0 is sufficient

Solstice Contract Upgrade

  • Contract upgrade process kicks off today on mainnet
    • 1-week hold before it becomes live in mainnet state
    • Contract upgrades done on calibration; none yet on mainnet, but no issues foreseen
  • Open question: whether activation being one epoch after the upgrade matters for migration spanning that boundary
    • Will confirm via Fil Implementers post with input from those who know the system best

Comms and Community Readiness

  • Green light to start telling community to prepare for upgrade on Monday 19th October
  • Will ensure community discussion and other channels are updated with the activation epoch

F3 Stuck on Calibnet Since 1st October

  • F3 has not progressed on Calibnet since 1st October due to exponential backoff behavior
    • Last known issue: StoreSwift miner had an env variable explicitly disabling F3 participation
    • Current situation: appears nobody is participating, but power table looks unchanged
  • If not resolved soon, a manual reset on Calibnet will be required

Meeting Time Change and Next Steps

  • Next sync: 2 weeks from now, likely the day after the network upgrade (21st October)

Next Steps

  • Post clarification on Solstice activation epoch timing in Fil Implementers
    • Confirm whether migration spanning the epoch boundary matters; let subject-matter experts answer.
  • Engage on F3 Calibnet issue at FilOz breakout today
  • Set up F3 monitoring on Calibnet
    • Avoid relying on best-effort observation; write up the monitoring action item post-Solstice focus.

From the public notes; attributions removed.

NV29
Notes
Sep 22, 20262026-09-22 FIL Implementer Call
Solstice; Upgrade epoch
Notes (5 topics, 18 points)

Solstice (NV29) Status

  • Butterfly testing completed over the weekend successfully
  • Solstice branch merged into Lotus main by Rod earlier today
  • One remaining blocker: small built-in actors change
    • Adds extra event exposure for agent-driven governance contract usage
    • Produces Actors 19.0.1 release, then bubbles up to Lotus
  • Solstice contracts will be redeployed; Lotus must update to new contract proxy addresses
  • Lotus RC (1.37.0) expected within a couple of hours

Upgrade Timeline

  • Target: Thursday 24th September, 1300 UTC
    • Activation epoch set one epoch before 1300 UTC for clean datetime boundary on Solstice Orders
  • Open PR in Lotus to set upgrade epoch; merges once new actors bundle is ready
  • Calibration sectors needed by Wednesday 22nd September before 1300 UTC so they’re proven in time

Infra Provider Readiness

  • Forest: prepared, waiting on final Lotus release to cut NV29-compatible Forest release
  • ChainSafe: calibration bootstrappers need updating
  • Venus: no blockers
  • Priority: Glyph nodes must be on NV29-compatible Forest/Lotus before upgrade
    • safe.filecoin.io uses Glyph endpoint; critical to have it updated

Other Updates

  • Lotus NV29 release switches away from proofs.filecoin.io to Forest-provided infrastructure
  • Curio: Easy PDP epic wrapped up; one-line setup via web interface, blog post shared
  • New stake proposal from Hannah Howard in FIP discussion forum; Core Devs report also available
  • FOC working group: no update this sync; aim to cover next time

Next Steps

  • Cut Actors 19.0.1 and Lotus 1.37.0 RC branch
  • Run invariant checks and post results to Fil Implementers

From the public notes; attributions removed.

NV29
Notes
Sep 8, 20262026-09-08 FIL Implementer Call
Notes (1 topic, 3 points)

NV29 / Solstice Upgrade Status

  • Verbal share - will get written down update in #fil-implementers
    • Week of 2026-09-14
    • Calibration upgrade TBD
    • Official communication as dates solidify
  • Manusheel Gupta
    • The rust-libp2p maintainers have confirmed that they are working through a few remaining PRs and issues in the backlog and expect to complete the release this week.
  • Ainhoa - zondax
    • The first batch of comms to inform exchanges and providers has been sent. I’ll be following up more after the RC is available

From the public notes; attributions removed.

NV29
Notes
Aug 25, 20262026-08-25 FIL Implementer Call
NV29 scope; NV29 timeline; NV 29 naming; Ok to push this meeting back 30 mins?
Notes (1 topic, 6 points)

NV29 / Solstice Upgrade Status

  • Code freeze target: this Friday (Aug 28)
  • Upgrade now officially named “Solstice”; enough votes to confirm the name
  • FIP 118 is the primary target
  • Mainnet date shifted from Sep 30 to Oct 8, due to Golden Week
  • Filoz racing to get actor code freeze + Lotus RC for calibnet by next week
    • Goal: verify new contracts in the solstice repo all the way through at the Lotus level before calling code freeze
    • If Friday freeze isn’t achievable, will message out via Fil Implementers channel
  • Engineering tracking board (public) has all items needing to land this week

From the public notes; attributions removed.

NV29NV27FIP-0118
Notes
Aug 11, 20262026-08-11 FIL Implementer Call
NV 29 Timeline Upgrade; Solstice Implementation Timeline; FIP Backlog, looking ahead to NV30 (probably in 2027), What is T-shirt sizing for these efforts?
NV29FIP-0107FIP-0117
Notes
Jul 28, 20262026-07-28 FIL Implementer Call
nv29 upgrade/timeline/scope
NV29
Notes
Jul 14, 20262026-07-14 FIL Implementer Call
nv29 Bandwidth part 2
NV29FIP-0117
Notes
Jun 30, 20262026-06-30 FIL Implementer Call
CT (FF Gov): Review deferred items from nv28: nv29 Network Upgrade Planning · filecoin-project core-devs · Discussion #2; Solstice FIP Draft - Technically sound review; Calibration SPs
NV29NV28FIP-0107
Notes
Jun 16, 20262026-06-16 FIL Implementer Call
Anything remaining addressing in “SettleDealPaymentsExported messages consume massive gas, fill block space, crowd out l; nv29 tracking/planning next steps; FIP discussions: Clear State Simply; Securi
Notes (5 topics, 14 points)

Settled Deal Payments Gas Issue (FIP 115 / NV28)

  • Issue ticket: settled deal payments exported messages consuming massive gas, crowding out legitimate transactions (e.g. window post), without triggering base fee spikes
  • FIP 115 landed in NV28, fixing the core problem: base fee now responds to gas spikes
  • Remaining concern: these messages still consume a lot of gas, just no longer crowding others out
  • Plan: open a new built-in actors ticket for reducing gas consumption on settled deal payments, then close the original ticket with a backlink

NV29 Upgrade Prep

  • NV28 lessons learned added to the upgrade template doc
  • Template now in good shape to duplicate for NV29
  • Tip: ask in the implementer channel for status on any checklist item

Security Triage and AI Agents

  • Bug reports up 5-10x year over year: 130+ received to date
  • AI-assisted triage pipeline built end to end
    • Enforced POC requirements: no report accepted without a proof of concept
    • Audit kit built so researchers can spin up dev nets quickly for POCs
  • Interesting pattern: same bug reported 3-5 times across sessions, possibly due to AI models leaking issues between sessions
  • Offensive AI agent in development
    • Trained to find security issues, re-triage autonomously, and surface high-signal reports
    • Main challenge: building a detailed context and system graph for Filecoin’s many interconnected services
    • Suggestion: spend time with Rod for tribal knowledge on Filecoin context

Recommended Reading

  • Nikola (Filoz / Protocol Labs) published a Mythos blog post on Filecoin’s response to the latest wave of AI models, flagged as worth reading

Next Steps

  • Open new built-in actors ticket for reducing gas on settled deal payments, then close original ticket with backlink
  • Duplicate NV28 upgrade template and begin NV29 checklist

From the public notes; attributions removed.

NV29NV28FIP-0115
Notes
May 26, 20262026-05-26 FIL Implementer Call
NV28
Notes
May 12, 20262026-05-12 FIL Implementer Call
NV28
Notes
Apr 28, 20262026-04-28 FIL Implementer Call
NV28
Notes
Apr 14, 20262026-04-14 FIL Implementer Call
NV28FIP-0112FIP-0115
Notes
Mar 31, 20262026-03-31 FIL Implementer Call
NV28FIP-0115
Notes
Mar 17, 20262026-03-17 FIL Implementer Call
NV28FIP-0115
Notes
Mar 3, 20262026-03-03 FIL Implementer Call
NV28FIP-0115
Notes
Feb 17, 20262026-02-17 FIL Implementer Call
Recording · Notes
Feb 3, 20262026-02-03 FIL Implementer Call
Notes
Jan 20, 20262026-01-20 FIL Implementer Call
FIP-0086
Notes
Jan 6, 20262026-01-06 FIL Implementer Call
Notes
Dec 9, 20252025-12-09 FIL Implementer Call
Notes
Nov 25, 20252025-11-25 FIL Implementer Call
Some areas getting updated based on FDS discussion
Notes
Oct 28, 20252025-10-28 FIL Implementer Call
NV28
Recording · Notes
Oct 14, 20252025-10-14 FIL Implementer Call
NV28NV27
Notes
Sep 30, 20252025-09-30 FIL Implementer Call
NV28NV27
Notes
Sep 16, 20252025-09-16 FIL Implementer Call
NV27
Notes
Sep 2, 20252025-09-02 FIL Implementer Call
NV27
Notes
Aug 19, 20252025-08-19 FIL Implementer Call
NV27
Notes
Aug 5, 20252025-08-05 FIL Implementer Call
NV27
Notes
Jul 22, 20252025-07-22 FIL Implementer Call
NV27FIP-0100FIP-0101FIP-0103FIP-0106
Notes
Jul 8, 20252025-07-08 FIL Implementer Call
NV27FIP-0100FIP-0101FIP-0103FIP-0106
Notes
Jun 24, 20252025-06-24 FIL Implementer Call
NV27FIP-0100FIP-0103
Notes
Jun 10, 202510th June 2025 FIL Implementer Call
F3 Snapshots; Actor-utils release; Current status on the contact point for OpsGenie in (Starboard) Grafana for the F3 alerts?; Governance updates
Notes (3 topics, 7 points)

F3 Snapshot Format Discussion

  • New section with F3 snapshot format design proposals
  • Two main proposals presented
    • Proposal 1 (Naive and general)
    • Proposal 2 (CertStore aware)
  • Key Discussion Points
    • Forest team can handle go-f3 implementation
    • Masih requested
    • Need to address

Infrastructure Updates

  • Actor-utils release
    • Ownership transferred to @filecoin-crate-owner
    • Working on documentation of release process
    • Action item: Consider adding Forest team members for crate publishing capabilities
  • F3 alerts status
    • OpsGenie integration with Starboard Grafana confirmed
    • Team to post confirmation in Filecoin incident response channel

Governance Updates

  • FIP Draft Backlog Management
    • Implementing new scoring model for prioritization
    • Uses sentiment analysis and three-axis scoring system
    • Plan to review 2-3 highest priority FIP drafts weekly
  • Implementation Planning
    • FIP 77 moving to final status on June 16
    • Three removal FIPs in pipeline (101, 103, 106)
    • FIP 105 has open PRs pending
    • Action Items

From the public notes; attributions removed.

NV27FIP-0077FIP-0082FIP-0105
Notes
May 27, 202527th May 2025 FIL Implementer Call
Elliptic Research dissolving at the end of the month; nv27; FIP-100; Common Node APIs and RPC definitions
NV27FIP-0100
Notes
May 6, 20256th May 2025 FIL Implementer Call
F3 update; () F3-aware snapshots; () FYI: filecoin-project rust crate ownership is getting cleaned up per; () Are there topics we want to go deeper on together in Toronto / FDS?
Notes
Apr 22, 202522nd April 2025 FIL Implementer Call
F3 activation update; F3 operation items before F3 activation; Lotus F3-aware v2 APIs; nv25
NV25
Notes
Apr 8, 20258th April 2025 FIL Implementer Call
nv25 related date adjustments due to last week’s ref-fvm issue (read more); Retroing ref-fvm regression; F3 passive testing
NV25NV24
Notes
Mar 25, 202525th March 2025 FIL Implementer Call
nv25; Q2 planning
NV25FIP-0100
Notes
Mar 11, 202511th March 2025 FIL Implementer Call
Spark / IPNI ?; Elliptic Research; NV25 suggested scope, progress update/readiness
NV25FIP-0098FIP-0100
Notes
Feb 25, 202525th February 2025 Implementer Call
F3 contract activation integration; FIP-0100: Mining software removing BB; FIP-0098: Simplify termination fee calculation to a fixed percentage of initial pledge; Is that out now?
NV25FIP-0098FIP-0100
Notes
Feb 11, 202511th February 2025 Implementer Call
F3 sync items; FIP-0098
NV25FIP-0098
Notes
Jan 28, 202528th January 2025 Implementer Call
nv25 update; Decoupling FIPs / Network Upgrades timelines; DDO <> Spark <> Boost —> Could not be changed in Boost without redoing core Boost.
NV25NV24FIP-0097FIP-0098
Notes

From the implementers' public meeting notes (filecoindev.notion.site). An upgrade tag means the call named that upgrade or discussed its FIPs; mentions are not decisions.