chore: update FilBeamOperator contract address #407
Conversation
usage-reporter/wrangler.toml
Outdated
| [env.mainnet.vars] | ||
| ENVIRONMENT = "mainnet" | ||
| RPC_URL = "https://api.node.glif.io/" | ||
| FILBEAM_CONTRACT_ADDRESS = "0x" # TODO |
There was a problem hiding this comment.
Have you considered deploying FilBeam operator contract to the mainnet and update the mainnet contract address in the configuration as part of this pull request?
I am fine with leaving such change out of the scope of this PR, as long as there is a GH issue or a check-list item somewhere to remind us about this left-over task.
There was a problem hiding this comment.
Have you considered deploying FilBeam operator contract to the mainnet and update the mainnet contract address in the configuration as part of this pull request?
I don't think that new FWSS contract is deployed on mainnet and we're not able to update the FWSS contract after the operator deployment (configuration is immutable inside FilBeamOperator contract). That being said we're not able to deploy our operator contract until the new mainnet FWSS contract is deployed.
I am fine with leaving such change out of the scope of this PR, as long as there is a GH issue or a check-list item somewhere to remind us about this left-over task.
There is a related issue that tracks configuration updates.
There was a problem hiding this comment.
I don't think that new FWSS contract is deployed on mainnet
FWSS is deployed on mainnet, see https://github.com/FilOzone/filecoin-services/releases/tag/v1.0.0
Updates FilBeamOperator contract address for dev & calibration environments.
Related to #397