> ## Documentation Index
> Fetch the complete documentation index at: https://docs.canvas-protocol.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Canvas for partners

> The problem, the product, the market, and the team — an overview for partners and accelerators.

Canvas pays online communities to verify their own members, turning every group join into a priced, sponsored, human-verified transaction. It is a two-sided marketplace on Base: advertisers fund the captcha, group owners get paid in USDC, and humans get in.

<Info>
  This page separates **what is live and verifiable today** from **projections and vision**. Figures labelled as projections are estimates, not results. Where a claim depends on information we have not independently confirmed, it is marked `TODO`.
</Info>

## Live today (verifiable)

<CardGroup cols={2}>
  <Card title="On Base mainnet" icon="check">
    Escrow contract `0xf808b264E13Bf809C8e86afaF4e14c200931101E`, verified on Basescan. USDC settlement is in production.
  </Card>

  <Card title="Working product" icon="robot">
    `@CanvasVerificationBot` runs the full loop: join interception → conversational task → Kimi scoring → USDC payout. Advertiser and group-owner dashboards are live.
  </Card>

  <Card title="Whitelist phase" icon="shield">
    Groups are manually approved during early access to establish quality baselines before the permissionless marketplace opens.
  </Card>

  <Card title="Documented end to end" icon="book">
    Architecture, scoring, smart contract, and anti-gaming are all documented — see [Architecture](/architecture/system-overview).
  </Card>
</CardGroup>

## The problem

Every messaging platform and much of the open web runs the same toll booth — a bot-check on entry — hundreds of millions of times a day. Cloudflare has estimated humanity spends [about 500 years per day](https://blog.cloudflare.com/turnstile-private-captcha-alternative/) solving CAPTCHAs. That attention is real, recurring, and captured today by the platforms running the checks. Three parties lose:

<CardGroup cols={3}>
  <Card title="Owners earn nothing" icon="user-slash">
    Tens of thousands of joins hit communities daily. None of that activity pays the person who built the community.
  </Card>

  <Card title="Advertisers can't reach them" icon="ban">
    The most engaged audiences on the internet live inside chat platforms, where per-verified-human reach doesn't exist.
  </Card>

  <Card title="Data buyers pay for noise" icon="volume-high">
    AI labs pay for volume from context-free labor pools when what they need is verified, context-matched humans.
  </Card>
</CardGroup>

## The solution

Canvas replaces the bot-check with a sponsored task at that exact moment, then settles payouts on Base once Kimi scores the response as genuine. The captcha itself becomes the ad channel — and the data channel. Full mechanics: [How it works](/introduction/how-it-works).

1. A user requests to join a registered group and is muted and DM'd a short task
2. The Canvas agent runs a 2–4 message conversation generated from the advertiser's brief and the group's topic
3. Kimi scores the transcript; a passing score accrues a USDC payout, split 90% to the owner and 10% to Canvas, settled on Base

<Note>
  **Illustrative example (hypothetical).** A perps protocol sponsors a task in a Base DeFi group: *"What can you do on this protocol beyond perps — vaults, staking, or points?"* The user answers, Kimi scores it genuine, the owner is paid, and the protocol can offer the verified user a direct chat with its own agent. Verification becomes the first product touchpoint, not just a gate.
</Note>

## Why now

Onchain USDC settlement, cheap Base transactions, and LLM scoring good enough to grade open-ended conversation only recently became simultaneously available. Canvas needs all three: programmatic per-verification micropayments, and a scorer that can tell a genuine human answer from a pattern response. The incumbents (Google, Cloudflare) will not build this — pricing verified human attention onchain means giving up the data-and-attention moat they capture for free.

## Differentiation

<CardGroup cols={2}>
  <Card title="The captcha is the channel" icon="bullseye">
    Reach a context-matched human at the one moment they've self-selected into a specific community — not an impression, a verified interaction.
  </Card>

  <Card title="Provenance you can't fake later" icon="fingerprint">
    Each completion carries the group context, a Kimi quality score, and a verifiable on-chain settlement transaction. This can't be reconstructed by scraping audience lists after the fact.
  </Card>
</CardGroup>

## The bigger market: verified human data

Crypto is the wedge because both sides already speak the language. The market is every fandom and interest community. The same mechanism that verifies a DeFi trader can collect a preference label from a verified fan — reasoning data that exists nowhere else, because it requires a verified member explaining their own taste, in their own words, at the moment they chose to join. This is the RLHF thesis behind Canvas: context-matched, quality-scored human completions with delivered provenance.

## Economics

Canvas takes a **10% protocol fee**; the group owner keeps **90%** of the winning bid. The floor price is **\$0.10 per verification**, and advertisers bid above it — niche, high-intent groups command real competition, undifferentiated ones settle near the floor. Phase 2 re-verification turns a group's existing membership into recurring revenue at the same rate. Worked figures: [Business model](/protocol/business-model) and [Payouts](/group-owners/payouts).

<Note>
  Our June 2026 deck modelled a $0.05 floor with a 50/50 split; the **live product uses a $0.10 floor and a 90/10 split\*\* (owner/Canvas), matching the deployed contract and docs. `TODO: Founder input required` — confirm which model is canonical going forward and align the deck.
</Note>

## Market size (projections)

<CardGroup cols={2}>
  <Card title="TAM — RLHF platforms" icon="chart-line">
    Global RLHF platform market projected at **$12.4B (2025) → $111.1B (2034)**. *Source: Grand View Research, per company deck (June 2026).*
  </Card>

  <Card title="Closest comp — Telegram verification" icon="telegram">
    Rose, the leading Telegram verification bot, is cited at **\~2M monthly active chats** — the distribution Canvas targets. *Source: Rose bot FAQ, per company deck (May 2026).*
  </Card>
</CardGroup>

The go-to-market is bottom-up: onboard active crypto groups at the floor price, before any bidding war or re-verification cadence, then expand past crypto. {/* TODO: Founder input required — confirm the SOM figure to publish; the deck's $3M/yr estimate assumed the earlier $0.05 / 50-50 model. */}

## Traction

Canvas is in **mainnet beta, whitelist phase**. The contract, bot, scoring, payouts, and dashboards are live and verifiable. {/* TODO: Founder input required — groups onboarded, verifications completed, and USDC settled to date, if any. We publish real numbers only, never estimates as traction. */}

## Go-to-market

<CardGroup cols={2}>
  <Card title="Supply — group owners" icon="users">
    Direct outreach to crypto KOLs running active Telegram communities. The first owner earning real USDC from an existing group becomes the case study; supply grows from PR, not a sales motion.
  </Card>

  <Card title="Demand — advertisers" icon="briefcase">
    Crypto protocols and agents already understand verified attention — no education required. This is the deliberate, revenue-bearing half of the market. {/* TODO: Founder input required — confirm named design partners (e.g. Bankr, Avantis) and whether they can be listed publicly. */}
  </Card>
</CardGroup>

## Architecture

A Node/TypeScript agent server on Railway orchestrates Telegram, a conversational LLM, the Kimi scorer, Postgres state, and the Base escrow contract. Strict TypeScript, a test suite, and a Foundry-tested contract back it. Full detail: [System overview](/architecture/system-overview), [Verification flow](/architecture/verification-flow), [Scoring](/architecture/scoring), [Smart contract](/architecture/smart-contract).

## Team

<CardGroup cols={2}>
  <Card title="Rohit Sarkar — Product & Infrastructure" icon="user">
    Years across crypto infrastructure (0x, Caldera, InfStones). Selected for The Vault (an EigenCloud × ETH Foundation builder residency) as one of five featured projects, where the original Canvas architecture was built.
  </Card>

  <Card title="Alexander Vicol — Product & Engineering" icon="user">
    Full-stack systems engineer specializing in Base-native infrastructure and production onchain AI agents. Base Batches 002 alumnus; shipped agent infrastructure featured in the Base ecosystem.
  </Card>
</CardGroup>

**North star:** 100,000 group-chat owners able to pay their rent from Canvas earnings.

## Roadmap

Phase 1 (live) → Phase 2 re-verification (recurring revenue) → Phase 3 permissionless marketplace (staking, anti-sybil, self-serve) → Phase 4 Solana. Detail and targets: [Roadmap](/protocol/roadmap).

## Try it

<Card title="Add the bot to a group" icon="telegram" href="https://t.me/CanvasVerificationBot">
  Start a Telegram group with [`@CanvasVerificationBot`](https://t.me/CanvasVerificationBot), make it an admin, and you're set. Questions or partnership: <a href="mailto:hello@canvasprotocol.xyz">[hello@canvasprotocol.xyz](mailto:hello@canvasprotocol.xyz)</a>.
</Card>