FARPY POLICY

Acceptable Use

RENDER RAIL

Upload → Queue → Render → Package → Receipt → Paid

No receipt → no payment.

⇧

01 · Upload

Choose file

Select your scene.

○

02 · Queue

Waiting for GPU

Job enters queue.

▣

03 · Render

GPU rendering

Frames render on a node.

⬡

04 · Package

Preparing output

PNG or ZIP is sealed.

≡

05 · Receipt

Recording receipt

Settlement is written.

✓

06 · Paid

Completed

Receipt-backed finish.

Farpy is for bounded, receipt-backed batch compute. Use it for supported render jobs and lawful workloads only.

Plain rule: do not upload files or submit jobs that attack systems, harm people, violate rights, or break the render rail.

Allowed use

Supported Blender render jobs.
Files you own or are allowed to process.
Lawful creative, test, educational, and production rendering.
Reasonable use that does not overload, bypass, or abuse Farpy.

Disallowed files

Malware, exploit payloads, droppers, credential stealers, or destructive code.
Files designed to attack workers, escape sandboxes, mine crypto, or run unrelated software.
Illegal, stolen, abusive, or non-consensual content.
Files you do not have permission to upload, process, or publish proof metadata for.

Disallowed behavior

Bypassing balance checks, rate limits, auth, job caps, or receipt rules.
Submitting spam, floods, malformed jobs, or intentionally hostile workloads.
Interfering with NodeMunchers, workers, payout logic, receipts, outputs, or public proof pages.
Attempting to create false receipts, duplicate payouts, fake outputs, or misleading settlement records.

Security testing

Do not scan, fuzz, exploit, stress, or probe Farpy infrastructure without written permission. Public endpoints are not an invitation to test production systems.

Public proof

Completed jobs may publish proof metadata. Do not submit a job if public job IDs, costs, timestamps, output links, or receipt fields would create a problem for you.

Enforcement

Farpy may reject jobs, remove outputs, block accounts, throttle traffic, disable workers, preserve evidence, or refund/withhold settlement when abuse, fraud, safety risk, or legal risk is detected.

Worker protection

NodeMunchers are compute workers, not targets. Any attempt to exploit, overload, trick, or harm workers is prohibited.

Final rule

If a workload does not fit a sealed, bounded, receipt-backed batch model, do not submit it.

Effective: April 28, 2026