Skip to main content

Project Plutus

Project Plutus (PPCOIN) — 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 Plutus positions itself as a platform with AI agents for trading/analytics and onchain automation in the Solana ecosystem. Per Tier‑1 sources, the project describes “AI‑powered agents” (wallet/token/GitHub analysis, automation of DeFi actions) and the $PPCOIN token as a utility token for access/fee mechanics.

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: an “AI trading/automation hub” for Solana (agents and a dashboard for analysis and automation of actions).
  • Who it’s for: users/traders who need an assistant for wallet/token analysis and automation of DeFi tasks.
  • Why onchain/token: onchain — execution of actions on Solana; the $PPCOIN token is claimed as a utility for access/fee mechanics of the ecosystem.

How it works (very briefly)

  1. The user does: connects a Solana wallet/sets a request (wallet/token/repository analysis; automation setup).
  2. The system does: collects onchain data and forms conclusions/recommendations; automation scenarios are described (DCA, rebalancing, staking/LP, etc.).
  3. The user gets: a dashboard and a set of agent functions for analysis and automation.
  4. Where the blockchain is: trades/actions are executed on Solana; the token and assets are onchain.
  5. Token role (if any): $PPCOIN is claimed as the “fuel” of the ecosystem and access to features; part of the fees is claimed for buy&burn.

Quick links: AI thesis fit

Project passport

Field Value
Project name Project Plutus
Also known as (aliases) PPCOIN
Logo (logo) ../assets/418_project-plutus-ai_logo.svg
Token symbol (ticker) PPCOIN
Category AI/Agents | DeFi
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) —
Project status (status) active (based on the presence of the website/docs)
Token (standard) SPL
Token contract 76PsEyML7UV9uiBDWMdG3itRRuupDuRs6nNpjNBpump
Token model (token_type) utility (access)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) 20% fee for buy&burn (claimed); the token gives access to features
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agents for analysis/automation
Use‑case (use_case) trading + DeFi automation
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 1 / 1 / 3
Last verified 2026-02-11

General project overview

In its documentation, Project Plutus describes a set of AI agents and an interface (dashboard) for analyzing onchain data and automating actions on Solana. The focus is a “no code / prompt‑driven” approach to creating/launching agent scenarios (for example, DCA/rebalancing/DeFi operations), as well as analytical features (wallet/token/GitHub analysis).

Features/modules

  • AI agents for trading/analysis (wallet analysis, token analysis, GitHub analysis — per the release notes).
  • Onchain portfolio management (dashboard, management of assets on Solana — per the key features).
  • Intelligent automation: automation of DeFi tasks (staking/LP/claims — per the key features).
  • The $PPCOIN token as an access/fee economy mechanism (per PPNomics and the key features).

Typical scenarios

  • Scenario 1: the user enters a wallet address → receives an AI report/insights on holdings/activity/risks (per the release notes).
  • Scenario 2: the user sets a goal/command → the agent executes onchain actions on Solana (swap/DCA/rebalancing; per the description of the key features).

Getting started (wallet/network)

  • What you need: a Solana wallet and access to the product (the website mentions a “whitelist” for the alpha).
  • Network/chain: Solana.
  • Fees: Solana network fees for onchain operations; the project’s fee mechanics are described at the level of the token/platform (without parameters in Tier‑1 sources).

Architecture/tech (non‑AI)

  • Components: user interface/dashboard + offchain analysis services + onchain operations on Solana.
  • Participant roles: users (traders), liquidity providers/Solana protocols (as the execution environment for operations).
  • Where logic runs: analysis/recommendations — offchain; trades/automation — transactions on Solana.
  • Dependencies: Solana RPC/indexers (as the source of onchain data), DEX/DeFi protocols (as the venue for executing operations).

Token/economics (expanded, no forecasts)

  • Token utility: the token is claimed as “fuel” and as access to exclusive features/capabilities.
  • Protocol necessity drivers: the documentation states that $PPCOIN “drives” access to the ecosystem and is the currency of “wealth”.
  • Who pays fees: platform users (per the description).
  • Where fees go: it is claimed that 20% of fees are used for buy&burn of the token.
  • Issuance/burn: buy&burn of 20% of fees (the parameters and smart contracts of the mechanics are not disclosed in Tier‑1 sources).
  • Security/incentive mechanisms: — (not established per Tier‑1 sources).
  • Distribution and token issuance schedule: — (not established per Tier‑1 sources).
  • Treasury: — (not established).

Governance

  • Who makes decisions: — (not established per Tier‑1 sources).
  • How protocol parameters change: — (not established).
  • Where decisions are discussed/made: official channels (Docs/X/Telegram).
  • Keys/multisig: — (not established).

Security and incidents

  • Audits: — (not established per Tier‑1 sources).
  • Bug bounty: — (not established).
  • Incidents: — (not established).
  • Threat model: risks of automation/strategy errors, DeFi counterparty risks (DEX/LP), risks of input data quality and central components (if the analysis is performed offchain).

Project status and timeline

  • Current status: alpha/early access (the website indicates a whitelist for the alpha).
  • Key releases/milestones: “v.1 release” in the release notes.
  • Roadmap: see links_* (AI Map & Milestones).

Ecosystem/integrations

  • Integrations: Solana wallets; onchain actions via the DEX/DeFi ecosystem (per the description of the features).
  • Partners: — (not established per Tier‑1 sources).
  • Where it’s actually used: analysis of wallets/tokens and automation of actions (per the key features and release notes).

AI component of the project

  • What is real AI here? per the Tier‑1 description, AI agents analyze wallets/tokens/repositories and help automate strategies/actions.
  • What is truly onchain? portfolio management operations and DeFi actions are executed as transactions on Solana; the PPCOIN token is an SPL token.
  • Why is a token needed? the token is claimed as a utility for access/features and as part of the fee mechanics (buy&burn).
  • Red flags (based on the information found): no Tier‑1 implementation artifacts (repository/code not found); no public AI quality metrics; the details of the economic mechanics/contracts are not disclosed in Tier‑1 sources.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity low 1
Token necessity low 1
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 1.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI analyzes wallets/tokens/sentiment and forms recommendations/insights (per the description of the v.1 features).
  • Evidence: Tier‑1 — https://docs.projectplutus.ai/release-notes/v.1
  • Why sufficient / why not (one line): Tier‑1 describes what exactly the AI does (wallet/token/GitHub analysis).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a publicly reproducible demo/guide (without access restrictions) is not established in Tier‑1 sources.
  • Evidence: Tier‑1 — https://www.projectplutus.ai/
  • Why sufficient / why not (one line): the website indicates “not on whitelist” access, so the functionality cannot be checked hands‑on without access.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.projectplutus.ai/
  • Why sufficient / why not (one line): the docs/release notes contain no reproducible metrics of the quality/accuracy of the AI analytics.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): a tech description of the AI models/agent architecture is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.projectplutus.ai/
  • Why sufficient / why not (one line): Tier‑1 has a description of the features, but no architecture/model versions/methodologies.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: SPL mint: 76PsEyML7UV9uiBDWMdG3itRRuupDuRs6nNpjNBpump
  • Evidence: Tier‑1 — https://solscan.io/token/76PsEyML7UV9uiBDWMdG3itRRuupDuRs6nNpjNBpump
  • Why sufficient / why not (one line): onchain fact of the existence of the token/asset on the network.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: Tier‑1 does not establish specific addresses/contracts of protocol logic other than the token.
  • Evidence: Tier‑1 — https://docs.projectplutus.ai/
  • Why sufficient / why not (one line): there are descriptions of “on-chain portfolio management”, but no verifiable addresses/contracts were found in Tier‑1.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: without onchain, trades/DeFi operations as such are impossible, but the “criticality” of the blockchain as a separate layer of the product is not proven in Tier‑1 (rather an interface/automation on top of Solana).
  • Evidence: Tier‑1 — https://docs.projectplutus.ai/basics/key-features
  • Why sufficient / why not (one line): onchain is used as the execution environment, but the project’s specific onchain logic is not confirmed.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the $PPCOIN token exists on Solana.
  • Evidence: Tier‑1 — https://solscan.io/token/76PsEyML7UV9uiBDWMdG3itRRuupDuRs6nNpjNBpump
  • Why sufficient / why not (one line): the onchain explorer confirms the mint and the parameters of the token.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): the token is used for access to features/the ecosystem (utility/access).
  • Evidence: Tier‑1 — https://docs.projectplutus.ai/basics/ppnomics
  • Why sufficient / why not (one line): in PPNomics the token is described as “fuel” and a utility for access.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 0
  • Claim (one line): incentives/staking/slashing are not established in Tier‑1.
  • Evidence: Tier‑1 — https://docs.projectplutus.ai/
  • Why sufficient / why not (one line): the docs contain no confirmed staking/slashing terms per Tier‑1 sources.
  • 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 sources.
  • Evidence: Tier‑1 — https://docs.projectplutus.ai/
  • Why sufficient / why not (one line): the available Tier‑1 pages contain no governance mechanics.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the token is claimed as an access/economy mechanism; replaceability has not been assessed per Tier‑1.
  • Evidence: Tier‑1 — https://docs.projectplutus.ai/basics/ppnomics
  • Why sufficient / why not (one line): insufficient data from Tier‑1 to prove replaceability or irreplaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.projectplutus.ai/release-notes/v.1 description of the AI analytics features (wallet/token/GitHub analysis)
Tier‑1 https://docs.projectplutus.ai/basics/key-features description of the key modules (agents, onchain portfolio management, automation)
Tier‑1 https://docs.projectplutus.ai/basics/ppnomics token utility and buy&burn (claimed)
Tier‑1 https://solscan.io/token/76PsEyML7UV9uiBDWMdG3itRRuupDuRs6nNpjNBpump onchain fact: the SPL mint of the PPCOIN token
Tier‑1 — No Tier‑1 source for claim “public open-source GitHub of the product” was found.
Tier‑2 https://dexscreener.com/solana/dmmg42zlxezmj6n4feavdvBNsGfzzmTax6XuEBGfW7gA DEX pair/context (for reference)
Tier‑2 https://www.coingecko.com/en/coins/project-plutus aggregator (context/for reference)

No comments to display

Back to top