Reivol1 · Task
Try it on your own GPU first if you want to see the output.
1 to 255
-2.0000
-1.2500
0.01953 per pixel
Fixed point with 12 fraction bits, at most 16,384 pixels, the whole image inside −2 … 2. One byte per pixel: the escape count.
2 · Job preview
- Result
- 16,384 bytes, stored in the submit transaction's log
- Work
- 2,097,152 fixed-point iterations at most
- Your check
- 8 random 16 × 16 tiles recomputed in your browser (full recompute on request)
- GPU needs
- WebGPU with compute shaders and a 65,536-byte storage buffer (every WebGPU adapter allows at least 128 MB)
GPU listings
Reading listings…
Asks and benchmarks are what each provider published; the run estimate divides this job's work by the provider's self-reported benchmark and leaves out claim and submit time.
3 · Price, bond and windows
Held in escrow until the job closes
The provider locks it at claim and loses it to you on a proven fault or no result. 0 lets anyone claim for free, so a stalling provider costs them nothing.
No claim by then: your price comes back
From claim to result; then price + bond come back
You must check within it; after it the provider is paid
- You lock now
- —
- Network fee (estimate)
- Connect a wallet and enter a price to estimate it
- Worst case for you
- Nobody claims: price back after 1 d. Claimed, no result: price + bond back after 1 h. Wrong result you prove: price + bond back.
- Worst case for the provider
- A correct result is paid even if you never answer: anyone can finalize after the 1 d check window.
Public on chain: your address, the parameters, price, bond and every later step. New contract without an independent security review: post small amounts.