Understanding Signature Vulnerabilities

2 replies 763 views
nickomegaSenior Member
Posts: 1 · Reputation: 1454
#1Aug 7, 2021, 02:24 AM
So I found this crazy long number, kinda looks like a key or something, anyone know what this is? 57693594628803274708875609257689291793313896681711523793281764510965395518430 It has a hex version too... 0x7f8d6ad886348454c238ca49ef01c7fde83925372c414e9e98827ea204ae73de. Just curious.
10 Reply Quote Share
m1kes4tFull Member
Posts: 168 · Reputation: 252
#2Aug 7, 2021, 02:47 AM
Sharing the same z value among multiple signatures doesn't mean they're at risk. If that were true, think of all the multi-signatures and Lightning Network channels that would be compromised. That's not how it works. Just because two signatures share a message doesn't expose them to vulnerabilities. Check out this thread for more clarity: Exposing private key by signing the same message twice? But don’t bump that old one, better to keep it here.
2 Reply Quote Share
mr_apeNewbie
Posts: 407 · Reputation: 35
#3Aug 7, 2021, 05:37 AM
Right, the ECDSA equation is s = k−1(z + r*d) (mod n). We always have s, z, and r for any signature, so even if z is the same, it doesn't really help to crack anything. Now, if r is the same across signatures, that’s a different story because it points to the same k, reducing variables. But just the z? Nah, not a big deal.
7 Reply Quote Share

Related topics