-
-
Notifications
You must be signed in to change notification settings - Fork 834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade alfajores to op #2714
Upgrade alfajores to op #2714
Conversation
🦋 Changeset detectedLatest commit: a774762 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@aaronmgdr is attempting to deploy a commit to the Wevm Team on Vercel. A member of the Team first needs to authorize it. |
…nmgdr/celo-op-example/blob/main/config.ts add celoscan as block explorer
@@ -1,8 +1,10 @@ | |||
import { contracts } from '../op-stack/contracts.js' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for easier review this is
const contracts = {
gasPriceOracle: { address: '0x420000000000000000000000000000000000000F' },
l1Block: { address: '0x4200000000000000000000000000000000000015' },
l2CrossDomainMessenger: {
address: '0x4200000000000000000000000000000000000007',
},
l2Erc721Bridge: { address: '0x4200000000000000000000000000000000000014' },
l2StandardBridge: { address: '0x4200000000000000000000000000000000000010' },
l2ToL1MessagePasser: {
address: '0x4200000000000000000000000000000000000016',
},
}
@jcortejoso please review addresses |
@tmm I based the contracts on what base / op include in their config. there isn't any reason to have additional contract addresses defined right? slightly related but would it be correct to add additional celo core contracts to this config? |
Correct, unless they are used internally in Viem. (Can search
You are welcome to add additional ones that you know will be used downstream, but similar to block explorers/RPC urls, we try to keep things lean when we can! |
Alfajores will be upgraded from an L1 to an OP L2 at end of the month
This PR adds the relevant contract addresses to the chain definition
(pending review by team)
PR-Codex overview
This PR updates the Celo Alfajores chain configuration to include new contract addresses.
Detailed summary