Skip to main content

Morphware

Morphware (XMW) — 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).

Morphware — an AI/Compute | Infra project on Ethereum, token (symbol: XMW).

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/network for access to compute and AI inference (including LLM chat, embeddings, image generation) via a web dashboard and API.
  • Who it’s for: developers/teams that need an API for LLM/embeddings/image generation; network participants (GPU providers/task executors).
  • Why onchain/token: the XMW token exists on Ethereum; the tokenomics claim incentives/rewards for network participants and token voting (ERC20Votes).
  • What you can actually touch (Tier‑1): the product dashboard (API keys/credits/API access) — https://app.morphware.com

How it works (very briefly)

  1. The user does: registers in the product and obtains an API key (or uses the project’s client/wallet).
  2. The system does: provides access to AI endpoints (chat completions, embeddings, image generation) and/or to the execution of compute tasks on the network.
  3. The user gets: model outputs (text/vectors/images) and/or the results of task execution.
  4. Where the blockchain is: XMW is an ERC‑20 token on Ethereum; claimed token voting via ERC20Votes.
  5. Token role (if any): incentives/rewards for network participants and governance (as claimed in Tier‑1).

Quick links: AI thesis fit

Project passport

Field Value
Project name Morphware
Also known as (aliases) Morphware Token; XMW
Logo (logo) ../assets/111_morphware_logo.png
Token symbol (ticker) XMW
Category AI/Compute | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2024-09-18
Project status (status) active
Token (standard) ERC-20
Token contract 0x391cF4b21F557c935C7f670218Ef42C21bd8d686
Token model (token_type) utility (incentives + governance)
Max supply 1,232,922,769 XMW
Issuance fixed
Tokenomics (tokenomics, brief) per the tokenomics: total supply 1,232,922,769; the distribution lists shares for liquidity (50%) and treasury shelf (25%)
Governance token‑voting (ERC20Votes)
Admins/keys owner (Ownable; configuration of fees/limits/wallets; withdrawStuckETH/Token)
Audit —
Bug bounty —
Team (team) Kenso Trabing (founder); Darshan Raju (tech lead); Anthony Albertorio (community); Asim Jan (AI lead)
Funding (investors/funding) —
AI component (ai_component) API for LLMs, embeddings, image generation
Use‑case (use_case) AI inference/compute access via API
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 1 / evidence_score 0
Last verified 2026-02-11

General project overview

Morphware is positioned as a platform/network that connects consumers of compute (for example, for ML/AI tasks) with providers of computing resources. The documentation describes a peer‑to‑peer approach to executing compute tasks and a general thesis of “decentralization of computing resources”.

What the user actually has “in hand”, confirmed by Tier‑1, is the web product app.morphware.com and a set of API endpoints for AI functions: chat completion, embeddings and image generation (the documentation contains example curl requests).

Features/modules

  • Product (web app): API key creation, access/credit management, the entry point to the “Chat‑UI application” and the API.
  • AI API: chat completion (/api/chat/completions), embeddings (/ollama/api/embeddings), image generation (/images/api/v1/generations) + pricing/credits endpoints.
  • Desktop client (open source): a Morphware wallet + task creation and participation in bidding/work on tasks (per the repository README).

Typical scenarios

  • Scenario 1 (developer): a team obtains an API key → calls chat completions/embeddings/image generation over HTTP → integrates the responses into its application.
  • Scenario 2 (network participant): a user uses the desktop client → interacts with the wallet and participates in task creation/execution (job creation / bidding).

Getting started (wallet/network)

  • What you need: an account in app.morphware.com (for an API key/JWT) and basic skills in working with HTTP APIs.
  • Network/chain: Ethereum (the XMW token), if you interact with the token/voting.
  • Fees: Ethereum network fees for onchain operations; offchain — a “credits/pricing” model in the application (the credits/pricing endpoints are described in the API docs).

Architecture/tech (non‑AI)

  • Components: the web application app.morphware.com; the API layer; the onchain XMW token contract (ERC‑20); the desktop client (Electron + React UI + Express backend).
  • Participant roles: API users; integration developers; network participants/executors; token holders (governance).
  • Where logic runs: AI inference/compute — offchain; onchain — the token and the (claimed) voting.
  • Dependencies: Ethereum infrastructure; web access to the application; the client’s GitHub repository.

Token/economics (expanded, no forecasts)

  • Token utility: the tokenomics describe rewards/incentives for network participants and token‑based governance (ERC20Votes).
  • Protocol necessity drivers: Tier‑1 describes incentivization (community rewards/incentives) and governance via the token; no Tier‑1 confirmation that the API/compute is paid for specifically with the XMW token was found.
  • Who pays fees: onchain — Ethereum users in operations with XMW; offchain — API/product users (the credits/pricing model is described in the API docs).
  • Where fees go: — (no Tier‑1 found as a mandatory part of the protocol; the token contract has a distribution to fee wallets).
  • Issuance/burn: fixed total supply (a constant in the token contract code; mint in the constructor).
  • Security/incentive mechanisms: the tokenomics describe incentive mechanisms at the level of token distribution; details of staking/penalties are not established in Tier‑1.
  • Distribution and token issuance schedule: the tokenomics list shares and vesting (for example team & advisors: 9 months cliff + monthly vesting over 18 months).
  • Treasury: the tokenomics include a “treasury shelf” as a share of the distribution; the onchain mechanics of treasury management are not established in Tier‑1.

Governance

  • Who makes decisions: token holders via voting (ERC20Votes) — as described in the governance doc.
  • How protocol parameters change: — (a specific voting process/portal is not specified in the Tier‑1 links).
  • Keys/multisig: the XMW token contract is Ownable (there are owner powers; renounceOwnership is provided for).

Security and incidents

  • Audits: — (no public Tier‑1 reports found).
  • Bug bounty: — (no Tier‑1 program was found).
  • Incidents: — (no Tier‑1 postmortems found).
  • Threat model: the key risk is the centralized admin powers of the token contract (the owner can change fees/limits/wallets and withdraw “stuck” assets).

Project status and timeline

  • Current status: mainnet (the XMW token on Ethereum).
  • Key milestones: creation of the XMW token contract — 2024-09-18 (Etherscan); desktop client releases are published in GitHub Releases.
  • Roadmap: there is a separate roadmap page in the documentation.

Ecosystem/integrations

  • Integrations: HTTP API (LLM chat/embeddings/image generation) for external applications.
  • Where it’s actually used: API examples and endpoints (Tier‑1 docs); the open‑source client (Tier‑1 GitHub).

AI component of the project

  • What is real AI here? Tier‑1 describes AI endpoints for chat completion, embeddings and image generation (access to models via API).
  • What is truly onchain? the verifiable onchain artifact is the XMW token (ERC‑20) on Ethereum; additionally, Tier‑1 describes governance via ERC20Votes (token voting).
  • Why is a token needed? Tier‑1 claims incentives/rewards for network participants and a governance model via the token; payment for the AI API with the token is not confirmed in Tier‑1.
  • Red flags (based on the information found): token‑washing risk (if the token is not a mandatory payment primitive of the product), onchain‑washing risk (if onchain boils down to the token), admin risk (owner powers in the token contract). What to double‑check: whether there are onchain network/task contracts besides the token; whether there is Tier‑1 that XMW specifically is used to pay for compute/API.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is Tier‑1 confirmation of working AI functions via the API (AI_1=1), so AI_0 is not used as “intent only”.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the platform provides access to AI inference via API (chat completions, embeddings, image generation).
  • Evidence: Tier‑1 — https://docs.morphware.com/api-docs ; https://docs.morphware.com/api-docs/chat-completion ; https://docs.morphware.com/api-docs/ollama-embeddings ; https://docs.morphware.com/api-docs/image-generation
  • Why sufficient / why not (one line): the Tier‑1 documentation lists the AI endpoints and their purpose.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the product app.morphware.com is available, along with reproducible API call examples (curl) for the AI endpoints.
  • Evidence: Tier‑1 — https://app.morphware.com ; https://docs.morphware.com/api-docs/chat-completion ; https://docs.morphware.com/api-docs/ollama-embeddings ; https://docs.morphware.com/api-docs/pricing
  • Why sufficient / why not (one line): there is a public entry point of the product and example API requests.
  • 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): there are no reproducible quality metrics/benchmarks of the AI models or SLAs in Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there is no Tier‑1 specification of specific AI models/versions/architecture (apart from the API interfaces).
  • Evidence: Tier‑1 — https://docs.morphware.com/api-docs
  • Why sufficient / why not (one line): the API describes the interfaces but does not disclose model details (versions/training/quality).
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: the XMW token (ERC‑20): 0x391cF4b21F557c935C7f670218Ef42C21bd8d686
  • Evidence: Tier‑1 — https://etherscan.io/token/0x391cF4b21F557c935C7f670218Ef42C21bd8d686 ; https://etherscan.io/tx/0xf974861147a81d5e9755ccab74838378a9f6be03020a5f748ef64f2bb425a46d
  • Why sufficient / why not (one line): the explorer confirms the token address and the creation transaction (timestamp 2024‑09‑18).
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not confirmed (other than the token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the Tier‑1 sources contain no addresses/evidence of onchain network/task contracts besides XMW.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: Tier‑1 does not prove that the product breaks down without the blockchain.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the token is confirmed and token voting is described, but the criticality of the blockchain for the AI API/compute is not formalized.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, XMW (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x391cF4b21F557c935C7f670218Ef42C21bd8d686
  • Why sufficient / why not (one line): the token contract exists on Ethereum and has a max total supply.
  • Conflict note (if any): —

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): Tier‑1 does not confirm that payment for the AI API/compute must be made specifically in XMW.
  • Evidence: Tier‑1 — https://docs.morphware.com/api-docs/credits ; https://docs.morphware.com/api-docs/pricing
  • Why sufficient / why not (one line): Tier‑1 describes the credits/pricing system and API key/JWT, but does not describe mandatory payment for services in XMW.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the tokenomics claim community rewards/incentives, including rewards for GPU owners and developers.
  • Evidence: Tier‑1 — https://docs.morphware.com/economy/tokenomics
  • Why sufficient / why not (one line): the tokenomics directly describe the allocation for rewards/incentives and the purpose of the rewards.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): governance via token‑based voting (ERC20Votes).
  • Evidence: Tier‑1 — https://docs.morphware.com/legal/governance-and-community-engagement ; https://docs.morphware.com/economy/tokenomics
  • Why sufficient / why not (one line): Tier‑1 describes ERC20Votes and the role of token holders in decision‑making.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): incentives/payment and even voting could be implemented alternatively (for example stablecoin/points/offchain voting), and Tier‑1 does not prove the irreplaceability of XMW.
  • Evidence: Tier‑1 — https://docs.morphware.com/economy/tokenomics
  • Why sufficient / why not (one line): there is a description of the tokenomics and governance, but no strict proof that these functions are impossible without XMW.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.morphware.com/overview/introduction positioning: a peer‑to‑peer compute network; context on ML/compute
Tier‑1 https://docs.morphware.com/api-docs the existence of the set of Morphware API endpoints
Tier‑1 https://docs.morphware.com/api-docs/chat-completion chat completions endpoint + curl example
Tier‑1 https://docs.morphware.com/api-docs/ollama-embeddings embeddings endpoint + curl example
Tier‑1 https://docs.morphware.com/api-docs/image-generation image generation endpoint
Tier‑1 https://docs.morphware.com/api-docs/credits credits endpoint (access/accounting model)
Tier‑1 https://docs.morphware.com/api-docs/pricing pricing endpoint (pricing model)
Tier‑1 https://app.morphware.com the product/dashboard (the point for obtaining an API key and API access)
Tier‑1 https://docs.morphware.com/economy/tokenomics tokenomics: total supply, distribution, incentives, governance intent
Tier‑1 https://docs.morphware.com/legal/governance-and-community-engagement token‑based voting via ERC20Votes (governance)
Tier‑1 https://etherscan.io/token/0x391cF4b21F557c935C7f670218Ef42C21bd8d686 onchain fact: the XMW token (ERC‑20), max total supply
Tier‑1 https://etherscan.io/tx/0xf974861147a81d5e9755ccab74838378a9f6be03020a5f748ef64f2bb425a46d creation of the XMW token contract: 2024‑09‑18
Tier‑1 https://github.com/morphware/daemon open‑source desktop client: wallet + job creation/bidding (per the README)
Tier‑1 https://github.com/morphware/daemon/releases the existence of client releases (changelog via tags/releases)
Tier‑1 — No Tier‑1 source for claim “payment for the AI API/compute is mandatory in the XMW token” was found.
Tier‑1 — No Tier‑1 source for claim “onchain network contracts/addresses (besides the XMW token)” was found.

No comments to display

Back to top