01
TRIAGE, NOT VERDICT
Explain each signal.
The demo uses a small, visible set of text and URL heuristics. Every match is shown with a reason and a next step. It never labels a campaign “safe.”
Local rules · No browsing
AIRDROP RESEARCH / SAFETY TRIAGE
Check the claim.
Not your wallet.
A first-pass risk review for airdrop messages. Paste what you found; Proofline checks the text locally and shows its reasoning.
01 / INPUT
Review a claim
TRY A SAMPLE
02 / TRIAGE RESULT
Risk signals
Weighted rule points are not a probability.
OBSERVATIONS—
A low score does not mean a claim is safe.
NOT CHECKED BY THIS DEMO
Source authenticity · page contents · contract behavior · on-chain state · wallet request safety
03 / VERIFIABILITY
NOT CONNECTEDProof preview
What could be proven
without exposing the inputs?
“
This claim contains high-risk signals under the demo policy.
01
Policy runs locallyInput text stays in this browser tab.
✓02
Proof could attest a resultPrivate inputs need not be revealed.
○03
zkVerify could verify itIntegration is future work.
○No proof is created or submitted. This panel describes a possible architecture only.
LOCAL SESSION
Evidence log.
Reviews run during this tab session appear here. Nothing is uploaded or saved after you close the page.
SESSION HISTORY
Recent reviews
◎
Evidence is not proof.
This prototype logs which text rules fired. It does not independently confirm sources, fetch pages, inspect contracts, or generate a cryptographic proof.
DESIGN NOTES
Trust the process.
Agents can make useful recommendations, but a result should be inspectable and its limits should be obvious.
02
PRIVACY, BY DESIGN
Keep sensitive inputs private.
A future proving circuit could attest that a policy ran on an input without publishing that input. This prototype does not implement that circuit.
Concept only · No proof generated
03
VERIFY, DON'T ASSUME
Give verification a job.
In a production design, zkVerify could verify a compatible proof and return a checkable verification result. The app would still need trusted policy, data provenance, and careful threat modeling.
Future integration · Not connected
NEXT REAL BUILD STEPS
From demo to verifiable system
- 01 Define a narrow claim policy and test it against false positives.
- 02 Select a supported proof system and implement a circuit for a limited, privacy-safe predicate.
- 03 Verify generated proofs through the official zkVerify workflow; publish reproducible code and test vectors.
- 04 Document what the proof does not establish—especially source authenticity and scam safety.