Skip to main content

Neur

Neur (neur-app) — 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).

Neur — an AI/Agents project on Solana, token (symbol: NEUR).

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 open‑source “copilot for Solana” application that combines an LLM agent and a set of tools for actions in the Solana ecosystem (DeFi/NFT/wallet).
  • Who it’s for: Solana users and developers/teams who need an interface and an agent for operations on the network.
  • Why onchain/token: onchain is the purpose and the operating environment of the product (operations with the wallet/tokens/NFTs/DeFi); the utility of the project’s token is not established per Tier‑1.

How it works (very briefly)

  1. The user does: sets a task in the chat (natural language) and connects a wallet.
  2. The system does: the LLM agent selects tools (function calling) and executes onchain operations (swap/transfer/NFT operations, etc.).
  3. The user gets: the result of the operation + context/analytics (within the capabilities of the application).
  4. Where the blockchain is: transaction execution and data reading take place on the Solana network and its services.
  5. Token role (if any): the token in this card is confirmed as a mint in the Solana explorer; its purpose/utility require separate verification.

Quick links: AI thesis fit

Project passport

Field Value
Project name Neur
Also known as (aliases) neur-app, neur.sh
Logo (logo) ../assets/367_neur-sh_logo.svg
Token symbol (ticker) NEUR
Category AI/Agents | Infra
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 3N2ETvNpPNAxhcaXgkhKoY1yDnQfs41Wnxsx5qNJpump
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) the utility of the token is not established per Tier‑1
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) LLM agent + tool calling
Use‑case (use_case) copilot for Solana operations
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 2 / token_score 0 / evidence_score 2
Last verified 2026-02-11
Type Link
Website —
Docs https://github.com/NeurProjects/neur-app
GitHub https://github.com/NeurProjects
Releases / Changelog https://github.com/NeurProjects/neur-app/blob/main/CHANGELOGS.md
Whitepaper —
Roadmap https://github.com/NeurProjects/neur-app#roadmap
Security advisories https://github.com/NeurProjects/neur-app/security
Explorer https://solscan.io/token/3N2ETvNpPNAxhcaXgkhKoY1yDnQfs41Wnxsx5qNJpump
X https://twitter.com/neur_sh
Discord https://discord.neur.sh/
Telegram —
Medium —
Audit report(s) —
Bug bounty —
CoinGecko (profile, reference) https://www.coingecko.com/en/coins/neur-sh
CoinMarketCap (profile, reference) https://coinmarketcap.com/currencies/neur-sh/

General project overview

Neur describes itself as an open‑source full‑stack application, an “intelligent copilot for Solana”, which combines LLM model(s) and blockchain integrations. Per the README, the claimed scenarios are: interaction with DeFi protocols, NFT operations, an embedded wallet and the execution of complex onchain operations via function calling.

Features/modules

  • Chat interface + agent: an agent with NLU for Solana scenarios (DeFi/NFT).
  • Tooling (function calling): execution of onchain operations (for example, sending/swapping tokens).
  • Embedded wallet (claimed): wallet and portfolio management inside the application.
  • Integrations (claimed): Jupiter, Magic Eden and other Solana services.

Typical scenarios

  • Scenario 1: the user sets a task in the chat → the agent proposes an action → executes an onchain operation.
  • Scenario 2: the user manages an NFT collection/portfolio via the interface.
  • Scenario 3: the user uses DeFi integrations (swap/limit/ DCA, etc.) via the combination of tools.

Getting started (wallet/network)

  • What you need: building/running the application per the README and the repository instructions (Tier‑1); access to a Solana wallet.
  • Network/chain: Solana.
  • Fees: Solana fees for transactions; fees of the integrated protocols — per their rules.

Architecture/tech (non‑AI)

  • Components: web client, backend, tools for Solana operations, integrations with external services of the Solana ecosystem.
  • Participant roles: application users, external protocols/services (Jupiter/Magic Eden, etc.).
  • Where logic runs: the agent and processing — offchain; transactions and state — onchain (Solana).
  • Dependencies: RPC access to Solana, external APIs/protocols (Jupiter/Magic Eden, etc.), LLM provider(s) (depending on the configuration).

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1.
  • Protocol necessity drivers: in the Tier‑1 materials of the repository, the purpose of the token is not described explicitly.
  • Who pays fees: users for onchain operations on Solana.
  • Where fees go: network fees — to Solana validators.
  • Issuance/burn: not established per Tier‑1.
  • Incentive mechanisms: not established per Tier‑1.
  • Distribution/vesting: not established per Tier‑1.
  • Treasury: not established per Tier‑1.

Governance

  • Who makes decisions: not established per Tier‑1.
  • How product parameters change: changes via releases/PRs in the repository.
  • Where decisions are discussed/made: GitHub issues/PRs.
  • Keys/multisig: not applicable to the application as an offchain product; for the onchain parts, separate verification is required.

Security and incidents

  • Audits: no confirmation of public audits was found per Tier‑1.
  • Bug bounty: not found per Tier‑1.
  • Incidents: not established per Tier‑1.
  • Threat model (what to double‑check): key/wallet security, the permissions of the agent’s functions, trust in external APIs/protocols, limiting the agent’s actions.

Project status and timeline

  • Current status: active development (based on repository activity and the README).
  • Key releases/milestones: not established per Tier‑1.
  • Roadmap: described in the README (Tier‑1).

Ecosystem/integrations

  • Integrations (claimed): Jupiter, Magic Eden and other Solana services.
  • Partners: not established per Tier‑1.
  • Where it’s actually used: the descriptions in the README are confirmed; onchain usage metrics require separate verification.

AI component of the project

  • What is real AI here? an LLM agent and an NLU layer that interprets the user’s request and launches tools for Solana operations.
  • What is truly onchain? onchain operations on Solana (transactions, NFTs, DeFi integrations) — the central part of the product scenarios.
  • Why is a token needed? the purpose of the NEUR token is not established per Tier‑1 (apart from the fact that the mint exists).
  • Red flags (what to double‑check): the domains neur.sh and docs.neur.sh look parked/expired (Sedo Domain Parking pages); the security model around “the agent executes transactions”; the utility of the token and the sources of onchain addresses/contracts.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity medium 2
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): The AI component is described as part of the product (LLM agent), so AI_0 is not used as “intent only”.
  • Evidence: Tier‑1 — https://github.com/NeurProjects/neur-app
  • Why sufficient / why not (one line): there are descriptions of the AI agent and of the list of capabilities.
  • Conflict note: —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The LLM agent processes user requests and launches onchain tools (function calling) for operations on Solana.
  • Evidence: Tier‑1 — https://github.com/NeurProjects/neur-app
  • Why sufficient / why not (one line): this is described in the README (agent + tool system).
  • Conflict note: —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demo/app endpoint is established (the main Tier‑1 artifact is the repository).
  • Evidence: Tier‑1 — https://github.com/NeurProjects/neur-app
  • Why sufficient / why not (one line): there are instructions for the dev environment, but a “live demo” is not confirmed.
  • Conflict note: —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://github.com/NeurProjects/neur-app
  • Why sufficient / why not (one line): AI quality metrics are not provided in Tier‑1.
  • Conflict note: —

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

  • AI_4 (decision): 1
  • Claim (one line): there is a Tier‑1 repository of the open‑source application and tech docs for the dev environment.
  • Evidence: Tier‑1 — https://github.com/NeurProjects/neur-app
  • Why sufficient / why not (one line): the availability of the source code and the project structure is a technical artifact.
  • Conflict note: —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: SPL mint 3N2ETvNpPNAxhcaXgkhKoY1yDnQfs41Wnxsx5qNJpump
  • Evidence: Tier‑1 — https://solscan.io/token/3N2ETvNpPNAxhcaXgkhKoY1yDnQfs41Wnxsx5qNJpump
  • Why sufficient / why not (one line): onchain fact: the token identifier in the network explorer.
  • Conflict note: —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: execution of operations on Solana (swap/tokens/NFT/DeFi) as part of the agent tools.
  • Evidence: Tier‑1 — https://github.com/NeurProjects/neur-app
  • Why sufficient / why not (one line): the README lists onchain integrations and operations that are not reducible to the token.
  • Conflict note: —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no formal test of onchain criticality was found in Tier‑1; but the product is by design tied to Solana.
  • Evidence: Tier‑1 — https://github.com/NeurProjects/neur-app
  • Why sufficient / why not (one line): without an explicit test we set 0.
  • Conflict note: —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token (the mint is listed in links_*).
  • Evidence: Tier‑1 — https://solscan.io/token/3N2ETvNpPNAxhcaXgkhKoY1yDnQfs41Wnxsx5qNJpump
  • Why sufficient / why not (one line): onchain artifact of the token in the network explorer.
  • Conflict note: —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): No Tier‑1 description of payments for the service in the NEUR token was found.
  • Evidence: Tier‑1 — https://github.com/NeurProjects/neur-app
  • Why sufficient / why not (one line): the README describes the product and integrations, but does not record token payments.
  • Conflict note: —

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

  • TK_2 (decision): 0
  • Claim (one line): No Tier‑1 description of incentives/collateral/penalties via the token was found.
  • Evidence: Tier‑1 — https://github.com/NeurProjects/neur-app
  • Why sufficient / why not (one line): details of a protocol token economy are absent.
  • Conflict note: —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): No Tier‑1 description of governance via the NEUR token was found.
  • Evidence: Tier‑1 — https://github.com/NeurProjects/neur-app
  • Why sufficient / why not (one line): there is no description of a governance process.
  • Conflict note: —

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://github.com/NeurProjects/neur-app
  • Why sufficient / why not (one line): a specification of the token’s role in the product is needed.
  • Conflict note: —

Evidence (table)

Tier Source What it proves
Tier‑1 https://neur.sh/ The domain neur.sh shows Sedo Domain Parking (a parked page), so the project’s Website/Docs require clarification per Tier‑1.
Tier‑1 https://docs.neur.sh/ The domain docs.neur.sh shows Sedo Domain Parking (a parked page).
Tier‑1 https://github.com/NeurProjects/neur-app Tier‑1 description of the product: LLM agent, tool calling, Solana integrations and roadmap
Tier‑1 https://solscan.io/token/3N2ETvNpPNAxhcaXgkhKoY1yDnQfs41Wnxsx5qNJpump onchain fact: the mint of the NEUR token
Tier‑1 — No Tier‑1 source for claim “the token is needed for payment/access/incentives in the product” was found.
Tier‑2 https://www.coingecko.com/en/coins/neur-sh reference token card (aggregator; not proof of technology)
Tier‑2 https://coinmarketcap.com/currencies/neur-sh/ reference token card (aggregator; not proof of technology)

No comments to display

Back to top