dan2015

Thanks a ton! I’ll check it out.

Here's some code if anyone wants to test it with smaller numbers. Just tweak the values and curves as needed.

The index calculus algorithm is designed for large exponents. It doesn't really work well with small numbers.

Hey all, I'm curious if there are better methods to improve my Index Calculus Algorithm. Is what I have the best optimization? Would love to hear your thoughts. Here’s my code.

Received your script! Give me a day to check it out and I'll get back to you. Appreciate it. By the way, if anyone wants my Nonce Recurrence Attack script, I’ve got it here. It uses a generator, not the enhanced…

Hey everyone, I'm trying to improve the Nonce Recurrence Attack. I checked out a paper on it, but I wanna take it a step further. I need to figure out how to make some fake signatures that still link to the same public…

I skimmed that. Got some ideas brewing now. The formula mentioned is basically what I've been talking about, same concept. Two random scalar values for the r sig, but the stuff mentioned there is sparking some theories…

So, here's the deal. I figured out that you can usually create valid signatures with the private key for ecdsa secp256k1. There are libraries out there for this. But I noticed something interesting... if you keep the…

Thanks a ton!!

Got it, thanks a lot! But I still can't verify the K value I found. Your method only tells me if K+ or K- is right. I need code to brute-force the K value, what can I do?

So you're suggesting I rewrite it that way?

How do I check if the K value I got is right for an R signature and public key? I'm really struggling with it. Can someone help me out?

how do i add crypto payments to my website? like if i run a major site and wanna accept bitcoin or ethereum. is there any easy way to do this or do i need to build something from scratch?

you do realize that r = aG + bQ gives a valid signature for the right public key, right? if it’s not valid, like if the pubkey doesn’t match, then the signature could be valid according to ecdsa secp256k1 but totally…

looking at that formula again, once you have different a and b, you still land on the same r with different s and z. usually when using the same K nonce, r stays the same but you end up with different u1 and U2 values…

so, valid signatures are made like this: a = random, b = random, r = aG + bQ, and then s = r * modinv(b, N) % N and z = a * s (b, N)% N. but how do we achieve the same r while getting different s and z? I've been trying…

Just built a suite for ECDSA secp256k1 to see how signatures hold up against various attacks. It's aimed at helping devs spot weaknesses in their code. Honestly, I wish I could include every known issue but time's been…

Yeah, I could see that happening. If they ever drop S2 upgrade kits with the original specs, S4+ and S5 won’t sell at all.

you gotta download or clone the file from here and put it in the same folder as the LLL program. also, remember to use ice_secp256k1.dll or.so if you're on linux. check it out: https://github.com/iceland2k14/secp256k1

No point in running this. The RSZ generated won’t link to the correct private or public key. I tried it ages ago and it didn’t work.