INPUTS
What is uploaded.
Transcribe a Clip uploads the selected bounded MP4 to the NimProof backend for media validation, quote binding, and local faster-whisper processing. Translate Captions uploads the selected plain-text English SRT for validation and local translation. These files are not written to the Nimiq blockchain.
Full media and subtitle artifacts remain off-chain. During transcription, the worker writes the MP4 to a temporary directory and removes that directory when the worker exits. Transcription input bytes are cleared after a completed receipt or terminal failure and are omitted from durable restart persistence. Translate Captions keeps the submitted and translated SRT text in the off-chain request record so recovery and receipt generation can complete. The repository does not define an automatic record-retention deadline, so the deployment operator must configure temporary-file, request-store, backup, and log retention. NimProof does not make a zero-retention claim.
CHAIN DATA
What enters a transaction.
Transaction data contains only the compact versioned AR1: request commitment. It does not contain the MP4, SRT, translation output, receipt JSON, or private keys.
Quotes and receipts retain the metadata needed to verify the request: service terms, request ID, quote hash, recipient, Luna value, network, transaction reference, commitment, timestamps, and exact artifact SHA-256 hash.
LOCAL VERIFICATION
The recipient's file stays local.
Verified Delivery asks the recipient to select receipt.json and the delivered artifact. The browser hashes the artifact locally. It does not upload the receipt or artifact, connect a wallet, or use public artifact storage.
The browser may retain bounded recovery and presentation metadata needed to resume a request, such as request IDs, quote data, transaction references, and workflow state. It does not store wallet private keys or seed phrases.
WALLET AND TRAINING
What NimProof does not collect.
- NimProof never collects wallet private keys or seed phrases.
- Nimiq Pay owns wallet approval. NimProof receives the provider's transaction reference and verifies the same transaction.
- The local model paths in this repository do not use submitted media or artifacts for model training.
- Cookies and invasive analytics are not used to manufacture usage counts.
LIMITATION
Deployment matters.
This page describes the current repository architecture. A hosted deployment may add infrastructure logs, reverse-proxy retention, backups, or operational monitoring. Review the operator's retention configuration before uploading sensitive media.