Phone Farm

Loading fleet overview

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

Resolving route12%

Acurast Pulse

Loading live view

Syncing chain state, reward ledgers, and fleet telemetry.

Resolving route12%

Manager Phone Earnings #1859 | Acurast Pulse

#1859·5Gnxcb5y...yGXwLy·Phone Earnings

Staking

Farm payout

0.095115 ACU

epoch 3,885 · 1 hrs ago

Boost benefit

+0.004234 ACU

100.0% boosted · network 72.2%

5 of 5 devices · +11k compute

Reward basis total

91,926,083,109

epoch 3,885 · 5 devices positive basis

Epoch alignment

Aligned

payout 3,885 · contribution 3,885

Eligible devices

must heartbeat in epoch 3,884

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

5Gnxcb5y...yGXwLy block #3,496,526

Aligned allocation

Uses the exact retained farm payout and exact on-chain per-device reward-basis share from the same epoch. Devices are only included if they had a retained processor heartbeat in the previous epoch and have positive reward basis.

exact share basis

50 rows 100 rows 250 rows


5D1dpKKvai...ESacjFYpUnknown device	unknown+10% boost · 23,646 → 26,010	19,471,800,393version unknown	21.1820%	0.020147 ACU	3,885	—
5EoK9TC18x...yNLpcBK3Unknown device	unknown+10% boost · 23,198 → 25,518	19,051,148,432version unknown	20.7244%	0.019712 ACU	3,884	—
5E1Z6CMHWw...WZuBUcvJUnknown device	unknown+10% boost · 23,488 → 25,837	18,907,199,164version unknown	20.5678%	0.019563 ACU	3,884	—
5HEQstEe2f...CBeSY5yzUnknown device	unknown+10% boost · 22,849 → 25,134	18,768,797,659version unknown	20.4172%	0.019419 ACU	3,884	—
5FXQYzC5zJ...EkAtsDmDUnknown device	unknown+10% boost · 19,412 → 21,353	15,727,137,461version unknown	17.1084%	0.016272 ACU	3,884	—

5D1dpKKvai...ESacjFYpUnknown device

0.020147 ACUunknown+10% · 23,646→26,010

Reward basis19,471,800,393

Basis share21.1820%

Epoch3,885

Heartbeat—

5EoK9TC18x...yNLpcBK3Unknown device

0.019712 ACUunknown+10% · 23,198→25,518

Reward basis19,051,148,432

Basis share20.7244%

Epoch3,884

Heartbeat—

5E1Z6CMHWw...WZuBUcvJUnknown device

0.019563 ACUunknown+10% · 23,488→25,837

Reward basis18,907,199,164

Basis share20.5678%

Epoch3,884

Heartbeat—

5HEQstEe2f...CBeSY5yzUnknown device

0.019419 ACUunknown+10% · 22,849→25,134

Reward basis18,768,797,659

Basis share20.4172%

Epoch3,884

Heartbeat—

5FXQYzC5zJ...EkAtsDmDUnknown device

0.016272 ACUunknown+10% · 19,412→21,353

Reward basis15,727,137,461

Basis share17.1084%

Epoch3,884

Heartbeat—

Showing 1-5

Excluded Devices1

These devices are managed by the farm but were excluded from derived payout because they did not satisfy the previous-epoch heartbeat rule or had zero reward basis.

Device	Reason	Reward Basis	Prev Epoch Heartbeat
5CFoDzVXVL...SNGPQ5giUnknown device	No previous-epoch heartbeat	0	No

How This Page WorksFAQ

What is exact?

Farm payout is exact from the retained manager reward transfer. Device reward basis is exact from the live on-chain processor rewardContribution field, and is shown here 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 3,885 on this page: derived_payout = 0.095115 * (device_basis / 91,926,083,109)

When is it strongest?

When payout epoch and reward-basis epoch match. That means the device share basis and the farm payout belong to the same epoch.

Who is eligible?

A device must have a retained processor heartbeat in the previous epoch and a positive reward basis to appear in the payout table.

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.