Skip to main content

Supra

Supra (SUPRA) — 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).

Supra — an AI/Agents vertically integrated ecosystem around its own L1 (native oracles, automation, bridge, MultiVM) and the SUPRA token.

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 Layer‑1 network with “vertical integration” of services (oracles/randomness/automation/bridge) and an SDK/VM stack for developers.
  • Who it’s for: dApp developers and users of the Supra L1 ecosystem and its native services.
  • Why onchain/token: SUPRA is the gas token, the staking/security token of the network and the economic backing of the native services; it is also described as a data‑access token for the oracles (per the Tier‑1 tokenomics article).

How it works (very briefly)

  1. The developer writes smart contracts (MoveVM or EVM) and deploys a dApp on Supra L1.
  2. The dApp uses the native services: data oracles, dVRF, automation, bridge (per the docs).
  3. The user interacts with the dApp on the Supra network, paying gas and participating in staking/services as needed.
  4. Where the blockchain is: contract execution, settlement, security and data/events — onchain on Supra L1.
  5. Token role: gas fees, staking and security of the network/validators, economic guarantee of the native services, access to data/services (per the Tier‑1 tokenomics).

Quick links: AI thesis fit

Project passport

Field Value
Project name Supra
Also known as (aliases) Supra Labs; Supra L1; Supra Oracles
Logo (logo) ../assets/107_supra_logo.webp
Token symbol (ticker) SUPRA
Category AI/Agents
Primary chain (chain) Supra Layer 1
Type L1
Network status mainnet
Consensus (consensus) PoS + Moonshot BFT
Launch date (launch_date) —
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (gas + staking + governance)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) distribution by category (Foundation/Treasury 22.6%, Validators&Stakers 21.0%, Early contributors 20.7%, Team 16.0%, Ecosystem&Community 11.0%, Airdrop 4.0%, etc.) + gas/staking/services utility (per the tokenomics)
Governance governance is mentioned as a possible utility of the token (per the tokenomics)
Admins/keys —
Audit yes
Bug bounty yes
Team (team) Entropy Foundation / Supra (per the website; legal block in the tokenomics article)
Funding (investors/funding) —
AI component (ai_component) AI agents + threshold AI oracles
Use‑case (use_case) L1 for dApps with native services
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 3 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

Supra is positioned as an L1 “full‑stack” ecosystem for dApps: in addition to smart contract execution, the network has built‑in native services (data oracles, dVRF, automation, bridge), as well as support for several VMs (MoveVM and EVM) and an SDK/documentation for developers.

As a separate product line, Supra publishes materials on “AI Agents” and “Threshold AI Oracles”: the idea is to give dApps access to AI insights onchain (with cryptographic verification) and to integrate AI agents with onchain execution (via automation and L1 execution).

Features/modules

  • Supra L1 + MultiVM: development for MoveVM and EVM (per the docs).
  • Moonshot consensus: a family of BFT protocols focused on latency/throughput (per the docs).
  • Native Oracles: data feeds and dVRF (per the docs overview).
  • Native Automation: “0‑block delay” automation (per the docs overview).
  • SupraNova bridge: bridge/interoperability (per the docs overview).
  • AI Agents: materials/tools for onchain agents and AI‑Finance (per the website).
  • Threshold AI Oracles: a protocol for “AI insights onchain” (per the article and the whitepaper link in the article).

Typical scenarios

  • Scenario 1 (dApp on L1): a developer deploys a dApp → uses native oracles/automation → users make transactions and pay gas in SUPRA.
  • Scenario 2 (oracle/VRF): a dApp receives prices/data via the built‑in data feeds or randomness via dVRF → builds DeFi/GameFi.
  • Scenario 3 (AI‑enabled): a dApp/agent requests an AI insight via Threshold AI Oracles → receives a response with cryptographic guarantees → the smart contract executes the logic/automation.

Getting started (wallet/network)

  • What you need: a wallet/account in the Supra ecosystem, the SUPRA token for gas (and, if needed, for staking).
  • Network/chain: Supra L1 mainnet (explorer: SupraScan).
  • Fees: gas fees in SUPRA for transactions; service fees/parameters — depend on the specific product/module.

Architecture/tech (non‑AI)

  • Components: the L1 network + validators/nodes, the VM layer (Move/EVM), native services (oracles/dVRF/automation/bridge), documentation/SDK, the SupraScan explorer.
  • Participant roles: users, dApp developers, validators/stakers, service providers (within the protocol), bridge relayers (for the SupraNova modules).
  • Where logic runs: the core logic and state — onchain; some services may include offchain compute/committees (for example, in the AI oracle description), but the result is anchored onchain.
  • Dependencies: its own network, explorer, documentation; for SupraNova — interaction with external chains.

Token/economics (expanded, no forecasts)

  • Token utility: gas fees on the L1; staking and security; economic guarantee of the native services (oracle/VRF/bridge/automation); data access token (per the tokenomics article).
  • Protocol necessity drivers: as the L1 gas/staking token, it is necessary for executing transactions and for network security.
  • Who pays fees: users and dApps pay gas; validators/operators — stake to participate (the article mentions the required stake for a node).
  • Where fees go: network fees and rewards — to security participants (validators/stakers) and ecosystem mechanisms (in general terms).
  • Issuance/burn: —.
  • Incentive mechanisms: staking, rewards, node stake requirements (per the tokenomics article).
  • Distribution/vesting: the Tier‑1 article describes the distribution percentages and the key lock/unlock principles (0 team tokens at TGE; lock periods).
  • Treasury: the distribution includes a Foundation and Treasury share (22.6%).

Governance

  • Who makes decisions: governance as a utility of SUPRA is mentioned (wording “may also facilitate”) — the details of the mechanics are not confirmed by Tier‑1.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: the SupraNova docs publish audit reports (Move and Solidity) by RektProof (PDF).
  • Bug bounty: yes (links_*).
  • Incidents: no Tier‑1 postmortems were found.
  • Threat model: L1 risks (consensus/validators), bridge risks (SupraNova), risks of the oracle/automation modules, risks of the AI‑oracle pipeline (if/when enabled).

Project status and timeline

  • Current status: Supra L1 mainnet (per SupraScan) + active docs/products.
  • Key milestones: tokenomics article dated 2024‑12‑04; Threshold AI Oracles article dated 2025‑05‑22.
  • Roadmap: there is a future roadmap page for the SupraNova bridge (links_*).

Ecosystem/integrations

  • Integrations: SupraNova bridge; native services; dev tools/SDK (docs).
  • Partners: there are “partnerships” and “ecosystem” pages, but specific agreements are not verified by Tier‑1.
  • Where it’s actually used: dApps on Supra L1 and the native services (per the website/docs).

AI component of the project

  • What is real AI here? “Threshold AI Oracles” are described as a protocol that delivers AI insights onchain; “AI Agents” — a framework/tools for agent scenarios using sensing/thinking/acting, where “thinking” is tied to the AI oracle.
  • What is truly onchain? Supra L1 execution and state; AI‑oracle requests and results are anchored onchain; automation executes calls onchain.
  • Why is a token needed? SUPRA — gas, staking/security, economic guarantee of the services and access to data/services.
  • Red flags (based on the information found): AI‑washing — medium (many materials, but no Tier‑1 metrics/demo of an “AI oracle in production” in this card); onchain‑washing — low (it is an L1); token‑washing — low (clear L1 utility). Double‑check: the status/ready‑state of Threshold AI Oracles (mainnet?), the exact supply/emission parameters, a formal governance model.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 1
Onchain necessity high 3
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): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 1.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Threshold AI Oracles deliver ML/AI “insights” onchain: committees, BLS threshold signatures, just‑in‑time requests from smart contracts, structured responses/commands (per the article).
  • Evidence: Tier‑1 — https://supra.com/academy/threshold-ai-oracles-brings-intelligence-on-chain/
  • Why sufficient / why not (one line): it is described what exactly the AI function is and how it integrates with onchain execution.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): the card has no Tier‑1 demo confirming “AI oracle/AI agents” as a working production module with verifiable examples.
  • Evidence: Tier‑1 — https://supra.com/ai-agents/
  • Why sufficient / why not (one line): the page has descriptions and a “Start building” link, but no verifiable examples of AI output.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://supra.com/academy/threshold-ai-oracles-brings-intelligence-on-chain/
  • Why sufficient / why not (one line): quality metrics for AI responses/errors are not provided.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a high‑level architecture is described (committees, signatures, phases), but there is no exact specification of the models/versions/inference pipeline in the text of the page.
  • Evidence: Tier‑1 — https://supra.com/academy/threshold-ai-oracles-brings-intelligence-on-chain/
  • Why sufficient / why not (one line): insufficient for a full technical verification of the AI component.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Supra Layer 1 (mainnet)
  • Addresses/identifiers: network/explorer SupraScan (native token SUPRA)
  • Evidence: Tier‑1 — https://suprascan.io/, https://docs.supra.com/
  • Why sufficient / why not (one line): the L1 network and the explorer are confirmed.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: smart contract execution (Move/EVM), native oracles/automation/bridge as onchain services/protocols (described in the docs).
  • Evidence: Tier‑1 — https://docs.supra.com/, https://docs.supra.com/automation/
  • Why sufficient / why not (one line): the functionality of the network is clearly broader than “just a token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without the L1, trustless execution, consensus and the native protocols (oracles/automation/bridge) as onchain infrastructure disappear.
  • Evidence: Tier‑1 — https://docs.supra.com/
  • Why sufficient / why not (one line): it is an L1; “replacing the blockchain” changes the nature of the system.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the network has a token, SUPRA.
  • Evidence: Tier‑1 — https://supra.com/academy/supra-token-tokenomics-and-utility/
  • Why sufficient / why not (one line): the Tier‑1 article describes the token, its distribution and utility.
  • 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): SUPRA is used as the gas token and the data access token (including for the native oracles/services).
  • Evidence: Tier‑1 — https://supra.com/academy/supra-token-tokenomics-and-utility/
  • Why sufficient / why not (one line): the utility is listed explicitly.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): SUPRA is used for staking and for securing the network (including a stated stake requirement to run a node).
  • Evidence: Tier‑1 — https://supra.com/academy/supra-token-tokenomics-and-utility/
  • Why sufficient / why not (one line): the existence of staking and its role in security is described in Tier‑1.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance is mentioned as a possible utility (“may also facilitate”) without specific mechanics.
  • Evidence: Tier‑1 — https://supra.com/academy/supra-token-tokenomics-and-utility/
  • Why sufficient / why not (one line): the wording does not confirm an operating governance mechanism.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): as the gas/staking token of the L1, SUPRA is functionally irreplaceable within the network (by design).
  • Evidence: Tier‑1 — https://supra.com/academy/supra-token-tokenomics-and-utility/
  • Why sufficient / why not (one line): the L1 “gas + security” utility usually requires a native token; in Tier‑1 it is described as the primary gas token.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.supra.com/ description of Supra as a full‑stack L1 (native oracles/automation/bridge, MoveVM/EVM)
Tier‑1 https://docs.supra.com/moonshot Moonshot consensus (BFT family)
Tier‑1 https://suprascan.io/ Supra mainnet explorer (the fact that the mainnet/network exists)
Tier‑1 https://supra.com/academy/supra-token-tokenomics-and-utility/ utility of the SUPRA token + distribution and lock/unlock principles
Tier‑1 https://supra.com/ai-agents/ AI Agents positioning and the “sense/think/act” stack + mention of AI‑enabled AutoFi
Tier‑1 https://supra.com/academy/threshold-ai-oracles-brings-intelligence-on-chain/ Threshold AI Oracles: “AI insights onchain”, committees, signatures, phases
Tier‑1 https://docs.supra.com/supranova/audit-reports the existence of audit reports (RektProof) for the SupraNova/HyperNova contracts
Tier‑1 https://supra.com/bug-bounty/ the existence of a bug bounty program

No comments to display

Back to top