Skip to content

feat: update bgb address and add usdt0 address#131

Open
SpectreMercury wants to merge 1 commit intomorph-l2:mainfrom
SpectreMercury:feat-update-contract-address
Open

feat: update bgb address and add usdt0 address#131
SpectreMercury wants to merge 1 commit intomorph-l2:mainfrom
SpectreMercury:feat-update-contract-address

Conversation

@SpectreMercury
Copy link
Contributor

@SpectreMercury SpectreMercury commented Feb 16, 2026

Summary by CodeRabbit

  • Documentation
    • Updated contract address references, including a new USDT0 entry and restructured BGB contract information.

@SpectreMercury SpectreMercury requested a review from a team as a code owner February 16, 2026 08:22
@SpectreMercury SpectreMercury requested review from Web3Jumb0 and removed request for a team February 16, 2026 08:22
@SpectreMercury
Copy link
Contributor Author

@MarvelFisher

@coderabbitai
Copy link

coderabbitai bot commented Feb 16, 2026

📝 Walkthrough

Walkthrough

Updated the Morph Hoodi Contracts documentation section by splitting the existing BGB entry into BGB (old) and a new BGB entry with different addresses, and introduced a new USDT0 contract entry with its corresponding address.

Changes

Cohort / File(s) Summary
Contract Address Documentation
docs/build-on-morph/developer-resources/1-contracts.md
Updated Morph Hoodi Contracts section: separated legacy BGB contract address into a distinct "old" entry, added new BGB contract address, and introduced new USDT0 contract entry with address.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Suggested reviewers

  • Web3Jumb0

Poem

🐰 Hops through the contracts with glee,
BGB splits into old and new decree,
USDT0 joins the blockchain tale,
Addresses shine without fail!

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and specifically describes the main changes: updating the BGB address and adding a USDT0 address in the contracts documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
docs/build-on-morph/developer-resources/1-contracts.md (1)

139-143: Clarify the deprecation status of “BGB (old)”.

Right now “BGB (old)” vs “BGB” is ambiguous. Consider adding a short note (e.g., “deprecated as of ” or “legacy token address”) to prevent users from integrating the wrong address.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant