Tokenization Radar

A read-only directory of on-chain tokens linked to gitlawb apps. Live on the tokens dashboard. Refreshed every 15 minutes.

Sources

The Radar scans three Base-network launchpads:

Clanker — covers Clanker direct + bankr (bankr deploys via the Clanker contract)
Flaunch — Uniswap V4 pool launches
External — for tokens not launched on a discovery-supported launchpad (e.g., the gitlawb network token itself)

Each token surfaces with: symbol, market cap, 24h volume, 24h change, launchpad badge, linked repo (when matched), and a Buy CTA to the launchpad's own page.

How tokens get linked to repos

Two paths get a token into the Radar:

(a) Curated registry

A small JSON file in the indexer maps {repoPath, tokenAddress, launchpad, source} for tokens the team has manually vetted. Used for founder-confirmed launches.

(b) Auto-discovery

The indexer scans Clanker and Flaunch for tokens whose socials or description contain a strong URL signal pointing back at an indexed gitlawb repo. Accepted signals:

{repoName}.gitlawb.app subdomain (the standard gitlawb Playground app URL)
gitdex.app/repo/{id} (explicit linking by the builder)
node.gitlawb.com/{owner}/{name} (the canonical clone URL)

Matched rows are tagged source: "discovered". No matching by token name — that would flood the Radar with impersonators and meme tokens. URL signals only.

Anti-impersonation

Token names like $AGENTVM are unique to one repo only if URL signals confirm it. A different deployer launching $AGENTVM without linking back to the real agentvm repo will not appear in the Radar (or will appear separately, never replacing the verified one).

This is the trade-off: we miss some legitimate launches whose creators forgot to add the URL signal, but we never link a meme or scam under a real builder's name.

Curated vs discovered priority

When both paths surface the same token address:

Curated rows always win (team-vetted, never overwritten)
Discovered rows refresh on each indexer run, replacing any stale auto-match

Market data freshness

Token prices, mcap, and 24h volume are enriched every 15 minutes by a watcher that pings the launchpad APIs (or GeckoTerminal for V4 pools). The Updated X ago indicator on the /tokens page reflects the most recent enrichment timestamp across all tokens.

If a token isn't refreshing (gone dark), it gets filtered out of the live ecosystem view via liveTokens (only tokens with mcap > 0 or 24h volume > 0 appear).

Featured token on landing

The landing page chart shows one featured token at a time, sourced via:

FEATURED_TOKEN_ADDRESS env override (if set)
The gitlawb network token ($GITLAWB) as default
Auto-pick: top live token in DB by 24h volume

For tokens not in our index (the network token itself), metadata is fetched live from the GeckoTerminal API.