Accounting & consensus

The owner publishes signed finalized accounting. Independent validators verify the signature and chain evidence, resolve miner identities, calculate the same weights locally and submit with their own hotkeys. Signed accounting is authenticated operator input, not independent proof of customer payment or provider invoices.

#Shared epoch assignments

All validators read the signed assignment for the actual chain epoch from /mainnet/v1/validator/allocations/{chainEpoch}.json. It identifies one accounting report and its payload hash. Accounting windows and chain distribution epochs have different boundaries, so do not select reports from a validator-specific backlog.

Validators verify the chain epoch, historical boundaries, registration, permit, owner/burn target, constraints and identity before signing. A repeated accounting target can have a signed reuse/burn assignment rather than paying the same report twice. Missing feeds wait; they do not authorize invented zero-work reports or arbitrary older reports.

#Emission budgets and weight calculation

The active chain-miner-emission-v1 policy reconstructs the miner bucket from finalized alpha-out rates and emission splits. The reviewed mainnet miner share is approximately 33%, not an assumed 41% and not 33% of a 41% bucket. Validators independently check the signed emission evidence against chain history.

Approved work value, reviewed recovery adjustments and any published surcharge enter the report totals. Each validator recomputes the capped value allocation with exact arithmetic. See Rewards & emissions for the current quality uplift and recovery rules. Historical reports keep their original interpretation.

#What TEE verification covers

The worker/coordinator path verifies approved workload attestation, input binding, output integrity and signed receipts. Independent validators do not rerun generation models or receive miners' provider API keys. A TEE establishes execution evidence, not artistic quality or exact provider cost.

#Adding models

New model IDs alone do not require a validator upgrade. Public scores aggregate earningsMicrousd, surchargeMicrousd and job counts per miner; there is no validator model allowlist. The coordinator and workers still need the model contract, pricing, provider integration and valid receipt/accounting path.

A change to the signed report schema, reward semantics or verification rules can require a coordinated reader upgrade before the owner changes published reports. CLI, worker and validator releases are separate. A successful direct-provider generation is not automatically miner work.

#Consensus and payment

Identical report selection avoids one source of diverging weights, but Yuma consensus still depends on stake, timing and other validators. A finalized commit is not a reveal, applied weights are not a wallet receipt, and an approved recovery is not a confirmed repayment. Use finalized chain evidence for actual alpha credits.