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
When doing a presentation on tokenization for a corporate client, a concern was raised that the use of a static retirement public key would allow for correlation of retirement events as having all been done by a single entity.
Need to allow both "Static" and "Pseudonymous" public keys, with the default being the pseudonymous one, where a new derivation of the public key is created each time.
Note this will have a significant impact on the verification of keys, as we'll have to test multiple possible derivations to determine if we have the matching secret key for a given public key.
The text was updated successfully, but these errors were encountered:
When doing a presentation on tokenization for a corporate client, a concern was raised that the use of a static retirement public key would allow for correlation of retirement events as having all been done by a single entity.
Need to allow both "Static" and "Pseudonymous" public keys, with the default being the pseudonymous one, where a new derivation of the public key is created each time.
Note this will have a significant impact on the verification of keys, as we'll have to test multiple possible derivations to determine if we have the matching secret key for a given public key.
The text was updated successfully, but these errors were encountered: