Skip to main content

Megapix

Megapix — 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).

Megapix — an AI/Other | Consumer project on the Solana network, token (symbol: MPIX).

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 service for generating AI images and enhancing/processing images (including via a Telegram bot).
  • Who it’s for: users and creators who need fast text‑to‑image and basic image processing.
  • Why onchain/token: the token is used for token gating/access tiers to the generation and processing features.

How it works (very briefly)

  1. The user does: writes a prompt or uploads an image for processing.
  2. The system does: runs the generation/processing in the AI engine.
  3. The user gets: a finished image (generation) or an enhanced version (processing).
  4. Where the blockchain is: onchain is used for accounting of the token/access (the token contract is observable via the Explorer).
  5. Token role: MPIX is used for access tiers (token tiers) to the features.

Quick links: AI thesis fit

Project passport

Field Value
Project name Megapix
Also known as (aliases) MPIX
Logo (logo) —
Token symbol (ticker) MPIX
Category AI/Other | Consumer
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 GEdBv2DnES89DvasmZ35TaxP9kBibznYKbacXpoGTEBU
Token model (token_type) utility (payments)
Max supply 1,000,000,000 MPIX (total supply)
Issuance fixed
Tokenomics (tokenomics, brief) Total supply 1B; token tiers unlock generation/processing limits (Explorer/Creator/Visionary tiers).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) generative AI art engine + Telegram bot
Use‑case (use_case) text-to-image generation + image enhancement
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 2
Last verified 2026-02-11

General project overview

Megapix positions itself as a product for creating AI art: image generation from a text description and image processing. The website separately mentions a Telegram bot for generation/enhancement and an access model via token tiers.

Features/modules

  • Generative AI Engine: image generation from a prompt.
  • Telegram bot: commands for generation/processing (for example, /gen, /enhance, /colorize).
  • Token tiers: access tiers (generation/processing limits) depending on the amount of MPIX.

Typical scenarios

  • Scenario 1: a user describes an idea → receives a generated image.
  • Scenario 2: a user uploads an image → receives an enhanced/processed version.
  • Scenario 3: a user connects a token tier → receives increased generation/processing limits.

Getting started (wallet/network)

  • What you need: access to the product (website/Telegram); when using token tiers — a Solana wallet and the MPIX token.
  • Network/chain: Solana.
  • Fees: Solana network fees for operations with the token; the fee/payment model inside the product is not established per Tier‑1 sources.

Architecture/tech (non‑AI)

  • Components: an AI service (offchain) + the MPIX token on the Solana network (onchain) + interfaces (website/Telegram).
  • Participant roles: users; product operators.
  • Where logic runs: image generation/processing — offchain; accounting of token ownership/transactions — onchain.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: token tiers (Explorer/Creator/Visionary) unlock image generation and processing limits.
  • Protocol necessity drivers: the token is used as a mechanism of access/limits for product features (token gating).
  • Who pays fees: users, when they interact with the token on the Solana network.
  • Where fees go: to Solana validators (network fees).
  • Issuance/burn: total supply 1,000,000,000 MPIX (per the Tier‑1 description on the website).
  • 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: not found per Tier‑1 sources.
  • Bug bounty: not found per Tier‑1 sources.
  • Incidents: —.
  • Threat model: risks of centralization of the AI service (offchain) and of a gap between the “AI product” and the onchain part (only the token/access).

Project status and timeline

  • Current status: mainnet (the token on the Solana network is observable via the Explorer).
  • Key releases/milestones: —.
  • Roadmap: not found per Tier‑1 sources.

Ecosystem/integrations

  • Integrations: Telegram (bot) and website (see links_*).
  • Partners: —.
  • Where it’s actually used: user generations/processing via the product (Tier‑1 described on the website).

AI component of the project

  • What is real AI here? A generative AI engine for creating images and basic image processing (claimed on the official website).
  • What is truly onchain? Onchain, the MPIX token on the Solana network is observable (Explorer); the AI part runs offchain.
  • Why is a token needed? The token is used for token tiers/access tiers and limits of the generation/processing features.
  • Red flags (based on the information found): the onchain part looks like token gating around an offchain product; Tier‑1 model quality metrics were not found (AI_3=0).

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 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): In the Tier‑1 description, the product is already presented as an AI service (image generation/processing), not only as a “plan”.
  • Evidence: Tier‑1 — https://megapix.ai/
  • Why sufficient / why not (one line): AI_0 applies when there is only intent without a description of the feature; here there is a description of the AI feature (see AI_1), hence 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Generative AI Engine: image generation from a prompt and basic processing (enhance/colorize) via the product/bot.
  • Evidence: Tier‑1 — https://megapix.ai/
  • Why sufficient / why not (one line): The official website explicitly describes AI art generation and the bot commands for generation/processing.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): A public demo/endpoint for a “one‑click” check is not recorded per Tier‑1 sources (other than the description on the website).
  • Evidence: Tier‑1 — https://megapix.ai/
  • Why sufficient / why not (one line): AI_2=1 requires a confirmed app/demo URL in links_* and Evidence; under the conservative rule 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://megapix.ai/
  • Why sufficient / why not (one line): Tier‑1 quality metrics/benchmarks (with version/date context) were not found in Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A technical description of the architecture/model versions was not found in Tier‑1 sources.
  • Evidence: Tier‑1 — https://megapix.ai/
  • Why sufficient / why not (one line): In the absence of a tech description/versions we conservatively set 0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: the MPIX token (SPL) — GEdBv2DnES89DvasmZ35TaxP9kBibznYKbacXpoGTEBU
  • Evidence: Tier‑1 — https://solscan.io/token/GEdBv2DnES89DvasmZ35TaxP9kBibznYKbacXpoGTEBU
  • Why sufficient / why not (one line): The existence of an onchain token identifier and its observability in the Explorer is sufficient for OC_1=1.
  • 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 (per Tier‑1, mostly an offchain product is described; onchain — the token and access).
  • Evidence: Tier‑1 — https://megapix.ai/ ; https://solscan.io/token/GEdBv2DnES89DvasmZ35TaxP9kBibznYKbacXpoGTEBU
  • Why sufficient / why not (one line): OC_2=1 requires specific useful onchain logic (not just the token); per Tier‑1 sources this is not confirmed.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: per Tier‑1 sources, it is not established that a key property of the product breaks down without the blockchain.
  • Evidence: Tier‑1 — https://megapix.ai/
  • Why sufficient / why not (one line): With insufficient data on onchain criticality we set 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, MPIX (SPL, Solana).
  • Evidence: Tier‑1 — https://megapix.ai/ ; https://solscan.io/token/GEdBv2DnES89DvasmZ35TaxP9kBibznYKbacXpoGTEBU
  • Why sufficient / why not (one line): The website gives the contract and the tokenomics, and the Explorer allows observing the token 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): MPIX is used as a mechanism of access/tiers (token tiers) to the generation and processing capabilities.
  • Evidence: Tier‑1 — https://megapix.ai/
  • Why sufficient / why not (one line): The official website describes the access tiers and the requirements for the amount of MPIX.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Token‑based incentives/collateral/penalties are not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://megapix.ai/
  • Why sufficient / why not (one line): No description of staking/slashing/collateral was found in Tier‑1; we conservatively set 0.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of the token for governance is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://megapix.ai/
  • Why sufficient / why not (one line): TK_3=1 requires a Tier‑1 voting mechanic; in its absence — 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token (for example, with a subscription) is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://megapix.ai/
  • Why sufficient / why not (one line): TK_4=1 requires proof of replaceability without loss of meaning; in its absence — 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://megapix.ai/ Positioning of the product (AI art/bot) and the description of token tiers + tokenomics (total supply, contract).
Tier‑1 https://solscan.io/token/GEdBv2DnES89DvasmZ35TaxP9kBibznYKbacXpoGTEBU Onchain fact: the MPIX token and its address on the Solana network (observability via the Explorer).
Tier‑2 https://www.coingecko.com/en/coins/megapix Token profile (context/navigation).
Tier‑2 https://coinmarketcap.com/currencies/megapix/ Token profile (context/navigation).
Tier‑3 — —

No comments to display

Back to top