Nimbus AI

Nimbus 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).

Nimbus AI — an AI/Infra project on Ethereum, token (symbol: NAI).

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 messenger focused on privacy and local AI features (per their documentation).
Who it’s for: for users who value the privacy of correspondence and convenient “smart” features (translation/suggestions).
Why onchain/token: the token is claimed as a means of payment/access to premium features and incentives (details — in Evidence).

How it works (very briefly)

The user does: exchanges messages in the application.
The system does: messages are encrypted end‑to‑end; routing/federation via Matrix is claimed.
The user gets: private chats + local AI suggestions/translation (claimed).
Where the blockchain is: blockchain logic of the product is not established in the available Tier‑1 materials; only the token on the Ethereum network is confirmed.
Token role (if any): payments within the ecosystem and access to premium features (claimed in the docs).

Quick links: AI thesis fit

Project passport

Field	Value
Project name	Nimbus AI
Also known as (aliases)	Nimbus Chat; $NAI
Logo (logo)	../assets/865_nimbus-ai_logo.png
Token symbol (ticker)	NAI
Category	AI/Other \| 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	0x32f4768FC4A238A58fc9da408d9a0Da4333012E4
Token model (token_type)	utility (premium access + payments)
Max supply	1,000,000,000
Issuance	fixed
Tokenomics (tokenomics, brief)	initial circulating supply: 600,000,000; transaction tax (as claimed in the docs)
Governance	—
Admins/keys	—
Audit	—
Bug bounty	—
Team (team)	—
Funding (investors/funding)	—
AI component (ai_component)	on-device AI (answers + translation)
Use‑case (use_case)	private messenger on Matrix
DecAI Fit — AI thesis fit	3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary	2 / 1 / 2 / 0
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://nimbuschat.ai/
App / Demo	https://linktr.ee/nimbus_AI
Docs	https://docs.nimbuschat.ai/
GitHub	—
Releases / Changelog	—
Whitepaper	—
Roadmap	—
Security advisories	—
Explorer	https://etherscan.io/token/0x32f4768FC4A238A58fc9da408d9a0Da4333012E4
X	https://twitter.com/NimbusChatAI
Discord	—
Telegram	https://t.me/Nimbus_AI
Medium	—
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/nimbus-ai
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/nimbus-ai/

General project overview

Nimbus AI is positioned as a private messenger with decentralized routing (via Matrix) and AI features that are processed locally on the user’s device. Per their documentation, the goal is to provide “smart” suggestions (replies/translation/insights) without sending correspondence to external cloud AI services.

Features/modules

Matrix‑compatible communication (claimed): federation via homeservers.
End‑to‑end encryption (claimed): keys are stored locally.
Local AI features (claimed): smart replies, translation, contextual analysis.

Typical scenarios

Scenario 1: a user exchanges messages → receives end‑to‑end protected communication (claimed).
Scenario 2: a user communicates in different languages → receives local translation of messages (claimed).
Scenario 3: a user replies to messages faster → uses smart replies suggestions (claimed).

Getting started (wallet/network)

What you need: join the beta / get access links (see links_* → App / Demo).
Network/chain: Ethereum — only for the $NAI token.
Fees: Ethereum network fees apply to token transactions; fees within the application are not established per Tier‑1 sources.

Architecture/tech (non‑AI)

Components (per the docs): Matrix homeservers (federation), client devices, E2E encryption.
Participant roles: users, homeserver operators (including self‑hosted).
Where logic runs: communication — on the Matrix network; AI processing — locally on the device; blockchain — only the $NAI token (per the available Tier‑1 data).
Dependencies: Matrix protocol.

Token/economics (expanded, no forecasts)

Token utility (per the docs): payments within the ecosystem; access to premium features; incentives for network participants.
Protocol necessity drivers: per Tier‑1 materials, this is claimed utility; verifiable onchain logic that makes the token “irreplaceable” is not established.
Fees: Ethereum network fees apply to token transactions.
Issuance: total supply 1,000,000,000 (fixed supply, per the docs).
Distribution (per the docs): liquidity pool 50%; network emissions 20%; CEX liquidity 5%; treasury 5%; angel investors 20%.
Transaction tax (per the docs): a transaction tax is claimed for operating expenses and “ecosystem health”.

Governance

Who makes decisions: not established per Tier‑1 sources (the docs mention “governance participation (future)”).
How protocol parameters change: not established.

Security and incidents

Audits: not established per Tier‑1 sources.
Bug bounty: not established per Tier‑1 sources.
Incidents: not established per Tier‑1 sources.
Threat model: E2E encryption and local AI processing are claimed; audit/verification details are not established per Tier‑1 sources.

Project status and timeline

Current status: a “beta program” is mentioned (the participation link is on the website).
Key releases/milestones: not established per Tier‑1 sources.
Roadmap: not established per Tier‑1 sources.

Ecosystem/integrations

Integrations: Matrix protocol (claimed).
Partners: not established per Tier‑1 sources.
Where it’s actually used: public cases/integrations are not established per Tier‑1 sources.

AI component of the project

What is real AI here? Local AI features are described in Tier‑1 documentation: smart replies, translation, contextual analysis.
What is truly onchain? The $NAI token on the Ethereum network is confirmed per Tier‑1; blockchain logic of the messenger (other than the token) is not established.
Why is a token needed? The docs claim payments/premium access and incentives for network participants; the actual irreplaceability of the token is not proven per Tier‑1.
Red flags and what to double‑check:
- AI‑washing: no metrics/benchmarks (AI_3=0).
- onchain‑washing: no confirmation of onchain logic other than the token was found (OC_2=0).
- token‑washing: utility and tax/distribution are claimed, but implementation and governance require re‑checking.

DecAI Fit component summary

DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis

Component	Level	Score
AI reality	medium	2
Onchain necessity	low	1
Token necessity	medium	2
Evidence	Tier‑1 present	0

Details

AI reality

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

AI_0 (decision): 0
Claim (one line): AI intent as “only a roadmap without implementation” does not apply: specific AI features are described in Tier‑1 documentation.
Evidence: Tier‑1 — https://docs.nimbuschat.ai/
Why sufficient / why not (one line): AI intent exists, but it is not “pure intent without implementation”, so AI_0=0.
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 1
Claim (one line): Smart replies, translation and context analysis are described in Tier‑1 documentation.
Evidence: Tier‑1 — https://docs.nimbuschat.ai/how-nimbus-works/ai-decentralization
Why sufficient / why not (one line): What exactly the AI features do is described (the minimum for AI_1=1).
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): A public demo/app demonstrating AI features is not established per Tier‑1 sources.
Evidence: —
Why sufficient / why not (one line): There is no verifiable “what you can touch” link (a requirement for AI_2=1).
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: not established per Tier‑1 sources
Context (version/date/how measured): not established per Tier‑1 sources
Evidence: —
Why sufficient / why not (one line): There are no quantitative quality metrics for the AI component in Tier‑1 materials.
Conflict note (if any): —

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

AI_4 (decision): 1
Claim (one line): There is a high‑level tech description of the architecture (Matrix + E2E + on‑device AI).
Evidence: Tier‑1 — https://docs.nimbuschat.ai/how-nimbus-works/technical-overview
Why sufficient / why not (one line): There is a Tier‑1 description of the architecture and AI processing principles (without model versions).
Conflict note (if any): —

Onchain necessity

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

OC_1 (decision): 1
Chain: Ethereum
Addresses/identifiers: 0x32f4768FC4A238A58fc9da408d9a0Da4333012E4
Evidence: Tier‑1 — https://etherscan.io/token/0x32f4768FC4A238A58fc9da408d9a0Da4333012E4
Why sufficient / why not (one line): There is a verifiable onchain artifact: the token address in 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: —
Why sufficient / why not (one line): No Tier‑1 confirmation of onchain logic of the product (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: per Tier‑1 sources, the criticality of the blockchain is not proven (other than the token).
Evidence: —
Why sufficient / why not (one line): There is no Tier‑1 justification that a key property of the product breaks down without the blockchain.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): The project has a claimed token, $NAI.
Evidence: Tier‑1 — https://docs.nimbuschat.ai/nimbus-token/overview-and-utility
Why sufficient / why not (one line): $NAI is described in Tier‑1 documentation.
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 docs claim that $NAI is used for payments/subscriptions/upgrades in the ecosystem.
Evidence: Tier‑1 — https://docs.nimbuschat.ai/nimbus-token/overview-and-utility
Why sufficient / why not (one line): There is a Tier‑1 claim about paying for services/upgrades with the token.
Conflict note (if any): —

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

TK_2 (decision): 1
Claim (one line): The docs claim incentives for network participants and “network emissions”.
Evidence: Tier‑1 — https://docs.nimbuschat.ai/nimbus-token/tokenomics
Why sufficient / why not (one line): There is a Tier‑1 description of the distribution of “network emissions” and incentives (without verifying the onchain implementation).
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): The docs mention governance as “future”, but the current mechanism is not described as operational.
Evidence: Tier‑1 — https://docs.nimbuschat.ai/nimbus-token/overview-and-utility
Why sufficient / why not (one line): This is an intent/plan without a verifiable implementation, so TK_3=0.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 0
Claim (one line): The replaceability/irreplaceability of the token is not established per Tier‑1 sources.
Evidence: —
Why sufficient / why not (one line): There is insufficient justification that the token is definitely replaceable or definitely irreplaceable.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://nimbuschat.ai/	Positioning of Nimbus as “privacy-first AI powered messaging”; a link to the documentation
Tier‑1	https://docs.nimbuschat.ai/how-nimbus-works/ai-decentralization	AI features: smart replies, translation, contextual analysis; local processing
Tier‑1	https://docs.nimbuschat.ai/how-nimbus-works/technical-overview	High‑level architecture (Matrix + E2E + on‑device AI)
Tier‑1	https://docs.nimbuschat.ai/nimbus-token/overview-and-utility	Token utility: payments/premium access; incentives (claimed)
Tier‑1	https://docs.nimbuschat.ai/nimbus-token/tokenomics	Total supply 1B; distribution; transaction tax (claimed)
Tier‑1	https://etherscan.io/token/0x32f4768FC4A238A58fc9da408d9a0Da4333012E4	Onchain fact: the $NAI token on the Ethereum network (contract address)
Tier‑1	—	No Tier‑1 source for claim “the messenger has onchain logic other than the token” was found.