Rewards & emissions

Serving value, provider expense, weight allocation and received alpha are different quantities. Everycli earnings is coordinator accounting, not a wallet receipt or guaranteed USD income.

Accepted output → Review approval → Finalized accounting → Shared assignment
→ Validator weights → Commit/reveal/application → Actual chain alpha credits

#What counts as work

Work counts after acceptance with a verified receipt and validated output, review approval and reward eligibility for genuine eligible demand. Failed, unknown, expired, disputed, synthetic and review-held work does not count as approved earnings.

Recognition is exactly once through the immutable job/attempt ledger. Work reviewed after its original window can enter a later closed report. Administratively disabled miners are excluded; going offline after completing work is different from an administrative disable.

The amount is the discounted reward target locked at assignment, not a provider invoice. New bids and prices do not retroactively reprice it.

everycli jobs --status completed --limit 20
everycli earnings

#Value-capped allocation

work_i       = approved earnings_i + reviewed recovery_i + surcharge_i
pool_usd     = reconstructed miner alpha bucket × report alpha/USD price
weight_i     = work_i / max(pool_usd, sum(work))
unused_share = 1 - sum(weight_i)

The active chain-miner-emission-v1 policy reconstructs the miner bucket from finalized per-block alpha-out rates and chain emission splits. The reviewed SN117 miner share is approximately 33%: not fixed at 41%, not 33% of 41%, and not inferred by halving an owner-cut remainder. Historical reports retain their original policy and prices.

For a $100 pool and $30/$20 of total approved values, allocations are 30%/20% with 50% unused. With $120/$80 of values, capped allocations are 60%/40%, before integer rounding. These illustrate accounting, not promised wallet receipts.

Unused weight goes to the chain-resolved owner target under the chain's Recycle or Burn setting. The historical cap-and-burn name does not mean every mainnet allocation is literally burned.

#Quality uplift

The owner accounting policy reviewed 31 October 2026 adds a surcharge on current approved work: a 5% base, rising toward 20% for reliable service across multiple providers. It looks back seven days, requires at least five counted attempts for additional credit, and reaches full provider coverage at three successfully served providers. Reliability credit scales from 80% to 95% accepted attempts, subject to excluded failure reasons.

Available pool capacity can reduce the uplift. Recoveries do not receive another uplift. The signed score includes the surcharge, allowing compatible independent validators to calculate the same weights with the existing report format.

The policy can change through reviewed future accounting. It does not eliminate consensus/timing effects or guarantee reimbursement, margin or a fixed alpha amount. Saving unused API keys alone is not successful multi-provider service.

#Accounting and chain application

Accounting windows use fixed tempo + 1 block intervals; actual distribution epochs have different boundaries. All validators follow the same signed assignment per chain epoch, rather than their own local report backlog. See accounting and consensus.

Missing signatures, prices or chain evidence defer publication/verification. An unpublished feed is not a zero-work report. A genuine empty window or signed scheduled reuse can produce an owner-only vector, called a burn-only vector in older tooling, when chain constraints permit it.

A finalized commit is not a reveal; applied weights are not a wallet receipt. Previous weights can remain effective while new ones are pending. Emissions, stake, other validators and Yuma consensus affect actual receipts.

#Historical recovery

A skipped owner report does not prove zero payment: other validators or previous weights can still produce alpha. Corrections require reviewed chain receipts and complete original work records.

Conservative FIFO reconciliation credits all verified alpha against the oldest eligible work first at each original report's alpha/USD price. It queues only the matured remainder, rejects reused receipts/sources and excludes market-price losses.

Approved recovery enters future accounting from remaining capacity after current work and its applicable uplift. Recipients must remain eligible; an unavailable recipient remains owed rather than invalidating unrelated work. Independent validators consume the shared report, not private owner recovery tools or historical weight replays.

Approval, sealing, submission and reveal are not confirmed repayment. Recovery is a reviewed correction mechanism, not a blanket promise to compensate any historical difference.

#Check actual rewards

Use the leaderboard for serving/accounting and network status. Verify actual alpha with the correct wallet, UID/hotkey, period and finalized chain records. Work value and present-day token value are not interchangeable.

Use your own coldkey. Recipients associated with the subnet owner's coldkey are not independent miner recipients. Provider and hosting bills remain yours; traffic and profit are not guaranteed.