Product
The project-authored whitepaper describes an orchestrator, reputation engine and attestation service in the consensus layer, with developers off-loading computations to a modular execution layer.
Supported
Project announcement
Evidence (2): 2 supporting
End-to-end confidentiality and correct execution across currently supported devices, runtimes and workloads were not independently tested. The scope of production AZKR support is not established by the reviewed sources.
Not yet verifiable
No evidence recorded.
Acurast documentation says developers may select a public processor pool via its Matcher or use dedicated processors, including trusted or self-service processors.
Supported
Project announcement
Evidence (2): 2 supporting
- supports: Acurast Docs
developers can directly leverage the Acurast Matcher to select from a public pool of processors
- supports: Acurast Docs
use dedicated processors
Acurast describes a decentralized compute network that runs applications on smartphones rather than in data centers, using secure hardware for confidential execution and verifiable results.
Supported
Project announcement
Evidence (2): 2 supporting
- supports: Acurast
Acurast is a decentralized, verifiable compute network powered by phones.
- supports: Acurast
Instead of data centers, it runs applications on smartphones, using each phone’s secure hardware (a Trusted Execution Environment) so code runs confidentially and its results can be verified.
The execution-layer documentation describes a secure-hardware runtime (ASHR) and a zero-knowledge runtime (AZKR), with different hardware and cryptographic trust assumptions. These descriptions do not establish that both are deployed for all workloads.
Supported
Project announcement
Evidence (1): 1 supporting
- supports: Acurast Docs
The Acurast execution layer natively offers two runtimes, the (1) Acurast Secure Hardware Runtime (ASHR) and (2) Acurast Zero-Knowledge Runtime (AZKR).
Acurast lists confidential LLMs, data analytics, web scraping, indexing, automation and proof generation among its target workloads; this is positioning rather than independent confirmation of production use.
Supported
Project announcement
Evidence (3): 3 supporting
- supports: Acurast
Confidential LLMs for enterprise data Distributed analytics & secure database integrations
- supports: Acurast
Web scraping & blockchain indexing
- supports: Acurast
Scalable zkProof generation
Back to sectionsFunding
Tech.eu names Gavin Wood, Leonard Dörlochter, Michael van de Poppe, Scytale Digital, Ogle and Vineet Budki among Acurast backers.
Supported
Evidence (1): 1 supporting
- supports: Tech.eu / Cate Lawrence (reports issuer announcement)
Dr. Gavin Wood (Co-founder, Ethereum; Founder, Polkadot), Leonard Dörlochter (Founder, peaq ), Michael van de Poppe (Founder, MN Capital), Scytale Digital, Ogle (Founder, GlueNet; CoinDesk’s Most Influential), and Vineet Budki (CEO, Sigma Capital).
Tech.eu reported that the cumulative $11 million included $5.4 million raised in a May 2025 CoinList public token sale; the $5.4 million is not an additional round to add to that total.
Supported
Evidence (1): 1 supporting
Current cash runway, audited financial statements, revenue, burn rate, private-round dollar proceeds and a reconciled funding total after November 2025 are not established by the fetched sources.
Not yet verifiable
No evidence recorded.
The issuer filing lists a June 2023 seed SAFT and June 2024 strategic SAFT of 32.5 million ACU each, plus a May 2025 CoinList SAFT for 65 million ACU. Dollar proceeds by private round were not independently verified.
Unverified
Evidence (1): 1 supporting
Tech.eu reported on 13 November 2025 that Acurast announced $11 million raised cumulatively, combining non-dilutive grants and token-based rounds during 2023–2025. This is reporting of the announcement, not an audit of receipts.
Supported
Evidence (2): 2 supporting
Back to sectionsTechnical progress
In its 6 November 2026 post, Acurast reports mainnet tests serving Qwen3.5-9B on 16 GB Android phones with an OpenAI-compatible HTTPS API. This is a project test, not an independent benchmark or evidence that Coinbase is an Acurast customer.
Supported
Project announcement
Evidence (2): 2 supporting
Acurast reports up to 85.2 prompt tokens per second and 9.3 generated tokens per second for Qwen3.5-9B on its fastest tested Snapdragon 8 Elite-class phones using MNN. It reports about 14 ACU spent over roughly 60 phone runs; results and costs are workload-specific.
Supported
Project announcement
Evidence (2): 2 supporting
The project audit register lists Monethic chain/pallet and compute-pallet audits dated 23 October 2025 and 11 March 2026, an inference ERC20 audit dated 23 October 2025, and a Compass Security Android app pentest dated 27 March 2024. Only the register was fetched, not the underlying reports.
Supported
Project announcement
Evidence (4): 4 supporting
Audit findings, remediation completeness, deployed commit matches, chain uptime, independent throughput and performance comparisons remain unverified. The audit register alone does not prove current software is secure.
Not yet verifiable
No evidence recorded.
Acurast announced Mainnet and TGE live on 20 January 2026 and says its Canary network began on 7 July 2023. Mainnet lifecycle classification relies on this announcement; native-chain block production was not independently queried.
Supported
Project announcement
Evidence (3): 3 supporting
GitHub API metadata identifies the public Acurast/acurast-substrate repository as Rust, not archived, with a push timestamp of 10 November 2026. Repository activity is not evidence of deployment or code quality.
Supported
Evidence (4): 4 supporting; 1 needs review
Acurast authors published the serverless-cloud whitepaper on arXiv in March 2025 and revised it in January 2026; the entry labels it a whitepaper, not a peer-reviewed evaluation.
Supported
Project announcement
Evidence (2): 2 supporting
Back to sectionsAdoption
CoinList published an interview in May 2025 that claimed over 70,000 phones in 130+ countries. CoinList hosted the token sale, so this does not independently validate network reach.
Unverified
Evidence (1): 1 supporting
At retrieval, the Acurast homepage displayed 357,000+ onboarded phones, 1.1B+ on-chain transactions and 751K+ compute deployments. These are project counters, not independently measured active devices, paid jobs or distinct customers.
Supported
Project announcement
Evidence (1): 1 supporting; 1 needs review
- supports: Acurast
357,000+ Onboarded Phones 1.1B+ On-chain Transactions Processed 751K+ Compute Deployments
Needs review
Paying customer count, recurring revenue, compute-fee totals, hardware utilization, daily active processors, repeat paid jobs and the proportion of AI versus other workloads were not independently established.
Not yet verifiable
No evidence recorded.
The January 2026 launch post reports over 169,000 onboarded phones, 364,000 deployments and 589 million on-chain transactions before launch; those historical figures should not be interpreted as current mainnet demand.
Supported
Project announcement
Evidence (1): 1 supporting
The reviewed sources do not establish independent customer-side confirmation of production AI workloads. Demonstrating a model that Coinbase fine-tuned does not establish a Coinbase partnership.
Not yet verifiable
No evidence recorded.
Back to sectionsToken status
The current project table allocates 24% each to Team and Advisors and Community Treasury, 11.5% to Operational Funds, 10% to Liquidity Provision, 6.5% each to Early Backers, CoinList and Early Compute Providers, 5% each to Community Activation and Listing Incentives, and 1% to Cloud Rebellion Airdrop.
Supported
Project announcement
Evidence (10): 10 supporting
- supports: Acurast Docs
Community Activation 5% 50,000,000
- supports: Acurast Docs
Early Backers 6.50% 65,000,000
- supports: Acurast Docs
6.5% 65,000,000
- supports: Acurast Docs
Cloud Rebellion Airdrop (Community Activation) 1% 10,000,000
- supports: Acurast Docs
Listing Incentives (Community Activation) 5% 50,000,000
- supports: Acurast Docs
CoinList Token Launch (Community Activation) 6.50% 65,000,000
- supports: Acurast Docs
Operational Funds 11.50% 115,000,000
- supports: Acurast Docs
Community Treasury 24.00% 240,000,000
- supports: Acurast Docs
Team and Advisors 24.00% 240,000,000
- supports: Acurast Docs
Liquidity Provision * 10% 100,000,000
The official BSC, Base and Peaq addresses are respectively 0x6EF2FFB38D64aFE18ce782DA280b300e358CFeAF, 0xc5fEd7c8cCC75D8A72b601a66DffD7A489073F0b and 0x165bcb970836F83c15b22c3c1622279d97A20446. CoinGecko matches all three after case normalization.
Supported
Evidence (2): 2 supporting
- supports: CoinGecko API (aggregated token and market metadata)
"peaq":"0x165bcb970836f83c15b22c3c1622279d97a20446","base":"0xc5fed7c8ccc75d8a72b601a66dffd7a489073f0b","binance-smart-chain":"0x6ef2ffb38d64afe18ce782da280b300e358cfeaf"
- supports: Acurast Docs
BSC 56 (0x38) 0x6EF2FFB38D64aFE18ce782DA280b300e358CFeAF 12 ACU Base 8453 (0x2105) 0xc5fEd7c8cCC75D8A72b601a66DffD7A489073F0b 12 ACU Peaq 3338 (0xd0a) 0x165bcb970836F83c15b22c3c1622279d97A20446 12 ACU
The January announcement distinguishes cACU on Canary from mainnet ACU. It describes user-selected conversion timing, with default 1:1 conversion at a maximum commitment of 19,353,600 blocks, estimated at 3.7 years, and earlier conversion after a minimum period. This is a published conversion design, not a currently tested redemption guarantee.
Supported
Project announcement
Evidence (2): 2 supporting
- supports: Acurast / Andreas Gassmann
the canary network , with its fast-paced update cycles , will remain, and so will cACU.
- supports: Acurast / Andreas Gassmann
a default 1:1 conversion if the commitment reaches the maximum time of 19353600 blocks, translating to roughly 3.7 calendar years.
The official documentation lists Ethereum ACU at 0x216b3643ff8b7BB30d8A48E9F1BD550126202AdD; CoinGecko lists the same address after case normalization. This establishes a documented project-to-contract match, not an independent contract audit.
Supported
Evidence (2): 2 supporting
Published inflation descriptions conflict: current docs specify fixed 5% annually, while the 18 January 2026 announcement retains a paragraph specifying 1%–5% depending on metrics and governance. The same announcement headline also says fixed 5%. Current docs are used for classification, but runtime issuance was not checked.
Disputed
Evidence (3): 2 supporting, 1 contradicting
Acurast publishes a split of annual issuance: 70% Staked Compute, 10% benchmark rewards, 15% treasury and 5% collators. These percentages split inflation rather than the genesis supply.
Supported
Project announcement
Evidence (1): 1 supporting
- supports: Acurast Docs
distributed to Staked Compute Pool (70%), Compute Pool (10%), On-chain Treasury (15%), Collators (5%)
Acurast publishes an initial supply of one billion ACU and current fixed annual inflation of 5%. Initial supply is not a maximum-supply cap.
Supported
Project announcement
Evidence (2): 2 supporting
The table marks CoinList and Listing Incentives fully available at TGE and Liquidity Provision unlocked, but its liquidity footnote says only 30% of that allocation was allocated at TGE. An unlocked allocation and actual circulation are different quantities; no circulating-supply reconstruction was performed.
Supported
Project announcement
Evidence (2): 2 supporting
- supports: Acurast Docs
Listing Incentives (Community Activation) 5% 50,000,000 100% 0 0 CoinList Token Launch (Community Activation) 6.50% 65,000,000 100% 0 0
- supports: Acurast Docs
No lockups but only 30% allocated at TGE.
Tech.eu reported a planned Genesis Mainnet and token debut for 17 November 2025; the later official TGE announcement is dated 20 January 2026. The earlier report records an expectation, not proof of a November token launch.
Supported
Project announcement
Evidence (2): 1 supporting, 1 context
ACU is a launched token: Acurast announced TGE on 20 January 2026, KuCoin scheduled ACU/USDT spot trading that day, and CoinGecko currently indexes ACU markets for the project-linked contract. The May 2025 sale predates TGE and is not treated as the launch date.
Supported
Evidence (4): 4 supporting; 1 needs review
Acurast lists native ACU on Polkadot parachain 3396 with no token contract, and 12-decimal representations on Ethereum, BSC, Base and Peaq. It describes HyperDrive between native Acurast and Ethereum and LayerZero for onward EVM bridging.
Supported
Project announcement
Evidence (2): 2 supporting
- supports: Acurast Docs
Acurast Mainnet ParachainID: 3396 native, no token contract 12 ACU
- supports: Acurast Docs
Deployed on its native chain, it can be bridged to Ethereum using the Acurast HyperDrive bridge and further from Ethereum to various EVM chains via LayerZero bridges.
Native genesis time, deployed bytecode, proxy and minting authorities, bridge backing, live supply, vesting enforcement and wallet concentration were not independently queried on-chain. Address agreement with CoinGecko cannot establish any of those facts.
Not yet verifiable
No evidence recorded.
The token ticker is ACU, matching Acurast documentation and CoinGecko metadata.
Supported
Evidence (2): 2 supporting
Acurast describes ACU uses as deployment and network fees, staking and delegation rewards, collator compensation and governance. The TGE page says compute-provider collateral can be slashed for failure to deliver; this was not independently tested.
Supported
Project announcement
Evidence (4): 4 supporting
- supports: Acurast Docs
Holders of ACU can engage in protocol governance by voting
- supports: Acurast
Compute providers stake ACU against the capacity they commit to. Fail to deliver and part of that stake is slashed.
- supports: Acurast Docs
Deployment Fees : Submitted by developers using Acurast Compute Network Fees : Required for transaction fees on the Acurast network
- supports: Acurast Docs
Collator rewards : Rewards for validators and block producers
The published schedule gives Team and Advisors a six-month cliff plus 36-month linear vesting; Operational Funds and Community Treasury a three-month cliff plus 24-month linear vesting; and Early Backers 24-month linear vesting with no cliff. On-chain enforcement and actual unlocked balances were not checked.
Supported
Project announcement
Evidence (3): 3 supporting
- supports: Acurast Docs
Team and Advisors 24.00% 240,000,000 0% 6 36
- supports: Acurast Docs
Operational Funds 11.50% 115,000,000 0% 3 24 Community Treasury 24.00% 240,000,000 0% 3 24
- supports: Acurast Docs
Early Backers 6.50% 65,000,000 0% 0 24
Back to sectionsRisks
The published genesis table assigns 24% to Team and Advisors and 6.5% to Early Backers, totaling 30.5%. It also specifies ongoing 5% annual issuance. These are material supply considerations; no investment conclusion is inferred.
Supported
Project announcement
Evidence (3): 3 supporting
The conversion post-mortem describes transient replay protection cleared on unlock and a kill switch that did not stop inbound processing or retries. It reports the bridge fixed and no realized loss; independent checks described within the post remain issuer-provided analysis.
Supported
Project announcement
Evidence (3): 3 supporting
The Blockworks-hosted filing is dated 15 September 2026 but its incident response is explicitly as of 29 June 2026; it does not establish an incident-free current state. Reconciliation with later security disclosures remains necessary.
Not yet verifiable
Evidence (1): 1 context; 1 needs review
Current governance docs say only council members may submit referenda, with one Root track gating privileged protocol operations. Tokenholder voting therefore does not imply unrestricted proposal submission.
Supported
Project announcement
Evidence (2): 2 supporting
- supports: Acurast Docs
Currently there is a single track (the Root track) which gates all privileged protocol operations
- supports: Acurast Docs
In the current configuration only council members can submit new referenda.
Governance docs specify a 48-hour decision period, six-hour confirmation and two-hour minimum enactment delay. Required support declines from 50% to 0% of active issuance during the decision period, while approval declines toward 50%. No historical referendum participation or control analysis was performed.
Supported
Project announcement
Evidence (3): 3 supporting
- supports: Acurast Docs
Decision period 48 hours Confirm period 6 hours Min enactment period 2 hours
- supports: Acurast Docs
approval starts at 100% at the beginning of the decision period and decreases toward 50%
- supports: Acurast Docs
the required support starts at 50% at the beginning of the decision period and decreases linearly to 0% by the end.
The execution documentation acknowledges ASHR relies on key attestation and hardware trust assumptions. Such a design requires confidence in hardware and attestation rather than only a cryptographic proof of arbitrary execution.
Supported
Project announcement
Evidence (1): 1 supporting
- supports: Acurast Docs
ASHR rely on key attestation procedures and hardware-based trust assumptions
Independent reproduction of the reported fixes, reconciliation of the September residual and November burn totals, burn transaction verification and confirmation that all affected deployed versions are patched remain outstanding. Different dated remediation totals are not treated as a contradiction by themselves.
Not yet verifiable
No evidence recorded.
Independent legal classification, jurisdictional restrictions, regulatory approvals, privacy compliance, hardware supply dependence and commercial sustainability were not assessed. No absence of regulatory or business risk is inferred.
Not yet verifiable
No evidence recorded.
The issuer filing discloses three market makers, a 1.75% token allocation committed for 24 months and names/structure under NDA. Counterparty identity and terms cannot be assessed from that disclosure.
Unverified
Evidence (1): 1 supporting
Acurast disclosed excess staking-reward payments and said approximately 71,000 ACU remained after larger recipients agreed to burns, to be covered by Association operational funds. This is the September account, not the latest remediation total.
Supported
Project announcement
Evidence (2): 2 supporting
The updated staking post-mortem says the bug doubled accrued delegation rewards from an existing pool, without extra inflation. It says about 571,875 ACU across 421 addresses was burned on 4 November 2026 and dates the vulnerable period from 30 October 2025 to 20 July 2026. These are project-reported findings; burn transactions were not independently fetched.
Supported
Project announcement
Evidence (3): 3 supporting
Acurast says it deployed protocol fixes 26.3–26.5 before publishing source code because early publication would expose vulnerabilities. It says it then returned to publishing source before governance votes. This limits contemporaneous public review of those emergency changes.
Supported
Project announcement
Evidence (2): 2 supporting
Back to sectionsNothing on this site is financial advice.