DecentraMind
DecentraMind — 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).
DecentraMind — an AI/Agents project on Ethereum, token (symbol: DMIND).
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 “Telegram aggregator bot” for several AI platforms (OpenAI, Gemini, Bedrock and others) via API keys (Tier‑1 website).
- Who it’s for: Telegram users who need a unified interface to several AI services (claimed).
- Why onchain/token: the ERC‑20 token DMIND on Ethereum is confirmed onchain; the website describes the token as a means of access to premium features of the bot (claim).
How it works (very briefly)
- The user does: interacts with the Telegram bot (as claimed on the website).
- The system does: routes requests to different AI providers/models via API keys (claim).
- The user gets: responses/analytics from the selected AI model (claim).
- Where the blockchain is: onchain — the DMIND token on Ethereum.
- Token role: the website claims that the token is used for access to premium features.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | DecentraMind |
| Also known as (aliases) | DMIND, DecentraMind AI |
| Logo (logo) | — |
| Token symbol (ticker) | DMIND |
| Category | AI/Agents | Infra |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0x3Eb9c7ee5F72E51F61e832137719Fe8d1E53A2ce |
| Token model (token_type) | utility (access) |
| Max supply | 10 000 000 DMIND |
| Issuance | — |
| Tokenomics (tokenomics, brief) | The website claims that the token is used for access to premium features of the bot. |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI platform aggregator in Telegram |
| Use‑case (use_case) | unified interface to multiple AI models |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 1 / onchain_score 1 / token_score 1 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://decentramind.bot/ |
| Docs | https://decentramind.bot/whitepaper |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://decentramind.bot/whitepaper |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0x3Eb9c7ee5F72E51F61e832137719Fe8d1E53A2ce |
| X | https://twitter.com/decentramindeth |
| Discord | — |
| Telegram | https://t.me/decentramindeth |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/decentramind |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/decentramind/ |
General project overview
DecentraMind describes the product as a Telegram bot that integrates several AI platforms via API keys and provides the user with a unified interface. Per the Tier‑1 source, the project also describes the DMIND token as a means of access to advanced features. A direct Tier‑1 link to a specific bot account for a demo was not identified in links_*, so the AI_2 flag remains 0.
Features/modules
- Aggregator AI (claimed): integration of several AI providers into one Telegram bot.
- Token access (claimed): DMIND is used for premium features.
Typical scenarios
- Scenario 1: a user sends a request to the Telegram bot → receives a response from the selected AI provider (claim).
- Scenario 2: a user interacts with the DMIND token → operations are visible onchain.
Getting started (wallet/network)
- What you need: Telegram; an Ethereum wallet — if performing onchain operations with the token.
- Network/chain: Ethereum mainnet.
- Fees: Ethereum network fees for transactions.
Architecture/tech (non‑AI)
- Components: offchain Telegram bot/AI integrations; onchain DMIND token.
- Participant roles: users, service operators, AI platform providers, Ethereum infrastructure.
- Where logic runs: offchain — request routing and processing; onchain — the token.
- Dependencies: external AI providers (API keys) and Ethereum infrastructure.
Token/economics (expanded, no forecasts)
- Token utility: access to premium features of the bot (claim).
- Supply parameters: max total supply 10 000 000 DMIND (onchain).
- Who pays fees: users (gas in ETH) for transactions.
- Where fees go: to Ethereum network validators/stakers (within the network mechanics).
- Issuance/burn: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Where decisions are discussed/made: —.
- Keys/multisig: —.
Security and incidents
- Audits: not found per Tier‑1.
- Bug bounty: not found per Tier‑1.
- Incidents: —.
- Threat model: risks of offchain integrations (API keys) and the token.
Project status and timeline
- Current status: token on Ethereum mainnet; product descriptions are available on the website.
- Key releases/milestones: —.
- Roadmap: described on the website (high‑level items).
Ecosystem/integrations
- Integrations: AI platforms via API keys (claimed).
- Partners: —.
- Where it’s actually used: not established per Tier‑1 (other than claims).
AI component of the project
- What is real AI here? The Tier‑1 website describes aggregation of several AI providers/models in a Telegram bot (claim).
- What is truly onchain? The ERC‑20 token DMIND on Ethereum.
- Why is a token needed? The website specifies use of the token for premium features; the mechanics and the necessity of the token require clarification.
- Red flags (based on the information found): absence of a direct link to the bot account/demo in links_*; many marketing formulations on the website without technical details.
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): AI is described as part of the current product (aggregator), not just intent.
- Evidence: Tier‑1 — https://decentramind.bot/
- Why sufficient / why not (one line): There is a Tier‑1 description of features.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): Aggregates several AI platforms (OpenAI/Gemini/Bedrock and others) and provides access from Telegram.
- Evidence: Tier‑1 — https://decentramind.bot/
- Why sufficient / why not (one line): The Tier‑1 source describes the purpose and the integration principle (via API keys).
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): A direct Tier‑1 link to the bot/demo (app/bot URL) is not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is a Telegram channel/community in links_*, but not a bot account for a demo.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Quality metrics were not found.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): The architecture/model versions and a tech description of integrations are not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Insufficient technical details.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: ERC‑20 token contract for DMIND: 0x3Eb9c7ee5F72E51F61e832137719Fe8d1E53A2ce
- Evidence: Tier‑1 — https://etherscan.io/token/0x3Eb9c7ee5F72E51F61e832137719Fe8d1E53A2ce
- Why sufficient / why not (one line): The token contract and supply parameters are verifiable onchain.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: not established per Tier‑1 (other than the token).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 confirmation of the key onchain logic of the product.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established.
- Evidence: Tier‑1 — —
- 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 an ERC‑20 token, DMIND, on the Ethereum network.
- Evidence: Tier‑1 — https://etherscan.io/token/0x3Eb9c7ee5F72E51F61e832137719Fe8d1E53A2ce
- Why sufficient / why not (one line): The existence of the token is verifiable onchain.
- 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 website describes the DMIND token as a means of access to premium features within the bot.
- Evidence: Tier‑1 — https://decentramind.bot/
- Why sufficient / why not (one line): A Tier‑1 statement about the utility function of the token.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Staking/incentives via the token are not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no description of specific mechanics.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): Governance use of the token DMIND is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no description of a governance process.
- 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.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Insufficient data on the necessity of the token.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://decentramind.bot/ | Tier‑1 description of the AI aggregator and a claim about the utility of the DMIND token. |
| Tier‑1 | https://etherscan.io/token/0x3Eb9c7ee5F72E51F61e832137719Fe8d1E53A2ce | Onchain facts: DMIND token, Ethereum network, contract, max supply. |
| Tier‑2 | https://coinmarketcap.com/currencies/decentramind/ | Aggregator profile (for reference). |
No comments to display
No comments to display