add L1 BGB and L2 BGB(CCIP) #122
Conversation
Deploying morph-doc with
|
| Latest commit: |
6f6f7ac
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f2d4bbdb.morph-doc.pages.dev |
| Branch Preview URL: | https://feat-update-token-contracts.morph-doc.pages.dev |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
pre-rail | 6f6f7ac | Jan 20 2026, 07:10 AM |
📝 WalkthroughWalkthroughDocumentation update to the contracts reference guide, adding a new BGB token entry and updating an existing entry with a label to distinguish it as the legacy version. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docs/build-on-morph/developer-resources/1-contracts.md`:
- Around line 121-122: Update the BGB entries for Morph L2: replace the
incorrect lowercase address entry with the properly checksummed address
0x389C08bc23A7317000A1fd76C7C5b0cB0B4640B5 or remove it if it’s redundant, and
ensure the primary BGB contract is the correct Morph L2 address
0x55d1f1879969bdbB9960d269974564C58DbC3238 (mark as "old" only if intentional);
make the intent explicit in the surrounding text so addresses and labels are
consistent with the document's checksum formatting standard.
🧹 Nitpick comments (1)
docs/build-on-morph/developer-resources/1-contracts.md (1)
141-143: Use checksummed formatting for the new L2 BGB address and confirm correctness.The new L2 BGB address is lowercase while other entries are checksummed. Please normalize to EIP‑55 checksum format and verify the address against the official deployment/source to avoid copy/paste mistakes.
| [BGB](https://etherscan.io/address/0x54D2252757e1672EEaD234D27B1270728fF90581): 0x54D2252757e1672EEaD234D27B1270728fF90581 | ||
|
|
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n docs/build-on-morph/developer-resources/1-contracts.md | sed -n '115,150p'Repository: morph-l2/morph-doc
Length of output: 2159
🌐 Web query:
BGB token Morph L1 Ethereum address 0x54D2252757e1672EEaD234D27B1270728fF90581
💡 Result:
The Ethereum contract 0x54D2252757e1672EEaD234D27B1270728fF90581 is the Bitget Token (symbol: BGB) — an ERC‑20 token (listed on explorers as “BitgetToken / BGB”). CoinGecko shows this address as BGB on Ethereum and links a Morph L2 contract for the token. See Etherscan and CoinGecko for on‑chain and platform details, and an exchange listing note (LBank) referencing the same contract. [1][2][3]
Sources
- Etherscan (token/contract page). [1]
- CoinGecko token metadata (Ethereum and Morph L2 addresses). [2]
- LBank listing announcement referencing the contract. [3]
🌐 Web query:
BGB token Morph L2 address official
💡 Result:
The official BGB (Bitget Token) contract address on Morph L2 is:
0x55d1f1879969bdbB9960d269974564C58DBc3238. [1][2]
Sources:
- Morph docs — Contracts / L2 Tokens (BGB). [1]
- CoinGecko — Bitget Token (morph-l2 platform entry). [2]
🏁 Script executed:
python3 << 'EOF'
from eth_keys import keys
from eth_utils import to_checksum_address
# Verify checksums
address_lowercase = "0x389c08bc23a7317000a1fd76c7c5b0cb0b4640b5"
try:
checksummed = to_checksum_address(address_lowercase)
print(f"Address: {address_lowercase}")
print(f"Checksummed: {checksummed}")
print(f"Match (in lowercase): {checksummed.lower() == address_lowercase}")
except Exception as e:
print(f"Error: {e}")
EOFRepository: morph-l2/morph-doc
Length of output: 148
🌐 Web query:
BGB token migration Morph L2 0x389c08bc23a7317000a1fd76c7c5b0cb0b4640b5
💡 Result:
Short answer: Bitget migrated BGB to the Morph Layer‑2 (BGB is now supported on the Morph Bridge and is the native gas/governance token on Morph). Official announcements and blog posts confirm bridging support, the token migration program/airdrops, and that Bitget transferred a large BGB allocation to the Morph Foundation. [1][2][3]
If you want me to check the specific address 0x389c08bc23a7317000a1fd76c7c5b0cb0b4640b5 (token contract or wallet) I can look it up on the appropriate block explorer (Ethereum and Morph L2) and show the token/transfer details — tell me which chain(s) you want checked and I’ll fetch the transactions and contract info.
Sources:
- Morph blog / announcement (BGB on Morph Bridge). [1]
- Bitget press release on transfer/upgrade to Morph L2. [2]
- Coverage summarizing the transfer and burn/lock plan. [3]
🌐 Web query:
Bitget Token BGB current address Morph mainnet 2025
💡 Result:
BGB on Morph mainnet (Morph L2) — contract: 0x55d1f1879969BdbB9960d269974564C58DbC3238 (18 decimals). Sources: CoinGecko and Morph blog. [1][2]
Correct L2 BGB labeling and checksum on line 143. The current BGB contract on Morph L2 is 0x55d1f1879969bdbB9960d269974564C58DbC3238 (labeled "old" on line 141), not the lowercase address on line 143. Either remove the lowercase entry or clarify its purpose; if it is intentional, it must be checksummed (0x389C08bc23A7317000A1fd76C7C5b0cB0B4640B5) to match the formatting standard used throughout the document.
🤖 Prompt for AI Agents
In `@docs/build-on-morph/developer-resources/1-contracts.md` around lines 121 -
122, Update the BGB entries for Morph L2: replace the incorrect lowercase
address entry with the properly checksummed address
0x389C08bc23A7317000A1fd76C7C5b0cB0B4640B5 or remove it if it’s redundant, and
ensure the primary BGB contract is the correct Morph L2 address
0x55d1f1879969bdbB9960d269974564C58DbC3238 (mark as "old" only if intentional);
make the intent explicit in the surrounding text so addresses and labels are
consistent with the document's checksum formatting standard.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.