Sieveworks

Pay strangers
to compute.
Prove they did.

Verifiable distributed compute, starting with the hardest case: search. Strangers run chunks in a browser tab, paid per verified chunk. Proving the work costs under 1%, not the 200% of running it three times.

no active job0.00% covered
unclaimed searching verified record rejected
✓ witnessmaxseed·rechecked in0.4ms
0
Chunks verified
0
Contributors
0
Seeds total
0.45%
Verify overhead

The fix wasn't cryptography.
It was asking a different question.

Paying anonymous people to search something has one hard problem: the most common honest answer is also the cheapest lie.

✕ unverifiable
“Did you find it in this range?”

A negative answer leaves no artifact. Nothing to check, nothing to recompute, no way to tell an hour of work from an instant reply.

worker → "nothing here"
cost to fake: 0.00s

Everyone else answers this by running every chunk two or three times and comparing. The buyer pays 200% extra for the privilege of not being robbed.

✓ verifiable
“What's the best thing in this range?”

Now the honest answer is a specific claim with a witness attached: a seed that has to actually produce the score you reported.

worker → max 47 · seed 8829371
cost to check: 0.7ms

There is no “nothing” left to fake, and nothing to outvote. Results get recomputed, not polled. A thousand colluding nodes fail the same check one does.

What happens to a chunk

A chunk is a unit of compute: the fixed range of candidates one contributor evaluates. Four verification layers touch every chunk, not just the interesting ones. Under-reporting and over-reporting are caught from opposite directions.

Leased

A range goes out

A contributor takes 100,000 seeds. Abandon it and the lease expires; the range goes back in the pool.

no install · browser tab
Submitted

A witness comes back

The best score found, the seed that produced it, and a Merkle root over every 1,024-seed bucket along the way.

signed by the worker's wallet
Checked

Four ways to catch a lie

Regenerate the witness. Compare against seeds we already know. Open random buckets and recompute them. Slash the stake if any fails.

0.4ms + 1ms + 155ms expected
Settled

Paid, and credited

Earnings accrue per verified chunk. Beat the record and the find is written on-chain, permanently, to your wallet.

credit no one can take back

Any search. Bring your own module.

A worker module defines what a search means: how to score one candidate. Upload any WebAssembly module with three exports and it's fundable; a conformance gate proves it's deterministic before it goes live. Publish it for everyone, or keep it private.

Don't write C? The docs include a ready-made AI prompt: fill in three lines describing your search, paste it into any AI, and upload what it builds.

The money settles on Solana

Nothing here runs on promises. The budget exists on-chain before anyone works, records are attributed permanently, and earnings leave the escrow only with two signatures.

Funded

Locked before work starts

Posting a priced bounty locks the full budget in the job's escrow account. Contributors can see it's real; the funder can reclaim whatever goes unspent.

one escrow per job, on-chain
Attested

Records written permanently

Every verified record is attested on-chain: job, seed, score, finder, slot. Priority no one can rewrite, credit no one can take.

a real explorer link, per record
Claimed

Paid from the escrow

Workers claim accumulated earnings with a voucher co-signed by the coordinator. Replaying an old voucher pays nothing, by arithmetic.

SOL, straight to your wallet

Live on Solana devnet · program on the explorer

It's live. Join the swarm.

A browser tab is a worker. No install, no signup.