MindSync
MindSync — 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).
MindSync — a project with an onchain token artifact on the Ethereum network, 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 project with an onchain token contract on Ethereum and Tier‑1 development artifacts (the
mindsync-aiorganization’s GitHub). As of the verification date, the website at themindsync.aidomain returns “website coming soon”. - Who it’s for: not established.
- Why onchain/token: a token contract on Ethereum is recorded; the necessity of onchain/the token for the product is not established per Tier‑1 sources.
How it works (very briefly)
- The user does: — (no unified Tier‑1 “quickstart” was found).
- The system does: —.
- The user gets: —.
- Where the blockchain is: the token contract on Ethereum.
- Token role (if any): the existence of the token is established per the contract; no Tier‑1 confirmation of the token utility in the product was found.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | MindSync |
| Also known as (aliases) | MindSync.ai |
| Logo (logo) | ../assets/730_mindsync_logo.svg |
| Token symbol (ticker) | MAI |
| Category | AI/Other |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | ERC-20 |
| Token contract | 0x75387e1287Dd85482aB66102DA9f6577E027f609 |
| Token model (token_type) | — |
| Max supply | 106,929,209 MAI (Etherscan) |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | — |
| Use‑case (use_case) | — |
| DecAI Fit — AI thesis fit | 2/6 — low alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 1 / onchain_score 1 / token_score 0 / evidence_score 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://mindsync.ai |
| Docs | — |
| GitHub | https://github.com/mindsync-ai |
| Releases / Changelog | https://github.com/mindsync-ai/crowdsale-contracts/commits |
| Whitepaper | https://mindsync.ai/docs/whitepaper.pdf |
| Roadmap | — |
| Security advisories | https://github.com/mindsync-ai/crowdsale-contracts/security |
| Explorer | https://etherscan.io/token/0x75387e1287Dd85482aB66102DA9f6577E027f609 |
| X | https://twitter.com/mind_sync |
| Discord | — |
| Telegram | https://t.me/mindsyncai |
| Medium | https://medium.com/mindsync-ai |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | — |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/mindsync/ |
General project overview
MindSync has a Tier‑1 public GitHub for the mindsync-ai organization (including repositories for ML tasks and smart contracts), as well as an onchain token artifact on the Ethereum network. However, as of the verification date, the official website at the mindsync.ai domain returns “website coming soon”, so product claims are verified only against the available Tier‑1 artifacts.
Features/modules
- Public GitHub: development artifacts (including “docker images for running machine learning tasks”).
- Token on Ethereum: an observable onchain artifact.
Typical scenarios
- Scenario 1: a user studies the public repositories → checks which components/contracts/ML infrastructure are available in Tier‑1.
- Scenario 2: a user checks the token contract → uses the explorer to view the address and basic parameters.
Getting started (wallet/network)
- What you need: a wallet for the Ethereum network (for operations with the token).
- Network/chain: Ethereum.
- Fees: Ethereum network fees apply to transactions with the token.
Architecture/tech (non‑AI)
- Components: —.
- Participant roles: —.
- Where logic runs: —.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: No Tier‑1 confirmation of the token utility in the product was found.
- Protocol necessity drivers: not established.
- Who pays fees: token users (transactions on Ethereum).
- Where fees go: to Ethereum validators (network fees).
- Issuance/burn: —.
- Security/incentive mechanisms: —.
- Distribution and token issuance schedule: —.
- Treasury: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Where decisions are discussed/made: —.
- Keys/multisig: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: —.
Project status and timeline
- Current status: —.
- Key releases/milestones: —.
- Roadmap: —.
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? There are Tier‑1 development artifacts related to ML tasks (for example, docker images for running machine learning tasks); however, no Tier‑1 confirmation of a specific AI component of the product/protocol was found.
- What is truly onchain? The token contract on the Ethereum network.
- Why is a token needed? The existence of the token is established per the contract; the necessity/utility of the token is not established per Tier‑1 sources.
- Red flags (based on the information found): risk of AI‑washing; risk of onchain‑washing (if “onchain” boils down to the token only); what to double‑check: whether the Tier‑1 documents contain explicit AI intent and protocol onchain logic beyond the token.
DecAI Fit component summary
- DecAI Fit: 2/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 partially present | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 1
- Claim (one line): The organization’s Tier‑1 repositories contain artifacts for running/servicing ML tasks (AI intent at the development/infrastructure level).
- Evidence: Tier‑1 — https://github.com/mindsync-ai ; https://github.com/mindsync-ai/docker-python
- Why sufficient / why not (one line): Tier‑1 development artifacts confirm a focus on ML tasks, even if the website’s product materials are unavailable.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): It is not established per Tier‑1 what exactly “the AI does” as a component of the product/protocol.
- Evidence: Tier‑1 — https://github.com/mindsync-ai
- Why sufficient / why not (one line): Without a specific description of the AI feature in Tier‑1, we set 0.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): Tier‑1 demos/examples of the product’s AI component are not established.
- Evidence: Tier‑1 — https://github.com/mindsync-ai
- Why sufficient / why not (one line): Without an explicit demo surface for AI, we set 0.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://github.com/mindsync-ai
- Why sufficient / why not (one line): No reproducible set of AI quality metrics/benchmarks was found in the available Tier‑1 sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): A Tier‑1 tech description specifically of the AI component/model versions is not established.
- Evidence: Tier‑1 — https://github.com/mindsync-ai
- Why sufficient / why not (one line): Without an explicit AI tech description/versions, we set 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: token contract 0x75387e1287Dd85482aB66102DA9f6577E027f609
- Evidence: Tier‑1 — https://etherscan.io/token/0x75387e1287Dd85482aB66102DA9f6577E027f609
- Why sufficient / why not (one line): The contract address and onchain history are observable 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 token).
- Evidence: Tier‑1 — https://github.com/mindsync-ai
- Why sufficient / why not (one line): No Tier‑1 confirmation of onchain logic beyond the token was found.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established.
- Evidence: Tier‑1 — https://github.com/mindsync-ai
- Why sufficient / why not (one line): OC_3=1 requires an explicit justification of onchain criticality; not found.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token (contract on Ethereum).
- Evidence: Tier‑1 — https://etherscan.io/token/0x75387e1287Dd85482aB66102DA9f6577E027f609
- Why sufficient / why not (one line): The existence of the token contract is a sufficient onchain fact for TK_0=0.
- 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): Utility as “payment for the service” is not established per Tier‑1.
- Evidence: Tier‑1 — https://github.com/mindsync-ai
- Why sufficient / why not (one line): Without a verifiable description of payments with the token, we set 0.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Incentives/collateral/penalties with the token are not established per Tier‑1.
- Evidence: Tier‑1 — https://github.com/mindsync-ai
- Why sufficient / why not (one line): Without Tier‑1 incentive mechanics, we set 0.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): Governance use of the token is not established per Tier‑1.
- Evidence: Tier‑1 — https://github.com/mindsync-ai
- Why sufficient / why not (one line): TK_3=1 requires explicit Tier‑1 governance mechanics; not found.
- 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 per Tier‑1.
- Evidence: Tier‑1 — https://github.com/mindsync-ai
- Why sufficient / why not (one line): There is no Tier‑1 justification of replaceability.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://mindsync.ai | Official project website (as of the verification date: “website coming soon”). |
| Tier‑1 | https://github.com/mindsync-ai | Public project GitHub (Tier‑1 development artifacts). |
| Tier‑1 | https://github.com/mindsync-ai/docker-python | Docker images for running machine learning tasks (a Tier‑1 AI intent artifact). |
| Tier‑1 | https://etherscan.io/token/0x75387e1287Dd85482aB66102DA9f6577E027f609 | Onchain fact: the token contract on the Ethereum network. |
| Tier‑1 | https://etherscan.io/token/0x75387e1287Dd85482aB66102DA9f6577E027f609 | No Tier‑1 source for claim “the token is necessary for the service/incentives/governance” was found (the token page contains links, but the utility is not confirmed). |
| Tier‑2 | https://coinmarketcap.com/currencies/mindsync/ | Reference token profile. |
No comments to display
No comments to display