Acurast is a decentralized compute network that uses smartphones to run software tasks. Developers submit workloads, phone operators provide processing capacity, and the network coordinates execution and payments. ACU is its mainnet token, used for network fees, compute-related activity, staking, rewards, and governance. It is not the same asset as cACU, the token used on Acurast’s Canary network.
Acurast belongs to a category often called decentralized physical infrastructure networks, or DePIN. Instead of building one fleet of servers, it coordinates devices supplied by independent operators. Its choice of hardware is a defining feature: the network uses phones as processors.
That description raises practical questions. What can a phone run for a developer? How does the network assign work? Why would someone stake ACU if they do not own a processor? And does one billion tokens mean the supply cannot grow? The answers depend on the difference between Acurast’s compute system and its token economy.
Acurast at a glance
| Item | Description |
|---|---|
| Project | Acurast |
| Mainnet token | ACU |
| Network purpose | Coordinate compute workloads across phone-based processors |
| Developer uses | Applications, APIs, scheduled tasks, and other supported workloads |
| Processor role | Supply device capacity and execute assigned work |
| Other token to distinguish | cACU, used on the Canary network |
| Initial ACU supply | 1 billion tokens |
| Supply model | Annual inflation under the published tokenomics; not a fixed one-billion-token maximum |
Acurast launched its mainnet and token-generation event on January 20, 2026. Its Canary network preceded the mainnet and uses different token and staking rules. This distinction matters when reading older guides: a process described for Canary may not apply to mainnet ACU.
How does Acurast work?
A developer defines a deployment: the instructions to run, when to run them, and where the output should go. Acurast’s network then matches the deployment’s requirements with processor capacity. The processors execute the work, while the network records and coordinates the activity.
The system has three broad layers. Its application layer contains the workloads developers deploy. Its execution layer contains the environments in which processors run those workloads. Its consensus layer coordinates activities including matching and processor reputation. Acurast’s documentation calls the matching component the Matcher. It pairs available resources with deployment requirements rather than assuming every phone is suitable for every job.
A phone operator runs Acurast’s processor software on a supported device. The phone may then contribute capacity to the network. Providing a phone does not guarantee a fixed payment: rewards depend on the program’s rules, device benchmarks, network activity, and, where applicable, staking arrangements. Acurast measures processor characteristics including CPU performance, memory, and storage for parts of its reward system.
Acurast emphasizes trusted execution environments, or TEEs. A TEE is a hardware-backed environment intended to protect code and data while a device processes a task. In Acurast’s design, this supports claims about execution and confidentiality even though the phone belongs to an independent operator. It does not eliminate every risk. Device security, implementation flaws, software updates, and the requirements of a given workload still matter.
What can developers use Acurast for?
The network’s documentation lists uses such as APIs, webhooks, scheduled jobs, confidential data processing, and language-model inference. These are different workloads. A short scheduled task has different requirements from an application that needs sustained capacity or fast responses.
| Use case | What the processor does | What a developer should check |
|---|---|---|
| Scheduled task | Runs instructions at defined times | Timing, failed-job handling, and cost |
| API or webhook | Processes an incoming request | Response time and availability |
| Confidential computation | Handles data within a supported execution environment | Data flow, verification, and threat model |
| AI inference | Runs a supported model or part of a workload | Device capacity, performance, and pricing |
These are examples of supported categories, not a claim that every workload runs on every phone. Developers need to check technical requirements, deployment tools, and current pricing before selecting the network. Acurast’s documentation says developer access can involve ACU or USDC, while ACU is required for mainnet transaction fees. The payment path for a deployment should be checked in the current interface rather than inferred from a token description.
What is the ACU token used for?
ACU connects participants who use, supply, and help secure the network. Its roles are broader than exchange trading.
| ACU function | Role in the network |
|---|---|
| Transaction fees | Pays fees for activity on Acurast mainnet |
| Compute activity | Supports the economic process around deployments |
| Processor incentives | Funds eligible rewards for providing compute |
| Staked Compute | Allows tokens to back commitments to provide capacity |
| Delegation | Lets holders support a compute provider without running a phone |
| Governance | Gives holders a route to participate in protocol decisions |
Acurast’s architecture makes an important distinction about compute payments. Its documentation says a deployment’s compute cost is burned when that deployment executes; it does not describe a direct transfer of that payment to the processor. Processors instead receive rewards through the applicable reward pools, with execution affecting reward weight. Saying “developers pay processors directly” would therefore misstate the documented mechanism.
Staking introduces another role for ACU. A compute provider can commit tokens alongside a promise to maintain a specified level of capacity. A holder without hardware can delegate to a provider. Both arrangements can receive rewards under the rules, but rewards are not a guaranteed return. If a provider falls short of its compute commitment, the protocol’s slashing rules can reduce staked tokens; delegators share that risk.
ACU tokenomics: initial supply is not maximum supply
Acurast’s published tokenomics set initial supply at 1,000,000,000 ACU and describe 5% annual inflation. The documentation says the inflation allocation can be adapted through governance. CoinMarketCap lists no finite maximum supply and shows total supply above one billion. Those statements are consistent: initial supply refers to the starting allocation, not a permanent cap. Current circulating and total supply figures can change and should be checked at the time of publication.
| Destination for published annual inflation | Share |
|---|---|
| Staked Compute Pool | 70% |
| On-chain treasury | 15% |
| Compute Pool benchmark rewards | 10% |
| Collators, which produce blocks | 5% |
The initial allocation is separate from annual inflation. It includes community activation, a community treasury, operational funds, liquidity provision, early backers, and team and adviser allocations. These categories have different release schedules. For example, the published allocation assigns 24% of initial supply to the community treasury, 24% to team and advisers, and 6.5% to early backers. A release schedule matters because an allocated token is not necessarily circulating or available to trade on day one.
Inflation and token burns also need to be considered together. Acurast documents burns associated with deployment execution and with part of certain slashing penalties. That does not make ACU a fixed-supply token, nor does it establish that burns will offset new issuance. Those outcomes depend on network activity and protocol rules over time.
ACU, cACU, and MIST: what is the difference?
The three names appear in Acurast material but do not mean the same thing.
| Name | What it represents |
|---|---|
| ACU | Native token of Acurast mainnet |
| cACU | Token of the separate Canary network |
| MIST | Points used in Acurast community activities, not a mainnet token |
This distinction is important for wallets, staking, and transfers. Receiving a token on one network does not mean it is already usable on another. Acurast has documented a migration and conversion process for qualifying Canary holdings, with time limits and conditions. Anyone handling an older cACU balance should consult those rules rather than assume that cACU and ACU can be exchanged at any time.
ACU also exists in forms on other chains. The correct contract or receiving network depends on where the token is held and where it needs to be used. Before a transfer, confirm the network, token instance, address, and supported route in the relevant wallet or service. A matching ticker alone is not sufficient verification.
What are the main risks?
For developers, a network may not meet a workload’s performance or availability needs. Confidential execution also requires a review of the workload’s actual security model; the presence of a TEE should not be treated as a blanket guarantee.
For processor operators, rewards depend on device performance and network rules, while maintaining capacity creates operational costs. Operators who stake against a compute commitment face slashing if they fail to meet it.
For delegators, the provider’s performance becomes part of their risk. Acurast’s staking documentation also describes a cooldown before an exited mainnet stake can be withdrawn. During cooldown, reward weighting falls while slashing exposure remains. A holder who may need to sell at short notice should understand that constraint before staking.
For token holders, market price, liquidity, inflation, and scheduled allocation releases matter. Network usage and token price are not the same metric. More phones registered or more deployments reported do not, on their own, prove how much paid compute customers use or what price ACU should have. Compare activity measures, token issuance, and real demand rather than relying on one headline number.
Can you trade ACU on Phemex?
Phemex listed an ACU/USDT spot pair in January 2026, but announced its delisting effective September 3, 2026. It also announced the delisting of ACUUSDT futures effective August 4, 2026. An old listing page is therefore not evidence that either market remains available. Check current platform notices and supported transfer options before acting on an older trading guide.
Frequently asked questions
Is Acurast a blockchain or a phone-compute network?
It is both a network coordinating phone-based compute and a mainnet that handles related activity, including fees, staking, and governance. Developers submit workloads; processors supply capacity; the network matches and records their activity.
Does a person need a phone to hold or stake ACU?
No. A person can hold ACU without providing compute. Acurast also permits delegation to a compute provider, subject to its staking and slashing rules.
Is ACU capped at one billion tokens?
No. One billion is the published initial supply, not a fixed maximum. Acurast documents annual inflation, and CoinMarketCap does not list a finite maximum supply.
Bottom line: Acurast connects developers with phone-based compute providers, while ACU supports fees, incentives, staking, and governance. The central questions for a reader are whether the network meets a real compute need, how its rewards and penalties work, and which token and network they are using.
