benseed

Step 1: Libellious. Step 2: its no magic. its just maths. its not opaque. it has already been explain here. https://github.com/secp8x32/blog/blob/master/2020_05_26_secp256k1_twist_attacks/secp256k1_twist_attacks.md ..…

Hi everyone. Thank you for messaging me and giving me links. This method has now been solved. I was hinted by 1 of the user here on using the in build function of discrete logarithm problem function within sagemath. i…

I've come to realize that we can't attack SECP256k1 directly, but we can create a twist on the curve by introducing a new Y coordinate on the twisted version of the curve. I've already validated this using the public…

you make a very good point.

oh.. thanks for the info. i shall correct it now.

Just a quick update from a previous discussion here. I’ve included Taproot addresses now, among other things. So, here’s what I got: I really tried to make the code easy to read, so take a look and let me know what you…

i have read it. hmm.. some ideas are running in my head now. the formula he had used is essentially what had been done above. its the same. 2 random scalar values for r sig but the things said in there are really giving…

So, here’s the deal, the beginning of the script shows the usual way to create valid signatures using a private key with ecdsa secp256k1. There are tons of libraries out there that handle this too. What struck me is…

in case you need the full code i had use in sagemath.

I currently ran the program on i9 processor and a Nvidia 3090 GPU.

wow. Thank you. Please do. I still feel 6 weeks is too long though. I just got lucky.

yes the result is from real rsz from a dormant wallet of 8 years.

i did. it went i i did it went into some imaginary calculations that wasted my time, sometimes 2 days until i realize the calculations are not right.

OH

Hey all, I’ve been using this method from ecdsa123 to figure out the K nonce. After 6 weeks, I finally got the right k nonce (256 bits) using his approach. Just curious if there’s a quicker way to calculate k nonce. Can…

ah ok.. yeah... i was wondering why you put up old flaws...but yeah.. i get it now. you are right.

this flaw is a known flaw in old software. most version these days dont have these flaws. as k =will always be random.randint in the code these days

I put together an ECDSA secp256k1 Security toolkit to analyze how vulnerable signatures are to different attacks. This way, developers can get a clearer picture of their software's weaknesses. Honestly, I wish I could…

hi Cassandra. Yes I have received your dm.. thanks. Hey man. How are you. Long time no talk. Yeah... I hate that place. They hate me too. It's mutual. We argued a lot there. Coz the admins was pretty rude. So I hack one…

I was playing around with two signatures, both generated using different K nonces. As we all know, using different nonces won't lead to the right private key unless you reuse the same one. But I tweaked my code to…