Acurast Processor Update V1.27.0
Acurast Processor Update V1.27.0
Setting up a dedicated phone as an Acurast Processor has meant a factory reset, the Acurast Hub open on a laptop, and a QR code scanned across the gap between the two. Pairing is the step in that sequence most exposed to a weak connection, and until now, when it went wrong, there was no way to simply try again.
Acurast Processor 1.27.0, currently available for Android only, rebuilds that flow, and tightens what happens on the phone once it is in.
Most of what changed is setup and stability rather than new capability.
Processor Update V1.27.0
Onboarding, Rebuilt
New setup screens. The Hub inside the app. Fewer silent failures.
Setting Up a Phone
The changes land on Processor Lite, the version that runs on an everyday phone alongside everything else you use it for, and on Processor Core, the version that gives a dedicated phone over to compute entirely.
A Welcome Screen and a Cleaner Account Setup
Lite now opens on a proper welcome screen, and the account setup behind it has been redesigned, including the step where you save the recovery phrase.
A Provisioning Screen for Core and Lite
Both versions get a new provisioning screen: the stage where the app configures the phone and registers it as a Processor.
On Android, that stage is also where the Work Profile is created, a separate managed space on the phone that keeps Acurast’s workloads walled off from personal apps and data.
Pairing That Survives a Bad Connection
Pairing links a phone to the account that manages it, and it needs both sides reachable at the same moment, which is why a patchy connection breaks this step before any other.
The flow is now more resilient to network hiccups. When something does go wrong, you can retry manually instead of starting over.
The Hub, Without the Laptop
The Acurast Hub is the console where you manage Processors, watch their status, create Deployments and stake. A manager account held locally on a phone used to need a desktop browser to reach it.
The Local Manager can now open the Hub inside the app. Not a cut-down mobile view — the full Hub, on the phone that already holds the account.
Processor Core now also opens the phone’s full system settings, whereas previously only Wi-Fi settings were reachable.
What Changes for Developers
Two runtime changes, and an error message worth reading.
A Rendering Surface You Control
Cargo and Node.js Deployments can drive an embedded browser on the phone, which is how scraping jobs, screenshot pipelines and anything else that needs a real rendering engine get their work done.
That browser used to paint to a surface the size of whatever display the phone happened to have. A Deployment scheduled across a fleet of mixed hardware therefore rendered a different page on every phone, which is a problem when the output is meant to be comparable.
Deployments can now set the size and pixel density of that surface, and read it back. The request has bounds: each side between 240 and 2560 device pixels, no more than 2560×1440 pixels in total, and a scale factor between 0.5 and 4. Set it before the first tab opens, or the surface is created at the phone’s display size as before.
Find more information on Cargo here, and for Node.js here.
A Newer Llama Build
The Node.js runtime’s bundled Llama library, the inference engine behind on-phone language model work, moves to build b10164.
Cargo Errors Worth Reading
Cargo execution errors reported on chain are clearer and more precise. When a container fails on a phone on the other side of the world, the on-chain error message is most of what you have to work with.
Note: Cargo runs on attested Android Core phones. Processor Lite on iOS continues to serve Node.js workloads as before.
Fewer Failures in the Background
Deployment code is fetched over IPFS, the peer-to-peer network Acurast distributes workloads through. When a fetch failed, it could take a Heartbeat down with it — the status check-in every Processor sends roughly every 30 minutes to prove it is alive and earning.
IPFS stability has been improved, and the team expects those failures to become much less common. The release also carries security patches for the execution runtimes and more detailed usage logs, which exist so problems get traced from a record rather than reproduced by hand.
Getting the Update
Processor 1.27.0 carries version code 130 and follows 1.26.0. It reaches phones through Google Play and the App Store, and the Hub can signal a phone to update rather than waiting for the store to get to it.
The full release notes, along with the build for the Canary network, are published on GitHub.
Building on Acurast? If the browser surface controls or the Cargo error reporting change how you deploy, the team wants to hear how it lands. Join the Discord.
