-
-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preventing hd counter reuse, Allow to spend such mints #1036
Conversation
This pull request introduces 2 alerts when merging d94f48b into 677b54c - view on LGTM.com new alerts:
|
This pull request introduces 2 alerts when merging dc2fd38 into 677b54c - view on LGTM.com new alerts:
|
This pull request fixes 3 alerts when merging 52b3dd0 into e2c8db6 - view on LGTM.com fixed alerts:
|
This pull request introduces 2 alerts when merging 2a44cab into 8192c5f - view on LGTM.com new alerts:
|
a650e53
to
4a69aa5
Compare
This pull request introduces 2 alerts when merging 1c00b8d into 8f01f63 - view on LGTM.com new alerts:
|
This pull request fixes 3 alerts when merging 50a0c74 into f488a2a - view on LGTM.com fixed alerts:
|
During Lelantus mint creation there was missing a check if a sigma mint with the same private data already exists on chain, and due to that there were created lelantus mints with reused HD counter. The check added.
As during spend serial number use check was done on both sigma and lelantus used serial sets, such lelantus mints became unspendable, After HF block we are checking sigma serials only on sigma used serial set, and lelantus serials only on lelantus used serial set.