Getting WarpCoin listed (CoinGecko / CoinMarketCap)

This document maps the common listing-tracker requirements to what WarpCoin already provides, and lists the few items that require off-chain action (a public domain, social channels, and an exchange listing for price data).

What a tracker needs, and where WarpCoin provides it

Requirement	Status	Where
Working blockchain with public nodes	✅ built	warpcoin node, seed/DNS roles in deploy/
Public block explorer	✅ built	warpcoin explorer → HTML at /, blocks/txs/addresses, rich list
Circulating supply API (live number)	✅ built	GET /api/supply/circulating (plain decimal)
Total supply API	✅ built	GET /api/supply/total
Max supply	✅ built	GET /api/supply/max (also fixed in metadata)
Machine-readable supply (JSON)	✅ built	GET /api/supply, GET /api/stats
Address & transaction lookup API	✅ built	/api/address/{addr}, /api/tx/{id}, /api/block/{id}
Coin metadata (name, symbol, decimals, supply)	✅ built	branding/coin-metadata.json
Logo (square PNG ≥200×200 + vector)	✅ built	branding/logo.png (256²), branding/logo.svg
Project description / docs	✅ built	README.md, docs/DESIGN.md
Public website / domain	⛔ off-chain	host the explorer at a real domain
Social channels (X, Telegram, Discord)	⛔ off-chain	create and fill into coin-metadata.json
Market/price data	⛔ off-chain	requires listing on an exchange with a public ticker API

Supply definitions (what the endpoints return)

All figures are derived on-chain and served live by the explorer:

• Max supply — premine + every future block subsidy across all halving eras (≈ 229,999,999.77 WARP).
• Total supply — premine (20,000,000 WARP) + all subsidy mined to the tip. Transaction fees are transfers, not new issuance, so they are excluded.
• Circulating supply — total supply minus the balances still held by the genesis reserve addresses (treasury, development, ecosystem). As reserves are distributed on-chain, circulating supply rises automatically and verifiably.

The plain endpoints return a bare decimal number (no JSON), which is the format CoinGecko's "Supply API" fields expect:

$ curl https://explorer.warpcoin.example/api/supply/circulating
9350.00000000

Steps to apply

1. Host a public explorer. Deploy the explorer role (see deploy/) and put it behind a domain with TLS, e.g. https://explorer.warpcoin.example.
2. Run seed + DNS-seed nodes so the network is reachable and decentralized.
3. Publish the supply API URLs (above) — submit the three plain endpoints as the circulating/total/max supply sources in the listing application.
4. Fill in branding/coin-metadata.json with your real domain and social links, and submit branding/logo.png as the logo.
5. List on at least one exchange with a public ticker/orderbook API. Trackers pull price and volume from exchanges — this is the one piece that cannot be produced by the node software itself.
6. Submit the application to CoinGecko (/request-form) / CoinMarketCap with the explorer URL, supply API URLs, logo, source repo, and exchange ticker.

Verifying the data a reviewer will check

# Run a local explorer
warpcoin explorer --http 127.0.0.1:8340

curl 127.0.0.1:8340/api/supply               # JSON: max/total/circulating
curl 127.0.0.1:8340/api/supply/circulating   # plain number
curl 127.0.0.1:8340/api/stats                # height, tx count, difficulty
open  http://127.0.0.1:8340/                  # browse blocks/txs/addresses