Latest posts of: Jean

Show Posts
Pages: « 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 »

161

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 14, 2020, 04:43:13 PM

@PietCoin97 You need a server with a powerful CPU and the needed RAM according to the number of DP bits you choose. It is good to have more RAM however than the computed Expected RAM. The server does not receive kangaroos from clients so no -ws. @HardwareCollector Thanks for the test Interesting, a key very near to the border 0x3FFFFFFFFFFFFFFFEFFFFF has taken more than 4 times more DP than expected: 2^21.75/2^19.55

162

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 14, 2020, 12:08:32 PM

I released the 1.5. I tested the windows server as much as I can with several clients, connection, re-connection, backup, linux clients... It seems to work rather well. Thanks for testing it

163

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 13, 2020, 06:39:57 PM

I made an other fix 1.5alpha3, hope it solve the issue. I will also get rid of from the Windows error message system which is quite inconvenient ! A client cannot solve a key as it does not perform collision check, it just calculate path and send DP to the server.

164

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 13, 2020, 02:22:44 PM

Yes the problem is the server. if it gets too much points it will slow down all clients. You have to carefully deal with the distinguished bit number in order to avoid to flood the server and get a reasonable TMTO. The server needs RAM and a powerful CPU. At the server side the insertion and collision check is not parallelized (difficult to do). Still possible to have several servers and to merge work files coming from servers.

165

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 13, 2020, 01:49:27 PM

Quote from: Jean_Luc on May 13, 2020, 01:28:12 PM I managed to reproduce the issue with the windows server. I'll have a look on that Fixed in 1.5alpha2

166

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 13, 2020, 01:28:12 PM

I managed to reproduce the issue with the windows server. I'll have a look on that

167

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 13, 2020, 12:54:01 PM

Thanks for the test A http like connection is very unefficient. I tried this first but it slows down the client. I will see what I can do. I didn't try through a ssh tunnel.

168

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 13, 2020, 12:35:28 PM

lol Not very good ! The error messages with windows are the hell with FormatMessage() and MAKELANGID Could you starts the server and post the full ouput ? Same for one client Thanks

169

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 13, 2020, 11:56:01 AM

Done Release 1.5alpha https://github.com/JeanLucPons/Kangaroo/releases

170

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 13, 2020, 11:22:42 AM

A first draft of the client/server is ready on github (source only). The client and server can be run on both windows or linux. There is few words on the readme. Thanks to test it

171

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 13, 2020, 02:29:59 AM

Hi, I'm working on the client/server solution. Almost ready, commit probably tomorrow. Difficulty to find an efficient protocol for handling dead kangaroo and server backup. @MrFreeDragon HT Max : 9 [@ 01598C] HT Min : 0 [@ 000003] HT Avg : 0.88 HT SDev : 0.94 This is the distribution of DP in the HashTable: 9 DP at hash 01598C (largest entry) 0 DP at hash 000003 (smallest) 0.88 DP per hash in average 0.94 standard deviation of DP distribution in the HashTable @Hardware collector: I'm sure you will solve the #110 With the client/server version, only the server (without GPU) will need a large amount of memory. @arulbero I didn't worked yet on endomorphism optimization and studied your proposal. I will be on holidays (in mountains, far from computer) the next week, I would like to try to publish the client/server release first...

172

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 11, 2020, 05:32:18 PM

Quote from: PietCoin97 on May 11, 2020, 03:56:59 PM Here is loaded file with new code So it takes now up to 6sec to transfer the kangaroos, try with a timeout of ~10sec. I don't know if cuda can do parallel transfer on multiple GPU... I'll add a way to set the up the timeout in the next release and see if I can speed up more this data transfer...

173

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 11, 2020, 02:39:05 PM

I did a small patch to try to speed up kangaroo transfer and also changed the timeout to 3 sec. Could you try it and tell me if it improves something ?

174

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 11, 2020, 01:28:55 PM

When you save kangaroo, the CPU has to get back all kangaroos from GPUs memory this might be long. Could you reload a work and post the output ?

175

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 11, 2020, 01:13:19 PM

I presume you are using -ws and you have lots of kangaroos, may be multiple GPU ?

176

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 11, 2020, 01:10:28 PM

Do you have this error always or only from time to time ?

177

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 11, 2020, 01:00:59 PM

Try to change the timeout to 3000. Code: int timeout = 3000;

178

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 11, 2020, 12:20:33 PM

Multiple search is possible but I won't work on it first. I will work on a distributed client/server version. The #110 will be likely solved soon. With the distributed version, I'm almost sure the #115 will also be solved.

179

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 11, 2020, 03:54:28 AM

Good luck to solve the puzzle #110, I have the felling that It will be found very soon Wink

Take care of well configuring the 109bit range:

Puzzle #110: 109bit 12JzYkkN76xkwvcPT6AWKZtGX6w2LAgsJg

Code:

2000000000000000000000000000
3FFFFFFFFFFFFFFFFFFFFFFFFFFF
0309976ba5570966bf889196b7fdf5a0f9a1e9ab340556ec29f8bb60599616167d

Ex for puzzle #80 (79bit key) 1BCf6rHUW6m3iH2ptsvnjgLruAiPQQepLe

Code:

80000000000000000000
FFFFFFFFFFFFFFFFFFFF
037E1238F7B1CE757DF94FAA9A2EB261BF0AEB9F84DBF81212104E78931C2A19DC

Code:

:\C++\Kangaroo\VC_CUDA10>x64\Release\Kangaroo.exe -d 17 -t 0 -gpu in79.txt
Kangaroo v1.4
Start:80000000000000000000
Stop :FFFFFFFFFFFFFFFFFFFF
Keys :1
Number of CPU thread: 0
Range width: 2^79
Jump Avg distance: 2^38.96
Number of kangaroos: 2^18.58
Suggested DP: 20
Expected operations: 2^40.60
Expected RAM: 496.9MB
DP size: 17 [0xFFFF800000000000]
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(12x256) (45.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
SolveKeyGPU Thread GPU#0: 2^18.58 kangaroos [2.0s]
[159.53 MK/s][GPU 159.53 MK/s][Count 2^39.82][Dead 0][01:55:44 (Avg 02:54:02)][228.4/292.0MB]
Key# 0 [1S]Pub:  0x037E1238F7B1CE757DF94FAA9A2EB261BF0AEB9F84DBF81212104E78931C2A19DC
       Priv: 0xEA1A5C66DCC11B5AD180

Done: Total time 01:55:48

I will have a look if i can do something with endomorphism.

180

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: May 10, 2020, 11:50:21 AM

Thanks for the info I didn't look at all addresses, the #110 is the only one remaining with the pub key exposed ?

Pages: « 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 »