27th May 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

Team/Area	Section Owner	⬅️Updates Since Last Meeting	➡️Upcoming Plans
FilOz	@Orjan Roren	- nv27 skeleton added to ref-fvm / GST / filecoin-ffi. Lotus PR in review.

FDS-6: Had some really good sessions with the Forest team.
Developer work related to PDP / Payments contracts.
- Preparing for hackathon/builders test out the contracts and a SDK on 2025-06-04. | - Clean up F3 code.
Prebuilt filecoin-ffi go modules: https://github.com/filecoin-project/filecoin-ffi/issues/209 | | Forest | [email protected] | - FDS-6, put some takeaways from Forest’s perspective: https://github.com/ChainSafe/forest/discussions/5643,
Changed GC in Forest,
Faucet refactoring & automated testing
read state API,
finalized (hopefully!) common node API FIP,
F3-augmented snapshots design | - USDFC faucet
more faucet refactoring,
RPC perf improvements,
F3 augmented snapshots implementation | | ChainSafe Infra | [email protected] | - Infra Faucet updated! it is now 💫 fancy 💫
working on improvements across the board for snapshot service backend | - PDP Snapshots
supporting USDFC faucet | | Venus | [email protected] | | | | Curio | [email protected] | | | | Elliptic Research | [email protected] | | | | Filecoin Monitoring & Analysis | [email protected] | | | | Filecoin Spark (Retrieval Check) | [email protected] | | | | FIPs | [email protected] | | | | FF Security | [email protected] | - Dealing with lots of LLM based Go-F3 bug reports and aftermath. Working with the platform to resolve it.
Debugging couple of issues with Antithesis. Sync related.
Integrated rpc v2 API with Antithesis and it will be up from this week.
New bug bounty leaderboard up https://fil.org/security/bug-bountyalso includes researchers reporting valid but OOS issues. | - (Blocker): Unable to bootstrap F3 at arbitrary epoch given breaking changes post F3 launch. | | Governance | @Anonymous | Please review FIP Lifecycle Overview: https://tanisha-fil.github.io/FIPLifecycleManagement/ | - Determine and understand the scope for nv27 better— call to be scheduled with Steve |

Sync Agenda & Notes

(Steve) Elliptic Research dissolving at the end of the month
- Items being tracked: https://filecoinproject.slack.com/archives/CEGB67XJ8/p1748291041428129?thread_ts=1747951405.844879&cid=CEGB67XJ8
nv27
- With Tanisha hired by the FF, FilOz is going to step back and let FF drive this more.
  - Ideal to increase bus-factor.
- Please add potential items in scope to https://github.com/filecoin-project/core-devs/discussions/196
F3
- New go-f3 release coming within the next week with various performance improvements
- (Forest) Snapshots
  - https://github.com/ChainSafe/forest/issues/5627
  - https://docs.google.com/document/d/1uVPlItYb3JZ2ZsAWLhlpE8EccNkdtn4MNtoRDJtLEok/edit?tab=t.0 ready for input
    - Proposes to change to the snapshot header. Single CID that points to multiple
  - Next steps
    - FRC
    - https://github.com/filecoin-project/go-f3/issues/480
    - Forest implement export/import
    - Lotus: https://github.com/filecoin-project/lotus/issues/13129
  - Note: new snapshots will be published after the next network upgrade.
    - Notes from Hubert:
      1. Have nodes updated before NVXX
      2. nv27
      3. New Forest release - with new ones in snapshot service
- Other next steps
  - Drive adoption of F3 aware APIs so the ecosystem gets the benefits
FIP-100
- Blog entry coming. Push to get the information out to the SP community.
Common Node APIs and RPC definitions
- (Forest) https://github.com/filecoin-project/FIPs/pull/1158 ready for review. We want to get this merged quick.
- (Steve) https://github.com/filecoin-project/lotus/issues/13114
  - Lotus maintainers looking at how we can be having API discussions on a spec.
  - In issue above, looking at potentially doing that outside the Lotus repo.

Governance Updates — Action Time!

— FIP 0105 is progressing forward and will be presented for community inputs in the Core Devs call before moving to “Accepted” — Moving Discussion #1143 to a potential FIP Draft - Reached out to the author

Title	Add Support for EIP-2537 (BLS12-381 Precompiles) in the FEVM	EIP-7702 Support on FEVM (Set EOA Account Code)
Type	FIP-0105 PR#1142	Discussion #1143
Status	Draft	Discussion
Summary	Introduces BLS12-381 precompiles to the Filecoin Virtual Machine (FEVM), enabling efficient BLS signature verification. This enhancement facilitates interoperability with Ethereum and supports applications requiring BLS cryptography.	Proposes implementing EIP-7702 in the FEVM, allowing Externally Owned Accounts (EOAs) to delegate execution to smart contracts. This feature enables functionalities like atomic batching, sponsored transactions, and permissioned subkeys, aligning with account abstraction goals.
Security Considerations	- Is it compatible with existing systems?

Does it warrant any security audit? | - Does modifying EOA behavior introduce complexities in transaction execution and state management? | | Technical Feasibility (Pros/Cons) | Enhances cryptographic capabilities and interoperability with Ethereum | Aligns with Ethereum's account abstraction efforts, offering enhanced flexibility | | Implementers Leading | TBD | TBD | | Target Network Upgrade Cycle | TBD | TBD | | Target Date for Implementation | TBD | TBD | | Link / URL | ‣ | https://github.com/filecoin-project/FIPs/discussions/1143 | | Action Needed This Week | Review the proposal's technical details and assess potential impacts on existing systems. | Engage in the discussion to evaluate the feasibility and implications of adopting EIP-7702 in the FEVM. |

Governance — Review Time!

6 FIPs that have been “Accepted” but not “Final”

Title	ID (FIP / FRC)	Status	Summary	Security Considerations	Technical Feasibility (Pros / Cons)	Implementer(s) Responsible	Target Network Upgrade (Cycle)	Target Date for Implementation	Discussion Link / FIP URL	Action Needed This Week

Add support for aggregated replica update proofs	FIP-0082	Accepted	Proposes enabling miners to submit multiple sector update proofs as a single Groth16 aggregate proof, allowing simultaneous data updates across sectors.	Ensuring the correctness and security of aggregate proof verification is critical to prevent potential vulnerabilities.	✅ Improves efficiency by reducing on-chain messages. ❌ Requires implementation of aggregate proof verification logic.	Lotus, Forest	TBD	TBD	FIP-0082	Assess the complexity of implementing aggregate proof verification and provide feedback on potential challenges.

PoRep Security Policy & Replacement Sealing Enforcement	FIP-0067	Accepted	Establishes a policy for handling flaws in proof-of-replication (PoRep) and enforces replacement sealing to maintain network integrity.	Critical to ensure that replacement sealing mechanisms do not introduce new vulnerabilities or loopholes.	✅ Enhances network security by addressing potential PoRep flaws. ❌ May require significant changes to sealing processes.	Lotus, Forest	TBD	TBD	FIP-0067	Review the proposed policy and assess the impact on current sealing workflows.

Supporting Ethereum Accounts, Addresses, and Transactions	FIP-0055	Accepted	Aims to support Ethereum-style accounts and transactions within the Filecoin network to enhance interoperability.	Must ensure that integrating Ethereum account structures does not compromise existing security models.	✅ Facilitates cross-chain compatibility. ❌ Potential complexity in aligning Ethereum and Filecoin account models.	Lotus, Forest	TBD	TBD	FIP-0055	Evaluate the integration approach and identify any security concerns or implementation hurdles.

Introduce new versions of PreCommitBatch and ProveReplicaUpdates methods	FIP-0041	Accepted	Suggests new versions of PreCommitBatch and ProveReplicaUpdates methods to simplify future updates.	Requires careful validation to ensure new methods do not introduce inconsistencies or vulnerabilities.	✅ Streamlines future updates. ❌ Necessitates thorough testing of new methods.	Lotus, Forest	TBD	TBD	FIP-0041	Analyze the proposed method changes and determine the scope of required modifications.