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.
Understanding Signature Vulnerabilities
2 replies 451 views
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.
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.
Related topics
- Clipboard Vulnerabilities in Cryptocurrency Transactions 8
- Understanding the Differences Between Traditional and Simplified Chinese Mnemonics 6
- Understanding Square and Cube Roots in secp224k1 6
- Understanding Fees with Taproot Script Usage 3
- Issues with ripemd160 on Ubuntu 22 9
- New Bitcoin Improvement Proposal with $100 Reward 9