Tri-Proof ProtocolWeb3 Security PlatformOpen navigation
Learn the workflow, then use the right Tri-Proof surface with confidence.
Academy is the guided product layer. It explains what to do in ScamGuard, the extension, Telegram, Group Guardian, Sybil Analyst and the API without mixing those walkthroughs into technical reference docs.
Choose by the decision you need to make.
ScamGuard protects a user before interaction. Group Guardian protects a community conversation. Sybil Analyst protects a campaign allocation. APIs embed the same decision infrastructure into another product.
Use ScamGuard before you interact.
The scanner is for a concrete target you are about to open, trust, approve or sign.
- 01
Choose the target
Select URL, Wallet, Token or Transaction based on what you are about to open, trust or sign.
- 02
Choose chain context
Use Solana or EVM when the target is chain-specific. URL scans can begin without chain selection.
- 03
Read decision before score
Start with risk level, confidence, primary reason and evidence. The score is a summary, not the explanation.
- 04
Act on the next step
Stop on critical evidence. For caution, verify the official source and compare the wallet popup with the action you intended.
Put ScamGuard next to the wallet prompt.
The Chrome extension brings supported page and signing context into the browsing flow without asking for seed phrases or private keys.
- 01
Install from Chrome Web Store
Use the official ScamGuard Web3 Shield listing rather than downloading an unpacked archive.
- 02
Pin the extension
Keep ScamGuard visible beside the address bar so the current page can be checked quickly.
- 03
Review supported wallet requests
When a supported request appears, compare decoded intent, source context and the final wallet popup.
- 04
Keep the wallet as source of truth
ScamGuard adds evidence and warnings; it never replaces the wallet confirmation screen or asks for secret wallet material.
Use ScamGuard in a private Telegram chat.
The bot is useful when a suspicious target is already circulating in a chat and you want a readable decision without leaving Telegram.
- 01
Open the official bot
Start a private chat with the official ScamGuard Bot and use /start to see available commands.
- 02
Submit a target
Use /scan or paste a supported URL directly. Wallets, tokens and transaction requests can also be reviewed.
- 03
Read the explained report
The bot separates decision, evidence and recommended action instead of returning only a risk score.
- 04
Use history when comparing threats
Review recent scans when the same campaign, sender or target appears again.
Protect a Telegram group with controlled automation.
Group Guardian adds monitoring and repeated-threat context while keeping thresholds and moderator actions under authorized administrator control.
- 01
Choose Community or eligible API access
Group Guardian is a managed community-protection workflow rather than a generic public bot setting.
- 02
Connect the Telegram group
Authorize the group from the Developer workspace, then complete the connection from an eligible group administrator.
- 03
Choose an alert threshold
Start with high-risk for most public communities; tighten the policy only after moderators understand the alert volume.
- 04
Review repeated activity
Guardian adds sender and repeated-target context so moderators can distinguish one-off links from recurring campaigns.
- 05
Enable moderation deliberately
Time-limited mute actions require the correct Telegram permissions and remain admin-controlled.
Turn a participant CSV into reviewable decisions.
Sybil Analyst enriches wallet evidence, groups suspicious relationships, separates uncertainty, and lets operators test policy before enforcement.
- 01
Prepare the participant CSV
Use one wallet per row. Referral, funder and event timestamps are optional but can strengthen relationship evidence.
- 02
Configure the analysis
Choose chain, on-chain or hybrid evidence mode, and Conservative, Balanced or Strict risk policy.
- 03
Review evidence and clusters
Inspect clear participants, gray-zone cases, funding relationships, timing, known entities and cluster reasoning.
- 04
Simulate policy before enforcement
Use Policy Simulator to preview Allow, Review and Exclude outcomes before changing campaign eligibility decisions.
- 05
Export after human review
Resolve gray-zone cases, then use the Decision Package or exports for the campaign workflow. Tri-Proof remains decision support.
Embed explained security decisions into your product.
Use the documented API contract that matches the workflow, keep keys server-side, and preserve evidence semantics in your own UI.
- 01
Choose the right contract
Use API v1 for ScamGuard and general analysis integration. Use Campaign API v2 for campaign-native policy, decisions, clusters and run history.
- 02
Create a private API key
Generate keys in Dashboard → Developer and store them only in server-side environment variables.
- 03
Use purpose-built endpoints
Call ScamGuard before signing and campaign analysis before eligibility or reward distribution.
- 04
Preserve explanation
Show decision, confidence, strongest evidence and next action rather than reducing the response to a single score.
- 05
Add signed webhooks when needed
Use webhook events for backend automation while keeping wallet decisions and policy boundaries explicit.
Use the billing model that matches the product.
ScamGuard plans are time-based access. Sybil analysis uses persistent wallet credits. Community and API plans unlock their respective operational surfaces.