You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hash which is used at Role is useing hashCode instead of a cryptographic hash.
hashCode is not guaranteed to be determinisitic across JVM implementations and versions so we must not use that in any consensus relevant use case. The hash for Role seems to have not much usage atm but will likely get more at least for arbitrators, mediators and maybe seed node operators. So better to fix that before the mainnet launch...
The text was updated successfully, but these errors were encountered:
The consequences with the change with the current data and network is that a because of the hash change a bonded role is not found anymore and interpreted as bonded reputation.
If a bonded role was locked up it cannot be revoked in the UI. So when we add this change there can be smaller confusions but it should not break consensus.
The hash which is used at Role is useing hashCode instead of a cryptographic hash.
hashCode is not guaranteed to be determinisitic across JVM implementations and versions so we must not use that in any consensus relevant use case. The hash for Role seems to have not much usage atm but will likely get more at least for arbitrators, mediators and maybe seed node operators. So better to fix that before the mainnet launch...
The text was updated successfully, but these errors were encountered: