What Is MEW\u2019s Permanent Default Token List?<\/h2>\n\n\n\n
MyEtherWallet<\/a>, usually called MEW, provides interfaces for Ethereum and several compatible blockchain networks. A default token can appear automatically after MEW recognizes its contract. Users should not import that token manually.<\/p>\n\n\n\n By contrast, custom tokens may remain local to one browser. Therefore, custom imports do not provide global visibility. Read the official MEW custom-token guide<\/a> before testing permanent support.<\/p>\n\n\n\n Correct metadata helps users identify the intended contract. Furthermore, a verified logo reduces confusion between similar symbols. Token owners may also improve other wallet listings. For example, follow Tokpie\u2019s Trezor token guide<\/a>. Then, review the MetaMask token logo guide<\/a> for another important wallet workflow.<\/p>\n\n\n\n The public MEW repository accepts network-specific token files. These files describe the token and its official contract. Next, a separate image file supplies the token logo. After review, MEW maintainers may merge both files.<\/p>\n\n\n\n A metadata pull request does not set any USD price. Therefore, never place a fixed price inside token JSON. Instead, MEW must map the exact network and contract to an accepted live market asset. Many projects first pursue market tracking. Tokpie explains exchange token listing<\/a> in a separate guide.<\/p>\n\n\n\n Furthermore, projects can review Tokpie\u2019s CoinMarketCap listing guide<\/a> before requesting price support. Projects can also open the Tokpie exchange platform<\/a> without leaving this publication.<\/p>\n\n\n\n Record the token name, on-chain symbol, checksum contract address, decimals, website, support contact, and social links. Then, verify those values on the correct blockchain explorer. Never copy details from a similarly named token. For external explorers, add verification links with nofollow. For example, use the relevant contract page carefully.<\/p>\n\n\n\n MEW separates token files by network. Therefore, an Ethereum token and a BNB Smart Chain token use different directories. For example, a BEP-20 token belongs inside the BSC directory. Do not place it inside Ethereum\u2019s token folder. Ethereum owners can inspect the MEW Ethereum token directory<\/a>. However, BSC owners must use the BSC folder.<\/p>\n\n\n\n Use a square PNG with a transparent background. MEW recommends a 128 by 128 pixel image. Next, compress the image without destroying transparency. A small file loads faster across web and mobile interfaces. The image filename should contain the symbol, checksum contract address, and network suffix.<\/p>\n\n\n\n For a BNB Smart Chain token, use the network suffix shown by current repository examples.<\/p>\n\n\n\n The next stage uses the official MEW ethereum-lists repository<\/a>. First, confirm your GitHub account is correct. Then, fork the repository before adding network-specific files.<\/p>\n\n\n\n The repository name reflects MEW\u2019s history. However, the same repository now contains several supported blockchain networks. Therefore, a BNB Smart Chain owner still forks the complete repository. The token later enters the BSC subdirectory.<\/p>\n\n\n\n By contrast, Ethereum tokens use their own network directory. Never place a BEP-20 file inside Ethereum\u2019s folder.<\/p>\n\n\n\n Click the repository\u2019s Fork control. Next, select the intended GitHub account as the new repository owner. Keep the repository name unchanged. Also, copying only the master branch is enough for a normal contribution.<\/p>\n\n\n\n GitHub redirects to the new personal repository. Confirm that the page states it was forked from MyEtherWallet. Furthermore, confirm that the master branch matches the upstream repository before creating any token files.<\/p>\n\n\n\n GITHUB-FORK-CREATED-SUCCESSFULLY.webp<\/strong><\/p>\n\n\n\n After creating the fork, open Before adding anything, search the repository for the complete contract address. This prevents duplicate token records. GitHub may truncate large directories. Therefore, use repository code search instead of checking only visible filenames. The expected token filename uses the checksum contract address followed by the JSON extension.<\/p>\n\n\n\n If a matching file exists, update that record instead. However, create a new file when the search returns no match.<\/p>\n\n\n\n Open the current branch menu inside the BSC directory. Then, enter a clear branch name for your token submission.<\/p>\n\n\n\n Next, create the new branch from Use the Add file menu inside Enter the complete checksum contract address as the filename. Next, add the Then, paste the token metadata into the editor. Check every address character before continuing.<\/p>\n\n\n\n Set MEW validates token objects against a fixed field list. Therefore, unsupported keys can make automated checks fail. Review the current MEW token validator<\/a> before using a new field. Put tracker pages and security audits in the pull request description. However, keep them outside the token JSON.<\/p>\n\n\n\n Choose a clear commit message describing the token metadata addition. Then, commit directly to your dedicated branch. After that, reopen the file from GitHub. Confirm that the saved JSON matches the approved content.<\/p>\n\n\n\n The metadata file and repository icon are separate files. Therefore, upload the approved PNG after committing the JSON.<\/p>\n\n\n\n Return to your dedicated branch. Next, open Confirm the branch name before uploading anything. Otherwise, GitHub may place the icon on the wrong branch.<\/p>\n\n\n\n Name the PNG with the token symbol, checksum contract address, and correct network suffix.<\/p>\n\n\n\n For other networks, inspect nearby icons and use their current suffix. However, never guess the network label.<\/p>\n\n\n\n Use the approved 128 by 128 transparent PNG. Then, verify the filename contains no spaces or hidden characters. The hosted Select Add file, then choose the upload option. After that, select the final PNG from your computer. Confirm the displayed filename carefully. Next, choose a short commit message describing the token icon. Commit directly to the same dedicated branch. Therefore, the JSON and PNG will enter one pull request.<\/p>\n\n\n\n Open the committed icon from GitHub. Confirm its branch, filename, dimensions, transparency, and visible file size. Then, record the commit link as evidence. You will also use that link during later troubleshooting.<\/p>\n\n\n\n Open GitHub\u2019s compare view against the latest upstream The base repository should be MyEtherWallet\u2019s official repository. Next, select Review the commit count, file count, additions, and deletions. Then, inspect every displayed filename and diff. The source changes should include the network token JSON and its repository icon. Remove unrelated files before continuing.<\/p>\n\n\n\n MEW\u2019s generator extracts the checksum address from each icon filename. Therefore, the address casing must remain exact. The generator matches icons by checksum address, not only by symbol. A network suffix can remain after the address. Review the current MEW address extraction code<\/a> when checking unusual filenames.<\/p>\n\n\n\n Read the official MEW pull request workflow<\/a> before testing your branch.<\/p>\n\n\n\n The token validator checks required fields, supported token types, address format, and exact object keys. Therefore, unsupported price, audit, or tracker fields must remain outside the token JSON.<\/p>\n\n\n\n The compile command rebuilds MEW\u2019s distribution lists. After that, inspect every generated file before committing it.<\/p>\n\n\n\n Include the network-specific generated changes when compilation updates them. However, exclude unrelated generator noise. Furthermore, confirm the generated master entry contains the correct network, address, symbol, and repository icon URL.<\/p>\n\n\n\n For a BSC submission, compilation updates two network files and the global master list.<\/p>\n\n\n\n The normal JSON remains readable. However, the minified version stores identical data without extra formatting. The master list uses the repository icon URL. Therefore, confirm it does not depend only on the hosted logo. Commit these files to the same token branch. Then, compare that branch against upstream GitHub should show only intended source and generated files. Furthermore, it should report automatic merge ability. Review every addition and deletion carefully. A minified file may appear as one replaced line.<\/p>\n\n\n\n When the comparison is clean, select Create pull request. Next, confirm both repositories and branches again.<\/p>\n\n\n\n The base must be the official MyEtherWallet repository. Select Use a direct title containing the token name, symbol, and network. Then, summarize the metadata and icon changes. Include these verification details in the description:<\/p>\n\n\n\n Keep tracker and audit links outside token JSON. However, they can help maintainers verify the project.<\/p>\n\n\n\n Create the pull request only after reviewing its preview. Then, save its number and permanent GitHub URL.<\/p>\n\n\n\n Open the MEW pull-request list<\/a> and search using the saved pull request number. Then, compare the result with a previously merged MEW token contribution<\/a>. Tokpie also keeps the original approval-status reference<\/a> available for returning readers. Do not open duplicate pull requests for the same token. Instead, push later corrections to the existing branch.<\/p>\n\n\n\n A public GitHub review on July 17, 2026 found 51 pull requests opened during the previous 24 months. None were merged. Six were closed without a merge, while 45 remained open. This equals 0% merged, 11.8% closed without merge, and 88.2% still open. However, GitHub does not label unmerged closures as rejections. Four of the six were closed by their authors. The remaining two had unavailable actor data.<\/p>\n\n\n\nWhy Permanent Token Metadata Matters<\/h3>\n\n\n\n
Understand the Logo and Price Split<\/h2>\n\n\n\n
The Token Repository Controls Identity Data<\/h3>\n\n\n\n
MEW\u2019s Market Backend Controls Price Data<\/h3>\n\n\n\n
Prepare Everything Before Opening GitHub<\/h2>\n\n\n\n
Collect the Canonical Token Details<\/h3>\n\n\n\n
Choose the Correct Blockchain Directory<\/h3>\n\n\n\n
Prepare the Token Logo<\/h2>\n\n\n\n
SYMBOL-0xChecksumContractAddress-network.png<\/code><\/pre>\n\n\n\n![\"MEW](\"https:\/\/tokpie.io\/blog\/wp-content\/uploads\/2020\/12\/MEW-TOKEN-LOGO-REQUIREMENTS-1024x781.webp\"){kind=logo}
Logo Checklist<\/h3>\n\n\n\n
\n
Fork the Official MEW Token Repository<\/h2>\n\n\n\n
Why BSC Tokens Still Use ethereum-lists<\/h3>\n\n\n\n
src\/tokens\/bsc\/<\/code><\/pre>\n\n\n\nCreate the GitHub Fork<\/h3>\n\n\n\n
![\"GitHub](\"https:\/\/tokpie.io\/blog\/wp-content\/uploads\/2020\/12\/GITHUB-FORK-MEW-ETHEREUM-LISTS-1024x756.webp\")
Confirm the Fork Was Created<\/h3>\n\n\n\n
Open the BSC Token Directory<\/h2>\n\n\n\n
src<\/code>, then tokens<\/code>, and finally bsc<\/code>. The complete path must read src\/tokens\/bsc<\/code>. Therefore, verify the breadcrumb before creating any file.<\/p>\n\n\n\n![\"MEW](\"https:\/\/tokpie.io\/blog\/wp-content\/uploads\/2020\/12\/BSC-TOKEN-DIRECTORY-GITHUB-1024x355.webp\")
Search for an Existing Contract File<\/h3>\n\n\n\n
0xChecksumContractAddress.json<\/code><\/pre>\n\n\n\nCreate a Dedicated Token Branch<\/h2>\n\n\n\n
add-your-token-symbol-bsc<\/code><\/pre>\n\n\n\nmaster<\/code>. GitHub should select that branch automatically after creation. Confirm the new branch name beside the file tree. Therefore, later changes will stay separate from your master branch.<\/p>\n\n\n\n![\"Dedicated](\"https:\/\/tokpie.io\/blog\/wp-content\/uploads\/2020\/12\/GITHUB-FORK-CREATED-SUCCESSFULLY-1024x826.webp\")
Create the BSC Token Metadata File<\/h2>\n\n\n\n
src\/tokens\/bsc<\/code>. Then, select the option for creating a new file.<\/p>\n\n\n\nName the File With the Checksum Contract Address<\/h3>\n\n\n\n
.json<\/code> extension without extra characters.<\/p>\n\n\n\n0xChecksumContractAddress.json<\/code><\/pre>\n\n\n\n![\"GitHub](\"https:\/\/tokpie.io\/blog\/wp-content\/uploads\/2020\/12\/CREATE-BSC-TOKEN-JSON-FILE-1024x536.webp\")
Use the Supported MEW Token Fields<\/h3>\n\n\n\n
type<\/code> to BEP20<\/code> for BNB Smart Chain tokens. Also, enter decimals as an integer. The symbol should match the contract\u2019s on-chain symbol. However, avoid changing punctuation for marketing preferences.<\/p>\n\n\n\n{\n \"symbol\": \"TOKEN\",\n \"name\": \"Token Name\",\n \"type\": \"BEP20\",\n \"address\": \"0xChecksumContractAddress\",\n \"ens_address\": \"\",\n \"decimals\": 18,\n \"website\": \"https:\/\/example.com\/\",\n \"logo\": {\n \"src\": \"https:\/\/example.com\/token-logo.png\",\n \"width\": \"128px\",\n \"height\": \"128px\",\n \"ipfs_hash\": \"\"\n },\n \"support\": {\n \"email\": \"support@example.com\",\n \"url\": \"https:\/\/example.com\/support\"\n },\n \"social\": {\n \"blog\": \"\",\n \"chat\": \"\",\n \"discord\": \"\",\n \"facebook\": \"\",\n \"forum\": \"\",\n \"github\": \"\",\n \"gitter\": \"\",\n \"instagram\": \"\",\n \"linkedin\": \"\",\n \"reddit\": \"\",\n \"slack\": \"\",\n \"telegram\": \"\",\n \"twitter\": \"\",\n \"youtube\": \"\"\n }\n}<\/code><\/pre>\n\n\n\nDo Not Add Unsupported Price or Audit Fields<\/h4>\n\n\n\n
Commit the Metadata File to Your Branch<\/h3>\n\n\n\n
Upload the Token Logo to the MEW Icons Directory<\/h2>\n\n\n\n
Open the Shared Icons Folder<\/h3>\n\n\n\n
src<\/code>, then open the icons<\/code> directory.<\/p>\n\n\n\nsrc\/icons\/<\/code><\/pre>\n\n\n\nUse the Repository Icon Naming Pattern<\/h3>\n\n\n\n
SYMBOL-0xChecksumContractAddress-bsc.png<\/code><\/pre>\n\n\n\nKeep the Final PNG Ready for Review<\/h4>\n\n\n\n
logo.src<\/code> remains useful. However, it does not replace the repository icon in this contribution.<\/p>\n\n\n\nUpload and Commit the Icon<\/h3>\n\n\n\n
![\"GitHub](\"https:\/\/tokpie.io\/blog\/wp-content\/uploads\/2020\/12\/UPLOAD-MEW-TOKEN-ICON-1024x635.webp\"){kind=icon}
Verify the Uploaded File<\/h4>\n\n\n\n
Review the Token Branch Before Opening a Pull Request<\/h2>\n\n\n\n
master<\/code> branch. Do not compare only against your fork.<\/p>\n\n\n\nConfirm the Base and Head Branches<\/h3>\n\n\n\n
master<\/code> as the base branch. Your fork should be the head repository. Then, select the dedicated token branch as the comparison branch. GitHub should report that the branches can merge automatically. However, this message does not replace repository tests.<\/p>\n\n\n\n![\"GitHub](\"https:\/\/tokpie.io\/blog\/wp-content\/uploads\/2020\/12\/REVIEW-MEW-BRANCH-DIFF-1024x875.webp\")
Inspect Every Changed File<\/h3>\n\n\n\n
Confirm the Icon Can Match by Address<\/h4>\n\n\n\n
Run the Current MEW Pull Request Checks<\/h3>\n\n\n\n
npm install\nnpm run compile\nnpm run lint\nnpm run test:checkMasterFile\nnpm run test:checkToken\nnpm run test:checkContract\nnpm run test:checkNft<\/code><\/pre>\n\n\n\nReview Generated Distribution Files<\/h4>\n\n\n\n
dist\/tokens\/NETWORK\/tokens-NETWORK.json\ndist\/tokens\/NETWORK\/tokens-NETWORK.min.json\ndist\/master-file.json<\/code><\/pre>\n\n\n\nCommit the Three Generated Files<\/h3>\n\n\n\n
\n
dist\/tokens\/bsc\/tokens-bsc.json<\/code><\/li>\n\n\n\ndist\/tokens\/bsc\/tokens-bsc.min.json<\/code><\/li>\n\n\n\ndist\/master-file.json<\/code><\/li>\n<\/ul>\n\n\n\nmaster<\/code> again.<\/p>\n\n\n\n![\"GitHub](\"https:\/\/tokpie.io\/blog\/wp-content\/uploads\/2020\/12\/GENERATED-MEW-DISTRIBUTION-FILES-1024x498.webp\")
Check the Final Comparison Summary<\/h4>\n\n\n\n
Open the MEW Token Pull Request<\/h2>\n\n\n\n
Confirm the Pull Request Direction<\/h3>\n\n\n\n
master<\/code> as the base branch. The head must be your fork and dedicated token branch. Otherwise, the contribution may target the wrong repository.<\/p>\n\n\n\nWrite a Verifiable Pull Request Description<\/h3>\n\n\n\n
\n
Record the Pull Request Number<\/h4>\n\n\n\n
![\"MEW](\"https:\/\/tokpie.io\/blog\/wp-content\/uploads\/2020\/12\/CREATE-MEW-TOKEN-PULL-REQUEST-1024x498.webp\")
Track the Pull Request Approval Status<\/h3>\n\n\n\n
MEW Pull Request Statistics: Last 24 Months<\/h2>\n\n\n\n