RACKVO
Open dashboard

Building on it

Receipt Inspector

Check downloaded receipt and result files for structure, Job association and output hash consistency.

Public integration status

Production endpointShell
curl --fail-with-body https://www.rackvo.fun/api/compute/config

This public endpoint reports integration availability without provider credentials or private RPC settings.

Local development onlyShell
curl --fail-with-body http://127.0.0.1:6230/api/compute/config

Choose the two files

Open the Dashboard, complete a demo task, and download its receipt and result. Open Receipt Inspector and select both files. Files are read in your browser; this inspection does not submit a task or transfer funds.

What the Inspector checks

CheckScope
StructureSupported receipt schema, required fields, quote arithmetic and a parseable result file.
Job associationThe result Job ID matches the receipt ID and the embedded result agrees. Older demo files without a result Job ID are linked through the exact result and hash.
Input hashSHA-256 of the trimmed input encoded as UTF-8.
Output hashSHA-256 of UTF-8 JSON.stringify(result), including its property order.
Record consistencyCompare the uploaded receipt to the full selected Job when one is available.

The downloaded JSON may be pretty-printed. Hash the parsed result object using JSON.stringify, not the complete result file and not the pretty-printed receipt bytes. Reordering result properties changes this digest. This rule is the same one used when the browser demo creates a receipt.

Manual JSON inspection

Read a receipt fileShell
python3 -m json.tool receipt.json

JSON syntax validation only establishes that a file can be parsed. Use the Inspector to compare the associated result and digest. Unsupported schemas, missing files, mismatched IDs and changed output must not be reported as consistent.

Inspection limits

Requirements for live records

A live integration needs an approved receipt schema, authenticated provider identity, persisted quote and Job, and verified payment records. Optional provider signatures require their own authenticated signing key and verification rules. Solana payment confirmation remains a separate server check.

Last updated 29 October 2026.