Why ArcLens is different
On a brand-new chain, the hardest problems aren’t technical — they’re about trust and recognition.
- Early builders ship real work and get no users, no revenue, and no recognition.
- The AIs that increasingly read their docs and contracts pay them nothing.
- Newcomers — human or agent — can’t tell what’s real from what’s noise.
ArcLens exists to fix that, and it does it with three things most directories don’t have:
1. A real trust layer
Every project carries a trust standing derived from on-chain attestations, not vibes. It’s the same signal humans see on a project page and that agents read over the API. See The trust layer.
2. An agent that pays builders
Lens AI doesn’t just answer questions about Arc — it pays the verified builders whose work grounded each answer, a fraction of a cent in USDC, on-chain, with a receipt. The payment isn’t income; it’s a public signal that the ecosystem’s own AI relied on a real team. See Lens AI.
3. A nanopayment economy that can’t be farmed
Payments only flow to Arc-native builders at the Verified, Established, or Claimed tiers — never to infrastructure, the chain itself, or risk-flagged projects. Caps, per-caller de-duplication, and accrue-to-claim keep it honest. See The nanopayment economy.
The result: building on Arc becomes something that earns recognition, automatically — and any agent gets a trustworthy source for “who’s real on Arc.”
What we believe
- Builder-first — every feature is built around what builders and testers actually need.
- USDC-native — Arc is the first L1 where USDC is the native gas token. Every metric on ArcLens is shown in real dollars, not gwei or ETH.
- Open to read — browse the ecosystem, metrics, and trust layer freely, no account needed to start.
- Community-powered — the ecosystem directory and campaigns are built by and for the Arc community.