Fraud, Audit & Oracles
A decentralized marketplace cannot rely on a central operator to police quality. VirtEngine distributes that job across several modules that together form the network’s trust fabric.
Fraud detection (x/fraud)
Section titled “Fraud detection (x/fraud)”The fraud module records and evaluates fraud signals from across the protocol. Inputs arrive from automated checks, including the usage-reporting fraud checker, which validates:
- timestamp validity (no future timestamps),
- duration bounds on usage records,
- resource-ratio limits, and
- signature verification.
Anomalies detected off-chain (see Usage Reporting) escalate into on-chain fraud reports when they cross severity thresholds. Critical findings — such as negative metric values or zero-duration records with usage — can block settlement entirely.
Auditor attestations (x/audit)
Section titled “Auditor attestations (x/audit)”Independent auditors publish signed attestations about providers on-chain. Tenants can then require audited providers in their orders, turning audits into a market signal with real economic weight. An audit is not a one-time badge: attestations are on-chain objects that can be revoked or superseded.
Benchmarks (x/benchmark)
Section titled “Benchmarks (x/benchmark)”The benchmark module records provider performance measurements on-chain, so “fast” is a verifiable claim instead of marketing copy. Benchmarks combine with audits and reviews to inform bid evaluation — see Choosing Providers.
Reviews (x/review)
Section titled “Reviews (x/review)”Tenants leave reviews of providers they have actually leased from, building a reputation history that is tamper-evident and tied to verified identities (VEID). Because reviewers are verified accounts with real lease history, review-bombing and fake-review farming are materially harder than on conventional platforms.
Oracles (x/oracle)
Section titled “Oracles (x/oracle)”The oracle module brings external data on-chain — for example, pricing feeds used by economic logic. Oracle reports are validator-verified before protocol code consumes them, keeping external inputs inside the same trust model as the rest of consensus.
Support (x/support)
Section titled “Support (x/support)”Disputes that automation cannot resolve need a human path. The support module implements on-chain ticketing and escalation workflows, so even exception handling leaves an auditable trail.
How the pieces reinforce each other
Section titled “How the pieces reinforce each other”| Signal | Produced by | Consumed by |
|---|---|---|
| Fraud reports | Automated checks, participants | Settlement blocking, enforcement |
| Audit attestations | Independent auditors | Tenant order requirements |
| Benchmarks | Measurement runs | Bid evaluation, provider ranking |
| Reviews | Verified tenants | Provider selection |
| Oracle data | External feeds via validators | Economic modules |
| VEID verification | Validators / verification services | Everything — identity underpins each signal |