-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Disallow key duplicates #12
Comments
Which key duplicates are we talking about? Node properties, cryptographic keys, or something else? |
I meant the secp256k1 public keys. The problem is that if a signature is given for a key, but that is repeated through the Miniscript it becomes really hard to reason about malleability. ~~See the linked issue for more details.~~
…-------- Original Message --------
On May 1, 2022, 8:17 PM, stickies-v wrote:
Which key duplicates are we talking about? Node properties, cryptographic keys, or something else?
—
Reply to this email directly, [view it on GitHub](#12 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AFLK3F6WX7AXOCEXUV5K3RTVH3DFJANCNFSM5UEWMZTQ).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
It should be trivial to check for now that we have the python-bip380/bip380/descriptors/__init__.py Lines 38 to 42 in 8aa1e2f
|
Where is the link? |
🤦 thanks for pointing that out @SomberNight. There was no link, and i don't remember what i was referring to now. We introduced this change in the C++ implementation in sipa/miniscript#116. |
No description provided.
The text was updated successfully, but these errors were encountered: