# Gonka weight changes at epoch boundaries

Weight belongs to a host within an epoch. A new participant list, model assignment or weight is not itself a deduction from the previous epoch. GNK payment requires separate settlement records.

- Canonical: https://iotahome.site/en/learn/gonka-epoch-rollover-weight-history
- Publisher: IOTA Watch
- Topics: Gonka
- Published: 2026-10-26
- Updated: 2026-10-26

## At a glance

Weight belongs to a host within an epoch. A new participant list, model assignment or weight is not itself a deduction from the previous epoch. GNK payment requires separate settlement records.

## What to check

Capture the host address, epoch number, phase, model, weight and source time on each side of the boundary. Compare dashboards only after matching epochs. If one source still serves the previous epoch, preserve its timestamp rather than carrying that value into a blank current-epoch field. This distinguishes a stale snapshot from a change in participation.

## Example

Example: a host has weight in epoch 100 but is absent from the current view of 101. Record the absence at that observation time and follow 101’s later stages. The weight difference does not provide a measured GNK loss.

## Continue

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

## Sources and implementation

- [gonka.ai](https://gonka.ai/docs/host/network-node-api/)
- [gonka.gg](https://gonka.gg/network)