Listing new assets

Overview

Listing a new cryptocurrency asset in a wallet or exchange is more than a call to an API — it’s a responsible process that protects users, preserves network integrity, and keeps your platform compliant. This presentation outlines a practical, developer-friendly workflow for evaluating, onboarding, and publishing new assets to Trust ecosystem integrations.

Why a formal listing process?

Hasty listings can expose users to scams, poorly audited tokens, or network instability. A repeatable process reduces risk, speeds approvals, and creates a clear audit trail for teammates and regulators.

High-level steps (what we cover)

• Initial discovery & triage (project metadata)
• Technical validation (token contracts & network compatibility)
• Security & audit checks
• Legal & compliance screening
• Integration & QA (UI, gas estimations, transaction flows)
• Publishing, monitoring and de-listing criteria

1. Initial discovery & triage

Collect canonical project information: contract addresses, token standards (ERC‑20, BEP‑20, SPL, etc.), official website, whitepaper, and verified social accounts. Store metadata in a structured registry and assign a risk score.

Checklist

• Verified contract address and chain ID
• Official project sites and community channels
• Tokenomics summary and total supply data
• Project team disclosure (if available)

2. Technical validation

Run static checks on the token contract: confirm bytecode, check for proxy patterns, and verify token decimals and symbol. Confirm the chain parameters (RPC endpoints, chain ID, native asset, gas model) and any special handling required (fee tokens, wrapped assets).

Tools & commands

Use explorers, block explorers APIs, and contract ABI inspection. Example: eth_getCode, contract verification endpoints, and on‑chain token metadata queries.

3. Security & audit checks

Look for third‑party audits, known vulnerability patterns, and multisig ownership. For tokens without audits, require expanded monitoring and a conservative initial exposure for users.

Best practices

• Require audit reports (or sign an internal risk waiver)
• Check for honeypot behavior and transfer restrictions
• Prefer tokens with timelocks or transparent treasury management

4. Legal & compliance screening

Assess sanctions lists, regional restrictions, and whether the token resembles a security under relevant laws. Work with legal counsel to determine if geographic restrictions are required in listings.

Flags that need legal review

• Centralized governance with profit sharing
• Unclear ownership or anonymous teams with opaque treasury
• Tokens promoted as investment contracts

5. Integration & QA

Implement token UI metadata, ensure correct decimal handling, and test all user flows: send, receive, swap (if available), and view history. Validate gas estimation across RPC nodes and fallback nodes for reliability.

QA checklist

• Accurate token symbol, decimals and logo placement
• Successful testnet/mainnet transactions with varied fees
• Edge cases: failed transactions, reorgs, chain splits

6. Publishing & monitoring

Publish the asset to the registry with a timestamped changelog. Monitor on‑chain behavior for anomalies—sudden large transfers, minting, or rug‑pull patterns—and be prepared to pause or delist if needed.

Monitoring tips

• Set alert thresholds for abnormal token movement
• Use on‑chain analytics and P2P reports
• Keep a rollback playbook: delist, notify users, and freeze UI interactions

De‑listing criteria

Common reasons to remove an asset include confirmed exploits, regulatory orders, or sustained malicious behavior. Document each delisting with why it happened and steps taken to protect users.