How it works

The Thousands Loop

Fund creators. Track outcomes under rules. Execute transfers. Record receipts.

FundCreateProcessTransferReceipt
1

Fund

Partner

Partner deposits budget (USDC/ETH) into a smart campaign vault. The budget is locked and programmable.

  • Define your target outcome (installs, signups, swaps, etc.)
  • Set maximum CPA and total budget
  • Configure quality gates (geo, retention, etc.)
  • Funds remain in a campaign vault and transfers execute only when campaign conditions are met
2

Create

Creator

Independent creators join the campaign, get tracking links/instructions, and publish content to their audience.

  • Creators browse open campaigns and apply
  • Approved creators receive unique tracking links
  • Content published across supported platforms
  • Real-time dashboard shows clicks and conversions
3

Process

Infrastructure

Outcome data is processed from designated data sources according to predefined campaign rules.

  • Attribution via MMP partners (Adjust, AppsFlyer, Singular)
  • Fraud detection: device fingerprinting, IP analysis, behavioral signals
  • Quality gates: geo-targeting, retention checks, deep funnel events
  • Onchain event processing for web3 outcomes (swaps, bridges, stakes)
4

Transfer

Smart Contract

When campaign conditions are met, smart contracts execute transfers from partner-funded campaign vaults to creator wallets.

  • Transfers execute programmatically when conditions are met
  • No manual invoice processing
  • Transfers can be configured as real-time or scheduled per campaign terms
  • Creators can use third-party offramps when available
5

Receipt

Blockchain

A tamper-resistant onchain record of reported outcomes for partner reconciliation and review.

  • Every transfer creates a permanent onchain record
  • Receipt includes: amount, creator, campaign, conversion data hash
  • Partners can reconcile spend and outcomes from receipts
  • Exportable reports for finance/accounting teams

The Three Roles

Partner

The entity funding the campaign. Could be a brand, app, protocol treasury, or foundation.

Responsibilities:

  • • Define campaign outcome & budget
  • • Set quality requirements
  • • Review & approve creators
  • • Monitor performance dashboards

Creator

Content creators who drive attention and conversions through their audience and content.

Responsibilities:

  • • Apply to relevant campaigns
  • • Create authentic content
  • • Drive real conversions
  • • Follow platform guidelines

Operator

Curated entities that manage campaign configuration and run verification infrastructure.

Responsibilities:

  • • Configure campaign parameters
  • • Run verification nodes
  • • Handle dispute resolution
  • • Ensure data integrity
Note: Operators are permissioned initially

Reporting & receipts

Partners get reconcilable reporting (per creator, per outcome, per transfer) backed by onchain receipts.

Outcome reporting
See outcomes by campaign rules and time window
Creator breakdown
Attribution by creator and channel
Quality signals
Fraud + quality gates applied per campaign
Exportable summaries
Finance-friendly exports for reconciliation

Measurement Models

Different campaigns need different measurement approaches. We're honest about what works when.

Recommended

CPA (Cost Per Action)

Pay only when a specific action is completed. Best when you can track the full funnel from click to conversion.

Best for:

  • Mobile app installs
  • Web signups with tracking pixels
  • Onchain actions (swaps, stakes, bridges)
  • Any trackable conversion event
Requires: Attribution integration (MMP, pixel, or blockchain)
Alternative

CPM / Flat Fee

Pay per impression or flat fee when conversion tracking isn't possible. Used for brand awareness or walled-garden destinations.

Use when:

  • Destination is a walled garden (Steam, console)
  • Brand awareness is the goal
  • Integration isn't ready yet
  • Testing before full CPA deployment
Less accountability, but still provides onchain receipts
Why blockchain

Receipts without overhead

It's not about ideology. It's about operational efficiency: transfers execute programmatically and receipts are recorded onchain for reconciliation and review.

Designed for finance teams

No invoices

Transfers execute programmatically when campaign conditions are met.

Global by default

Execute transfers globally without wire transfer overhead.

Onchain record

Anyone can independently review receipts for campaign transfers.

Ready to see it in action?