Does an Acurast registration mean the phone is running a deployment?
Acurast phones provide compute. They are not hashrate miners. Official heartbeats are about every 30 minutes. A successful lookup here returns registration plus Core/Lite and Android/iOS classification, not the current deployment.
| Signal | Source | It can show | It cannot show |
|---|---|---|---|
| Registered + type | This site’s mainnet index lookup | The address is a processor and a recognized mode | A deployment or heartbeat right now |
| Heartbeat | Official: about every 30 minutes; recent tracking via the Telegram monitoring bot | A report reached the chain | That count on this site |
| Deployment in this epoch | Busy Bonus condition in the official rewards page | A deployment was detected on the epoch’s first successful heartbeat | The epoch’s payout amount |
| Higher benchmark | Official: Core often scores about 15–20% above Lite | May raise base benchmark rewards and committable compute | This handset’s actual score |
The Acurast Processor on a phone provides verifiable compute. It is not a conventional proof-of-work miner. Official docs define Lite as an everyday phone you activate when you can, and Core as a locked-down phone used only for Acurast. Rewards under those rules require the app to be running and the phone to be online. Registered on this site does not carry that meaning.
On the Acurast project page a successful result has two lines: mainnet processor registration, and device classification. The type repeats Android, iOS, Core, or Lite when the index recognizes them. There is no deployment name, heartbeat count, or benchmark score.
Where to look for the job
- Open this device in Hub and confirm the Processor app is running, not merely installed once.
- Official docs say the device heartbeats about every 30 minutes. For recent performance they point to the Acurast Monitoring Bot on Telegram. Scanning every heartbeat on chain is possible and, as the docs say, slow.
- The rewards page states a Busy Bonus: if a deployment is detected executing on the first successful heartbeat of an epoch, benchmark metrics get 10% extra weight. That raises scoring for that epoch in both the compute pool and the staked compute pool. It is not a separate payslip.
- Deployment fees paid by developers are burned after successful execution. That is a supply rule, not the amount credited to your phone.
Example
Illustration, not a measured case: processor P shows Android · Lite and Registered here. In Hub the phone has no deployment, and the last heartbeat was two hours ago. Both can be true. The index can still list the processor while this epoch may not meet “executing a deployment.” Do not read Registered as Busy Bonus already applied.
Next step and limit
Whether a missed heartbeat can still leave benchmark rewards, see offline and missed heartbeats. How the pools are split, see reward scope. This site does not control the phone app and cannot infer a benchmark score or deployment name from the registration line.
Common questions
The type says Lite, but Hub shows no running deployment. Why?
Lite is the install mode, not a job switch. Official docs allow an everyday phone to provide compute only when it is convenient. The mainnet index can still list the processor when no deployment is running.
Does the Busy Bonus 10% mean 10% more ACU?
The rewards page describes 10% extra weight on benchmark metrics, which raises scoring in both pools for that epoch. It is not a flat 10% added to your balance. This site does not compute that amount.
Can I see the four benchmark pool names here?
No. The rewards page says base rewards are split across four benchmark pools and phones compete inside them. Pool names and your scores stay in Hub and the official benchmark material. Do not substitute the type line.