THE PROTOCOL

What It Means for a Review to Be Verified

By VeriBureau Research··2 min read

The research

Research from the World Economic Forum ('The Global Risks Report 2024') estimates that misleading online content — including fabricated reviews — influences significant consumer spending globally. The FTC has taken enforcement actions against companies engaged in review fraud (FTC, 'Combating Fake Reviews', 2023). Trustpilot's own Transparency Report (2023) documents the removal of 5.8 million reviews that violated their guidelines. These numbers reflect the scale of the challenge, not the failure of any single platform.

Sources: FTC Consumer Protection reports, World Economic Forum Digital Trust research, Harvard Business School review platform studies.

The structural problem

These are not failures of intent. Each platform has invested significantly in trust systems. The challenge is structural: verification applied after publication is fundamentally different from verification required before publication. The first approach catches some fraud. The second prevents it architecturally.

The word 'verified' appears on billions of reviews across the internet. In most cases, it means very little. On Amazon, a 'Verified Purchase' badge confirms that the account made a purchase on the platform — but not necessarily of the product being reviewed (Amazon Help, 'About Customer Reviews'). On Trustpilot, a 'verified' label indicates the business invited the reviewer through their integration — a meaningful step, but not proof of a specific transaction (Trustpilot Support, 'Verification methods'). On Google, there is no verification mechanism at all — any account holder can review any business.

The VeriBureau approach

VeriBureau approaches verification differently. Every review in the protocol begins with a Proof Token — a cryptographic identifier generated from a real transaction between a specific business and a specific customer. Without a valid Proof Token, no review can enter the system. This is enforced by architecture, not moderation. Each review is then weighted by the reviewer's verified history across the entire protocol. First-time reviewers have minimal influence. Consistent, honest contributors earn more weight over time. The result is a Trust Score (0–100) computed from verifiable data, calibrated by industry.

// Verification flow
Transaction → POST /api/v1/tokens → Proof Token → Review → SHA-256 → Merkle Tree → Audit Chain
// Public verification: GET /api/v1/audit/verify

Limitations and honest disclosure

VeriBureau is a young protocol. Our current dataset is small. The Proof Token is generated by the business, which means a business could theoretically generate tokens for fictitious transactions. We mitigate this through cross-referencing patterns and reviewer independence, but we do not claim the system is invulnerable. We claim it is architecturally stronger than the status quo — and we invite scrutiny to prove it.

Frequently asked

Is VeriBureau free?

Yes. During the founding period, all features are free with no limits. Future pricing will be per-token, not subscription — announced with advance notice.

Is VeriBureau immune to fake reviews?

No system is immune. VeriBureau raises the cost of fake reviews significantly by requiring cryptographic proof of transaction, but a business could theoretically generate tokens for fictitious transactions. We mitigate this through pattern analysis and the public audit chain, and we are transparent about this limitation.

How long does integration take?

Dashboard registration takes 2 minutes. API integration depends on your stack — most developers complete it in under an hour. No-code options (email invitations, QR codes) work immediately.

The protocol is open

Examine the protocol. Verify the audit chain. Decide for yourself.

CONTINUE READING