Skip to main content

OctaSpace

OctaSpace (OCTA / wOCTA) — 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).

OctaSpace — an AI/Compute / Infra decentralized cloud computing platform: a marketplace for renting CPU/GPU/traffic, ready‑made “one‑click” applications (including for AI/ML), a render farm and a VPN. The economy is tied to the native coin OCTA and its wrapper wOCTA.

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 marketplace for renting computing resources (including GPUs) + ready‑made applications (AI training/image/video gen, etc.), rendering and a VPN.
  • Who it’s for: developers/teams that need compute/GPUs; hosts (hardware owners) who rent out resources.
  • Why onchain/token: OCTA is used to pay for services and to reward nodes; the network describes its own L1/L2 blockchain architecture for settlements and billing.

How it works (very briefly)

  1. The user does: chooses a ready‑made application/instance type, selects a node (CPU/GPU) and deploys a workload.
  2. The system does: orchestrates the launch of containers/VMs on the selected node, meters usage and billing.
  3. The user gets: access to compute (SSH/WebSSH), can train/run models, render, etc.
  4. Where the blockchain is: the whitepaper describes an L1 (PoW) for financial operations and an L2 (PoA) for fast billing transactions, plus a staking mechanism.
  5. Token role (if any): OCTA — payment for services, rewards to nodes/miners/stakers; wOCTA — an ERC‑20 wrapper on Ethereum.

Quick links: AI thesis fit

Project passport

Field Value
Project name OctaSpace
Also known as (aliases) OCTA Chain; OctaRender; OctaVPN; wOCTA
Logo (logo) ../assets/156_octaspace_logo.svg
Token symbol (ticker) OCTA
Category AI/Compute | Infra
Primary chain (chain) OCTA Chain
Type Appchain
Network status mainnet
Consensus (consensus) PoW (OCTA Chain)
Launch date (launch_date) 2022-06-19 (start of the Octa epoch — per the whitepaper timeline)
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (payments + staking + incentives)
Max supply Total supply L1: 48,000,000 OCTA (whitepaper).
Issuance fixed (finite monetary policy; PoW reward schedule by epochs — whitepaper).
Tokenomics (tokenomics, brief) OCTA is the payment instrument for services + rewards to nodes/miners/stakers; the staking collateral (100,000 OCTA) is described in the whitepaper.
Governance — (a governance model is not described in the whitepaper)
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) — (the whitepaper claims no premine/presale)
AI component (ai_component) GPU marketplace for AI/ML workloads
Use‑case (use_case) GPU rental for model training/inference
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 2 / 2 / 3
Last verified 2026-02-11

General project overview

OctaSpace is a decentralized “cloud compute” platform that connects hardware owners (nodes) and users who need resources (CPU/GPU/traffic/storage). In the whitepaper, the project describes itself as a distributed system with a marketplace of services (GPU rental, VPN, rendering, etc.) and its own blockchain architecture (L1 + L2) for financial operations and billing.

In the DecAI context, the key scenario is the GPU marketplace for AI/ML tasks: renting GPU instances for training/running models and the ability to combine instances into a cluster for distributed computing.

Features/modules

  • GPU marketplace: renting/renting out GPUs, SSH access, optionally Jupyter/LiveBook (whitepaper).
  • Containers and VMs: management of Docker containers and microVMs (Firecracker) on nodes (whitepaper).
  • OctaRender: distributed rendering.
  • OctaVPN: a pay‑as‑you‑go VPN (WireGuard/ShadowSocks/OpenVPN — whitepaper).
  • HashCache: a distributed password recovery/compute service (whitepaper).
  • Own blockchain scheme: L1 (PoW) + L2 (PoA) and gateways for a unified API (whitepaper).

Typical scenarios

  • Scenario 1 (AI/ML): a user rents a GPU instance → connects via SSH/notebooks → trains/runs a model → pays for usage.
  • Scenario 2 (host): installs the node software → passes verification → rents out CPU/GPU/traffic → receives payouts/rewards in OCTA.
  • Scenario 3 (VPN): a user chooses a VPN node/protocol → uses pay‑as‑you‑go → pays for traffic.

Getting started (wallet/network)

  • What you need: an account/access to the marketplace; for payments/staking — an OCTA wallet.
  • Network/chain: OctaSpace L1 (OCTA Chain); wOCTA exists on Ethereum as a wrapper.
  • Note on networks (passport normalization): the passport lists OCTA Chain (L1) as the primary chain. The project also has a wOCTA wrapper on Ethereum and a separate L2 layer for billing (per the whitepaper).
  • Fees: network fees (L1 PoW, L2 PoA for billing) + payment for the use of services in OCTA.

Architecture/tech (non‑AI)

  • Components (whitepaper): L1 PoW blockchain + L2 PoA sidechain, blockchain gateways, the “OCTA CORE” layer, the ORC node software, the resource layer (hardware), API/UI.
  • Participant roles: end‑users (renters), node owners/hosters, L2 miners/validators, stakers.
  • Where logic runs: financial operations — L1; high‑frequency billing/internal transactions — L2; execution of workloads — on nodes (offchain compute); orchestration — OCTA CORE.
  • Dependencies: Docker/Firecracker, node infrastructure and marketplace clients; (per the roadmap) integrations with Hugging Face and others.

Token/economics (expanded, no forecasts)

  • Token utility (whitepaper): OCTA is the “primary payment instrument” for services, rewards for node owners and “dividend payments” for holders; staking gives additional rewards.
  • Supply (whitepaper): total supply 48,000,000 OCTA; monetary policy by epochs/block rewards.
  • Mining/issuance: PoW blocks (block time 15s), reward schedule and halving by epochs (whitepaper).
  • Staking (whitepaper): collateral 100,000 OCTA; node reliability and verification requirements; a weekly reward distribution scheme is described.
  • Fees/billing: L2 PoA is used to speed up “billing operations”.

Governance

  • Governance: not described in the Tier‑1 sources used.

Security and incidents

  • Node security (whitepaper): measures are claimed: open‑source ORC for auditing, running under an unprivileged user, regular updates; node verification.
  • Audits/bug bounty: not confirmed by Tier‑1 in this card.
  • Risks: compromise of nodes/containers, supply‑chain risks (images), billing/accounting risks, quality/availability risks of a marketplace node.

Project status and timeline

  • Current status: an active product (website + docs + whitepaper).
  • Roadmap: a 2026 roadmap has been published (updated 2026‑01‑07).

Ecosystem/integrations

  • Integrations: the roadmap claims a Hugging Face integration and “clusters” for ML tasks; ready‑made applications and launching containers from DockerHub/HuggingFace are also described (website).
  • Where it’s actually used: the roadmap provides aggregated usage metrics (sessions, frames) and directions (render/vpn/ai tools).

AI component of the project

  • What is real AI here? This is compute infrastructure for AI/ML (GPU marketplace, “AI training tools”, ready‑made applications for running models); own models are not described.
  • What is truly onchain? The own L1/L2 architecture and onchain accounting/billing/staking, plus the onchain wOCTA wrapper on Ethereum.
  • Why is a token needed? OCTA — payment for services and incentives for nodes/miners/stakers.
  • Red flags (based on the information found): AI‑washing — do not confuse “compute for AI” with an “AI protocol of models”; onchain‑washing — it is important to separate onchain accounting from the offchain execution of workloads; token‑washing — check which services actually require OCTA as payment.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
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): — (there is AI_1: the AI/ML use case and tools are described in Tier‑1).
  • Evidence: Tier‑1 — https://whitepaper.octa.space/octaspace-whitepaper.pdf ; https://octa.space
  • Why sufficient / why not (one line): AI_0 applies only if 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 provides GPU compute for AI/ML tasks (training/inference) and “AI tools/ready‑to‑launch apps”.
  • Evidence: Tier‑1 — https://whitepaper.octa.space/octaspace-whitepaper.pdf ; https://octa.space
  • Why sufficient / why not (one line): The whitepaper and the website directly name AI/ML as the focus of using the GPU marketplace.
  • Conflict note (if any): This is infrastructure, not own models (AI_4=0).

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): The reviewed Tier‑1 sources contain no specific reproducible “model → result” demo case on OctaSpace.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is a description of the marketplace and applications, but without specific AI examples of outputs.
  • 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): Product metrics (sessions/frames) are provided, but there are no quality metrics of AI/ML models.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A technical description of AI models is not applicable/not disclosed (the project is compute infrastructure, not a model provider).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The whitepaper describes the architecture of the compute platform, but not the architectures of models.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: OctaSpace L1 (native OCTA) + Ethereum (wOCTA ERC‑20)
  • Addresses/identifiers: wOCTA ERC‑20: 0xfA704148D516b209D52C2D75f239274C8f8EAF1A
  • Evidence: Tier‑1 — https://etherscan.io/token/0xfA704148D516b209D52C2D75f239274C8f8EAF1A ; https://whitepaper.octa.space/octaspace-whitepaper.pdf
  • Why sufficient / why not (one line): The explorer confirms the ERC‑20 address; the whitepaper confirms the existence of the own blockchain and the OCTA coin.
  • Conflict note (if any): wOCTA is a wrapper and does not necessarily reflect the L1 supply.

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the own L1/L2 blockchain architecture for financial operations and billing; the staking mechanism and reward distribution.
  • Evidence: Tier‑1 — https://whitepaper.octa.space/octaspace-whitepaper.pdf
  • Why sufficient / why not (one line): The whitepaper describes the L1 PoW and L2 PoA, gateways and the staking/reward rules.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: a compute marketplace can be implemented in a centralized way; Tier‑1 has no strict argumentation that “without onchain the rationale breaks down”.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): OC_3 requires an explicit “replace the blockchain” test, which is absent.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a native coin, OCTA, and an ERC‑20 wrapper, wOCTA.
  • Evidence: Tier‑1 — https://whitepaper.octa.space/octaspace-whitepaper.pdf ; https://etherscan.io/token/0xfA704148D516b209D52C2D75f239274C8f8EAF1A
  • Why sufficient / why not (one line): The whitepaper describes the monetary policy of OCTA; the explorer confirms wOCTA.
  • 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): OCTA is the currency for paying for OctaSpace services (compute/VPN/rendering, etc.).
  • Evidence: Tier‑1 — https://whitepaper.octa.space/octaspace-whitepaper.pdf
  • Why sufficient / why not (one line): The whitepaper states that OCTA is the primary payment instrument for services.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Staking mechanism: collateral 100,000 OCTA + reward distribution to nodes (weekly billing period).
  • Evidence: Tier‑1 — https://whitepaper.octa.space/octaspace-whitepaper.pdf
  • Why sufficient / why not (one line): The “Staking” section sets the conditions and the reward distribution scheme.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): A governance role of the token is not described in the Tier‑1 sources used.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The whitepaper describes payments/mining/staking in detail, but not governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): OCTA is the native currency of the protocol (fees/payments + staking + rewards), so it cannot be replaced without changing the protocol.
  • Evidence: Tier‑1 — https://whitepaper.octa.space/octaspace-whitepaper.pdf
  • Why sufficient / why not (one line): The described monetary policy/mining/staking presuppose a native coin.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://whitepaper.octa.space/octaspace-whitepaper.pdf Architecture (L1 PoW + L2 PoA), GPU marketplace, focus on ML, monetary policy (48M supply), staking conditions.
Tier‑1 https://octa.space Product description of the marketplace (AI apps, Docker/VM), positioning as a “decentralized GPU network”.
Tier‑1 https://docs.octa.space/2026-roadmap Tier‑1 roadmap and the claimed directions in AI infrastructure (Hugging Face integration, clusters, distributed AI).
Tier‑1 https://etherscan.io/token/0xfA704148D516b209D52C2D75f239274C8f8EAF1A Onchain confirmation of wOCTA ERC‑20 on Ethereum (address, supply per the wrapper).
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top