Skip to main content

Nora

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

Nora — an AI/Agents project on the Solana 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: an AI agent and an application for mental health support (chat interaction and community features).
  • Who it’s for: users who need quick support/self‑help and communication in a topical community.
  • Why onchain/token: per Tier‑1 sources, a combination of AI and Web3/privacy is claimed; the necessity of the token as a mandatory mechanism of the product is not established.
  • What you can actually touch (Tier‑1): the AI agent on X (@talktonora) and mobile applications (iOS/Android) via the official documentation.

How it works (very briefly)

  1. The user does: asks a question/describes their state in the chat (on X or in the application).
  2. The system does: forms a response and recommendations in a conversational format.
  3. The user gets: support/hints and the ability to interact with the community (in the application).
  4. Where the blockchain is: the Tier‑1 documentation claims that part of the “anonymized session metadata” is stored onchain; implementation details/addresses are not provided.
  5. Token role (if any): Tier‑1 describes a “community token” for use in future applications/features; whether it is mandatory for the product to work is not established.

Quick links: AI thesis fit

Project passport

Field Value
Project name Nora
Also known as (aliases) TalkToNora
Logo (logo) ../assets/631_nora_logo.svg
Token symbol (ticker) —
Category AI/Agents | 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 3Yie9s6iuEmk8aiXYC19xaq2iccTuFzyfKBWv6gFpump
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Fair‑launch community token; usage is described as “future apps/features”, whether it is mandatory is not established.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agents for mental health support
Use‑case (use_case) mental health (chat support + community)
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 0 / evidence_score 1
Last verified 2026-02-11

General project overview

Nora is positioned as an AI system for mental health support: the user can interact with the AI agent publicly on X and privately via the mobile application. The Tier‑1 documentation describes the target scenarios (support, community interaction) and claims a combination of AI + Web3 privacy (including the idea of storing part of the metadata onchain).

Features/modules

  • AI agent on X: public interaction and responses.
  • Mobile application: private sessions, community features (Tribes/Feed).
  • AI framework: a high‑level architecture and approaches to training/deployment are described (Tier‑1).

Typical scenarios

  • Scenario 1: the user mentions @talktonora on X → receives a response/hint.
  • Scenario 2: the user chats in the application in private mode → receives support and can participate in groups/feeds.

Getting started (wallet/network)

  • What you need: an X account or installation of the mobile application.
  • Network/chain: Solana is required only for onchain interactions with the token (if the user performs them).
  • Fees: Solana network fees arise only for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: the AI agent (X) and mobile applications (iOS/Android); an onchain component in the form of a token on the Solana network.
  • Participant roles: users, the community, the team/product operators.
  • Where logic runs: interaction with the AI — offchain; onchain — operations with the token.
  • Dependencies: X as an interaction channel; app stores; Solana as the network for the token.

Token/economics (expanded, no forecasts)

  • Token utility: described in Tier‑1 as a community token for “future applications/features”; no specific mandatory utility is recorded.
  • Protocol necessity drivers: the necessity of the token as a mandatory part of the product’s operation is not established per Tier‑1.
  • Who pays fees: users, if they perform onchain operations with the token.
  • Where fees go: to the Solana network validators (per the network rules).
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: — (not established per Tier‑1).
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: privacy risks/quality risks of the AI system’s advice; risks of the token as a separate crypto asset (not related to “help” as a service).

Project status and timeline

  • Current status: an active product (there are “live features” in the Tier‑1 documentation).
  • Key releases/milestones: —.
  • Roadmap: published in the official documentation (see links_*).

Ecosystem/integrations

  • Integrations: X, iOS/Android applications.
  • Partners: —.
  • Where it’s actually used: user interactions are available via X and the mobile applications (Tier‑1).

AI component of the project

  • What is real AI here? The Tier‑1 documentation describes an AI agent for conversational support (including the architecture and the training/deployment process).
  • What is truly onchain? Per Tier‑1, a token on the Solana network is established; additionally, storage of anonymized metadata onchain is claimed, but without implementation details.
  • Why is a token needed? Described in Tier‑1 as a community token for future features/applications; its necessity as a mandatory mechanism of the product is not established.
  • Red flags (based on the information found): mixing “AI disclaimers/architecture” with verifiable quality metrics (metrics not found); claims about onchain privacy without contracts/addresses; “token utility in the future” without current mandatory functions.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described as an already working component of the product (not only an “intent”).
  • Evidence: Tier‑1 — https://docs.speaktonora.com/
  • Why sufficient / why not (one line): Tier‑1 describes “live features” and the AI agent, so this intent flag is not used.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The AI agent conducts a conversation and provides support on mental health topics.
  • Evidence: Tier‑1 — https://docs.speaktonora.com/ ; https://docs.speaktonora.com/interacting-with-nora
  • Why sufficient / why not (one line): Tier‑1 directly describes the purpose and the channels of interaction with the AI agent.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There are instructions on how to interact with the AI agent on X and in the mobile applications (iOS/Android).
  • Evidence: Tier‑1 — https://docs.speaktonora.com/interacting-with-nora
  • Why sufficient / why not (one line): This is a reproducible “demo surface”: one can contact the account and install the applications via the Tier‑1 links.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found in Tier‑1 sources.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://docs.speaktonora.com/ai-agent-framework
  • Why sufficient / why not (one line): Tier‑1 describes approaches/architecture, but no unified set of quantitative quality metrics was found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): Tier‑1 describes the architecture of the AI agent (transformer‑based), training methodologies, and privacy/deployment aspects.
  • Evidence: Tier‑1 — https://docs.speaktonora.com/ai-agent-framework
  • Why sufficient / why not (one line): There is a structured tech description (architecture/training/deployment) at the documentation level.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: SPL mint 3Yie9s6iuEmk8aiXYC19xaq2iccTuFzyfKBWv6gFpump
  • Evidence: Tier‑1 — https://solscan.io/token/3Yie9s6iuEmk8aiXYC19xaq2iccTuFzyfKBWv6gFpump
  • Why sufficient / why not (one line): There is a verifiable onchain artifact (a token on the Solana 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 Tier‑1 (other than the token).
  • Evidence: Tier‑1 — https://docs.speaktonora.com/ai-agent-framework
  • Why sufficient / why not (one line): The documentation contains claims about blockchain integration, but without contracts/addresses/a description of onchain logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification was found that the product breaks down without the blockchain.
  • Evidence: Tier‑1 — https://docs.speaktonora.com/
  • Why sufficient / why not (one line): OC_3 requires an explicit Tier‑1 statement “why it is impossible without onchain”; none was found per Tier‑1.
  • 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 Solana network (SPL).
  • Evidence: Tier‑1 — https://solscan.io/token/3Yie9s6iuEmk8aiXYC19xaq2iccTuFzyfKBWv6gFpump
  • Why sufficient / why not (one line): The onchain page of the token confirms the existence of the token.
  • 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): Payment for the service with the token as a mandatory function is not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.speaktonora.com/token-utility
  • Why sufficient / why not (one line): Tier‑1 describes possible future usage scenarios, but not a mandatory “pay‑for‑service”.
  • 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.
  • Evidence: Tier‑1 — https://docs.speaktonora.com/token-utility
  • Why sufficient / why not (one line): The utility description contains no specific mechanism of incentives/collateral/penalty.
  • 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.
  • Evidence: Tier‑1 — https://docs.speaktonora.com/
  • Why sufficient / why not (one line): TK_3 requires an explicit Tier‑1 description of governance mechanics via the token; none was 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://docs.speaktonora.com/token-utility
  • Why sufficient / why not (one line): A clear mechanic of “what breaks down/does not break down without the token” is required; Tier‑1 has no sufficient justification.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.speaktonora.com/ Official description of the product and “live features” (AI agent + mobile applications).
Tier‑1 https://docs.speaktonora.com/interacting-with-nora How to interact with the AI agent (X) and links to the iOS/Android applications (demo surface).
Tier‑1 https://docs.speaktonora.com/ai-agent-framework Tech description of the AI approach (architecture/training/deployment/privacy) without quality metrics.
Tier‑1 https://solscan.io/token/3Yie9s6iuEmk8aiXYC19xaq2iccTuFzyfKBWv6gFpump The existence of the token on the Solana network (SPL mint).
Tier‑1 https://docs.speaktonora.com/token-utility Description of the “community token” and the claimed (including future) usage scenarios.
Tier‑1 — No Tier‑1 source for claim “the token is necessary as a mandatory part of the protocol” was found.

No comments to display

Back to top