FARPY verifies
- The completed render bytes match the recorded output hash.
- The receipt belongs to that job.
- Recorded payment and completion facts for that job, when a receipt exists.
What FARPY proves
Proof shows which file belongs to which completed render.
After a render finishes, FARPY records the job, the downloadable ZIP, a SHA-256 output hash, and a receipt. That chain is how you check you received the same bytes FARPY stored for that job — and what was charged for the completed work.
What a finished FARPY job looks like
Public-safe fields only. This page does not show customer identity, private job IDs, download tokens, filenames, provider IDs, or internal paths.
- Exact quote
- Frame count × $0.01, locked before start. The quote is the price.
- Captured payment
- Wallet debit for completed frames after the approved quote. Unfinished work is not billed as a completed render.
- ZIP artifact
- The downloadable result for that job: finished frames packed as a ZIP.
- SHA-256
- Byte identity of that ZIP. Matching hash means matching bytes. It is not a claim the picture looks right.
- Receipt
- The execution and payment record for that completed job. Open it from Your renders after the ZIP is ready.
Rendered, charged, completed, hashed
- What was rendered
- Your .blend on Blender 4.1.1 Cycles GPU for the frame range on the fixed quote. Published GPU pages show BenchMork measurements of a frozen workload, not your scene.
- What was charged
- Completed frames at $0.01 per frame after that quote. Unfinished, failed, or cancelled work is not billed as a completed render.
- What completed
- A ZIP of finished frames, a receipt in Your renders, and a SHA-256 of those ZIP bytes. Payment status on the receipt is the charge record for that job.
- What SHA-256 proves
- Byte identity. Anyone can rename a ZIP. The output hash is a fingerprint of the exact file. If the hash matches, the file is the recorded result. If it does not, it is a different file.
- What SHA-256 does not prove
- It does not prove the picture looks right, that the scene was what you meant, or that a BenchMork score predicted this job's runtime. Hash match is integrity, not art review.
Job, file, hash, receipt, payment
Proof connects one completed render to one output file. The SHA-256 output hash proves byte identity: these are the same bits. It does not prove the picture looks right, that the scene was what you meant, or that the render is “correct” as art.
- 1Job
The render you submitted: the .blend, the frame range, and the job identity on the receipt.
- 2Completed render
The downloadable result for that job, usually a ZIP of finished frames.
- 3Output hash
A SHA-256 fingerprint of those exact bytes. Same hash means same file. A different hash means a different file.
- 4Receipt
The execution and payment record for that job: identity, what finished, and cost facts when payment applied. A receipt is not a SHA-256, and a hash is not a receipt.
- 5Payment and completion evidence
What was charged for completed work, and that the job reached a finished state. Unfinished work is not billed as a completed render.
Receipt is the record. SHA-256 is byte identity.
A receipt is not a gallery. It is the execution and payment record you keep next to the file. SHA-256 is a fingerprint of the ZIP bytes — integrity, not semantic correctness. Open the receipt from Your renders after a job completes.
- Job identity
- Which render the receipt belongs to, including the file name and frame range when those were recorded.
- Output hash
- The SHA-256 of the completed render. Compare it to the file you downloaded. Matching hashes mean matching bytes.
- Workload and runtime facts
- What ran: renderer, frames completed, and how long the render took when that was recorded. Runtime on a receipt is not a BenchMork prediction for the next scene.
- Payment and cost
- What was charged for completed work, at $0.01 per frame where price is shown. A receipt is not a second charge.
- Completion evidence
- That this job finished and produced a recorded result. Failed or cancelled jobs are not completed renders.
FARPY does not verify
- That the image looks correct or matches your artistic intent.
- That a renamed or edited copy is the original — a changed file gets a different hash.
- Anyone else’s jobs. This page does not list other accounts.
An output hash is 64 hexadecimal characters. Receipts show it in grouped form so you can compare it to a hash you compute from the downloaded file. Example layout:a1b2c3d4 e5f60718 9aabbccd …— not a live customer hash.
Real public evidence, not reviews
These are records FARPY already publishes. They are not reviews, user counts, or a live feed of customer ZIPs. Customer receipts stay with the account that paid.
Published RTX 3090 Blender GPU result
- What was rendered
- One frozen BenchMork Blender GPU workload on a named NVIDIA GeForce RTX 3090. Public facts: 24 GB VRAM, 4.08s render time, Farpy Score 24203, verification PASS.
- What was charged
- Nothing. This is a measurement record, not a customer invoice. FARPY customer jobs are quoted separately at $0.01 per completed frame.
- What completed
- A verified BenchMork result you can inspect on /gpu/rtx-3090/. Other 3090 systems may perform differently.
- What SHA-256 proves
- The published result identifies that measured run. It is not a SHA-256 of a customer ZIP.
- What SHA-256 does not prove
- It does not predict how long your scene will take, and it is not a quote for your file.
Blender 4.1.1 compatibility on RTX 3090
- What was rendered
- A bounded Labs compatibility study for Blender 4.1.1 on RTX 3090 — the same public Blender version FARPY customer Cycles jobs use.
- What was charged
- Nothing. Research records are not customer receipts.
- What completed
- A public research page with the study scope and findings. It is not a live feed of customer jobs.
- What SHA-256 proves
- The research page is the public record of that study. It does not publish customer output hashes.
- What SHA-256 does not prove
- It does not prove a customer image looks correct, and it does not replace a receipt.
What a completed paid render records
- What was rendered
- Your .blend, Blender 4.1.1, Cycles GPU, and the frame range you accepted on the fixed quote. This page does not republish other accounts’ files or names.
- What was charged
- Completed frames at $0.01 each after that quote. Failed or cancelled work is not billed as completed output.
- What completed
- A downloadable ZIP, a receipt in Your renders, and a SHA-256 of those ZIP bytes. Payment status on the receipt shows whether the quoted work was charged.
- What SHA-256 proves
- If you hash the downloaded ZIP and it matches the receipt, you have the same bytes FARPY stored for that job.
- What SHA-256 does not prove
- Byte identity is not semantic correctness. A matching hash does not mean the picture looks right, that the scene was what you meant, or that BenchMork time predicted this job.
Where to find yours
You do not need FARPY internals. After you sign in, Your renders is the place for your jobs, downloads, and receipts.
- Open Your renders
Sign in and go to the workspace. That is the list of your jobs and their status.
- Download the completed render
When a job is ready, download the result from that job. That file is the artifact the hash describes.
- Open the receipt
The receipt on the same job shows job identity, output hash, runtime facts, and payment facts.
There is no live public proof feed here
This page does not publish a live stream of customer jobs, receipts, or hashes. FARPY is not inventing activity to fill the page. Other people’s completed renders stay in their accounts.
No public live feed of customer proofs.Published verified RTX 3090 / Blender evidence is already on the GPU result page and the Blender 4.1.1 research record. Those pages are the public examples. They are not a substitute for your own receipt.
Service uptime belongs on the public status page, not here. This page does not expose other accounts, provider names, machine IDs, secrets, or filesystem paths.
Upload your .blend for an exact fixed quote. That quote is for completed frames. It is not a predicted render time.