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.
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.