February 2025 FIL Implementer Call

<aside> ‼️

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

</aside>

Aync updates

• Prepping for launch of contract on mainnet by end of March. Blog post with timelines F3:
• New release v0.8.0
• Chaos-testing in Butterfly network.
• Activation Contract Removing batch-balancer FIP | - Get PDP contract ready for audit
• Finish F3 activation contract.
• Implementation of removing batch-balancer FIP. | | Forest | [email protected] | - support CARv2
• RPC methods fixes/impls
• internal - switched to ARM GH workers (faster & cheaper!) | - continue work on RPCs
• start RPC benchmarking | | ChainSafe Infra | [email protected] | - mainnet archival node syncing, expected to reach chain tip in 16 days! | | | Venus | [email protected] | | | | Curio | [email protected] | | | | Elliptic Research | [email protected] | - Ongoing release testing and SuperSnaps feature testing | - Working on documenting potential 2025 roadmap items | | Filecoin Monitoring & Analysis | [email protected] | | | | Filecoin Spark (Retrieval Check) | [email protected] | We shipped support for sampling DDO deals (more details). | Implement support for Curio (tracking issue). | | FIPs | [email protected] | - FIP0098 Last Call extended for another 2 weeks. | - Soft launch of a FIPs Tracking Tool - Use case testing for the temp check tool - FIP0099 Last Call readiness | | FF Security | [email protected] | - Continuous testing presentation in Stack Leads call on Thursday.
• NV25 testing in Antithesis.
• Zellic PDP audit onboarding.
• Two Filecoin IR Monthly WG Calls to accommodate more folks from ecosystem. (Ping myself or Ken for invite, if not on group already). | - More work on unifying metrics and dashboard for IR.
• Libp2p messages fuzzing. (Any ideas would be appreciated on what protocols/messages to focus on, working on identify). |

Sync Agenda & Notes

• F3 sync items:

  • Delegation of Authority:

    • Venus and Forest to merge their keys into this PR: https://github.com/filecoin-project/FIPs/pull/1112#issuecomment-2637370787
      • Example of when Forest did it: https://github.com/filecoin-project/FIPs/pull/1119
    • Integrating f3-activation-contrct into clients
      • (Still WIP) Example of Lotus integrating f3-activation-contract: https://github.com/filecoin-project/lotus/pull/12861
        • We’ll share when this is out of draft

  • v0.8.0 released: https://github.com/filecoin-project/go-f3/pull/883

    • Will be bubbled up here:

    https://github.com/filecoin-project/lotus/pull/12893

  • Calibration network

    • F3 is already active here.
    • Make sure there are no breaking changes, so that it can be rolled out with no coordination need.
      • All changes should be backwards compatible.

  • F3 activation contract

    • In progress in Lotus, will post in #fil-implementers once done.
• FIP-0098:
  • Huber written a draft implementation, missing some details for this to be finalised?
    • Not sure what should be there in implementation.
  • Costly migration is needed in the proposal at hand. Can ignore them, and mark for deletion in the futre.
    • Benchmark migration when we ignore?
      • Just set the fields to zero, will be similar to a skeleton migration.
  • Discussion places
    • https://github.com/filecoin-project/FIPs/discussions/1036
    • https://filecoinproject.slack.com/archives/C01EU76LPCJ/p1738919923744379?thread_ts=1737645219.889989&cid=C01EU76LPCJ