Update Testnet Contract Address

[RedHorse823]

Update 3 contract address for accuracy

Summary by CodeRabbit

• Documentation
  • Updated developer resources to display current contract addresses for core network components on the Morph Holesky Testnet. These revisions ensure that integration details remain accurate for users referencing the documentation.

[coderabbitai]

Walkthrough

This update revises the documentation for the Morph Network by modifying contract addresses listed for the Holesky Testnet. Specifically, the addresses for the L1USDCGateway, Staking, and Rollup contracts have been updated in the developer resources file.

Changes

File Path	Changes
docs/.../1-contracts.md	Updated contract addresses for the Morph Holesky Testnet: - L1USDCGateway: 0x2C831...b289 → 0xc90453...7535 - Staking: 0x868dd5...d389 → 0xcb4496...3ad8 - Rollup: 0xd8c5c5...4985c → 0x165b77...f205

Suggested reviewers

• r3aker86

Poem

I'm a rabbit, hopping through lines of code,
Updating contracts on a whimsical road.
New addresses gleam on testnet ground,
Each change a beat in a joyful sound.
With every hop, our docs shine bright –
Celebrating progress with pure delight!
🐇💻

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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 generate docstrings to generate docstrings for this 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

docs/build-on-morph/developer-resources/1-contracts.md (3)

69-70: Review Updated L1USDCGateway Address and Markdown Formatting
The contract address for L1USDCGateway has been updated to 0xc9045350712a1dcc3a74eca18bc985424bbe7535, which aligns with the latest testnet information.
Note: The Markdown link is split across two lines; please verify that this formatting renders correctly in all documentation viewers.

---

155-156: Confirm Updated Staking Contract Address and Link Structure
The Staking contract address has been updated to 0xcb4496399ffd2a94c4c0132c5561b420b8c73ad8 as expected.
Additionally, please check that the line-break within the Markdown hyperlink does not affect the link’s functionality.

---

158-159: Confirm Updated Rollup Contract Address and Link Formatting
The updated Rollup contract address is now 0x165b77247e71fbf53460ede5aecca4e49fbdf205, which reflects the intended changes.
Again, verify that the split Markdown link (across two lines) renders properly in all environments.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 585c260 and e435ef7.

📒 Files selected for processing (1)

• docs/build-on-morph/developer-resources/1-contracts.md (2 hunks)