feat: Make FilBeamOperator contract upgradeable

[Chaitu-Tatipamula]

Description

This PR implements the UUPS (Universal Upgradeable Proxy Standard) proxy pattern for the FilBeamOperator contract, enabling safe contract upgrades while preserving all state.

Closes #3

Motivation

• Enable bug fixes and feature additions without redeploying a new contract
• Preserve state (usage data, ownership, configuration) across upgrades
• Maintain a stable contract address for integrations

Key Implementation Details

• Inherits Initializable, Ownable2StepUpgradeable, UUPSUpgradeable
• initialize() replaces constructor (can only be called once)
• _disableInitializers() prevents implementation contract initialization
• _authorizeUpgrade() restricted to owner
• version() function returns "1.0.0"

Testing

• 74 tests pass including new upgrade tests:
  • test_CannotInitializeTwice
  • test_CannotInitializeImplementationDirectly
  • test_OnlyOwnerCanUpgrade
  • test_OwnerCanUpgrade
  • test_Version

How to Test

forge build
forge test -vvv

[pyropy]

Great start! 👏🏻

I believe we're missing two very important things:

• Deployment script that upgrade the old contract without deploying a new proxy
• State view contract (I'm not sure if this is needed with UUPS contract but I've seen that you have mentioned it in the docs).

It is very important to us NOT to lose on-chain state during upgrades as that could potentially cause loss for both FilBeam and storage providers.

[pyropy]

Great work! Let's upgrade the documentation before proceeding to merge this.

[pyropy]

Suggested change

	uint256 cacheMissRatePerByte, // Rate per byte for cache-miss usage
	address filBeamOperatorController // Address authorized to report usage
	uint256 cacheMissRatePerByte // Rate per byte for cache-miss usage

filBeamOperatorController is removed from the initialize method.

[Chaitu-Tatipamula]

you mean filBeamOperatorController is the only thing kept in initialize method! the addresses and the rates were the ones moved to constructor to be immutable

[pyropy]

@juliangruber would you also be able to give this a look?

[rjan90]

Thanks for the PR. Unfortunately, we’ll need to close it for now. We can revisit, clean it up, and reopen it when there’s sufficient bandwidth and FilBeam is prioritized again.