Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thinkware Token information update request #27858

Closed
wants to merge 3 commits into from

Conversation

teamthinkware
Copy link

Hello, we would like to request that the information and logo of our thinkware token project in the BSC network listed on the CMC platform be updated/added in trustwallet applications.

Hello, we would like to request that the information and logo of our thinkware token project in the BSC network listed on the CMC platform be updated/added in trustwallet applications.
@merge-fee-bot
Copy link

merge-fee-bot bot commented Apr 6, 2024

PR Summary

Files OK: 2
Token in PR: BEP20 0x9689f6e1a4b85d4e0de34c5d7441027adc271f2d
Symbol: ThinkwareAI decimals: 9
Links: Logo Info Website Explorer
Tags: staking-native
Token check error:
❌ id is not in checksum format, should be 0x9689F6e1A4b85d4e0de34C5d7441027ADC271f2D (not 0x9689f6e1a4b85d4e0de34c5d7441027adc271f2d). Please rename it. You may need to rename to a temp name first, then to the checksum format, because lowercase-uppercase-only renames are often ignored by the Git client or the filesystem
❌ number of holders not checked: please, check it manually

@merge-fee-bot
Copy link

merge-fee-bot bot commented Apr 6, 2024

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 with the memo 27858 to the TWT-BEP2 (Binance Chain) address bnb158fgd782we4tz9vwwcj9pmmxvxhl6z46lfm7c8.
Alternatively, 2 BNB is also accepted (same memo & 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

merge-fee-bot bot commented Apr 7, 2024

@teamthinkware, kind reminder: please pay fee: 500 TWT with the memo 27858 to the address bnb158fgd782we4tz9vwwcj9pmmxvxhl6z46lfm7c8.
Alternatively, 2 BNB is also accepted (same memo & address).

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

Correction of error areas
@merge-fee-bot
Copy link

merge-fee-bot bot commented Apr 7, 2024

PR Summary

Files OK: 2
Token in PR: BEP20 0x9689f6e1a4b85d4e0de34c5d7441027adc271f2d
Symbol: ThinkwareAI decimals: 9
Links: Logo Info Website Explorer
Tags: staking-native
Token check error:
❌ number of holders not checked: please, check it manually

Correction of error areas
@merge-fee-bot
Copy link

merge-fee-bot bot commented Apr 7, 2024

PR Summary

Files OK: 2
Token in PR: BEP20 0x9689f6e1a4b85d4e0de34c5d7441027adc271f2d
Symbol: ThinkwareAI decimals: 9
Links: Logo Info Website Explorer
Tags: staking-native
Token check error:
❌ number of holders not checked: please, check it manually

@cryptomanz1
Copy link
Collaborator

As per our policy, there is a minimum requirement of 10,000 holder addresses and 15,000 transactions.
See the criteria at : https://developer.trustwallet.com/listing-new-assets/requirements .

@cryptomanz1 cryptomanz1 closed this Apr 7, 2024
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