[Core Protocol] Example of how to upgrade Proposer or Challenger addresses in L2OutputOracle.sol? #258
Unanswered
RnkSngh
asked this question in
Core Protocol
Replies: 1 comment 1 reply
-
https://github.com/ethereum-optimism/optimism/blob/a06cae81ed60c85d1566f48f45d9f9c0e48cc47c/packages/contracts-bedrock/scripts/getting-started/config.sh#L48 Here we can see pre-deployed contract configuration information. https://etherscan.io/address/0xdb5d932af15d00f879cabebf008cadaaaa691e06#code In the logic contract, these pieces of information are initialized (including other information not mentioned in the comments). I believe upgrading them would require deploying a new logic contract. Then, the address of the executing contract should be updated in the proxy contract. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Did you check the documentation?
Did you read the specs?
Did you check for duplicate questions?
Issue Description
I was looking through the L2OutputOracle.sol and on this line the comment says the address of the Proposer can be updated via upgrade. It also says something similar for the Challenger.
I was curious how an example of updating either address would look like? Is it basically upgrading to a new L2OutputOracle logic contract that has a setter function to set a new Proposer/Challenger? If so, why is this comment only present on the Challenger and Proposer variables (presumably you can do the same to all other variables stored in the contract) ?
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions