Menu
NETWORK / CHECKING

NIMPROOF / THE PROOF PATH

How work becomes verifiable.

NimProof coordinates bounded specialist work with explicit NIM approval and a portable record of what was agreed, paid, and delivered.

THE FLOW

One controlled path from request to artifact.

  1. Select a bounded service and provide the supported input.
  2. NimProof creates signed service terms and a signed quote.
  3. Review the exact amount, recipient, network, expiry, and compact request commitment.
  4. Explicitly approve the payment in Nimiq Pay. Nothing is signed or sent on page load.
  5. The local specialist performs only the bounded task.
  6. The delivered artifact is hashed from its exact UTF-8 bytes.
  7. Payment, commitment, artifact, and receipt are checked independently.
  8. Download or share the Verified Delivery files for another person to check locally.

FLAGSHIP / AGENT RELAY

Two specialists. One linked result.

Agent Relay first pays and runs Transcribe a Clip. The English SRT must match the verified transcription artifact before the next quote appears.

Translate Captions is a separate child job. It has its own quote, recipient, payment, cancellation, recovery, artifact hash, and receipt. The second child payment always needs a separate explicit user approval.

AR-RELAY-1 is a hash-linked parent receipt containing independently signed child receipts.

The parent links both child receipt hashes, the English artifact hash, the translation input hash, and the final Spanish artifact hash. It is not described as an independently signed parent.

VERIFIED DELIVERY

Proof that travels with the file.

A recipient selects receipt.json and the delivered artifact locally. The browser hashes the selected bytes and performs separate checks for signatures, terms, payment, commitment, and artifact integrity. The verifier needs no wallet and never uploads the artifact.

When a payment lookup is unavailable, the payment check stays unknown and retryable. It is not changed into a payment failure. When one artifact byte changes, terms and payment can remain valid while artifact and overall delivery become invalid.

BOUNDARIES

What the proof does not say.

Translate Captions accepts plain-text English SRT files with up to 300 cues and 3,000 subtitle characters. This is a bounded processing safeguard, not a claim about general subtitle support. Receipts establish the recorded payment, request commitment, service terms, and artifact linkage. They do not prove translation quality, transcription quality, legal compliance, ownership, safety, endorsement, or suitability for a particular purpose.