# Nosana history after replacing a host identity

Reinstallation does not necessarily change the host identity; compare the actual address first. If the public key changed, old jobs remain associated with the old identity. A shared machine nickname does not merge two network identities.

- Canonical: https://iotahome.site/en/learn/nosana-replaced-host-address-history
- Publisher: IOTA Watch
- Topics: Nosana
- Published: 2026-10-26
- Updated: 2026-10-26

## At a glance

Reinstallation does not necessarily change the host identity; compare the actual address first. If the public key changed, old jobs remain associated with the old identity. A shared machine nickname does not merge two network identities.

## What to check

Before a change, save the public host address, last Job ID and time. After startup, compare the active address and inspect each identity in official records. Linking records in a device overview is an organizational step, not a migration of keys, jobs or NOS. Recovering a public history does not require uploading the old private key.

## Example

Example: gpu-1 keeps its name while address A changes to B. A can retain completed jobs while B starts at zero. Compare both addresses before concluding that the history was erased.

## Continue

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

## Sources and implementation

- [learn.nosana.com](https://learn.nosana.com/deployments/jobs/job_execution_flow)
- [dashboard.nosana.com](https://dashboard.nosana.com/)