6th 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	@Anonymous	- F3 activated on Mainnet

FDS online presentation and track leading
PDP hackathon
First F3 “Incident”: https://github.com/filecoin-project/lotus/issues/13094 | - Toronto Colo
FDS
Ship v2 F3-aware APIs in the Lotus v1.33.0 release | | Forest | [email protected] | - PDP hackathon
“snapshot GC”
Forest Faucet improvements
RPC methods work (fixes + benchmarking) | - FDS
improve performance of some RPC methods that didn’t benchmark very nicely
(tentatively) start work on /v2 APIs | | ChainSafe Infra | [email protected] | | | | 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] | - Investigating a potential sync issue in Forest via continuous testing.
F3 telemetry to monitoring.
Potential audit of safe implementation. | - Patching forest for more p2p resilience testing for lotus.
New security bounty page coming up with revamped leaderboard and added incentives. |

(Orjan) F3 update:
- Initially after activation had less participation than we saw in passive testing, but 3 days after activation participation increased to the levels we had in passive testing
- F3 unable to decide at Instance 6017: https://github.com/filecoin-project/lotus/issues/13094
  - Currently catching up to the head of the chain
  - Followup steps: https://github.com/filecoin-project/go-f3/issues/983
    - Update whenever it is ready., no need for a network upgrade to ship this change.
(@Steve (biglep)) F3-aware snapshots: https://github.com/filecoin-project/go-f3/issues/480
- What will we need to do to move this forward?
  - Need to finish the design here and implement the same thing between Lotus and Forest.
  - FilOz will own the design work here.
(@Steve (biglep)) FYI: filecoin-project rust crate ownership is getting cleaned up per https://github.com/filecoin-project/github-mgmt/issues/104
(@Steve (biglep)) Are there topics we want to go deeper on together in Toronto / FDS?
- Implementers look at the FIP lifecycle management. A more formal process (link?).
- Magik: SealerID - working on updating the FIP.
- Mayank: Working on the markets 2.0
Lotus v2 APIs: https://www.notion.so/filecoindev/Filecoin-V2-APIs-1d0dc41950c1808b914de5966d501658

(Tanisha) Governance Updates:

Title	Add Support for EIP-2537 (BLS12-381 Precompiles) in the FEVM	EIP-7702 Support on FEVM (Set EOA Account Code)
Type	FIP-01XX 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. |