Platform
Everything an aggregator, wallet, portfolio tracker or AI agent needs to list and display Diggers-launched tokens: public REST endpoints, a standard token list, on-chain metadata, and verified contract addresses that are identical on every chain.
Two public JSON endpoints serve DexScreener-shaped token data. Both return Access-Control-Allow-Origin: * and cache at s-maxage=60.
GET /api/token-info/{address} — full detail for one token: chain ID, name, symbol, decimals, total supply, icon, Open Graph image, description, IPFS metadata URI, social links, creator, timestamps, price, market cap, 24h volume, pool info, and a launchpad object with graduation progress (supply sold toward the 80% bar) and Blue chip progress (holders, volume, average mcap versus their targets).
GET /api/token-info?limit=100&offset=0 — paged list with summary fields (no links, pool or launchpad detail). Good for bulk pulls and discovery feeds.
GET /tokenlist.json serves the standard Uniswap token-list schema. Every tradable Diggers token across all supported chains, with address, chain ID, name, symbol, decimals (18), logo URI, and extensions (graduated, a launchpad marker). Cache: s-maxage=300.
Every DiggersToken exposes a public metadataURI() view returning an IPFS URI that points to a JSON object with name, symbol, description, image and social links. The Created event on the hub carries the same URI at creation time, so indexers can pick it up without an RPC call.
Diggers emits every protocol event, and serves every ecosystem read, from a single DiggersHubcontract per chain. Indexers subscribe to one address, plus each token's plain ERC-20 Transfer/Approval, and get the whole protocol: trades, harvests, points, holder counts, epoch settlements, graduations, Blue chip changes and locks.
The core contracts deploy at identical addresses on every chainand are verified on each chain's explorer (Etherscan on Ethereum, Blockscout at robinhoodchain.blockscout.com on Robinhood Chain, StableScan at stablescan.xyz on Stable):
0xdEBA423Ab2D46650061555aaBEC362673c811b440x5044E79669Fee78A7bC2007A8e7AE4f820252e4b0xF37b72a3cB71489F2b95Cf7373681a28AFEfD1A8Every launched token is an EIP-1167 minimal-proxy clone of a single immutable implementation deployed by the launchpad (readable via TOKEN_IMPLEMENTATION()). Once that implementation is verified, explorers auto-match all clones as verified proxies.