<aside> ‼️

The FIL implementer call notes are public, unpublisized security issues shall not be disclosed in this doc.

</aside>

Async updates

Team/Area	Section Owner	⬅️Updates Since Last Meeting	➡️Upcoming Plans
🐈 FilOz	@Anonymous	• Shipped Lotus v1.37.0 with Mainnet upgrade epoch set	• Likely will have an optional 1.37.1 with extra improvements and resiliency fixes
🌳 Forest	[email protected]	* RPC fixes & improvements
• drand via gossipsub (close to getting finalzed)
• more in https://github.com/ChainSafe/forest/discussions/7678
🪚ChainSafe Infra	[email protected]
🌞 Venus	[email protected]
🤔 Curio	[email protected]	Developing ACL & fast PDP TTFB (downloads).
StorSwift (lotus-miner, Boost)
⚖️ Governance	[email protected]
🔐 FF Security	[email protected]	1. Finalizing backend and UI dashboard for red team agent.

Bug bounty triage bot will get ability to reproduce it without executing reports PoC, safely in sandbox.
Landing security fixes with upcoming release. | 1. Safe Msig security review.
Closing all outstanding bug reports. |

Sync Agenda & Notes

Add agenda items here

(Steve) nv29 update
- Network upgrade: 2026-10-19 at 12:59:30 UTC
  - Epoch: 6470279
  - https://filecoin.blockscout.com/block/countdown/6470279
- Solstice activationEpoch: 2026-10-19 at 13:00:00 UTC
  - Epoch: 6470280
  - https://filecoin.blockscout.com/block/countdown/6470280
- FYI: Lotus may have an optional 1.37.1 later this week with extra improvements/fixes
(Steve) Ok to move back 30 minutes (e.g., 7am Pacific - 14 UTC)?
- Moving back 30 minutes is fine 👍
(Hubert) F3 on calibnet stuck since Oct 1 - might need (another) reset if it’s not addressed soon
- AI: make plan here and respond in slack thread: https://filecoinproject.slack.com/archives/C01D42NNLMS/p1790503967811499

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

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
- Steve’s belief: contract just checks “am I past the activation epoch?” so timing of migration relative to activation shouldn’t matter
- Orjan noted a null round at that epoch would also be fine for the same reason
- Will confirm via Fil Implementers post with input from those who know the system best

Green light to start telling community to prepare for upgrade on Monday 19th October
- Christian had held off pending CalNet concerns; now confirmed clear to proceed
Boost release status unclear; Steve to check it off the upgrade checklist today
Will ensure community discussion and other channels are updated with the activation epoch