NeuralAI
NeuralAI — 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).
NeuralAI — an AI/Inference | Infra project for generating 3D models (text‑to‑3D / image‑to‑3D): there is a user‑facing web product (dApp) and an open‑source implementation of a Bittensor subnet (miners/validators), where distributed miners generate 3D meshes and validators evaluate quality/speed. Token: NEURAL (ERC‑20 on Ethereum).
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 “on‑demand” 3D asset generator + a distributed network of compute providers (miners/validators) for generation.
- Who it’s for: game/VR developers, 3D artists, content teams.
- Why onchain/token: the token is used for payments/access (token‑gated services) and in the incentive economy; separately, there is an onchain token layer (ERC‑20) and subnet mechanics in Bittensor.
- What you can actually touch (Tier‑1): the public dApp gallery — https://app.goneural.ai/public-gallery; the technical description of the subnet (miners/validators) — https://github.com/GoNeuralAI/neural-subnet
How it works (very briefly)
- The user does: enters text/an image in the dApp to get a 3D model.
- The system does: (per the Tier‑1 repo) validators send requests to miners; miners generate a 3D mesh; validators render/compare and assign scores.
- The user gets: a 3D asset/mesh (and/or access to assets in the ecosystem).
- Where the blockchain is: incentives/weights/accounting of subnet participants are tied to the Bittensor approach (per the docs/README); the
NEURALtoken exists as an ERC‑20 asset on Ethereum. - Token role (if any): (per the Tier‑1 docs)
NEURALis used in marketplace transactions and for token‑gated access to GPU rent / miner templates.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | NeuralAI |
| Also known as (aliases) | GoNeuralAI; Neural Subnet; $NEURAL |
| Logo (logo) | ../assets/132_neuralai_logo.jpg |
| Token symbol (ticker) | NEURAL |
| Category | AI/Inference | Infra |
| Primary chain (chain) | Bittensor |
| Type | non-EVM |
| Network status | — |
| Consensus (consensus) | — |
| Launch date (launch_date) | 2024-03-21 (token launch per the project website) |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0x32b053f2cba79f80ada5078cb6b305da92bde6e1 |
| Token model (token_type) | utility (token-gating + payments + rewards) |
| Max supply | 10,000,000 NEURAL (Total Supply per the project website) |
| Issuance | fixed cap (10M total supply claimed on the website) |
| Tokenomics (tokenomics, brief) | marketplace: transactions in NEURAL + revenue share; token‑gated GPU rent / miner templates |
| Governance | — |
| Admins/keys | — |
| Audit | yes (Hacken audits page) |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | 3D mesh generation from text/images |
| Use‑case (use_case) | 3D assets for games/VR/simulations |
| DecAI Fit — AI thesis fit | 5/6 — high alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 3 / 2 / 2 / 3 |
| Last verified | 2026-02-05 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://goneural.ai/ |
| Docs | https://docs.goneural.ai/neuralai |
| Docs (utilities) | https://docs.goneural.ai/neuralai/utilities-summary |
| GitHub | https://github.com/GoNeuralAI/neural-subnet |
| Releases / Changelog | https://blog.goneural.ai/ |
| Whitepaper | https://goneural.ai/whitepaper |
| Roadmap | — |
| Security advisories | https://github.com/GoNeuralAI/neural-subnet/security/advisories |
| Explorer (ERC‑20) | https://etherscan.io/token/0x32b053f2cba79f80ada5078cb6b305da92bde6e1 |
| App / Demo | https://app.goneural.ai/public-gallery |
| Staking | https://stake.goneural.ai/ |
| X | https://twitter.com/goneuralai |
| Discord | https://discord.gg/neuralai |
| Telegram | https://t.me/NeuralAIGeneral |
| Medium | — |
| Audit report(s) | https://audits.hacken.io/neuralai/ |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/neuralai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/neuralai/ |
General project overview
In the Tier‑1 documentation, NeuralAI is described as a product that “leverages generative AI” for text‑to‑3D and image‑to‑3D, and also as an initiative to build a 3D AI Bittensor subnet: miners generate 3D assets, validators evaluate the results and assign weights/scores. The user side is visible as a dApp (public gallery), and the infrastructure side — as the open‑source code of the subnet.
Features/modules
- 3D dApp: generation of 3D assets from text/images (positioning in the docs).
- Subnet miners/validators: roles, installation and launch are described in the README.
- Marketplace/economy: the docs claim asset tokenization, transactions in
NEURALand fee distribution.
Typical scenarios
- Scenario 1 (user): enters a prompt → receives a 3D asset → exports/uses it in a pipeline.
- Scenario 2 (miner): receives a task from a validator → generates a 3D mesh → sends it to the validator → receives a score/weight.
- Scenario 3 (validator): distributes tasks among miners → compares the prompt and the renders → assigns scores and weights.
Getting started (wallet/network)
- What you need: to view the demo — web access to the public gallery; for onchain operations — an Ethereum wallet and
NEURAL(if participating in ERC‑20 operations). - Network/chain: token — Ethereum; the subnet part is described as a Bittensor subnet (non‑EVM).
- Fees: Ethereum gas for ERC‑20 actions.
Architecture/tech (non‑AI)
- Components: an open‑source subnet (Python); a generation environment (PyTorch/CUDA); the dApp.
- Participant roles: miners (compute), validators (quality/scoring), users.
- Where logic runs: generation — offchain; validation — offchain; incentives/weights — at the level of the Bittensor subnet mechanics (as an architectural goal/design).
Token/economics (expanded, no forecasts)
- Token utility: the Tier‑1 docs claim that marketplace transactions are conducted in
NEURALand that services such as GPU rent/miner templates will be token‑gated. - Where fees go: the Tier‑1 docs describe a 5% fee and its distribution: 2.5% to holders / 2.5% to project growth.
- Issuance/burn: a total supply of 10M is listed on the website; there are no other parameters in the available Tier‑1 sources →
—.
Governance
- Who makes decisions: —.
Security and incidents
- Audits: the public Hacken audits page lists NeuralAI as an audited project on Ethereum.
- Incidents: —.
Project status and timeline
- Current status: the dApp (gallery) is available; the repo is published.
- Key milestones: token launch 2024‑03‑21 (per the website); subnet versioning (v1/v2) is described in the README.
Ecosystem/integrations
- Integrations: Bittensor (subnet), Ethereum (ERC‑20), the dApp.
AI component of the project
- What is real AI here? generative model(s) create 3D meshes from text/visual inputs; validators evaluate quality using the “prompt → renders → similarity/scoring” scheme (described in the Tier‑1 repo).
- What is truly onchain? the ERC‑20 token
NEURALon Ethereum and the claimed subnet economy based on Bittensor. - Why is a token needed? token‑gating of services (GPU rent/miner templates) and settlements/fees in the marketplace with revenue share (Tier‑1 docs).
- Red flags (based on the information found): the onchain details of the Bittensor layer are not specified in the project’s docs (consensus/exact onchain primitives) → the assessment of onchain necessity is conservative.
DecAI Fit component summary
- DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | high | 3 |
| Onchain necessity | medium | 2 |
| Token necessity | medium | 2 |
| Evidence | Tier‑1 present | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): the AI part is described and demonstrated as a working product and subnet, not only as an intent.
- Evidence: Tier‑1 — https://docs.goneural.ai/neuralai; https://github.com/GoNeuralAI/neural-subnet
- Why sufficient / why not (one line): the existence of a product/repository takes the project above the level of “AI intent”.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): text‑to‑3D and image‑to‑3D generation of 3D models.
- Evidence: Tier‑1 — https://docs.goneural.ai/neuralai
- Why sufficient / why not (one line): the Tier‑1 documentation directly describes text‑to‑3D / image‑to‑3D.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): the public gallery demonstrates examples of generated assets.
- Evidence: Tier‑1 — https://app.goneural.ai/public-gallery
- Why sufficient / why not (one line): an accessible public product artifact confirms the existence of demos/examples.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there are no reproducible generation quality metrics in Tier‑1 sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): the miner/validator roles and the generation/validation process in the subnet are described, plus deployment instructions.
- Evidence: Tier‑1 — https://github.com/GoNeuralAI/neural-subnet (Miner and Validator Functionality; Installation)
- Why sufficient / why not (one line): the README gives enough architecture/operations details to consider the technical description confirmed.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum (ERC‑20 token) + Bittensor (subnet, per the positioning/README).
- Addresses/identifiers:
NEURALERC‑20:0x32b053f2cba79f80ada5078cb6b305da92bde6e1. - Evidence: Tier‑1 — https://goneural.ai/; https://etherscan.io/token/0x32b053f2cba79f80ada5078cb6b305da92bde6e1
- Why sufficient / why not (one line): the website and the explorer provide a verifiable onchain identifier of the token.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: the subnet incentive economy (weights/scores) as part of the Bittensor approach (miners/validators).
- Evidence: Tier‑1 — https://docs.goneural.ai/neuralai (Bittensor Subnet); https://github.com/GoNeuralAI/neural-subnet
- Why sufficient / why not (one line): Tier‑1 sources describe the miners/validators subnet structure and scoring, which goes beyond “just a token”.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: the miners/validators incentives and weight accounting could theoretically be implemented without a blockchain (centrally) — Tier‑1 proof of the irreplaceability of the onchain layer is not provided.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there are no Tier‑1 statements/proofs that without onchain the layer breaks down functionally.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token,
NEURAL(ERC‑20 on Ethereum). - Evidence: Tier‑1 — https://goneural.ai/; https://etherscan.io/token/0x32b053f2cba79f80ada5078cb6b305da92bde6e1
- Why sufficient / why not (one line): there is a public website with the token parameters and an onchain token page.
- 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): marketplace transactions are conducted in
NEURAL. - Evidence: Tier‑1 — https://docs.goneural.ai/neuralai/utilities-summary
- Why sufficient / why not (one line): the Tier‑1 docs explicitly state “All transactions are conducted using $NEURAL”.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): the marketplace fee is distributed between
NEURALholders and “project growth”; access to GPU rent/miner templates is token‑gated. - Evidence: Tier‑1 — https://docs.goneural.ai/neuralai/utilities-summary
- Why sufficient / why not (one line): the Tier‑1 docs describe revenue share (2.5% holder rewards) and token‑gating as incentives/an access mechanism.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): the governance role of the token is not confirmed in the Tier‑1 sources available without restrictions.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there are no clear Tier‑1 mentions of onchain governance via
NEURAL. - Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): per the Tier‑1 docs,
NEURALis the mandatory currency of marketplace transactions and the key to token‑gated services. - Evidence: Tier‑1 — https://docs.goneural.ai/neuralai/utilities-summary
- Why sufficient / why not (one line): if all transactions and access are tied to
NEURAL, the replaceability of the token does not follow from Tier‑1 sources. - Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://docs.goneural.ai/neuralai | Description of NeuralAI as generative AI text‑to‑3D / image‑to‑3D and as a Bittensor subnet for 3D modeling (miners/validators). |
| Tier‑1 | https://github.com/GoNeuralAI/neural-subnet | Tier‑1 technical artifact: miner/validator roles, description of the generation/validation pipeline, deployment instructions. |
| Tier‑1 | https://app.goneural.ai/public-gallery | Demo artifact: a public gallery of assets (example/demonstration of the result). |
| Tier‑1 | https://goneural.ai/ | Token parameters on the website (launch date, total supply) and the contract for purchase on ETH (link to the address). |
| Tier‑1 | https://etherscan.io/token/0x32b053f2cba79f80ada5078cb6b305da92bde6e1 | Onchain fact: the ERC‑20 token NEURAL and the contract address. |
| Tier‑1 | https://docs.goneural.ai/neuralai/utilities-summary | Tier‑1 token utility: marketplace transactions in NEURAL, token‑gated GPU rent/miner templates, revenue share (holder rewards). |
| Tier‑1 | https://audits.hacken.io/neuralai/ | Public mention of the audit/platform (Ethereum) on the Hacken audits page. |
No comments to display
No comments to display