A comprehensive, up-to-date collection of information about several thousands (!) of crypto tokens.
Go to file
Shrew 857ab33f9f
Adding updated Shrew contract, logo and information (#13535)
* Delete blockchains/smartchain/assets/0x0C13970D3c5db20d48446a24e29fB9A77cd60De4 directory

Shrew has done a token migration and we need to have the Trust Wallet app pick up the logo for the new contract and stop picking it up on the old one to stop any confusion. Everythings else in the JSON file remains the same apart from the explorer link and the contract. Therefore I propose deleting the directory  '0x0c13970d3c5db20d48446a24e29fb9a77cd60de4' folder and uploading a new one with the new contract and updated the JSON with the correct contract and explorer link.

Thank you so much!

The token has now changed from:
Contract: 0x0c13970d3c5db20d48446a24e29fb9a77cd60de4
Explorer link: https://bscscan.com/token/0x0c13970d3c5db20d48446a24e29fb9a77cd60de4

To:
Contract: 0x3c168c8e0bb11b0a6deeba6c0c6be100e82451bb
Explorer link: https://bscscan.com/token/0x3c168c8e0bb11b0a6deeba6c0c6be100e82451bb

I have uploaded a new folder with the new token name and details.

Announcements showing proof:

Bscscan.com has an official announcement on the old token page (scroll half way down) pointing to the new token address:

https://bscscan.com/token/0x0c13970d3c5db20d48446a24e29fb9a77cd60de4
Our official website explains the migration is complete and buy links / tokenomics section go to the new token address

https://www.Shrew.com shows the new contract.

Twitter announcement on official Twitter account:
https://twitter.com/Shrewdotcom/status/1427767628731457538?s=19

Old Dex Tools token chart redirecting to new token:
https://www.dextools.io/app/pancakeswap/pair-explorer/0xafd0ae1f6e8814a8dba2ecc7fade4b51afb0d570

* Shrew (SHREW) logo and information

Shrew has done a token migration and we need to have the Trust Wallet app pick up the logo for the new contract and stop picking it up on the old one to stop any confusion. Everythings else in the JSON file remains the same apart from the explorer link and the contract. Therefore I propose deleting the directory  '0x0c13970d3c5db20d48446a24e29fb9a77cd60de4' folder and uploading I have uploaded this new one with the new contract and updated the JSON with the correct contract and explorer link.

Thank you so much!

The token has now changed from:
Contract: 0x0c13970d3c5db20d48446a24e29fb9a77cd60de4
Explorer link: https://bscscan.com/token/0x0c13970d3c5db20d48446a24e29fb9a77cd60de4

To:
Contract: 0x3c168c8e0bb11b0a6deeba6c0c6be100e82451bb
Explorer link: https://bscscan.com/token/0x3c168c8e0bb11b0a6deeba6c0c6be100e82451bb

I have uploaded a new folder with the new token name and details.

Announcements showing proof of migration:

Bscscan.com has an official announcement on the old token page (scroll half way down) pointing to the new token address:

https://bscscan.com/token/0x0c13970d3c5db20d48446a24e29fb9a77cd60de4
Our official website explains the migration is complete and buy links / tokenomics section go to the new token address

https://www.Shrew.com shows the new contract.

Twitter announcement on official Twitter account:
https://twitter.com/Shrewdotcom/status/1427767628731457538?s=19

Old Dex Tools token chart redirecting to new token:
https://www.dextools.io/app/pancakeswap/pair-explorer/0xafd0ae1f6e8814a8dba2ecc7fade4b51afb0d570
2021-09-12 20:55:21 -04:00
.github Change fee to 1000 TWT (from 2000) (#13509) 2021-09-10 13:39:23 +02:00
blockchains Adding updated Shrew contract, logo and information (#13535) 2021-09-12 20:55:21 -04:00
dapps Re-add correct Autofarm logo (#13358) 2021-09-04 08:43:05 -07:00
history Fixes (sanity and consistency, auto), history 2021-09-12 23:48:49 +00:00
script Add fantom / arbitrum token type (#13296) 2021-09-02 13:42:58 +08:00
test
.eslintignore
.eslintrc.js
.gitignore
jest.config.js
LICENSE
package-lock.json Bump path-parse from 1.0.6 to 1.0.7 (#12683) 2021-08-11 22:30:03 -07:00
package.json [Internal] Update dependencies (#12532) 2021-08-05 09:32:11 +02:00
README.md Change amount of holders (#13094) 2021-08-26 10:10:18 +03:00

Trust Wallet Assets Info

Check

Overview

Trust Wallet token repository is a comprehensive, up-to-date collection of information about several thousands (!) of crypto tokens.

Trust Wallet uses token logos from this source, alongside a number of other projects.

The repository contains token info from several blockchains, info on dApps, staking validators, etc. For every token a logo and optional additional information is available (such data is not available on-chain).

Such a large collection can be maintained only through a community effort, so feel free to add your token.

How to add token

Please note that brand new tokens are not accepted, the projects have to be sound, with information available, and non-minimal circulation (for limit details see https://community.trustwallet.com/t/how-to-submit-a-token-logo/3863).

Assets App

The Assets web app can be used for most new token additions (Github account is needed).

Quick starter

Details of the repository structure and contribution guidelines are listed on the Developers site. Here is a quick starter summary for the most common use case.

Adding an ERC20 token checklist:

  • Make sure your smartcontract has more than 5000 address holders, otherwise you will be rejected
  • Fork the Github repository
  • Create folder with name of token smartcontact address in checksum format blockchains/ethereum/assets/<token_smartcontract_address>/.
  • Tell your designer that token image must be in PNG format, avoid transparent background, recommended size 256x256px, max. 512x512px, with max file size of 100kB, for further details read image rules.
  • Upload your logo with file named logo.png to previously created folder with smartcontract address, and if you done all correctly your path should look like this. blockchains/ethereum/assets/0x1234567461d3f8Db7496581774Bd869C83D51c93/logo.png
  • Create info.json file with info about the token/project
  • Create a pull request to the main repo
  • Pay the processing fee

Documentation

For details, see the Developers site:

Scripts

There are several scripts available for maintainers:

  • npm run check -- Execute validation checks; also used in continuous integration.
  • npm run check-sanity -- Strict subset of checks
  • npm run fix -- Perform automatic fixes where possible
  • npm run fix-sanity -- Stricter subset
  • npm run updateAuto -- Run automatic updates from external sources, executed regularly (GitHub action)
  • npm run update -- Run manual updates from external sources, for manual use.
  • npm test -- Run script unit tests
  • npm lint -- Run Lint static code check

On Checks

This repo contais a set of scripts for verification of all the information. Implemented as Typescript scripts, available through npm run check, and executed in CI build; checks the whole repo. There are similar check logic implemeted:

  • in assets-management app; for checking changed token files in PRs, or when creating a PR. Implemented as a Typescript library, checks diffs, can be run from browser environment.
  • in merge-fee-bot, which runs as a GitHub app shows result in PR comment. Also uses library, but executes in a non-browser environment.

Trading pair maintenance

Info on supported trading pairs are stored in tokenlist.json files. Trading pairs can be updated -- from Uniswap/Ethereum and PancakeSwap/Smartchain -- using update script (and checking in changes). Minimal limit values for trading pair inclusion are set in the config.ts file. There are also options for force-include and force-exclude in the config.

Disclaimer

Trust Wallet team allows anyone to submit new assets to this repository. However, this does not mean that we are in direct partnership with all of the projects.

Trust Wallet team will reject projects that are deemed as scam or fraudulent after careful review. Trust Wallet team reserves the right to change the terms of asset submissions at any time due to changing market conditions, risk of fraud, or any other factors we deem relevant.

Additionally, spam-like behavior, including but not limited to mass distribution of tokens to random addresses will result in the asset being flagged as spam and possible removal from the repository.