How Farpy Verification Works

A Farpy receipt is a signed statement about a compute job. Verification checks that the receipt was produced by Farpy and has not been altered.

What a receipt contains

• Identifiers for the job
• The input bytes observed by Farpy
• The output bytes observed by Farpy
• A cryptographic signature over those bytes

What verification proves

• The receipt was signed by Farpy
• The input and output bytes have not been modified
• The receipt corresponds to a specific job

What verification does not prove

• That the output is correct
• That the computation was deterministic
• That a specific model or environment was used
• That the output is safe, useful, or intended

Verify a receipt yourself

Verification is offline and reproducible using Farpy’s public artifacts:

• Signing specification
• Public key
• Reference verifier
• Receipts index

A typical verification flow:

RID_FILE="$(curl -fsS https://farpy.com/receipts/ | grep -oE 'RID-[A-Z0-9-]+\.json' | head -n1)" && \
curl -fsS "https://farpy.com/receipts/$RID_FILE" -o receipt.json && \
curl -fsS https://farpy.com/signing/public_key.pem -o public_key.pem && \
curl -fsS https://farpy.com/signing/verify.py -o verify.py && \
python3 verify.py receipt.json public_key.pem

If verification succeeds, the verifier prints OK:VERIFY.

← Back to Farpy