Neo Smart ChainJoin the launch

Developer documentation

Listing a Token on Neo Smart Chain

How a token joins the registry, with its metadata, documents and multi-chain deployment details.

Version
0.1
Last updated
November 17, 2026
Status
Draft
Download PDF

1.What listing means

The Neo Smart Chain token registry is a public directory of tokens launched on the network. Each listed token gets its own documentation hub with a whitepaper, legal and compliance documents, security reports, integration guides and the list of blockchains it is deployed on, in both web and PDF form.

Listing is a documentation and discovery service. It does not endorse a token, review its financial merits or guarantee its safety.

2.Requirements

  1. A contract deployed on Neo Smart Chain, with verified source code on the explorer.
  2. A token metadata file hosted at a public HTTPS address.
  3. A square logo image hosted at a public HTTPS address.
  4. Identification of the issuer: legal name, jurisdiction and contact.
  5. A whitepaper or litepaper that describes the token, how it works and its risks.
  6. Terms of use and a privacy policy where the token or its website is offered to the public.
  7. A security contact, and a link to an audit report if one exists.

3.Token metadata file

ERC-20 does not define a metadata format, so wallets and registries read a JSON file instead. Host this file at a stable address, such as the root of your own website, and keep it consistent with the on-chain name, symbol and decimals. The USD Neo token publishes its file at neosmartchain.com/metadata.json as a working example.

{
  "name": "USD Neo",
  "symbol": "USDN",
  "description": "A short description of the token and its issuer.",
  "image": "https://neosmartchain.com/logo.png",
  "external_url": "https://neosmartchain.com",
  "attributes": [
    { "trait_type": "Issuer", "value": "Issuer name" },
    { "trait_type": "Token Type", "value": "Utility Token" },
    { "trait_type": "Reference Currency", "value": "USD" }
  ]
}
FieldRequirement
nameFull token name. Must match the contract name().
symbolTicker. Must match the contract symbol().
descriptionOne or two plain sentences. No promises of returns.
imageAbsolute HTTPS URL to a square PNG, at least 256 by 256 pixels
external_urlThe official website of the token
attributesOptional name and value pairs shown on token pages

Serve the metadata file and the logo with an Access-Control-Allow-Origin header set to the wildcard so wallets and applications running in a browser can load them. Without it, many wallets will not display your token.

4.Documentation

Each document is published as a page with a download link for a PDF copy. Documents are grouped into three categories, which become the sections of your token page:

CategoryTypical documents
Whitepapers and researchWhitepaper, litepaper, tokenomics
Legal and complianceTerms of use, privacy policy, risk disclosure, legal opinion, compliance and reserve statements
Technical and securityAudit reports, verified source code, integration guide, bug bounty

A document can be hosted on the registry or linked from your own website. You can publish drafts, but mark them as drafts, and never present a document as final until the people responsible for it have approved it.

5.Deployments on other chains

A token page also lists every blockchain the token is deployed on, so holders can find the right contract address for each network. For each chain, record the chain name, the status (native, live or planned), the contract address, the explorer link and any chain-specific document, such as a bridge guide. The multi-chain guide covers how to keep them consistent.

6.Submitting a listing

  1. Prepare the metadata file, logo and documents described above.
  2. Send the contract address, metadata URL and document links to [listing contact].
  3. The registry team checks that the contract is verified, that the metadata matches the contract and that required documents are present.
  4. Once approved, the token appears at neosmartchain.com/tokens with its documentation hub.
  5. To change a document or deployment later, send an update to the same contact. The page always shows the latest version, and each document carries a version number and update date.

Review process and timing: [listing review process].

7.Delisting and corrections

The registry may remove or flag a listing if the contract is found to be malicious, if required information is false or missing, or if the issuer asks to be removed. Issuers must tell the registry promptly about a security incident, an upgrade or a change of control that affects holders.

Highlighted items in square brackets are network values that are confirmed and published before the public testnet. Code samples are for learning and are not audited. Have any contract that will hold real value reviewed before launch. The latest version is always on this page, and a PDF copy is available above.