Skip to content

Add USDT Staking (USDT.s) token on BNB Smart Chain#36251

Closed
skzfq7vcmj-sys wants to merge 1 commit intotrustwallet:masterfrom
skzfq7vcmj-sys:add-usdt-staking-bsc-token
Closed

Add USDT Staking (USDT.s) token on BNB Smart Chain#36251
skzfq7vcmj-sys wants to merge 1 commit intotrustwallet:masterfrom
skzfq7vcmj-sys:add-usdt-staking-bsc-token

Conversation

@skzfq7vcmj-sys
Copy link
Copy Markdown

Summary

Adding USDT Staking (USDT.s) token to the BNB Smart Chain (BSC) token list.

Token Details

Files Added

  • blockchains/smartchain/assets/0xF8Af0B1c89431250D03F6230D51441E7Ef71394d/logo.png (256x256)
  • blockchains/smartchain/assets/0xF8Af0B1c89431250D03F6230D51441E7Ef71394d/info.json

Checklist

  • Logo is 256x256 PNG
  • info.json follows the required format
  • Token contract is verified on BSC
  • Token has active liquidity on PancakeSwap V2

@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot bot commented Apr 12, 2026

PR Summary

Files OK: 2
Token in PR: BEP20 0xF8Af0B1c89431250D03F6230D51441E7Ef71394d
Symbol: USDT.s decimals: 6
Links: Logo Info Website Explorer
Tags: stablecoin
Token check error:
❌ missing required fields: website field
❌ at least 2 links are required, 0 present. Add as many as you can: twitter, github, telegram, reddit, etc
❌ number of holders not checked: please, check it manually

@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot bot commented Apr 12, 2026

Hi! In order to compensate for the efforts of processing PRs, we kindly ask for a contribution.
💀 As there is no refund, before paying the fee, make sure new tokens fulfill the minimum circulation and other acceptance criteria.
See also the PR Fee FAQ.

Please pay 500 TWT to the BEP20 (Binance Smartchain) address 0xFB30db6C89aFA7a177Adbe553bB0d15EA40A39E2.
Alternatively, 2.5 BNB is also accepted (same address).

QR code: Trust | other wallet

TWT Acquiring:

Notes:

  • New tokens without significant usage are rejected, see criteria mentioned above.
  • One PR should be for a single project; PR's with more than 10 logos will be rejected.
  • Payment evaluation happens automatically, but with a few minutes delay. When payment is detected, an Accept Review is automatically placed on the PR, which is a condition for merge.
  • Evaluating the PR is done manually, and it is merged only if all conditions are satisfied.
    There will be a fee to process this request. None of it goes to the developers.
    Before paying the fee, make sure new tokens fulfill the minimum circulation and other acceptance criteria.
    If you are paying TWT for the submission, this will be burned automatically. There will be no refunds.

@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot bot commented Apr 13, 2026

@skzfq7vcmj-sys, kind reminder: please pay fee: 500 TWT to the address 0xFB30db6C89aFA7a177Adbe553bB0d15EA40A39E2.
Alternatively, 2.5 BNB is also accepted (same address).

QR code: Trust | other wallet
See the Pull Request Fee FAQ.

2 similar comments
@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot bot commented Apr 13, 2026

@skzfq7vcmj-sys, kind reminder: please pay fee: 500 TWT to the address 0xFB30db6C89aFA7a177Adbe553bB0d15EA40A39E2.
Alternatively, 2.5 BNB is also accepted (same address).

QR code: Trust | other wallet
See the Pull Request Fee FAQ.

@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot bot commented Apr 14, 2026

@skzfq7vcmj-sys, kind reminder: please pay fee: 500 TWT to the address 0xFB30db6C89aFA7a177Adbe553bB0d15EA40A39E2.
Alternatively, 2.5 BNB is also accepted (same address).

QR code: Trust | other wallet
See the Pull Request Fee FAQ.

@merge-fee-bot
Copy link
Copy Markdown

merge-fee-bot bot commented Apr 14, 2026

This PR is being closed due to inactivity. If you wish to continue, please have us reopen the PR before sending your payment, or just create a new one.
Do NOT send payments for closed PR, as the fee may by lost!

@merge-fee-bot merge-fee-bot bot closed this Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants