<aside> ‼️

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

</aside>

Aync updates

• Due to few participants. Progressing again now.
• F3 cleanups.
• Shipped Synapse-SDK to hackathon builds, for easily onboarding and retrieving their data to PDP+Payments contracts. | - Finalize F3 cleanups
• Finalize cleanup FIPs:
  • ‣
  • ‣
  • FIP-0107: ‣ | | Forest | [email protected] | - implemented and published calibnet USDFC faucet: https://forest-explorer.chainsafe.dev/faucet/calibnet_usdfc
• continued work on augmenting the snapshots with F3 information design (thanks @Anonymous for reviewing!) | - Hopefully, finalize the F3 design and publish a formal FRC
• https://github.com/ChainSafe/forest/issues/5494
• RPC improvements | | ChainSafe Infra | [email protected] | | | | Venus | [email protected] | | | | Curio | [email protected] | | | | Elliptic Research | [email protected] | Elliptic Research has dissolved. Ownership of all rust crates has been transitioned to filecoin-crate-owner. | Finish getting repos using FilOz owned CI runners. | | Filecoin Monitoring & Analysis | [email protected] | | | | Filecoin Spark (Retrieval Check) | [email protected] | Our team is working on FilCDN, a project that provides fast retrievals for PDP deals and Filecoin Services. We launched the testnet version last week, see https://filcdn.com | | | FIPs | [email protected] | | | | FF Security | [email protected] | - Investigating a sync issue in Forest discovered by Antithesis.
• “Safe” selector results in negative height if called before 900 epochs in devnet. (https://github.com/filecoin-project/lotus/issues/13167)
• All bug tickets are resolved at the moment in terms of coordination.
• In talks with IR tooling vendors mainly for monitoring different contract conditions. | - F3 bootstrap in 2k.
• More ethereum contracts and rpc benchmark tests. | | Governance | @Tanisha Katara | | |

Sync Agenda & Notes

• F3 Snapshots:
  • A new section of F3 snapshot format design proposal: https://docs.google.com/document/d/1uVPlItYb3JZ2ZsAWLhlpE8EccNkdtn4MNtoRDJtLEok/edit?usp=sharing
  • 2 proposals
    • Proposal 1 (Naive and general)
    • Proposal 2 (CertStore aware)
• (Orjan) Actor-utils release
  • Transferred ownership to @filecoin-crate-owner.
  • https://github.com/filecoin-project/actors-utils/pull/256
• (Orjan) Current status on the contact point for OpsGenie in (Starboard) Grafana for the F3 alerts?
• (Tanisha) Governance updates

Notes

F3 Snapshot Format Discussion

• New section with F3 snapshot format design proposals: https://docs.google.com/document/d/1uVPlItYb3JZ2ZsAWLhlpE8EccNkdtn4MNtoRDJtLEok/edit?usp=sharing
• Two main proposals presented:
  • Proposal 1 (Naive and general):
    • Question raised about using CAR-format when data is not content-addressable
    • Represents raw block store with key-value pairs
    • Implementation-agnostic but may consume more disk space due to common key prefixes
    • Keys are strings (instance certificate/power table prefix + instance number)
  • Proposal 2 (CertStore aware):
    • More focused on Go certificate store implementation
    • Header contains additional information like latest instance
    • Uses CBOR encoding for certificates
    • Implementation-specific but more structured
• Key Discussion Points:
  • Forest team can handle go-f3 implementation
  • Masih requested:
    • Language-agnostic precise format specification
    • Documentation of initial power table location
    • Clarity on efficiency of imports
    • Specification of block ordering
    • Design rationale for implementation choices
  • Need to address:
    • Format must be self-contained and implementation-independent
    • Interface design for importing snapshots
    • Storage system agnostic approach

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:
    • Implementers to review pipeline for NV27
    • Need volunteers for DRI roles
    • Consider opening to community contributions through grants program
  • Additional consideration: Including FIP 82 (super stat snip) in pipeline

Governance Updates