Phone Farm

Loading fleet overview

Streaming live processor telemetry, deployment assignments, and reward history for this manager.

Loading page data…

Acurast Pulse

Loading live view

Loading the latest available information.

Loading page data…

Manager Phone Earnings #2708 | Acurast Pulse

Phone earnings

Manager #2708 · Latest completed epoch 5594

Heartbeat history ↗

Farm payout: 0 ACU
Heartbeat fees: —
After heartbeat fees: —
Included in payout: 0 / 3

#2708·Manager 2708·Phone Earnings

Staking

Showing the last completed payout epoch 5594. View older epochs in the heartbeat calculator.

Payout epoch 5594 uses reward basis from epoch 5593. Heartbeat fees cover payout epoch 5594. 0 of 3 current devices were included; the remaining 3 have no payout share because they were not present in that historical reward-contribution snapshot. Device status and last heartbeat are current.

Reward basis total

epoch 5,593 · 0 devices positive basis

Epoch alignment

Pending

payout 5,594 · contribution 5,593

Phone Earnings AllocationExact on-chain per-device reward basis, allocated by each device's share of that reward basis.

Historical payout allocation

Uses the retained completed farm payout and the historical reward-basis shares that produced it. Per-phone payouts are derived allocations, not individual on-chain transfers.

verification pending

HB fees are matched to payout epoch 5594. Missing fee breakdowns stay unknown. Derived net is shown only when the payout and its corresponding reward basis are verified; it excludes marketplace fees, electricity and hardware costs.

Heartbeat counts cover payout epoch 5594. “Without metrics” means an empty metrics payload, not proof of a deployment. Unclassified payloads count toward the total only. A dash means the breakdown is unavailable or still backfilling.

Find a phonePhone modelSort all phones

0 matching of 0 eligible phones · Showing 0–0. Sorting applies to all matching phones, before pagination.

Loading phone models: 0/3. Earnings and fleet-wide sorting are available.

No managed devices with current contribution state were available for this phone farm.

Devices without payout share3

These current fleet devices received no share of this completed payout. A device can be absent from the historical reward-contribution snapshot, or have a recorded zero reward basis.

Device	Why no payout share	Reward Basis
5DZrk7iXT8...AbWvtPY7Unknown device	Not included in reward-contribution snapshot for epoch 5593	0
5FY69BZbFt...Tjesd1RzUnknown device	Not included in reward-contribution snapshot for epoch 5593	0
5H3gtpQUPF...Ch1LSUrtUnknown device	Not included in reward-contribution snapshot for epoch 5593	0

How This Page WorksFAQ

What is exact?

Farm payout is exact from the retained manager reward transfer. Device reward basis comes from the retained historical snapshot for a completed epoch, or the on-chain processor rewardContribution field for a live allocation. It is shown in raw basis units rather than ACU.

What is derived?

Derived device payout is calculated by allocating the exact farm payout across devices using each device's exact reward-basis share.

Formula

Device basis share = device reward basis / total farm reward basis.

Derived device payout = exact farm payout × device basis share.

derived_payout = farm_payout * (device_basis / farm_basis_total)

For epoch 5,594 on this page: derived_payout = 0 * (device_basis / 0)

When is it strongest?

When the completed payout is linked to its retained reward basis from the preceding epoch, and heartbeat fees for the payout epoch are verified.

Who is eligible?

A device must have positive reward basis in the retained historical snapshot. Phones without retained basis are not assigned an invented payout.

Why can this differ from canonical phone payout?

The chain exposes exact processor reward basis and exact farm payout, but not a long historical canonical per-phone payout ledger. This page shows the best aligned allocation model from those exact inputs.