Skip to main content

Mindscraft

Mindscraft (MindsCraft.ai) — 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).

Mindscraft — an AI/Agents project on the Solana network, token (symbol: MINDS).

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 platform/service for creating and launching AI agents without code (drag‑and‑drop behavior configuration).
  • Who it’s for: users and teams who need AI agents and an interface for configuring/publishing them.
  • Why onchain/token: the $MINDS token is claimed as part of the ecosystem (including for staking/access); per Tier‑1 sources, the existence of onchain logic other than the token is not established.
  • What you can actually touch (Tier‑1): the web application app.mindscraft.ai.

How it works (very briefly)

  1. The user does: enters the interface and creates an AI agent (configures traits/behavior).
  2. The system does: saves the settings and provides an environment for launching/publishing the agent.
  3. The user gets: a working agent (and/or the ability to connect it to channels/tools).
  4. Where the blockchain is: onchain records the existence of the $MINDS SPL token; other onchain components are not established per Tier‑1 sources.
  5. Token role: “staking/access” scenarios are claimed on the Tier‑1 website/in the documentation, but the details of the mechanics are not established.

Quick links: AI thesis fit

Project passport

Field Value
Project name Mindscraft
Also known as (aliases) MindsCraft.ai, $MINDS, Schizo Terminal
Logo (logo) ../assets/614_schizo-terminal_logo.png
Token symbol (ticker) MINDS
Category AI/Agents
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 m1nd2qK91tpBrmX7yREJBc6D2fJ15kfiU9cdvxsSN6x
Token model (token_type) utility (access + staking)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Per Tier‑1 sources: the $MINDS token is claimed as the ecosystem token; the details of distribution/issuance are not established per Tier‑1 sources.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) no-code AI agent builder (traits/sliders)
Use‑case (use_case) no-code AI agent creation + launch
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

Mindscraft is positioned as a platform for creating and launching AI agents without the need to write code. The documentation describes a “no‑code” interface with control of the agent’s behavior via parameters/sliders, and the website contains links to the web application (builder) and related sections (for example, staking).

Features/modules

  • No‑code builder: configuration of the agent’s behavior via the interface.
  • Publishing/launch: launching/using the agent via the web product.
  • Multi‑agent coordination (claimed): “orchestrator/swarm” as a concept (implementation details are not established per Tier‑1 sources).

Typical scenarios

  • Scenario 1: a user creates an agent in the web application → configures traits → gets an agent for use/publishing.
  • Scenario 2: a user changes the agent’s parameters/behavior via the interface → updates the operating scenario.

Getting started (wallet/network)

  • What you need: web access to the application; for operations with the token — a Solana wallet.
  • Network/chain: Solana.
  • Fees: Solana network fees for onchain operations.

Architecture/tech (non‑AI)

  • Components: the web application (offchain) + the $MINDS SPL token (onchain).
  • Participant roles: users/agent creators.
  • Where logic runs: product functions — offchain; token operations — onchain (Solana).
  • Dependencies: Solana infrastructure (RPC/wallets) for onchain operations.

Token/economics (expanded, no forecasts)

  • Token utility: per the Tier‑1 website, the token is used as “powered by $MINDS” (a role in the ecosystem); a detailed utility/charging model is not established per Tier‑1 sources.
  • Staking/access (claimed): the Tier‑1 website has links to staking; the terms/parameters are not established per Tier‑1 sources.

Governance

  • Who makes decisions: — (no description of governance mechanics was found per Tier‑1 sources).

Security and incidents

Project status and timeline

  • Current status: the web product is available; the $MINDS token exists on the Solana network (see links_*).
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.

AI component of the project

  • What is real AI here? Per the Tier‑1 website/docs — creation and configuration of AI agents via a no‑code interface.
  • What is truly onchain? The $MINDS SPL token on the Solana network; other onchain components are not established per Tier‑1 sources.
  • Why is a token needed? Per Tier‑1 sources, the role of the token in the ecosystem and the presence of staking/access are claimed; the details of the model are not established.
  • Red flags (based on the information found): “onchain‑washing” (if the token is the only onchain part); absence of a public specification of the token utility/staking parameters in Tier‑1; absence of agent quality metrics.

DecAI Fit component summary

  • DecAI Fit: 4/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 3
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): Tier‑1 sources describe a product (no‑code AI agents), not just “plans/roadmap”.
  • Evidence: Tier‑1 — https://www.mindscraft.ai/ ; https://docs.mindscraft.ai/
  • Why sufficient / why not (one line): AI_0 is used as “intent without a product”; here there is a description of the product and the interface.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): An AI agent builder is claimed: behavior configuration/via the interface without code.
  • Evidence: Tier‑1 — https://www.mindscraft.ai/ ; https://docs.mindscraft.ai/
  • Why sufficient / why not (one line): The Tier‑1 website and docs describe the purpose and the interface for creating AI agents.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a web application (builder/interface) for creating AI agents.
  • Evidence: Tier‑1 — https://app.mindscraft.ai/ ; https://www.mindscraft.ai/
  • Why sufficient / why not (one line): The presence of a public web app is a verifiable demo artifact/usage example.
  • 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.mindscraft.ai/
  • Why sufficient / why not (one line): No reproducible set of agent/model quality metrics was 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 docs describe the interface/configuration of agents, but a full tech description of the architecture/model versions is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.mindscraft.ai/
  • Why sufficient / why not (one line): AI_4 requires a tech context (architecture/versions); the description found is insufficient.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: token mint m1nd2qK91tpBrmX7yREJBc6D2fJ15kfiU9cdvxsSN6x
  • Evidence: Tier‑1 — https://solscan.io/token/m1nd2qK91tpBrmX7yREJBc6D2fJ15kfiU9cdvxsSN6x ; https://docs.mindscraft.ai/getting-started/usdminds-token-information
  • Why sufficient / why not (one line): The Tier‑1 docs record the token CA, and the explorer provides onchain observability.
  • 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 sources, only the token was found).
  • Evidence: Tier‑1 — https://www.mindscraft.ai/ ; https://docs.mindscraft.ai/
  • Why sufficient / why not (one line): In Tier‑1 sources, no description of onchain protocol logic other than the token was found.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established that the product breaks down without the blockchain; per Tier‑1, onchain manifests through the token.
  • Evidence: Tier‑1 — https://www.mindscraft.ai/
  • Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality for the operation of the product.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, $MINDS (SPL, Solana).
  • Evidence: Tier‑1 — https://docs.mindscraft.ai/getting-started/usdminds-token-information
  • Why sufficient / why not (one line): The Tier‑1 docs record the ticker and the address of the token.
  • 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 sources.
  • Evidence: Tier‑1 — https://docs.mindscraft.ai/
  • Why sufficient / why not (one line): 1 requires an explicit “pay‑for‑service” mechanism in Tier‑1; not found.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): The Tier‑1 website has a staking scenario/section related to the token.
  • Evidence: Tier‑1 — https://www.mindscraft.ai/ ; https://app.mindscraft.ai/staking
  • Why sufficient / why not (one line): The presence of “Stake” and a staking section in the official product is sufficient to record the incentive mechanics as claimed.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of the token in governance mechanics is not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.mindscraft.ai/
  • Why sufficient / why not (one line): 1 requires a governance specification; not found per Tier‑1 sources.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): No Tier‑1 argument about the (ir)replaceability of the token was found.
  • Evidence: Tier‑1 — https://docs.mindscraft.ai/
  • Why sufficient / why not (one line): Design argumentation is required; not established.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.mindscraft.ai/ Product positioning: a no‑code platform for creating/launching AI agents; links to the web app and staking.
Tier‑1 https://docs.mindscraft.ai/ Documentation: description of the product/interface and configuration sections.
Tier‑1 https://docs.mindscraft.ai/getting-started/usdminds-token-information The $MINDS ticker and the token CA (Solana).
Tier‑1 https://app.mindscraft.ai/ Demo surface: the web application (builder).
Tier‑1 https://solscan.io/token/m1nd2qK91tpBrmX7yREJBc6D2fJ15kfiU9cdvxsSN6x Onchain object: the $MINDS SPL token on the Solana network.
Tier‑2 https://www.cyberscope.io/audits/coin-schizo-terminal External audit report (context; verification of correspondence to the object is required).

No comments to display

Back to top