FARPY LABSPublished research, findings, and evidence.
TECHNICAL BRIEF · REVIEW CANDIDATE · VERSION 0.4

FARPY Public Technical Brief

Verified distributed compute and receipt-backed execution

This document summarizes FARPY’s current public model and verified evidence. It intentionally omits private infrastructure and security-sensitive implementation details.

ARCHIVAL STATUS

Historical review candidate, not a later FRS result.

Historical review-candidate brief, version 0.4, dated 2026-07-22. Claims below are the original public-model summary. They are not upgraded. The originally linked per-result URL /benchmark/result/NMBENCH-V4-20260714T210332Z-898218 is a stale JS shell and is not restored; the inspectable public proof record is /proof?result=NMBENCH-V4-20260714T210332Z-898218.

StatusREVIEW CANDIDATE
Version0.4
Review date2026-07-22 UTC
ScopeCurrent public model and public evidence as of 2026-07-22
ABSTRACT

FARPY’s public model is organized around verifiable execution: published benchmark results connect a controlled workload, measured result, hardware configuration, and verification outcome to inspectable public evidence.

FARPY exists to make distributed compute easier to trust, compare, and use.

This brief describes the current public model, the evidence presently published, and the boundaries of those claims. It does not describe every internal mechanism.

CLAIMS
  • Verified benchmark results can be published with inspectable evidence.
  • Known physical inventory is separate from verified benchmark configurations and verified results.
  • Missing evidence remains missing rather than becoming an estimate.
NON-CLAIMS
  • Known inventory is not a claim that every listed GPU has a verified benchmark.
  • The current evidence does not establish verified RTX 3080 performance.
  • The current evidence does not establish verified Octane performance.
  • FARPY does not claim that every workload is deterministic, every result is independently reproduced, or arbitrary workloads are supported.
  • This brief makes no uptime, capacity, security-certification, compliance, or settlement guarantee.
SYSTEM MODEL
ControlValidates bounded work, coordinates execution, and evaluates returned evidence.
ExecutionRuns bounded workloads on eligible GPU hardware.
TruthPublishes inspectable result, benchmark, and proof artifacts when evidence qualifies for public classification.
EVIDENCE LIFECYCLE
  1. A bounded workload is submitted.
  2. An eligible worker executes that workload.
  3. Outputs and execution evidence are returned.
  4. Verification classifies the returned evidence as passing, failing, or unavailable.
  5. Accepted evidence governs result classification and accounting eligibility.

An accepted receipt records the evidence used to classify completed work and determine accounting eligibility under FARPY’s governing model. It does not, by itself, prove that a payment was completed. Payment completion is a separate event requiring its own evidence. This paper does not claim public payout volume, payment timing, or automatic payment completion.

No receipt, no payout. A payout cannot become eligible without an accepted receipt. This principle does not guarantee payment timing, payment completion, or public payout volume.

VERIFICATION SEMANTICS
  • Frozen method. The procedure, software versions, parameters, and evaluation rules are fixed before execution. Freezing a method does not make a workload deterministic.
  • Deterministic workload. The workload is expected to produce the same defined output under the same controlled conditions. Determinism does not, by itself, establish reproducibility or prove that independent reproduction occurred.
  • Comparable benchmark. Runs use sufficiently controlled methods to support comparison. Comparability does not establish that a result is reproducible.
  • Reproducible result. Repeated evidence supports the same result under the stated method and conditions. Reproducibility remains workload- and evidence-dependent.
  • Independently reproduced result. A separate execution reproduces the result and is explicitly recorded as such. FARPY does not claim independent reproduction without a separate matching execution record.
  • Failures remain visible.
  • Incomplete or failed evidence does not graduate into verified truth.
PUBLIC EVIDENCE AS OF 2026-07-22

The brief recorded one verified Blender configuration.

Verified benchmark configurations: 1
GPU: NVIDIA GeForce RTX 3090 with 24 GB
Renderer: Blender using CUDA/OptiX
Runtime: 4.08 seconds
Farpy Score: 24203
Verified Octane results: 0

Known physical GPUs recorded in the brief: 5 (4 RTX 3090, 1 RTX 3080). Inventory presence is not benchmark verification.

Result ID: NMBENCH-V4-20260714T210332Z-898218

WHAT IS NOT PROVEN
  • Public verified hardware coverage remains narrow.
  • Not every known GPU has a verified benchmark.
  • Workload support is intentionally bounded.
  • Experimental results do not automatically graduate into production truth.
  • This document describes current public behavior, not every internal mechanism.
VISION

A compute network where completed work is measurable, evidence is inspectable, and economic settlement follows proven execution.

VERSION HISTORY
0.4Evidence and terminology remediation; benchmark facts split across their supporting public records; determinism separated from independent reproduction; Octane evidence linked directly; reproducibility language aligned across public surfaces.
0.3Adversarial remediation; visible review date added; receipt eligibility separated from payment completion; frozen methods separated from deterministic methods; benchmark evidence linked to its specific public proof.
0.2Deep claim audit; unsupported language removed or narrowed; claims and non-claims, limitations, evidence links, and version history added.
0.1Initial public-safe draft.
EVIDENCE