Security & trust
Security & trust
What you control, what Tribes checks, and what no label guarantees.
Security and trust on Tribes are built around a few simple principles:
- users keep control of their own wallets and positions
- public activity should be attributable and verifiable
- verification should explain what has been checked, not imply guarantees
- trading risk should be clear
- invalid or manipulated activity should not remain part of trusted records
This section explains how those principles apply across the product.
Explore security and trust
- User control: how wallet and position control works.
- Trading risk: the risks involved in trading and why nothing on Tribes is financial advice.
- Token verification: what a Verified Token means and what it does not mean.
- Integrity: how invalid, fraudulent or manipulated activity is handled.
- Security: how Tribes approaches product and infrastructure security.
- Audits: published security reviews and audit information.
Trust through evidence
Tribes is designed around real activity rather than screenshots or self-reported claims.
Verified history, Calls, assigned trades and other attributable activity can create a record that people can evaluate over time.
Verified means checked. It does not mean guaranteed.
Was this page helpful?