mr_byte

If you're working with just one signature, I’d say it’s similar to Puzzle #136 if you already have the public key.

Are you talking about that Telegram group from ttdsales? I’ve been checking out kafeitianshi’s submissions. He’s been grinding hard for months, but I never chatted with him. There’s this flaw that lets users take out…

Only the puzzle creator knows the private key, right? Seems a bit too boring for them to exploit it personally though. I mean, who has that much time? But yeah, if the pool gets rekt because of this, it’s not cool.

Here are the base points and pubkey examples for nonces: First r, s, z: ('BP', (11558356594904916434672200454110459815025629227368860738740180068802059155766:…

Thanks for sharing! But, what exactly are nonces?

Try it Example, find signing secret. https://rawcdn.githack.com/nlitsme/bitcoinexplainer/aa50e86e8c72c04a7986f5f7c43bc2f98df94107/ecdsacrack.html My RSZ, K , Private Key is correct

It’s r from k, not the X coordinate of public key with private key. To find k, you need to know rsz + private key. pvk = (inv(r) * ((k*s)-z)) % N k = (inv(s) * (z + r * pvk)) % N s = (inv(k) * (z + r * pvk)) % N r =…

k = (inv(s) * (z + r * pvk)) % N s = (inv(k) * (z + r * pvk)) % N pvk = (inv(r) * ((k*s) z)) % N r * pvk = ((k*s) z) % N So yeah, R, S, Z, private key, and k can all be odd or even. But like, how do we get past that…

Hi, I want to try your code with these rsz: 1: r = 0x57a463b8ac30f2ed36767d5ccabf04fbe29c94b054b4309996f086556428c748 s = 0x5a4c7e96159688e8cd2525a3230ec5184597d6cfbaf037ca5815fa01097f67cc z =…

Try with your actual 6 weeks search rsz and let us know how long it takes to find k using cuda bsgs or cuda kangaroo.