FRC for Delegation of Authority for F3 Parameter Setting

[BigLep]

This is the FRC accompanying #1102

This FRC proposes introducing an on-chain smart contract that can manage F3 parameters dynamically. This contract would be owned/controlled through a multi-signature mechanism requiring consensus from all three major Filecoin implementations (Lotus, Forest, and Venus). The contract would allow for a one-time parameter update based on mainnet passive test results, effectively combining what would have been two network upgrades into one while maintaining security through multiple stakeholder approval, full onchain transparency, and built-in time delays for community review.

[BigLep]

@Kubuxu @masih @rjan90 : given timezone and end of the week, I wanted to get this out to you. I haven't read yet with a full fresh set of eyes, which I will do 2025-01-31. I particularly wanted to get any high-level items feedback from @Kubuxu before his vacation.

[BigLep]

Posting verbal comments I got from @Kubuxu on 2025-01-31

[BigLep]

Thanks @Kubuxu @masih and @rjan90 for the review. I believe I have incorporated all feedback. Feel free to look at the diff from bdb3d15 onwards.

At this point, I'll mark this as ready for review and link it to the discussion.

Once we have a PR showing Lotus integration, I'll followup with Venus and Forest to make sure they provide their keys and have a tracking item for integrating.

[anorth]

Please take FRC number 0099.

• Update the filename
• Update the header and title of the FIP document
• Update the index entry

[rvagg]

• Key ownership is communicated by each implementation team adding their keys to this FRC via PR in the Implementation section.

How do you want to handle this? Merge the PR and have the teams PR their keys into the text or PR into your PR before merging?

[BigLep]

• Key ownership is communicated by each implementation team adding their keys to this FRC via PR in the Implementation section.

How do you want to handle this? Merge the PR and have the teams PR their keys into the text or PR into your PR before merging?

I am thinking to have other teams merge into this PR and we merge it all when all the keys are here and the other TODOs are filled in.