Verified Orderbook Token Info

Token Logo

What Do I Need?

  • File Extension: png . Uppercase PNG is considered invalid

  • File Namelogo.png

  • Size: 256px by 256px

  • Background: Preferably transparent

Tip: You can use these online services:

2. Token Information File

  • File Extension: json . Uppercase JSON is considered invalid

  • File Nameinfo.json

What should be put in the info.json file as shown in the example below. Verify that the information provided is correct and formatted properly. The checksum address format must be used for the contract's delivery address (see next requirement).

{
    "name": "BNB Smart Chain",
    "website": "https://www.bnbchain.world/en/smartChain",
    "description": "A blockchain with a full-fledged environment for developing high-performance decentralized applications and cross-chain compatibility with Binance Chain.",
    "explorer": "https://bscscan.com/",
    "research": "https://research.binance.com/en/projects/bnb",
    "symbol": "BNB",
    "type": "coin",
    "decimals": 18,
    "status": "active",
    "tags": [
        "staking-native"
    ],
    "links": [
        {
            "name": "github",
            "url": "https://github.com/binance-chain/"
        },
        {
            "name": "twitter",
            "url": "https://twitter.com/BNBCHAIN"
        },
        {
            "name": "reddit",
            "url": "https://reddit.com/r/BinanceExchange"
        },
        {
            "name": "whitepaper",
            "url": "https://www.binance.com/resources/ico/Binance_WhitePaper_en.pdf"
        }
    ]
}

Fees for Submissions

Any contribution to the SEEDx Order-book repository will incur a nominal SEEDx or INRx cost. This is done to guarantee that priority is given to the projects or validators that really back SEEDx App.

Steps to Add a New Asset

  1. Create a folder whose name is the same as the token contract. Add an info.json file and a logo.png image to the folder.

  2. Choose Fork in the upper right, then wait for the action to finish.

  3. Choose the blockchain folder where the new asset will be stored. Do not close this window.

  4. Go back to the folder you have created and Step 1.

  5. Simply drag and drop the created folder to the active window on Step 4.

  6. In Commit changes box:

    • On the field: Add files via upload, add a meaningful subject line about what you adding to the repo.

    • In Add an optional extended description, please provide additional details on what this request is about. Click on Commit changes once you are done.

  7. The page will revert back to the forked asset screen. Click on Pull Request.

  8. The screen will now show more details about the commit you are about to submit. Click on Create pull request to continue.

  9. Almost done. On the Open a pull request screen, fill up the subject line and provide additional details about your request. Click on Create pull request.

  10. You have successfully submitted your Pull request. A maintainer will verify your request before it gets approved.

When Will The Asset be Added?

After more testing, a maintainer will integrate the pull request. In as short a time as feasible, this will be completed. If there are questions or issues with a pull request, the original submitter will get an email. There will be a new picture on your token after the pull request is merged. Adding the item to the repo, however, will take some time.

Disclaimer

The SEEDx team welcomes contributions of new assets from anybody. This does not, however, imply that we are involved with each and every initiative as a direct partner. Projects that the SEEDx staff determines are fraudulent or a scam will be rejected. Due to fluctuating market circumstances, the danger of fraud, or other causes, the SEEDx team retains the right to modify the terms of asset submissions at any moment. If the item is being used in a spam-like manner, such as being sent to a large number of random addresses, it will be marked as spam and maybe removed from the repository. Also, we are aware that certain projects are attempting to get their tokens included to the Asset database by airdropping tokens to several addresses in order to satisfy the token holder count and the transaction criteria. No unannounced airdrops to users are permitted. Our users should only get the tokens they signed up for, not any that may come their way. We'll be using strict submission screening and will remove these tokens from the app entirely.

Last updated