Tribe
Tribe — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).
Tribe — an AI/Other | NFT project on the BNB Smart Chain network, token (symbol: TRIBEX).
Disclaimer
Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.
TL;DR (for readers who are not into AI)
- What it is: a project that describes a reward system around airdrops and AI‑generated NFT collectibles.
- Who it’s for: token holders and participants in airdrop activities/staking, as well as project partners.
- Why onchain/token: the TRIBEX token (BEP‑20) is used as a “ticket” for the lottery/participation and can be staked to receive rewards (per the Tier‑1 website).
- What you can actually touch (Tier‑1): the Tribe website with a description of the mechanics and examples of AI collectibles — https://tribetoken.app/
How it works (very briefly)
- The user does: uses the TRIBEX token and/or participates in staking (per the description on the website).
- The system does: conducts airdrops/lotteries and distributes rewards/collectible NFTs.
- The user gets: NFTs/rewards (per the project rules).
- Where the blockchain is: the token and operations — onchain on BNB Smart Chain; NFTs may be on other networks (mentioned on the website).
- Token role (if any): TRIBEX is needed for participation (ticket) and staking/rewards (per the Tier‑1 description).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Tribe |
| Also known as (aliases) | TRIBEX, Tribex |
| Logo (logo) | ../assets/738_tribex_logo.png |
| Token symbol (ticker) | TRIBEX |
| Category | AI/Other | NFT |
| Primary chain (chain) | BNB Smart Chain |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoSA (BNB Smart Chain; 21 validators) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | BEP-20 |
| Token contract | 0x26E463F985A25fE6a20CA122410bE10Bb5782E0E |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI collectible NFT generation |
| Use‑case (use_case) | airdrops + lottery + NFT collectibles |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 2 / onchain_score 1 / token_score 1 / evidence_score 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://tribetoken.app/ |
| Docs | http://docs.tribetoken.app/ |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://tribetoken.app/whitepaper |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://bscscan.com/token/0x26E463F985A25fE6a20CA122410bE10Bb5782E0E |
| App / Demo | https://tribetoken.app/ |
| X | https://twitter.com/tribebsc |
| Discord | — |
| Telegram | https://t.me/TribeEN |
| Medium | https://medium.com/@TribeBsc |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | — |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/tribex/ |
General project overview
On the Tier‑1 website, Tribe describes a system around airdrops and AI‑generated NFT collectibles, where “1 TRIBEX = 1 lottery ticket” and staking is available to receive rewards. Within this card, we record verifiable elements: the Tier‑1 website/whitepaper page and the existence of the TRIBEX token on BNB Smart Chain.
Features/modules
- AI‑generated collectibles (NFT), described as “generated by artificial intelligence”.
- TRIBEX staking and airdrops/lottery for holders (per the description on the website).
Typical scenarios
- Scenario 1: a user holds TRIBEX → participates in the lottery/airdrops → receives an NFT/reward upon winning.
- Scenario 2: a user stakes TRIBEX → receives rewards (per the project rules).
Getting started (wallet/network)
- What you need: a wallet for BNB Smart Chain and access to the project website/interfaces.
- Network/chain: BNB Smart Chain.
- Fees: BNB Smart Chain network fees for transactions.
Architecture/tech (non‑AI)
- Components: the TRIBEX token (BEP‑20) and offchain components (website/draw rules), details are not confirmed by Tier‑1 sources.
- Participant roles: token holders/staking participants, project partners.
- Where logic runs: the token — onchain; distribution/rules and AI generation — not established (likely offchain).
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: per the Tier‑1 website, the token is used as a “ticket” and can be staked to receive rewards.
- Who pays fees: the user (BSC network fee).
- Issuance/burn: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: smart contract risks and risks of offchain draw/NFT generation processes (details not established).
Project status and timeline
- Current status: mainnet (the token on BNB Smart Chain).
- Key releases/milestones: —.
- Roadmap: —.
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? the Tier‑1 website mentions AI as the generation of collectible NFTs (AI‑generated collectibles).
- What is truly onchain? the TRIBEX token (BEP‑20) on BNB Smart Chain; token transactions are verifiable in the explorer.
- Why is a token needed? per the Tier‑1 website, the token is needed for participation (ticket) and for staking/rewards.
- Red flags (based on the information found): absence of metrics/a description of the AI generation process; dependence on offchain processes and draw rules.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 2 |
| Onchain necessity | low | 1 |
| Token necessity | low | 1 |
| Evidence | Tier‑1 present | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): AI is described as an operational function (generation of collectible NFTs), not just a “plan/intent”.
- Evidence: Tier‑1 — https://tribetoken.app/
- Why sufficient / why not (one line): The item about “intentions” does not add a signal when an AI feature is already claimed.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): Per the Tier‑1 website, AI is used to generate collectible NFT images.
- Evidence: Tier‑1 — https://tribetoken.app/
- Why sufficient / why not (one line): There is a description of the result (AI‑generated collectibles), but no metrics/architecture.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): The Tier‑1 website provides examples/a description of AI‑generated collectibles and participation mechanics.
- Evidence: Tier‑1 — https://tribetoken.app/
- Why sufficient / why not (one line): A public page with examples/a description of the product is sufficient as a demo surface.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://tribetoken.app/
- Why sufficient / why not (one line): No quantitative generation quality metrics were found per Tier‑1 sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): The tech description/architecture of AI generation were not found per Tier‑1.
- Evidence: Tier‑1 — https://docs.tribetoken.app/
- Why sufficient / why not (one line): 1 requires architectural details/versions; these were not found per Tier‑1 sources.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: BNB Smart Chain
- Addresses/identifiers: token contract 0x26E463F985A25fE6a20CA122410bE10Bb5782E0E
- Evidence: Tier‑1 — https://bscscan.com/token/0x26E463F985A25fE6a20CA122410bE10Bb5782E0E
- Why sufficient / why not (one line): The existence of the token and an observable contract in the explorer confirms an onchain artifact.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: No Tier‑1 confirmation of onchain logic of the product, other than the token, was found.
- Evidence: Tier‑1 — https://tribetoken.app/
- Why sufficient / why not (one line): 1 requires addresses/a description of protocol/logic contracts, not just the token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: per Tier‑1 sources, it is not established that a key property of the product breaks down without onchain.
- Evidence: Tier‑1 — https://tribetoken.app/
- Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, TRIBEX (BEP‑20).
- Evidence: Tier‑1 — https://tribetoken.app/ ; https://bscscan.com/token/0x26E463F985A25fE6a20CA122410bE10Bb5782E0E
- Why sufficient / why not (one line): The token is listed on the official website and observable in the explorer.
- Conflict note (if any): —
TK_1..TK_4 (1/0)
TK_1 — payment for the service (1/0)
- TK_1 (decision): 0
- Claim (one line): The use of the token as a mandatory payment for the service is not established per Tier‑1.
- Evidence: Tier‑1 — https://tribetoken.app/
- Why sufficient / why not (one line): 1 requires an explicit “pay‑for‑service” mechanism.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): Per the Tier‑1 website, the token is staked to receive rewards (airdrops in other tokens).
- Evidence: Tier‑1 — https://tribetoken.app/
- Why sufficient / why not (one line): Staking and reward distribution are ecosystem incentives around the token.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): No Tier‑1 confirmation of the governance role of the token was found.
- Evidence: Tier‑1 — https://tribetoken.app/
- Why sufficient / why not (one line): 1 requires an explicit governance process/documentation.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the token without loss of meaning is not established per Tier‑1.
- Evidence: Tier‑1 — https://tribetoken.app/
- Why sufficient / why not (one line): There is insufficient data on “replacing the token” with alternatives.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://tribetoken.app/ | The claimed “AI‑generated collectibles” model + the role of TRIBEX as a ticket and staking/airdrops. |
| Tier‑1 | https://docs.tribetoken.app/ | Whitepaper/documentation (context and project claims). |
| Tier‑1 | https://bscscan.com/token/0x26E463F985A25fE6a20CA122410bE10Bb5782E0E | The existence of the TRIBEX token on BNB Smart Chain (contract/network). |
| Tier‑3 | https://coinmarketcap.com/currencies/tribex/ | Token profile on an aggregator (context; not proof). |
No comments to display
No comments to display