Skip to content

Add OSDT Token Metadata for BSC (Chain 56) - #1932

Closed
justv030-cyber wants to merge 3 commits into
MetaMask:masterfrom
justv030-cyber:master
Closed

Add OSDT Token Metadata for BSC (Chain 56)#1932
justv030-cyber wants to merge 3 commits into
MetaMask:masterfrom
justv030-cyber:master

Conversation

@justv030-cyber

@justv030-cyber justv030-cyber commented Aug 28, 2026

Copy link
Copy Markdown

Token Information

  • Token Name: OSDT
  • Symbol: OSDT
  • Decimals: 18
  • Chain: Binance Smart Chain (BSC, Chain ID: 56)
  • Contract Address: 0x92e6cd65260fCbAaDb2E37B73499D882177dDAeF

Submission Checklist

  • Address is in checksum format
  • Logo provided (PNG format, square, high resolution)
  • Metadata JSON file created

Additional Details


Note

Low Risk
Metadata-only addition with no application or contract logic changes.

Overview
Adds a new OSDT token metadata entry for Binance Smart Chain (eip155:56) at contract 0x92e6cd65260fCbAaDb2E37B73499D882177dDAeF4.

The new JSON registers name/symbol OSDT, 18 decimals, marks the asset as ERC-20, and points the logo to the matching icon path under ./icons/.

Reviewed by Cursor Bugbot for commit 96adb75. Bugbot is set up for automated code reviews on this repo. Configure here.

@justv030-cyber
justv030-cyber requested review from a team and MRabenda as code owners August 28, 2026 23:55

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 96adb75. Configure here.

"symbol": "OSDT",
"decimals": 18,
"erc20": true,
"logo": "./icons/eip155:56/erc20:0x92e6cd65260fCbAaDb2E37B73499D882177dDAeF4.png"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Invalid token contract address

High Severity

The CAIP-19 filename and logo path append an extra 4 to the contract address, producing a 41-character hex string that is not a valid EVM address. Lookups for the real OSDT contract on BSC miss this entry, and the referenced logo file does not exist.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 96adb75. Configure here.

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