Search content
Sort by

Showing 5 of 5 results by superkatchu
Post
Topic
Board Development & Technical Discussion
Re: Pollard's kangaroo ECDLP solver
by
superkatchu
on 10/11/2021, 10:51:45 UTC
I've shared the basic pseudo code for RSA Bruteforce below. Can you please write a basic pseudo-code for this method?

You cannot solve RSA problems with the Kangaroo method because the ECDLP problem is not applicable for RSA, as there are no logarithms to solve for.

Not ECDLP but DLP so Pollard Rho and Pollard Kangaroo should be applicable no?
Post
Topic
Board Development & Technical Discussion
Re: 64. Can the Transfer of the Inventor of the Puzzle Be Manipulated?
by
superkatchu
on 30/10/2021, 16:01:04 UTC
Doubt. The creator of this puzzle is a very early adopter (if not even satoshi) and he probably has many, many more BTC than this puzzle is worth right now.
Post
Topic
Board Development & Technical Discussion
Merits 2 from 1 user
Re: ASAP how to get bulk r,s,z from bitcoin signatures ?
by
superkatchu
on 30/10/2021, 10:47:21 UTC
⭐ Merited by ETFbitcoin (2)
Oh man. Don't waste your time. There is a whole paper about trying to crack wallets by using the lattice attack. They tried most transactions already... . Try something new.
If you want to try anyways: best way is to modify bitcoin core  so it saves all transactions r,s,z to a file. I have those modifications but won't give them away for free.
Post
Topic
Board Development & Technical Discussion
Re: Pollard's kangaroo ECDLP solver
by
superkatchu
on 09/10/2021, 21:30:54 UTC
PureBasic executables get false positives cause some ransomware used PureBasic. You can search it with google.
Post
Topic
Board Bitcoin Discussion
Re: 120 puzle. Share 1.2 BTC 50/50 !!! ASAP Please !!!
by
superkatchu
on 12/09/2021, 02:12:22 UTC
Hi,
your upper range in searchspace is around 116 bit.

As you don't know in which bitrange the key is exactly to be found it will increase the searchtime.
I don't have the math but I think when using pollard kangaroo and you don't know the exact bitrange (somewhere between 1-116 bit), you will increase searchtime to the same (if not even more) as a regular 120bit key. BSGS will need too much memory and prepocessing time.

You might expose your calculations for the target key so people can audit and you could get more feedback.