Menu
NETWORK / CHECKING

NIMPROOF / SECURITY AND VERIFICATION

Release only when the evidence agrees.

NimProof treats terms, payment, request commitment, artifact bytes, and receipts as separate evidence that must reconcile.

SIGNED TERMS

Every job starts with a fixed quote.

Backend-signed terms and quotes bind the registered service, input hash, source and target language, exact Luna amount, configured recipient, network, request ID, expiry, signing key ID, and request commitment. The frontend verifies the quote before enabling approval. The backend verifies it again.

PAYMENT EVIDENCE

Hash, fields, and finality all matter.

The verifier checks the exact recipient, Luna value, sender, network, request commitment, successful execution, and finalized transaction state through the configured Nimiq RPC. A returned hash or inclusion alone is not enough. RPC unavailable, network unverified, still pending, not found, and field mismatch remain distinct states.

Payment verification unavailable is retryable. It never becomes a green payment state and it never triggers a replacement payment.

ARTIFACT EVIDENCE

Exact bytes, not a normalized copy.

Artifacts are hashed from their delivered UTF-8 bytes. The local verifier does not normalize line endings, add a final newline, remove a BOM, or upload the selected file. A one-byte change invalidates the artifact check while leaving independent terms and payment checks visible.

RECEIPTS

Portable proof with honest scope.

Single-service receipts contain signed terms, quote and payment evidence, commitment, artifact metadata, artifact hash, and a receipt signature. Agent Relay adds an AR-RELAY-1 hash-linked parent receipt containing independently signed child receipts. The parent commits to both child receipts and both artifact links, but is not independently signed.

Exports and share actions are available only when the release verification gate is complete. The local verifier can independently show receipt signature, quote signature, service terms, payment, payment fields, commitment, artifact hash, and overall status.

LIMITATIONS

Evidence has a defined boundary.

  • Receipts prove payment, commitment, and artifact linkage.
  • They do not prove translation quality, transcription quality, legal compliance, ownership, safety, endorsement, or suitability.
  • The system is non-custodial and does not provide escrow or payment release after delivery.
  • The public RPC is rate-limited and may be temporarily unavailable.

DEEPER NOTES

Read the implementation evidence.

See the Verified Delivery notes and the transcription packaging decision in the source repository.