feat: add USDC and USDT on BSC

[aimensahnoun]

Summary

• Add USDC and USDT on BSC

Summary by CodeRabbit

• New Features

  • Added support for two Binance Smart Chain stablecoins (USDC and USDT) so the app recognizes BSC-based balances, transfers, and token interactions.

• Chores

  • Updated package metadata: version bumped and timestamp now set automatically during deployment.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Token list metadata and version fields updated; two Binance Smart Chain tokens added (USDC-bsc, USDT-bsc) with ERC20 addresses, 18 decimals, network bsc, and chainId 56.

Changes

Cohort / File(s)	Summary
Token List JSON tokens/token-list.json	Metadata: "timestamp" changed to "Set automatically during deployment". Version bumped from 1.3.2 → 1.4.0. Added two BSC tokens: USDC-bsc (0x8AC76a51cc950d9822D68b83fE1Ad97B32Cd580d, 18 d) and USDT-bsc (0x55d398326f99059ff775485246999027b3197955, 18 d), both ERC20, chainId: 56.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: add USDC and USDT on BSC' directly and clearly describes the main change: adding two tokens (USDC and USDT) to the Binance Smart Chain network. It aligns perfectly with the PR objectives and file changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks 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

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

[greptile-apps]

Greptile Summary

Added two new tokens (USDC and USDT) for the Binance Smart Chain (BSC) network and bumped the version from 1.3.2 to 1.4.0 per the minor version increment convention for new token additions.

Key Changes:

• Added USDC-bsc entry with address 0x8AC76a51cc950d9822D68b83fE1Ad97B32Cd580d
• Added USDT-bsc entry with address 0x55d398326f99059ff775485246999027b3197955
• Both tokens use 18 decimals and chainId 56 (BSC)
• Version incremented to 1.4.0 (appropriate for new token additions)

Issues Found:

• Inconsistent JSON formatting with spaces around colons that don't match the existing code style
• USDT token name "Binance-peg BSC-USD" may be non-standard (typically "Binance-peg USDT")

Confidence Score: 3/5

• Safe to merge after addressing formatting inconsistencies
• The token additions are straightforward and the addresses appear valid. Version bump follows the repository's versioning convention. However, the JSON formatting inconsistencies should be fixed to maintain code quality, and the USDT token name should be verified.
• Only tokens/token-list.json requires attention for formatting corrections

Important Files Changed

Filename	Overview
tokens/token-list.json	Added USDC and USDT tokens for BSC network with version bump to 1.4.0, but contains formatting inconsistencies and potential naming issue

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant PR as Pull Request
    participant JSON as token-list.json
    participant CI as CI/CD Pipeline
    participant Repo as Repository

    Dev->>JSON: Add USDC-bsc token entry
    Dev->>JSON: Add USDT-bsc token entry
    Dev->>JSON: Bump version 1.3.2 → 1.4.0
    Dev->>PR: Create PR #24
    PR->>CI: Trigger validation checks
    CI->>JSON: Validate token addresses
    CI->>JSON: Check schema compliance
    CI->>JSON: Verify no duplicate IDs
    CI->>PR: Report validation results
    PR->>Repo: Await merge to main
    Note over Repo: After merge, create release
    Repo->>CI: Trigger deployment workflow
    CI->>JSON: Update timestamp
    CI->>Repo: Deploy to GitHub Pages

Loading

[greptile-apps]

_{1 file reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}