Project 89
Project 89 — 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).
Project 89 — a project with an “Agents Guide” and documents about the “AI Leader Protocol” (per the GitBook); network: Solana, token (symbol: —).
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 set of materials/documents (GitBook) about the “Project 89 Agents Guide” and related protocols/artifacts.
- Who it’s for: participants/the community of the project (not established more precisely per Tier‑1).
- Why onchain/token: there is a token on the Solana network; the necessity of the token in the product is not established.
How it works (very briefly)
- The user does: reads the materials/guides and follows the instructions (product details are not established).
- The system does: — (not established per Tier‑1).
- The user gets: — (not established per Tier‑1).
- Where the blockchain is: Solana (the token mint is in
links_*). - Token role (if any): not established (no Tier‑1 description of the token utility was found).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Project 89 |
| Also known as (aliases) | Project89 |
| Logo (logo) | ../assets/461_project89_logo.jpg |
| Token symbol (ticker) | — |
| Category | AI/Agents | Meme |
| Primary chain (chain) | Solana |
| Type | non-EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Solana) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | SPL |
| Token contract | CJjraBaedPnKzjnag12i7PVo5pSP6cB9heV8zr89bonk |
| 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) | agent protocols |
| Use‑case (use_case) | materials/guides for agents |
| DecAI Fit — AI thesis fit | 1/6 — low alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 1 / 1 / 0 / 0 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.project89.org/ |
| Docs | https://project89.gitbook.io/project89 |
| GitHub | https://github.com/project-89 |
| Releases / Changelog | https://github.com/project-89/whitepaper/commits/main/ |
| Whitepaper | https://github.com/project-89/whitepaper/blob/main/versions/v0.01/whitepaper.pdf |
| Roadmap | https://www.project89.org/ |
| Security advisories | https://github.com/project-89/whitepaper/security |
| Explorer | https://solscan.io/token/CJjraBaedPnKzjnag12i7PVo5pSP6cB9heV8zr89bonk |
| App / Demo | https://beta.project89.org/ |
| X | https://twitter.com/project_89 |
| Discord | https://discord.gg/project89 |
| Telegram | — |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/project89-2 |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/project89/ |
General project overview
Project 89 publishes a GitBook with an “Agents Guide”, a Strategy section (including the “AI Leader Protocol”) and a set of “Artifacts”. From the available Tier‑1 it is not established whether the project has a working AI product/demo; this card records only the existence of the documentation and of a token on the Solana network.
Features/modules
- GitBook: the “Project 89 Agents Guide” and related sections/artifacts.
- Whitepaper PDF in the repository (the link is in
links_*). - Token mint on the Solana network (the link is in
links_*).
Typical scenarios
- Use cases: not established (no Tier‑1 found).
Getting started (wallet/network)
- What you need: — (not established).
- Network/chain: Solana.
- Fees: Solana network fees (details not established).
Architecture/tech (non‑AI)
- Components: a token on Solana + documentation (GitBook/whitepaper).
- Participant roles: —.
- Where logic runs: —.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not established (Tier‑1).
- Protocol necessity drivers: —.
- Who pays fees: —.
- Where fees go: —.
- Issuance/burn: —.
- Security/incentive mechanisms: —.
- Distribution and token issuance schedule: —.
- Treasury: —.
Governance
- Who makes decisions: not established (Tier‑1).
- How protocol parameters change: not established (Tier‑1).
- Where decisions are discussed/made: GitBook/GitHub/Discord (links — in
links_*). - Keys/multisig: not established (Tier‑1).
Security and incidents
- Audits: not established per Tier‑1.
- Bug bounty: not established per Tier‑1.
- Incidents: not established per Tier‑1.
- Threat model: the token is not accompanied by a Tier-1 description of its utility; Tier-1 artifacts about the product and security are also absent.
Project status and timeline
- Current status: active (public resources are available; mainnet/testnet statuses are not applicable within the data found).
- Key releases/milestones: see
Releases / Changeloginlinks_*. - Roadmap: see
Roadmapinlinks_*.
Ecosystem/integrations
- Integrations: not established (Tier‑1).
- Partners: not established (Tier‑1).
- Where it’s actually used: not established (Tier‑1).
AI component of the project
- What is real AI here? Tier‑1 has an “Agents Guide” and sections related to agents, but there is no proof of a working AI component (demo/architecture/metrics) per Tier‑1 sources.
- What is truly onchain? The token mint on the Solana network (see Explorer).
- Why is a token needed? Not established (Tier‑1).
- Red flags (based on the information found): the existence of a token without a described utility; the absence of Tier‑1 artifacts for AI_1..AI_4.
DecAI Fit component summary
- DecAI Fit: 1/6 — low alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | low | 1 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 partial | 0 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 1
- Claim (one line): The GitBook contains materials about “Agents” and the “AI Leader Protocol” (as an intent of direction).
- Evidence: Tier‑1 — https://project89.gitbook.io/project89
- Why sufficient / why not (one line): There are Tier‑1 mentions of the agent topic, but no proof of a working AI component.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): What exactly the AI does in the product — not established per Tier‑1.
- Evidence: Tier‑1 — https://project89.gitbook.io/project89
- Why sufficient / why not (one line): The documentation is descriptive in nature; there is no description of an AI feature as a working component.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No demo/example of the AI component’s operation was found per Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): A public “game” surface of the project has been added to
links_*, but it is not a Tier‑1 demo of the AI component/agent as such (there is no verifiable AI flow/example). - Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: not established per Tier‑1.
- Context (version/date/how measured): —.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There are no Tier‑1 metrics.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): The tech description/architecture of the AI component are not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There are no Tier‑1 tech docs/architecture for the AI part.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Solana
- Addresses/identifiers: token mint
CJjraBaedPnKzjnag12i7PVo5pSP6cB9heV8zr89bonk - Evidence: Tier‑2 — https://solscan.io/token/CJjraBaedPnKzjnag12i7PVo5pSP6cB9heV8zr89bonk
- Why sufficient / why not (one line): The token address is given in
links_*via the explorer. - Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: not established (other than the existence of the token).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 description of onchain logic.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: no justification of onchain criticality was found in Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There are no Tier‑1 statements.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): There is a token mint on the Solana network (see Explorer).
- Evidence: Tier‑2 — https://solscan.io/token/CJjraBaedPnKzjnag12i7PVo5pSP6cB9heV8zr89bonk
- Why sufficient / why not (one line): The existence of the token is confirmed by 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): Payment for the service with the token is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 description of TK_1.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Mechanics of incentives/collateral/penalties via the token are not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 description of TK_2.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): Governance via the token is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 description of TK_3.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the token is not established (no Tier‑1 description of the token utility).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without Tier‑1 on token mechanics, replaceability cannot be strictly asserted.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://project89.gitbook.io/project89 | The existence of the “Agents Guide” and related sections (Strategy/Artifacts). |
| Tier‑1 | https://github.com/project-89/whitepaper/blob/main/versions/v0.01/whitepaper.pdf | Whitepaper (a Tier‑1 artifact of the project). |
| Tier‑2 | https://solscan.io/token/CJjraBaedPnKzjnag12i7PVo5pSP6cB9heV8zr89bonk | Token on the Solana network (mint address). |
| Tier‑1 | — | No Tier‑1 source for claim “there is a working AI component/demo/metrics” was found. |
| Tier‑1 | — | No Tier‑1 source for claim “the token is needed for payment/incentives/governance” was found. |
No comments to display
No comments to display