AsksOpen AsksPro Asks

Sandbox · nothing here is real money · How does this work?

One campaign, 1,362 approved completions: what we learned

A past clean-up campaign put 1,362 approved completions on the public record. What the verifier handled, why some failed, and what it means for any ask.

By Shaun Conway9 min read

Key takeaways

  • One clean-up campaign put 1,362 approved completions on the public record, each with a signed decision and a receipt anyone can open.
  • On the Map a mess ask, 1,354 of 2,420 completions were approved, about 56%, and the weekly rate held between 52% and 61%.
  • Most rejections were duplicates: 684 of 1,004 first failed the requirement that nothing approved is already within 60 m.
  • The verifier made about 53 decisions a day, and the median time from completion to approval on Map a mess was 23 seconds.
  • Approvals on Map a mess moved no money from the ask, so this case study is about approvals, not earnings.
On this page8 sections

One clean-up campaign has run on Asks at scale. By 30 Oct 2026, 1,362 completions on its asks had been approved, each with a signed decision and a receipt anyone can open (the campaign board, read on 30 Oct 2026).

Completions have nearly stopped, and clean-ups are not something we sell. It is the largest test the system has had, and every number below can be checked on the public record.

What the campaign was

The campaign was Spotless, run for World Cleanup Day 2026 under the tag wcd26 through the Spotless app (how it works, read on 1 Nov 2026). It was organised by the Yoma Impacts Exchange in collaboration with Trashcoin. On the public ledger every one of its asks was posted by one account, ixo1567g…aqvzlc. Its first asks opened on 18 Sep 2026 and its last on 30 Oct 2026. The first completions were decided on 18 Sep and the last on 30 Oct 2026 (the public ledger, read on 1 Nov 2026). It had two kinds of ask. Most were tied to one place: clean up the waste here and photograph it. One, called "Map a mess", was open to anyone: photograph illegal waste where you find it.

The campaign's dates. Spacing is by event, not to scale.

The scale, as of 30 Oct 2026:

WhatNumberSource
Asks in this campaign1,318Discover
Places on the campaign board977, with 964 still openCampaign board
Approved completions on the campaign's asks1,362Campaign board
Completions sent to "Map a mess"2,420, of which 1,354 were approvedDiscover

Most open places were in Nigeria (918), with others in South Africa (28), Georgia (17) and Slovenia (1). These counts are approximate, read from map coordinates on 30 Oct 2026.

All 1,362 approved completions are on this campaign's asks: 1,354 on "Map a mess", 5 on an earlier mapping ask that closed in September, and 3 on clean-up asks (the public ledger, read on 1 Nov 2026). The places stay open because each one is its own clean-up ask, open for 30 days after it was posted. Only 15 of the 1,352 clean-up asks received a completion. The last were posted on 30 Oct, so places keep closing until 29 Nov 2026, and the board showed 882 still open on 1 Nov. The "Map a mess" ask itself is open until 31 Jan 2027.

What the verifier handled

Every completion went to the Asks verifier, the default for new asks since 18 Sep 2026 (read on 31 Oct 2026). In the 30 days to 1 Nov 2026 it signed 1,589 decisions, 880 of them approvals: about 53 decisions a day, at its listed price of $0.50 a decision (the verifiers page and the public ledger, read on 1 Nov 2026). All but 4 of those decisions were on "Map a mess".

Over the whole life of the "Map a mess" ask, 1,354 of 2,420 completions were approved, about 56%. The rate held steady: in each week from 21 Sep to 25 Oct 2026, between 52% and 61% of decisions were approvals, and 55% in the last 30 days.

Map a mess over its whole life: about 56% of completions approved.

Speed held up at that volume. The board's median for the campaign's poster was 1 minute (the campaign board, read on 30 Oct 2026). That is the time from a completion arriving to its approval on the ledger, and the board never shows less than a minute. Across the 1,354 approvals on "Map a mess" the median was 23 seconds. On one receipt from 19 Oct 2026, a completion went from sent to a signed decision in 61 seconds.

What a passing completion had to meet

Since 21 Sep 2026 each completion to "Map a mess" has been held to nine requirements. The ask opened on 20 Sep with an earlier set of six, and each receipt pins the version it was judged against. Some were measured:

  • something was handed over
  • nothing in the photograph says an AI generator made it
  • it was taken at the place reported, and a location was given
  • nothing already approved on this ask is that close

Others were judged by AI review: that the photograph shows a real outdoor place, that it shows waste dumped where it does not belong, that the size given roughly matches, and that nobody in it is identifiable and no number plate is legible.

The completions were going to be public, so the requirements made privacy a condition of payment.

What failed checks looked like

We opened three rejected completions on the receipt page on 31 Oct 2026. The verifier checks the requirements in order and stops at the first one that fails. The record names that requirement and marks the rest "not reached".

  • Two completions from 20 Oct 2026 were already mapped. They met five requirements, then failed one: "Something approved on this ask is already within 60 m". One was decided in under 25 seconds. The other took under 10 minutes, most of it in the verifier's fact gathering.
  • A completion from 29 Oct 2026 met two requirements, then failed the AI review that the photograph shows a real place outdoors. The rest were not reached. It was decided in under 35 seconds.

In each case nothing was released, and the decision was signed like an approval.

Across all of them, we read the signed receipt of every rejected completion on 1 Nov 2026, from the decision engine's public receipts. Of the 1,004 rejections under the nine requirements, the first requirement each one failed was:

First requirement failedRejected completionsShare
Something approved on this ask is already within 60 m68468%
The photograph shows a real place outdoors10010%
The size given roughly matches9610%
A location was reported454%
The photograph shows dumped waste293%
Taken at the place reported222%
A fact could not be gathered, so a requirement could not be checked182%
Nobody identifiable and no number plate legible91%
Nothing says an AI generator made it1under 1%
Already mapped spots were 68% of rejections under the nine requirements. Bars are to scale.

The other 61 rejections came in the first two days, under the six requirements: 29 were already mapped, 10 gave no location and 22 failed an AI review. Where a fact was missing, the verifier rejected the completion rather than guess.

What we learned

Specific requirements make clear rejections. "Something approved on this ask is already within 60 m" leaves little to argue about. Every rejected completion names the requirement it failed, so a person who sends a duplicate can see why and go find a new spot.

The facts are fixed before the decision. The verifier gathers every fact first, the page says the facts were frozen, and only then is the decision made. The full trace is pinned by a hash, so anyone reading the receipt later sees what the decision was based on.

Public records need privacy rules written in. The requirement that nobody be identifiable kept the public record publishable.

One verifier handled the load: about 53 decisions a day, each signed by the Asks verifier, with a median under a minute, without the poster reading completions by hand.

What this means for any ask

The campaign was photographs of waste, but the lessons are about asks in general: a fact from a place, a written report, a translation or a code change all go through the same steps. Three things carry over.

Throughput is not the limit. Most asks get a handful of completions, so the pace is set by the person or agent doing the work, and a verifier that made about 53 decisions a day keeps up.

Measure what can be measured. Location, duplicates and file properties were measured, and only the rest went to AI review. Written work can be measured less, so its requirements need more care, and an ask can name a person who gives the final approval after the verifier's check. What is a Pro Ask? shows how that works when invited pros send reports.

The record can be public or private.

A public ask

  • Clean-up completions were public.
  • Each receipt shows the decision and which requirements were met.

A private ask

  • The approval is public and the completion stays private.
  • The person who did the work can point to it without exposing the poster.

When you post, write requirements the verifier can check, and say before work starts what counts as done. Read how verification works for the full walk through one decision, or compare verifiers on the verifiers page.

FAQ

What is a verifiable work record?

A record of a piece of work that anyone can check later: what was asked, what was sent, which requirements it met, who decided and when payment moved. On Asks each approved completion has a receipt page.

Is the clean-up campaign still running?

Its asks are still open on the ledger, but completions have nearly stopped: three were decided in the last week of October 2026. We describe it as a case study of the system at scale. Asks does not sell clean-up campaigns.

How many completions did the verifier reject?

On the "Map a mess" ask, 1,354 of 2,420 completions were approved as of 30 Oct 2026, so about 1,066 were not approved. The receipt page on 31 Oct 2026 listed 1,065 rejected and 1 waiting to be checked.

Who decided which completions were approved?

The Asks verifier, against requirements fixed before each completion was sent (nine since 21 Sep 2026), with each decision signed. On a Pro Ask, the person who posted it gives the final approval after the verifier's check.

Can I see the evidence for an approved completion?

On a public ask like this one, yes: each receipt shows the decision and which requirements were met. On private asks, such as Pro Asks, the approval is public and the report stays private.

Write your own ask

What is an ask? walks through posting one from start to receipt, and the board shows the asks open now.

Shaun Conway

Shaun Conway is a physician and founder of IXO, where he brings his expertise in human judgement and decision-making into building systems for voluntary intelligent cooperation that shapes the world we want.