Acurast is a DePIN Layer 1 that turns idle smartphones into confidential, verifiable cloud nodes. Developers deploy serverless workloads to TEE-secured phone processors; Compute Providers earn ACU. Mainnet and the ACU TGE went live on January 20, 2026.
Acurast sits in the broader DePIN projects category: community devices supply real-world capacity, and on-chain incentives coordinate supply and demand. Where many networks mainly coordinate hardware, Acurast emphasizes hardware-backed confidentiality and verifiability on phones. Official product and docs live at acurast.com and docs.acurast.com.
Key Takeaways
Acurast is a phone-powered DePIN compute Layer 1: idle Android and iOS devices can act as processors without buying specialized servers.
Workloads run inside TEEs (and optional zero-knowledge runtimes), so execution can stay confidential and produce verifiable results for a decentralized compute service.
After Mainnet and TGE (January 20, 2026), ACU is used to pay for compute, reward providers, stake, and participate in governance.
Device uptime, battery, bandwidth, token incentives, and competition with centralized clouds remain core risks for providers and developers across every region.
What is DePIN?
DePIN stands for Decentralized Physical Infrastructure Network. In traditional models, telecom, cloud storage, data, and AI capacity are often controlled by a few large operators. Blockchain-based DePIN designs let individuals contribute physical resources—servers, sensors, radios, or phones—and earn rewards for verified work, aiming for more open, transparent, and scalable decentralized infrastructure.
The practical value of DePIN is reducing intermediary lock-in in infrastructure markets while improving auditability of who provided which resource. That framing is useful when comparing storage, wireless, and compute networks; for a deeper sector map, see why DePIN matters. Acurast applies the idea specifically to confidential cloud computing on consumer phones.
What is Acurast
Acurast delivers a decentralized verifiable compute network historically associated with the Polkadot ecosystem and operates as a Layer 1 focused on decentralized serverless compute. Its core idea is to use smartphone Trusted Execution Environments so code can run confidentially on devices people already own, as an alternative to centralized data centers, instead of requiring participants to buy dedicated mining or server hardware. Android and iPhone devices can onboard as processors; developers can target workloads that resemble Web2 serverless patterns (for example Lambda-style functions) as well as Web3 automation across ecosystems.
Acurast forms a foundational layer for a decentralized compute economy through the combination of phone TEEs for confidentiality plus on-chain orchestration for matching deployments to processors. Official docs describe serverless APIs, scheduled jobs, LLM inference, and other confidential workloads running on a global phone pool that functions as a compute network, with access priced in ACU or, in some flows, USDC.
Project Background
Acurast was founded in 2022. Public traction figures on the project site (as of late 2026 messaging) include on the order of 334,000+ onboarded phones, 685K+ compute deployments, and 1B+ on-chain transactions processed—materially higher than earlier seed-era snapshots that cited roughly 7,500 deployments, 35,000 accounts, and 150 million transactions. The longer-term vision is utilizing billions of smartphones as compute power. The project completed a seed round in 2023 (amount undisclosed), has received foundation grants, and press coverage has cited a later $5.4M raise aimed at scaling Acurast’s decentralized cloud using smartphones. Compute Providers are active across many countries and regions rather than a single data-center footprint.
On January 20, 2026, Acurast launched Mainnet together with the ACU Token Generation Event, moving from its incentivized testnet and canary phases into production compute with a live economic layer. Planned total supply for ACU remains 1 billion tokens; utility covers compute payment, provider rewards, staking/security, and governance for token holders. The Mainnet economic layer is designed for mass adoption of decentralized compute. Approximately 70% of network inflation incentivizes resource providers (see Acurast TGE and project docs).
Acurast separates consensus, execution, and application concerns in a modular stack, with the Acurast Coordinator embedded in the consensus layer and a reputation engine used to score processor honesty. The modular base supports native settlement and cross-ecosystem interoperability without introducing a new trusted intermediary for confidential execution across applications.
The consensus layer is the foundation where the Orchestrator matches developer deployments with processors, coordinating global demand for deployments with available devices while the chain anchors confidential workloads through on-chain coordination and verification. Acurast’s consensus uses a Nominated Proof of Stake (NPoS) variant: validators secure the chain while nominators stake behind validators they trust. Economic and reputation incentives push nominators toward effective validators; limited validator seats create competition that supports network integrity.
The reputation engine updates processor scores so reliable devices are preferred for future work and dishonest behavior is harder to sustain. Nominators share economic risk if validators misbehave, and nominator credibility is tied to validator choice—so staking incentives and reputation reinforce each other.
Execution Layer
The execution layer is modular so runtimes can match the workload. Two processor runtime approaches are central: the Acurast Secure Hardware Runtime (ASHR) and the Acurast Zero-Knowledge Runtime (AZKR). A Universal Interoperability Layer adds modules for native interaction with environments such as EVM, WASM, and Substrate.
ASHR leans on hardware-level TEEs so computation and sensitive data stay on genuine hardware verified by the network. Acurast's Android and iOS clients check each phone's secure elements to help confirm device integrity, protecting confidentiality and integrity against casual inspection or remote tampering. AZKR uses recursive zero-knowledge proofs to produce general-purpose verifiable computation: proofs can be generated and aggregated so the network can check that a computation was performed correctly without revealing private inputs, supporting verifiable execution for confidential jobs. Together, these runtime choices underpin secure decentralized compute across verified devices.
Application Layer
The application layer is where Web2 and Web3 developers run secure applications on Acurast’s decentralized cloud. Early integrations focused on DeFi-style automation and confidential jobs; the roadmap emphasizes confidential AI, oracles, indexing, and other workloads that need both decentralization and privacy, including jobs with high security or AI requirements. Developers choose the runtime path (secure hardware, ZK, or both) based on trust and verification needs.
How to Participate and Earn Points Rewards
How to Become an Acurast Processor
Anyone with a spare smartphone can turn a mobile phone into an Acurast Processor and earn rewards for contributing unused compute power. The baseline service path is:
Download the Acurast Processor app for a supported Android or iOS device.
Complete on-device setup, then register the device on-chain.
Keep the phone online so the network can schedule deployments against your compute service capacity.
Monitor rewards in the hub; rates and quests can differ by region and program season.
Note: app store listings, attestation checks, and which Processor builds you can download vary by region. Always follow the live Processor guide before you download a second client or enroll another device into the same service account. If the first download fails attestation, re-check the supported-device list, then download the current build again rather than forcing an unsupported phone into production.
cACU Points Rewards
Compared with networks that require specialized GPUs or servers, Acurast lowers the hardware bar: users can onboard idle phones as processors from a potential supply base measured in billions of devices, with no specialized servers or data centers required. That spare-device model is how the network tries to scale compute power as a permissionless service. In earlier incentivized phases, participants tracked cACU (canary/points-era balances) in the Acurast hub, with messaging that each online phone could accrue on the order of 250 tokens per month, scaling with device count and uptime. Developers who deployed apps and consumed processor capacity could also receive additional incentives.
After Mainnet and TGE, the native asset is ACU (1 billion planned total supply). Historical cACU balances and conversion mechanics should be checked in the official hub and tokenomics docs rather than assumed from older points-era screenshots—exchange rates and migration steps are project-controlled and can change. Current provider docs emphasize installing the Processor app, registering on-chain, and earning ACU inside Acurast’s decentralized cloud for executed deployments.
Separately, Acurast’s Cloud Rebellion community program has used MIST points for ranking and quests. Common earning paths described in earlier program materials include:
Phones participating: each participating phone earning MIST on a timed cadence (historically about 1 point every 15 minutes while online), so uptime and fleet size raise hourly accrual.
Invites: referring users into Rebellion so both parties earn when the invitee runs a phone or joins processor flows.
Tasks: completing quests posted on the Rebellion dashboard.
MIST is a community/points layer, not a substitute for understanding ACU utility after TGE. Always verify live quest rules on rebellion.acurast.com before treating any rate as fixed.
Acurast is built for interoperability across Web3 environments. Integrations and runtime bridges target EVM, WASM, Substrate, and related stacks so deployments can settle or interact closer to the destination chain. That modularity matters for oracles, automation, and confidential jobs that must touch multiple ecosystems without forcing every app onto a single VM.
Note: partner lists and supported chains change over time—treat screenshots as illustrations, not a live service catalog. Developers should confirm which interoperability modules are available in their region before wiring production traffic to the compute service.
Acurast’s potential sits beside concrete operational and market risks. First, compute supply depends on phone hardware quality, network bandwidth, battery health, power draw, and user uptime—so capacity can fluctuate more than in a data-center SLA, especially when providers are asked to support mission-critical workloads. Second, ACU incentive design (inflation, staking, and pricing for deployments) can over- or under-reward providers, affecting participation and secondary-market volatility. Third, the project competes with centralized clouds such as Amazon AWS and Google Cloud on price, reliability, and developer tooling, and with other DePIN compute networks on verifiability claims, while using a different phone-based supply model. Finally, points programs and early rewards can lose appeal if long-term unit economics are unclear, which may reduce active processors.
Note: service quality is not uniform by region—device density, mobile networks, and electricity costs differ, so the same Processor setup can deliver different effective compute power from one region to another. A compute service that looks healthy in one metro region can underperform when you download the same app in a weaker coverage region. Readers evaluating provider or developer participation should treat TEE trust assumptions, attestation flows, and token unlock schedules as first-class diligence items, not marketing footnotes.
Future Development and Conclusion
Post-Mainnet priorities highlighted by the project include staked compute (with a large share of inflation directed to securing and rewarding compute), richer confidential AI workloads, and broader developer tooling (CLI, SDK, and payment paths such as USDC via agent-friendly flows). Compatibility across Android and iOS processors, staking/delegation for people without hardware, and new pricing models remain active product surfaces rather than finished checklists.
Acurast is no longer a pure pre-TGE experiment: Mainnet and ACU are live, while phone-scale DePIN compute is still early relative to hyperscale clouds. The roadmap points toward confidential, phone-based infrastructure delivered as a global service, but outcomes depend on execution quality and real demand in each region. Understanding the architecture, reward paths, and risks above is a better starting point than chasing points alone. For official definitions and setup paths—including where to download Processor builds for your region—use docs.acurast.com; for sector context, return to Gate Learn coverage of DePIN projects.
Summary
Acurast is a verifiable compute network built from smartphones, turning them into TEE-backed processors for a DePIN compute Layer 1 and pairing NPoS consensus and a reputation engine with secure-hardware and zero-knowledge runtimes. Participation shifted from cACU/MIST-era incentives toward live ACU rewards after the January 20, 2026 Mainnet and TGE. Architecture modularity and multi-ecosystem interoperability are strengths; device volatility, token design, and competition with centralized clouds are the main constraints. Always verify live reward rates and migration steps on official Acurast channels before committing hardware or capital.
FAQ
What is Acurast used for?
Acurast provides a decentralized serverless compute service on smartphones through a decentralized cloud: developers deploy APIs, jobs, automation, and confidential or AI-related workloads—including some mission-critical flows—while phone owners act as Compute Providers and can earn ACU for executed work. In short, you use the network to run secure jobs on distributed phone compute power rather than a single regional data center.
How is Acurast different from AWS, Google Cloud, or other decentralized cloud platforms?
Hyperscale clouds run in operator-controlled data centers with commercial SLAs and region-based service catalogs. Acurast coordinates many consumer phones with hardware TEEs so execution can be confidential and verifiable without trusting a single cloud landlord—typically with different reliability and ops trade-offs than centralized data centers. The service is closer to a distributed device fleet than to a classic regional availability zone.
Do I need special hardware to join as a provider?
No specialized server purchase is required for the baseline path: supported Android or iPhone devices—and even a spare phone—can download the Processor app and register on-chain to join Acurast’s decentralized cloud. Note that performance still depends on device class, network quality, power/thermal limits, and uptime. Prefer the official download links in docs over third-party mirrors.
What is the ACU token?
ACU is Acurast’s native token (planned 1 billion total supply). After TGE, it is used to pay for compute service usage, reward providers, stake for network security, and participate in governance by token holders. Older cACU balances belong to earlier network phases and should be migrated or redeemed only via official instructions. Note: live market price pages are separate from protocol utility—always treat secondary-market quotes as market data, not product documentation.
What are the main risks of running an Acurast phone?
Battery drain, heat, bandwidth use, inconsistent uptime, potential software/attestation issues, and token-price or incentive changes can all reduce effective rewards, especially if you expect to support mission-critical workloads. Power and thermal limits on a consumer device matter more than on rack servers. Treat participation as experimental decentralized compute contribution, not guaranteed yield. Before you download another Processor build or expand a multi-device fleet in a new region, re-check official attestation and reward notes for that region’s service rules.
Author: Grace
Translator: Viper
Reviewer(s): 林君樵、Pow、Elisa、Jayne
Translation Reviewer(s): Ashely、Joyce
Disclaimer
* The information is not intended to be and does not constitute financial advice or any other recommendation of any sort offered or endorsed by Gate.
* This article may not be reproduced, transmitted or copied without referencing Gate. Contravention is an infringement of Copyright Act and may be subject to legal action.
Solana faces both opportunities and challenges in its development. Recently, severe network congestion has led to a high transaction failure rate and increased fees. Consequently, some have suggested using Layer 2 and appchain technologies to address this issue. This article explores the feasibility of this strategy.
This article introduces the technical principles, framework, and applications of Zero-Knowledge (ZK) technology, covering aspects from privacy, identity (ID), decentralized exchanges (DEX), to oracles.
Sui is a PoS L1 blockchain with a novel architecture whose object-centric model enables parallelization of transactions through verifier level scaling. In this research paper the unique features of the Sui blockchain will be introduced, the economic prospects of SUI tokens will be presented, and it will be explained how investors can learn about which dApps are driving the use of the chain through the Sui application campaign.
Dewhales Research released a research report to delve into the mechanism and potential of AltLayer and explore how it can serve as a Rollup-as-a-Service solution in the rapidly developing blockchain environment. The article also introduces AltLayer’s Tokenomics, team and integration cases.
TronScan is the primary blockchain explorer for the TRON network. It allows users to check TRX and TRC-20 transactions, inspect wallet balances, analyze smart contracts, monitor tokens, and view network activity without logging in. By connecting a compatible wallet such as TronLink, users can also transfer assets, stake TRX, vote for Super Representatives, and interact with TRON ecosystem applications.
