Reivol

Put Idle GPUs to Work.

Shared GPU Power. Useful Work. Requesters pay for finished, checkable tasks, not GPU hours. Providers run them in a browser tab with WebGPU.

Post a jobOffer your GPU
Job board live on Robinhood Chain ↗2 task templates, small by designNo income promised

● Robinhood Chain reading…Block —Gas —ETH / USD —Jobs posted —In escrow —

A graphics card, drawn for Reivol
What runs today

Work you can check. Two task templates run today: a fractal render and a matrix multiply. Each result is checked in your browser in seconds, and a wrong value can be proven on chain.

Built on open pieces

  • WebGPU
  • Robinhood Chain
  • Freivalds' check
  • Fixed-point math

Pick a task template and its size. Before you book, the job preview checks which listed GPUs can run it, how many result bytes it makes and what it will cost at each provider's ask.

ReivolJob boardPost a jobProvideGPU listingsRules

Job preview

Fractal render, 128 × 128 pixels, 255 iterations at most. Checked by recomputing 8 random tiles of 16 × 16 in your browser.

Result size16,384 bytes
Work, at most4.18 M iterations
Listings that fitcompatible
Provider GPULimitsAsksEst. run
Listing 1fitsits askfrom its bench
Listing 2fitsits askfrom its bench
Listing 3too small——
Sample screen

Offer your GPU from a browser tab. WebGPU reports the adapter and its limits, a short benchmark runs here, and you set your price and hours. The listing lives on chain, no server needed.

ReivolJob boardPost a jobProvideGPU listingsRules

Your GPU, from this tab

WebGPU adapter, limits and a benchmark measured here. You set the price and the hours; the listing is stored on chain.

WebGPUavailable
Fractal bench— M it/s
Integer probe0 differences
Float probemeasured here
Ask, fractalyour price
Hours (UTC)your choice
Sample screen

Read the execution report. Status and times come from the chain. Your browser checks the output: sampled tiles for a fractal, Freivalds' algorithm for a matrix. One wrong value is enough to win a dispute.

ReivolJob boardPost a jobProvideGPU listingsRules

Execution report

Status, times from the chain, the output, and the check your browser ran on it.

StatusResult in, check window open
Check8 / 8 tiles match
If a value were wrongprove it on chain
Sample screen
Two sides

Work that can be checked

Post a task, or let your GPU run one. Both from a browser.

Post a job

Pick a template, set a price in ETH and a bond the provider must lock. The price waits in escrow until the result is checked.

Get startedLearn more

Offer your GPU

List the GPU you already have, set your own price and hours, claim jobs that fit, and get paid when the result stands.

Get startedLearn more
Results, not hours

Pay for the output, not the time

An hour of GPU time is not a result. Reivol prices the finished task and lets you check it.

Renting GPU hours

You pay for
Time on a machine, whether or not the job worked
You get back
Whatever ran in that time
Provider drops out
Depends on the operator
Checking
Up to you, after paying

A Reivol job

You pay for
One finished task with a fixed result size
You get back
The result bytes, on chain, with their hash
Provider drops out
Price and the provider's bond come back to you
Checking
In your browser before you accept; a wrong value is provable on chain

Bounded tasks

At most 16,384 result bytes per job. Small enough that the contract can recompute any single value.

Checkable output

Integer math only, so every GPU gives the same bits. Your browser checks; the chain settles a dispute.

Timeouts refund

No claim in time, or no result in time: the price goes back, with the provider's bond if one was locked.

From post to payout

One job, five steps, all on chain

  1. 01 · PostThe requester posts a job with a template, its parameters and a price. The price is held by the job board.
  2. 02 · ClaimA listed provider claims it and locks the bond the requester asked for. A run window starts.
  3. 03 · RunThe provider's browser runs it with WebGPU and submits the result bytes before the window ends.
  4. 04 · CheckThe requester's browser checks the result: sampled tiles or Freivalds' algorithm, in seconds.
  5. 05 · SettleAccept, prove a wrong value, or wait. The window closing without a proven fault pays the provider.
Nobody decides disputes. A requester wins only by naming one value the contract recomputes and finds wrong; otherwise the provider is paid when the check window closes. There is no arbiter and no admin.

Put your idle GPU to work

List it from a browser tab. No install, no account, only a wallet.

Record

A track record the chain keeps

Jobs paid, faults proven and jobs abandoned are counted by the contract for every listing. Nobody can edit them.

Benchmark

Measured in your browser

fractal + matmul
on your GPU

The numbers are self-reported by the provider's tab and shown as such. Requesters compare listings, then the result is what counts.

Payment

Paid in ETH when the job closes

your ask · ETH

Price plus your bond back on accept, or when the check window closes. Withdraw any time.

Limits

What Reivol does not do

  • 01Reivol does not run arbitrary AI workloads. Machine-learning inference and other task types are planned, and only after each one has a check that works.
  • 02No income is promised. What a provider earns depends on jobs posted, the price set, the GPU, and the electricity it uses.
  • 03If a provider disconnects after claiming, nothing is lost for the requester: when the run window ends, anyone can close the job and the price plus the provider's bond go back to the requester.
  • 04ReivolJobBoard is new code that holds ETH in escrow. It has not had an independent security review. It needs one before real volumes; until then use small amounts.

Run a task you can check

Try a template on your own GPU first: it runs here, with no wallet and no contract.

Try a templateRead the rules