Skip to main content

Nosana

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

Nosana — an AI/Compute | Marketplace decentralized marketplace of GPU resources for AI inference/workloads on Solana: clients pay for deployments with the NOS token, hosts run workloads via node software; token (symbol: NOS) on Solana (SPL).

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 “compute marketplace”: you run AI tasks on other people’s GPUs, and GPU owners rent out their capacity and get paid.
  • Who it’s for: developers/teams that need cheap GPU inference, and GPU owners who want to monetize idle hardware.
  • Why onchain/token: onchain is needed for settlement and the marketplace rules (smart contracts + transparency); the NOS token is needed as the payment currency for deployments and (via staking) as incentives/ranking.

How it works (very briefly)

  1. The user does: tops up a wallet with SOL + NOS, describes/launches a deployment (batch or online workload).
  2. The system does: matching of supply and demand in the network, orchestration of the workload launch on host nodes and accounting of the payment.
  3. The user gets: a running AI inference/service endpoint or a completed batch job.
  4. Where the blockchain is: payment for deployments with the NOS token, protocol operations and accounting — onchain on Solana; staking is implemented as a separate Solana program.
  5. Token role (if any): NOS — payment for deployments; staking NOS gives xNOS (a rank for votes/activities) and can be slashed per the logic of the staking program.

Quick links: AI thesis fit

Project passport

Field Value
Project name Nosana
Also known as (aliases) Nosana Network; Nosana Protocol; $NOS
Logo (logo) ../assets/128_nosana_logo.svg
Token symbol (ticker) NOS
Category AI/Compute | Marketplace
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) Solana PoS (PoH-based)
Launch date (launch_date) 2021 (founding; per the docs)
Project status (status) active
Token (standard) SPL
Token contract nosXBVoaCTtYdLvKY6Csb4AC8JCdQKKAaWYtx2ZMoo7
Token model (token_type) utility (payments + staking)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) NOS is needed to pay for deployments; the staking program gives xNOS (rank) and supports slashing
Governance —
Admins/keys —
Audit yes (staking: link to the audit report in the staking UI)
Bug bounty —
Team (team) —
Funding (investors/funding) Solana Foundation grant (per the docs background)
AI component (ai_component) running AI inference workloads on GPU
Use‑case (use_case) decentralized GPU marketplace (inference)
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 2 / 1 / 3
Last verified 2026-02-05

General project overview

Nosana is a network and a set of protocols/tools that connect GPU owners (hosts) and clients who need compute resources, primarily for AI inference. Per the Tier‑1 documentation, the project builds a “decentralised compute network” based on Solana and provides: a resource marketplace, node software for hosts and an API/SDK/CLI for clients who launch deployments (batch and online workloads).

Economically, deployments are paid for with NOS, while Solana network transaction fees are paid in SOL (this is stated explicitly in the docs). Separately, there is a NOS staking program as a Solana program with a clear set of instructions (stake/unstake/slash, etc.) and the xNOS indicator.

Features/modules

  • GPU marketplace for inference: access to distributed GPUs and dynamic pricing (per the website).
  • Deployments (batch/online workloads): on‑demand or scheduled (per the docs).
  • Host nodes: an open‑source reference implementation and tools for participation (per the docs).
  • CLI/SDK/API: tools for launching workloads (per the docs).
  • NOS staking: a staking dashboard + an onchain staking program with xNOS.

Typical scenarios

  • Scenario 1 (client): a team launches an inference workload → pays NOS → gets a running deployment/endpoint or batch‑job results.
  • Scenario 2 (host): a GPU owner connects a node → gets paid for completed workloads.
  • Scenario 3 (staker): a NOS holder stakes tokens → receives rewards/participates in activities; the stake can be slashed per the program logic.

Getting started (wallet/network)

  • What you need: a Solana wallet with SOL (fees) and NOS (payment for deployments).
  • Network/chain: Solana (mainnet).
  • Fees: Solana gas (SOL) + payment for deployments in NOS.

Architecture/tech (non‑AI)

  • Components: the onchain protocol on Solana (marketplace/accounting), the offchain network of hosts/nodes, client tools (CLI/SDK/API), the onchain staking program.
  • Participant roles: clients (launch deployments), hosts (provide GPUs), stakers/participants in the governance of activities.
  • Where logic runs: execution of workloads — offchain on hosts; payment/accounting/part of the rules — onchain (Solana).
  • Dependencies: Solana, the nosana-ci/* repositories.

Token/economics (expanded, no forecasts)

  • Token utility: NOS is used to pay for deployments; SOL is used for onchain transactions.
  • Incentive mechanisms: the staking program allows staking NOS for a term (variable duration) and yields xNOS (NOS × duration); the program has a Slash operation (punishment of bad actors).
  • Who pays fees: users pay SOL for network fees and NOS for deployments.
  • Issuance/distribution: not extracted from Tier‑1 sources within this check (the passport shows —).

Governance

  • Who makes decisions: — (there is no Tier‑1 description of a full DAO procedure in this card).

Security and incidents

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? The project is focused on running AI inference: the network provides GPUs and allows running AI workloads/services (per the website and docs).
  • What is truly onchain? Payment for deployments and protocol operations on Solana; a separate Solana program for NOS staking with stake/unstake/slash instructions.
  • Why is a token needed? NOS is needed to pay for deployments; staking NOS creates an xNOS rank and allows slashing.
  • Red flags (based on the information found): AI‑washing risk (Nosana is a compute marketplace, not a “proprietary AI model”); token‑washing risk (payment could theoretically be in a stablecoin, although Tier‑1 records NOS as required for deployments).

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): there is a Tier‑1 description that the network serves AI inference workloads (see AI_1/AI_4).
  • Evidence: Tier‑1 — https://docs.nosana.io/about/intro.html
  • Why sufficient / why not (one line): AI_0 applies only when AI_1..AI_4 = 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the platform allows running AI inference workloads and AI services on distributed GPUs.
  • Evidence: Tier‑1 — https://nosana.io; https://docs.nosana.io/about/intro.html
  • Why sufficient / why not (one line): Tier‑1 sources explicitly describe the target workload (AI inference).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no demo accessible without restrictions that shows the deployment of an AI deployment was found/extracted (some endpoints are unavailable via fetch).
  • Evidence: Tier‑1 — https://learn.nosana.com
  • Why sufficient / why not (one line): there is training/a guide, but without something to “touch”, we set 0 in this card.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.nosana.io/about/intro.html
  • Why sufficient / why not (one line): there are no Tier‑1 quality metrics for inference/SLAs/accuracy.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): the docs describe the architecture of the compute marketplace network (onchain protocol + node software + API/SDK) and support for batch/online workloads.
  • Evidence: Tier‑1 — https://docs.nosana.io/about/intro.html
  • Why sufficient / why not (one line): there is a technical description of the platform on which AI workloads are run.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: mint NOS: nosXBVoaCTtYdLvKY6Csb4AC8JCdQKKAaWYtx2ZMoo7; staking program: nosScmHY2uR24Zh751PmGj9ww9QRNHewh9H59AfrTJE
  • Evidence: Tier‑1 — https://docs.nosana.com/wallet/token.html; https://docs.nosana.io/protocols/staking.html
  • Why sufficient / why not (one line): Tier‑1 publishes the token address and the address of the Solana staking program.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: payment for deployments and the protocol rules of the marketplace on Solana; staking as a separate Solana program with instructions and slashing.
  • Evidence: Tier‑1 — https://docs.nosana.com/wallet/token.html; https://docs.nosana.io/protocols/staking.html
  • Why sufficient / why not (one line): the onchain mechanics include payment and the staking program, not only token issuance.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: a compute marketplace can be imagined as a centralized billing/matching service; Tier‑1 does not prove that a key property breaks down without a blockchain.
  • Evidence: Tier‑1 — https://docs.nosana.io/about/intro.html
  • Why sufficient / why not (one line): onchain is important for decentralization, but “criticality” per the replacement test is not proven → OC_3 = 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, NOS, on the Solana network (SPL).
  • Evidence: Tier‑1 — https://docs.nosana.com/wallet/token.html
  • Why sufficient / why not (one line): the Tier‑1 documentation describes NOS and its role in the protocol → TK_0 = 0.
  • 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): deployments on Nosana are paid for with the NOS token (while SOL is for onchain fees).
  • Evidence: Tier‑1 — https://docs.nosana.com/wallet/token.html
  • Why sufficient / why not (one line): Tier‑1 explicitly records the payment role of NOS.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the staking program allows staking NOS; the stake can be slashed (punishment of bad actors) and forms xNOS.
  • Evidence: Tier‑1 — https://docs.nosana.io/protocols/staking.html
  • Why sufficient / why not (one line): Tier‑1 describes staking and the existence of a Slash instruction.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): within the Tier‑1 sources of this card, no formalized governance mechanism via NOS was found.
  • Evidence: Tier‑1 — https://docs.nosana.io/about/intro.html
  • Why sufficient / why not (one line): there is no explicit governance description → TK_3 = 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): the role of NOS as the payment token for deployments could theoretically be replaced with a stablecoin/fiat; the necessity of specifically NOS as an irreplaceable asset is not proven.
  • Evidence: Tier‑1 — https://docs.nosana.com/wallet/token.html
  • Why sufficient / why not (one line): Tier‑1 records “NOS used to pay for deployments”, but does not prove non‑substitutable properties → TK_4 = 1.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.nosana.io/about/intro.html Tier‑1 description of Nosana as a compute network on Solana and the focus on AI workloads/inference.
Tier‑1 https://docs.nosana.com/wallet/token.html Tier‑1: deployments are paid for with NOS, Solana fees — with SOL; the NOS token address is listed.
Tier‑1 https://docs.nosana.io/protocols/staking.html Tier‑1: staking program, xNOS, the Solana program address, the existence of slashing (Slash).
Tier‑1 https://app.nosana.io/stake/ Staking UI + link to the audit report of the staking program.
Tier‑1 https://nosana.io Product positioning: a GPU marketplace for AI inference.
Tier‑1 https://github.com/nosana-ci Public repositories (CLI/SDK/dashboard/protocols).

No comments to display

Back to top