nomAI
nomAI — 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).
nomAI — an AI/Other project on the Base 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 token on the Base network; per the project website — AI positioning around “on‑chain data x AI”.
- Who it’s for: for users/the community; a practical product/demo is not established per the available sources.
- Why onchain/token: onchain records ownership and transfers of the token; the necessity of the token in the product is not established.
How it works (very briefly)
- The user does: buys/receives the token and transfers it on the Base network.
- The system does: executes standard ERC‑20 operations in the token’s smart contract.
- The user gets: the token balance and transaction history, verifiable via the block explorer.
- Where the blockchain is: the token contract and operations (transfers/balances) — onchain (Base).
- Token role (if any): per Tier‑1 it is not established that the token is mandatory for the operation of a specific product/service.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | nomAI |
| Also known as (aliases) | — |
| Logo (logo) | — |
| Token symbol (ticker) | — |
| Category | AI/Other |
| Primary chain (chain) | Base |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Base; Ethereum L2) |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | ERC-20 |
| Token contract | 0x4d70f1058b73198f12a76c193aef5db5dd75babd |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | positioning only (on-chain data) |
| Use‑case (use_case) | on-chain data/intelligence |
| 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 | http://nomai.ai |
| Docs | — |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://basescan.org/token/0x4d70f1058b73198f12a76c193aef5db5dd75babd |
| X | https://twitter.com/0x_nomAI |
| Discord | https://discord.gg/alphanomics |
| Telegram | — |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/nomai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/nomai/ |
General project overview
Per the available Tier‑1 sources, the project has a website and a token on the Base network with a public contract. Within the check, no Tier‑1 description of a working product/application (demo/code/docs) was found where the AI component and the necessity of the token would be verifiably shown.
Features/modules
- ERC‑20 token (Base): onchain contract and basic operations (balance/transfers).
- Project website: public claims/positioning “on‑chain data x AI” (without technical artifacts).
Typical scenarios
- Scenario 1: a user transfers the token between addresses → the transactions are visible in the Base explorer.
- Scenario 2: a user checks the token contract → uses the block explorer as a source of onchain facts.
Getting started (wallet/network)
- What you need: an EVM wallet.
- Network/chain: Base.
- Fees: Base network fees for onchain operations.
Architecture/tech (non‑AI)
- Components: the ERC‑20 token smart contract.
- Participant roles: users/token holders.
- Where logic runs: token operations — onchain (Base).
- Dependencies: Base network infrastructure (validators/nodes/RPC providers).
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1 sources per the available sources.
- Protocol necessity drivers: it is not established that the product does not work without the token.
- Who pays fees: users pay Base network fees for onchain operations.
- Where fees go: to the Base network validators (network level).
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Keys/multisig: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: smart contract risks and contract administration risks (if applicable; not established).
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? Per the Tier‑1 website, the project is positioned as on‑chain data x AI; no Tier‑1 tech description/code/metrics of the AI component were found per the available sources.
- What is truly onchain? The token contract and transactions on the Base network (verified via the block explorer).
- Why is a token needed? Not established per Tier‑1 sources per the available sources.
- Red flags (based on the information found): claims about AI without technical artifacts; absence of a Tier‑1 description of the necessity of the token; absence of Tier‑1 links to code/docs/demo.
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 partial | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): Intentions are not singled out as a separate signal, because we record the AI positioning in AI_1 as “what is claimed”.
- Evidence: Tier‑1 — https://www.nomai.ai/
- Why sufficient / why not (one line): In this card, intent is accounted for via AI_1 (a description of the claimed purpose).
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): Per the Tier‑1 website: “on‑chain data x AI” and a layer of onchain intelligence/data validation (in the project’s wording).
- Evidence: Tier‑1 — https://www.nomai.ai/
- Why sufficient / why not (one line): There is a Tier‑1 description of the purpose (what the AI part is trying to do), but without tech docs/metrics.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No Tier‑1 demos/examples of the AI component in operation were found per the available sources.
- Evidence: Tier‑1 — https://www.nomai.ai/
- Why sufficient / why not (one line): Without a link to a demo/guide/reproducible example, AI_2 remains 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://www.nomai.ai/
- Why sufficient / why not (one line): Public quality metrics of the AI component (with context) were not found per the available sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): No Tier‑1 tech description of the AI component (architecture/versions) was found per the available sources.
- Evidence: Tier‑1 — https://www.nomai.ai/
- Why sufficient / why not (one line): AI_4=1 requires a Tier‑1 artifact (tech docs/repo/architecture/versions).
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Base
- Addresses/identifiers: token contract: 0x4d70f1058b73198f12a76c193aef5db5dd75babd
- Evidence: Tier‑1 — https://basescan.org/token/0x4d70f1058b73198f12a76c193aef5db5dd75babd
- Why sufficient / why not (one line): The onchain contract page confirms the existence of the token and the network.
- 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 the available sources (other than the token).
- Evidence: Tier‑1 — https://basescan.org/token/0x4d70f1058b73198f12a76c193aef5db5dd75babd
- Why sufficient / why not (one line): per the available sources, no Tier‑1 confirmation of useful 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 per the available sources.
- Evidence: Tier‑1 — https://www.nomai.ai/
- Why sufficient / why not (one line): No Tier‑1 explanation of why onchain is critical for the product was 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 on the Base network (the contract is in the block explorer).
- Evidence: Tier‑1 — https://basescan.org/token/0x4d70f1058b73198f12a76c193aef5db5dd75babd
- Why sufficient / why not (one line): The existence of the token is confirmed by onchain data.
- 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): No Tier‑1 confirmation of payment for the service with the token was found per the available sources.
- Evidence: Tier‑1 — https://www.nomai.ai/
- Why sufficient / why not (one line): TK_1=1 requires Tier‑1 terms/tariffs/docs where the token is a mandatory payment.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): No Tier‑1 evidence of a mechanism of incentives/collateral/penalties with the token was found per the available sources.
- Evidence: Tier‑1 — https://www.nomai.ai/
- Why sufficient / why not (one line): TK_2=1 requires protocol/economy rules with a description of incentives.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): No Tier‑1 confirmation of the use of the token in governance was found per the available sources.
- Evidence: Tier‑1 — https://www.nomai.ai/
- Why sufficient / why not (one line): TK_3=1 requires a Tier‑1 governance process and a role of the token in voting.
- 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 the available sources.
- Evidence: Tier‑1 — https://www.nomai.ai/
- Why sufficient / why not (one line): TK_4=1 requires a Tier‑1 explanation that the token is not necessary (it can be replaced with payment/a subscription without loss of meaning).
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://www.nomai.ai/ | Tier‑1 source: public description/positioning “on‑chain data x AI” (without tech details/metrics). |
| Tier‑1 | https://basescan.org/token/0x4d70f1058b73198f12a76c193aef5db5dd75babd | Onchain fact: the token contract on the Base network (ERC‑20), transactions and metadata. |
| Tier‑1 | — | No Tier‑1 source for claim “why is a token needed” was found per the available sources. |
| Tier‑2 | https://www.coingecko.com/en/coins/nomai | Reference token profile (not proof of the necessity of the token/AI component). |
| Tier‑2 | https://coinmarketcap.com/currencies/nomai/ | Reference token profile (not proof of the necessity of the token/AI component). |
No comments to display
No comments to display