Day 1 · September 17, 2026

What Arc builders should build next.

Researched from the Arc DEX Screener Top-100 trending pairs, cross-checked against official project sites, docs, and product pages. Not a price report — a map of what's already being built, where it's getting crowded, and where the room still is.

Arc is moving from "launch everything" to "build the operating layer."

Executive summary

Launch → Trade → Discover is getting crowded.

The first wave of Arc was a simple sequence — launch, trade, discover — and that layer is filling up fast: launchpads competing on liquidity design and creator rewards, trading terminals racing on PnL and sniper tooling. The question builders should be asking is changing.

Was

"What can I launch on Arc?"

Now

"What infrastructure will every Arc project eventually need?"

Token lockers. Vesting. Creator revenue dashboards. Community tools. Treasury monitoring. Developer APIs. Agent tooling. The strongest Day 1 thesis: the best new products may be the ones that become more valuable as the number of Arc projects increases.

Already crowded

Launchpads and trading terminals.

Argus, Minara, Faze, Tolly, Archemist, Peach, Arcanium, Argos Bot, and Arcade are all differentiating on liquidity structure, creator economics, and anti-snipe mechanics — "we also launch tokens" is no longer enough. ArcTools and Faze are pushing similarly hard on wallet PnL, holder tracking, and trader discovery — a basic chart-price-holders-buy-button product is becoming a commodity.

A new entrant in either category needs a real answer to harder questions: what liquidity structure is meaningfully different, what happens after a token launches, can the product work with tokens created elsewhere, can other builders integrate it?

Where it's heading

AI, identity, and RWA — with caveats.

AI is moving to infrastructure

Parabolic's MCP tooling and CRA Agent's x402 payment stack point at the real opportunity: making Arc natively usable by autonomous software, not another chat interface bolted onto a token.

Identity as a primitive

.arc's readable wallet identity shows how builders can compose with existing primitives instead of rebuilding a username layer for every product.

RWA — be careful

ELLIPSE and LONG are exploring claim-token bridges, but custody, redemption, and legal rights add real complexity. Reserve dashboards and disclosure tools may be the lower-risk entry point.

New primitives are emerging

Kairo (prediction markets), Arc Index 10 (fee-funded indices), and ARCASH (gamified banking) show tokens becoming markets becoming applications — the transition Arc needs to deepen.

The opportunities

Seven things Arc still needs.

Infrastructure that gets more valuable as the ecosystem grows, rather than infrastructure that competes with it.

01 Generic token locker

Neutral infrastructure for arbitrary ERC-20s, not tied to one launchpad. Token → amount → beneficiary → unlock time → lock, with a publicly verifiable page. Gets more useful as more launchpads exist.

02 Generic vesting

Separate problem from liquidity locking. Cliff + linear, monthly, milestone, and multi-beneficiary schedules for teams, investors, advisors, and grants — serving the whole ecosystem, not one venue.

03 Cross-launchpad creator dashboard

Creator economics are fragmenting — every launchpad pays out differently. One wallet, one view: launches, earned, claimable, and reinvestment across every venue at once. Possibly the strongest opportunity here.

04 Community infrastructure

Token-gated roles, holder verification, and automatic role removal for Telegram and Discord — standardized the way trading bots already are. Useful without ever taking custody of user funds.

05 Distribution infrastructure

Beyond a basic multisender: CSV → validate → simulate → deploy → claim → track, with Merkle claims for larger campaigns and real reporting on who claimed and what remains.

06 Treasury & operations

Balances, stablecoins, liquidity positions, vesting obligations, and multisig signers in one dashboard. Read-only first — monitoring can create value long before it ever needs to sign a transaction.

07 Developer infrastructure

A normalized project schema (token, creator, launchpad, pool, quote asset, fees) exposed via REST, WebSocket, webhooks, and MCP — one layer powering every bot, explorer, and agent instead of each reverse-engineering the ecosystem alone.

What to optimize for

How infrastructure gets sticky.

Cross-project utility. Works beyond one token or one launchpad.

Composability. Other builders can integrate it.

Machine readability. APIs, events, schemas, MCP interfaces.

Low custody. Don't hold user funds unless custody is fundamental.

Observable value. Clearly saves time, money, risk, or effort.

A sensible progression: start with read-only infrastructure (indexing, dashboards, alerts) → add utility actions (gating, multisender, claims) → small audited contract utilities (lockers, vesting, escrow) → only then capital routing and execution. The security burden rises sharply at each stage.

Build for the ecosystem, not just your own token.

The first Arc race was who could launch fastest. The next is who builds the tools everyone else depends on.

See who's already building →