ONTOS VERIFY
Evidence for work completed by machines.
Ontos Verify is a published TypeScript SDK for defining physical-job evidence requirements, preparing signed evidence, requesting verification, and connecting a decision to settlement workflows.
Why physical tasks need evidence
A transaction record can show that a job was created or funded, but it cannot by itself prove that a physical action happened. Verification starts by defining the evidence required for the specific task before work begins.
Requirements can cover standard fields such as GPS, camera hashes, QR or NFC values, motion counts, timestamps, and device signatures. A new proof type requires a versioned schema and matching verifier support; arbitrary fields are not automatically trusted.
Capture, submit, and evaluate
The SDK prepares a canonical evidence envelope, validates it, signs it with the submitting wallet, stores the immutable payload through a configured evidence service, and commits its hashes. The hosted workflow can then invoke SEDA Fast and return an approved or rejected result.
Developer interfaces cover job creation and acceptance, evidence preparation and submission, verification polling, payment release, disputes, cancellation, and timeout refunds. Transaction methods require a Viem wallet client; read methods require only a public client.
Identity, permissions, and secure integration
The recommended identity adapter resolves and authorizes peaqOS Machine ownership. Browser integrations should use an application-owned proxy so evidence upload credentials and project secrets remain server-side.
Device attestation can be supplied through Apple App Attest, Google Play Integrity, TPM, or secure-element integrations. A development provider exists for local and testnet use, but hardened production services reject it.
Current supported boundary
The current npm release is version 0.2.0. It ships ESM JavaScript and TypeScript declarations for Node.js 20 or a modern browser bundler.
The published package documents the standard physical-evidence schema and Peaq/SEDA workflow. Production deployments still depend on configured chain, evidence, verification, attestation, and application infrastructure; future integrations should not be treated as implemented until documented and released.
Common questions
What is robot task verification?
Robot task verification evaluates signed, job-specific physical evidence against requirements that were defined for the task.
How can a robot prove it completed a task?
An integration captures the required evidence, binds it to the job and machine, signs a canonical payload, submits immutable evidence and hashes, and retrieves the verifier’s decision.
How can verification support settlement?
A verified result can drive payment release or a rejection path; disputes, cancellation, and timeout recovery remain explicit application actions.