# IOTA contribution after a new training run starts

Live throughput belongs to the selected training run; accounted rewards can cover earlier runs. A new run, a layer change or re-entry into a participant list can change the current contribution display. A smaller live value alone does not establish that previously recorded rewards were removed.

- Canonical: https://iotahome.site/en/learn/iota-new-run-previous-contribution
- Publisher: IOTA Watch
- Topics: IOTA
- Published: 2026-10-26
- Updated: 2026-10-26

## At a glance

Live throughput belongs to the selected training run; accounted rewards can cover earlier runs. A new run, a layer change or re-entry into a participant list can change the current contribution display. A smaller live value alone does not establish that previously recorded rewards were removed.

## What to check

Record the Miner ID, run identifier, layer and source time before comparing screenshots. Open training history and rewards separately. Compare contribution within the same run and ledger amounts within the same date range. Use a coldkey for payout checks, not as a replacement for the Miner ID. A screenshot without a run identifier cannot resolve a run-boundary discrepancy.

## Example

Example: run A has historical contribution while run B has just opened at 0 tokens/s. Check whether B has assigned work before diagnosing a stopped trainer. Review A’s ledger over A’s dates. Adding instantaneous rates from different runs cannot reconstruct rewards, and a run transition alone is not a reason to reinstall the application.

## Continue

[Open project monitor](https://iotahome.site/en/projects/iota)

## Sources and implementation

- [iota.macrocosmos.ai](https://iota.macrocosmos.ai/)
- [docs.macrocosmos.ai](https://docs.macrocosmos.ai/product-and-services/tah/tah-user-guide)
