Public BetaTri-Proof Protocol is currently in public beta. Features and risk models may evolve as validation continues.
Tri-Proof ProtocolSign in to scan
Public validation · not a customer endorsement

How a public wallet dataset becomes an explainable campaign decision.

Tri-Proof has not presented this dataset as an external customer success story. It is a transparent validation example that shows how Sybil Analyst organizes approved, gray-zone, and rejected/not-eligible results while the first real pilot case study is being earned.

Open the sample report Run a free mini audit
20
Wallets analyzed
A small public dataset designed to make the report structure easy to inspect.
6
Approved
Wallets suitable for inclusion based on the evidence available in the demo.
5
Gray-zone review
Wallets intentionally routed to human review instead of an automatic decision.
9
Rejected / not eligible
Wallets excluded from automatic reward inclusion for risk, inactivity, or entity reasons.
What this case study proves
It proves that the public report path and decision taxonomy can be inspected. It does not prove production throughput, customer ROI, or a protected reward amount.
The sample dataset is publicly downloadable.
Decision categories and representative reasons are visible.
Gray-zone handling demonstrates human-review boundaries.
No customer logo, quote, or protected-value claim is fabricated.
1

Submit the wallet list

The public CSV is processed through the same decision structure shown in the sample report.

2

Evaluate available evidence

Wallet history, entity context, behavior, policy, and relationship signals are considered where present.

3

Separate certainty from ambiguity

Clear outcomes are separated from gray-zone wallets that require project-side review.

4

Export an auditable result

The output shows decision counts, representative reasons, and downloadable sample artifacts.

Decision categories
Approved, gray-zone, and rejected/not-eligible outcomes make uncertainty visible instead of hiding it in one score.
Inspectable artifacts
The sample report links downloadable CSV and JSON artifacts for direct inspection.
Next validation step
A real pilot should measure list size, review rate, cluster findings, operational time saved, and customer-approved outcomes.

Run a real pilot with your campaign.

Tri-Proof will only publish a customer case study with verified metrics and permission. A selected pilot can establish the evidence required for that next step.

Request a pilot review