Fix contract addresses

[squdgy]

Description

A clear and concise description of the features you're adding in this pull request.

Tests

Please describe any tests you've added. If you've added no tests, or left important behavior untested, please explain why not.

Additional context

Add any other context about the problem you're solving.

Metadata

• Fixes #[Link to Issue]

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes primarily involve a comprehensive rebranding of documentation and code from "Optimism" to "Metal L2." This includes updates to titles, descriptions, and links across various files to reflect the new branding and associated functionalities. Additionally, new entries have been added to support the Metal L2 network, including changes to chain identifiers, explorer URLs, and RPC providers. The modifications ensure that all references are consistent with the new Metal L2 context.

Changes

Files	Change Summary
README.md	Updated title and description to reflect rebranding from "Optimism Docs" to "Metal L2 Docs."
components/TokenListTable.tsx	Added new entries to the explorers object for Metal L2 explorers.
pages/_meta.json	Replaced "Gas Tracker" with "Bridge" and "Status" with "Explorer," updated section headers and titles to reflect Metal L2.
pages/builders/app-developers/overview.mdx	Changed all references from "OP Mainnet" to "Metal L2," updating titles and content accordingly.
pages/builders/cex-wallet-developers/cex-support.mdx	Updated all references from "OP Mainnet" to "Metal L2," modifying titles and sections to align with the new terminology.
pages/builders/cex-wallet-developers/wallet-support.mdx	Similar updates as above, with all mentions of "OP Mainnet" changed to "Metal L2."
pages/builders/tools/connect/rpc-providers.mdx	Expanded to include Metal L2 node providers alongside Optimism nodes.
pages/chain/_meta.json	Updated keys related to "getting-started" and "differences" to reference Metal L2 instead of OP Mainnet.
pages/chain/addresses.mdx	Updated chain identifiers and section titles for Ethereum and Metal L2 contracts.
pages/chain/differences.mdx	Changed title and content to reflect differences between Ethereum and Metal L2.
pages/chain/getting-started.mdx	Updated title, description, and content to focus on Metal L2 development, including endpoint URLs and Hardhat contract details.
pages/chain/networks.mdx	Renamed sections and updated parameters to reflect Metal L2 and its Testnet, including new URLs and chain IDs.
pages/chain/tokenlist.mdx	Added sections for "Metal L2" and "Metal L2 Testnet" with corresponding token lists.
pages/connect/contribute/style-guide.mdx	Changed icon color specification from "Optimism Red" to "Metal L2 Yellow."
pages/index.mdx	Rebranded from "Optimism Docs" to "Metal L2 Docs," updating titles, descriptions, and sections accordingly.
pages/stack/_meta.json	Modified "getting-started" key value to reflect updated context.
pages/stack/protocol/fault-proofs/challenger.mdx	Adjusted graph styling by changing stroke color.
styles/colors.css	Updated CSS custom property for color from #FF0420 to #FC9237.
styles/global.css	Changed link color for class a.callout-link.
styles/theme.css	Added new color properties and hover states for link classes, modified SVG fill colors.
theme.config.tsx	Updated logo, project link, footer text, and SEO properties to reflect rebranding.
utils/constants.ts	Added new entries for Metal L2 and Testnet chain IDs with corresponding explorer URLs.

Possibly related PRs

• docs: Update README #905: The changes in the README.md file regarding the rebranding from "Optimism Docs" to "Metal L2 Docs" are directly related to the main PR's focus on updating the documentation to reflect the new branding.

Suggested reviewers

• sbvegan

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	2da3b35
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/66f583620de7d20008a01409
😎 Deploy Preview	https://deploy-preview-929--docs-optimism.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[squdgy]

created against wrong repo