Description
The fix for non-deterministic HashLock (replacing System.HashCode with deterministic IncrementalHasher) changes all computed HashLock values. Users with [NexusVersion(HashLock = ...)] attributes will get NEXNET019 errors after upgrading and must regenerate their HashLock values.
Location
Release notes / changelog for the next release.
Diagnostics
NEXNET019 error message provides the new correct value: "The NexusVersion on '{name}' does not match the calculated HashLock of '{value}'"
What Has Been Tried
The fix is merged. This issue tracks the documentation follow-up.
Gathered Information
- HashLock is compile-time only; no wire protocol impact
- The old values were non-deterministic (random per build), so any existing values were already unreliable
Suggested Approach
Add a breaking change note explaining that HashLock values must be regenerated after upgrading. Users can get the new value from the NEXNET019 error message.
Description
The fix for non-deterministic HashLock (replacing
System.HashCodewith deterministicIncrementalHasher) changes all computed HashLock values. Users with[NexusVersion(HashLock = ...)]attributes will get NEXNET019 errors after upgrading and must regenerate their HashLock values.Location
Release notes / changelog for the next release.
Diagnostics
NEXNET019 error message provides the new correct value: "The NexusVersion on '{name}' does not match the calculated HashLock of '{value}'"
What Has Been Tried
The fix is merged. This issue tracks the documentation follow-up.
Gathered Information
Suggested Approach
Add a breaking change note explaining that HashLock values must be regenerated after upgrading. Users can get the new value from the NEXNET019 error message.