Pages:
Author

Topic: Pollard's kangaroo ECDLP solver - page 55. (Read 60381 times)

full member
Activity: 1232
Merit: 242
Shooters Shoot...
May 23, 2021, 07:01:15 PM
So what does 256 bits look like stored in a work file, I need to see an example.

AF4560D2458D74B963C5F3B7FD7A65ECF6A860C23BD1AC97B3A1121B2BC657D8 F1978DCDCDCDCC8D76C8C5DC5D85CD5C765C5D7C57D5C7D5C57D5C75D7C57D5C

256bits (space) 256bits
full member
Activity: 706
Merit: 111
May 23, 2021, 06:00:53 PM
So what does 256 bits look like stored in a work file, I need to see an example.
newbie
Activity: 33
Merit: 0
May 23, 2021, 05:51:43 PM
Well it seems that each A100 is about 2.5 - 3 times faster than V100 so I won't even try for now. I have to ask my professor and it's going to be a pain accessing it anyway.

But it's interesting how computing power is basically the only thing required. I guess is just a matter of time until someone with access to a supercomputer might give it a try...

...and then get arrested like this guy? https://www.itnews.com.au/news/csiro-it-contractor-spared-jail-for-mining-monero-on-supercomputer-553535  Grin

On a more serious note, the software will have to improve to a level where it's not experimental before people start investing their resources into it.

Agree 100%. All sorts of people are resorting to crime, using resources without authorization, simply for profit. The reality is that it may very well work for a while but chances are statistically high that they will get a visit from the authorities. Anything related to crypto is by design built to leave 'some' traces. It's not a good business to steal computing power - whether that's for mining, things like this puzzle or anything related to crypto, really. They're just too many variables involved in terms of security and I'm not really sure who's dumb enough to think they will get away with it.   
full member
Activity: 1232
Merit: 242
Shooters Shoot...
May 23, 2021, 05:08:29 PM
Well it seems that each A100 is about 2.5 - 3 times faster than V100 so I won't even try for now. I have to ask my professor and it's going to be a pain accessing it anyway.

But it's interesting how computing power is basically the only thing required. I guess is just a matter of time until someone with access to a supercomputer might give it a try...

...and then get arrested like this guy? https://www.itnews.com.au/news/csiro-it-contractor-spared-jail-for-mining-monero-on-supercomputer-553535  Grin

On a more serious note, the software will have to improve to a level where it's not experimental before people start investing their resources into it.
What was the speed of your version?  Wasn't it a lot slower than Jean Luc's?

So with your version people can store 256 bits in the work files, right? Is that the only difference?

If so, I am not sure why people are using yours, especially if it is slower than the original.  If it is faster, I still don't know why they would use it for the puzzle since it will require more RAM/storage space.

Please enlighten me NotATether...I truly can't remember the speed and the differences in your version.
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
May 23, 2021, 04:28:13 PM
Well it seems that each A100 is about 2.5 - 3 times faster than V100 so I won't even try for now. I have to ask my professor and it's going to be a pain accessing it anyway.

But it's interesting how computing power is basically the only thing required. I guess is just a matter of time until someone with access to a supercomputer might give it a try...

...and then get arrested like this guy? https://www.itnews.com.au/news/csiro-it-contractor-spared-jail-for-mining-monero-on-supercomputer-553535  Grin

On a more serious note, the software will have to improve to a level where it's not experimental before people start investing their resources into it.
newbie
Activity: 33
Merit: 0
May 23, 2021, 02:09:33 PM
Well it seems that each A100 is about 2.5 - 3 times faster than V100 so I won't even try for now. I have to ask my professor and it's going to be a pain accessing it anyway.

But it's interesting how computing power is basically the only thing required. I guess is just a matter of time until someone with access to a supercomputer might give it a try...
full member
Activity: 1232
Merit: 242
Shooters Shoot...
May 23, 2021, 01:42:36 PM
I am not too sure how to calculate this, if someone can help me.

We have at the Uni one NVIDIA DGX A100

It packs 5 petaFLOPS, eight A100 GPUs with 320GB of GPU memory.

Realistically, if we get permission to run it 24/7 (which I doubt lol) for the 120 key, how long would it take? Is it feasible? And more important, would the Kangaroo even work on it?


Just run them and see how long the program tells you til it solves. The estimated time is pretty close to being accurate. No way to know since I don't know the speed and grid size of the A100s.
full member
Activity: 1232
Merit: 242
Shooters Shoot...
May 23, 2021, 01:39:00 PM
I am not too sure how to calculate this, if someone can help me.

We have at the Uni one NVIDIA DGX A100

It packs 5 petaFLOPS, eight A100 GPUs with 320GB of GPU memory.

Realistically, if we get permission to run it 24/7 (which I doubt lol) for the 120 key, how long would it take? Is it feasible? And more important, would the Kangaroo even work on it?

I remember WanderingPhilosipher saying that 256 V100's that were running simultaneously for several years only exhausted 15% of #120, and regardless of how faster an A100 is versus a V100, 8 of them definitely won't make the cut.

And you also have to worry about making Kangaroo dump the private key to a file (if it even supports that without stdout redirects), or you'll lose the key if your terminal session is disconnected.
Negative, that was for #64, using Bitcrack...not #120 using Kangaroo.  And it's the #64 pool that has been set up for a few years and I know that the 256 V100s have ran for weeks at a time along with other cards. Last I checked it was around 15% of total keys checked for #64.

I do not know if Zielar is running his V100s at #120.
newbie
Activity: 33
Merit: 0
May 23, 2021, 12:43:54 PM
Several years? Wow.

On GitHub here https://github.com/JeanLucPons/Kangaroo it says 2 months with 256 V100's. Must be wrong then - someone ought to correct that.  

I'll also ask our researchers and get back on this.


legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
May 23, 2021, 12:36:20 PM
I am not too sure how to calculate this, if someone can help me.

We have at the Uni one NVIDIA DGX A100

It packs 5 petaFLOPS, eight A100 GPUs with 320GB of GPU memory.

Realistically, if we get permission to run it 24/7 (which I doubt lol) for the 120 key, how long would it take? Is it feasible? And more important, would the Kangaroo even work on it?

I remember WanderingPhilosipher saying that 256 V100's that were running simultaneously for several years only exhausted 15% of #120, and regardless of how faster an A100 is versus a V100, 8 of them definitely won't make the cut.

And you also have to worry about making Kangaroo dump the private key to a file (if it even supports that without stdout redirects), or you'll lose the key if your terminal session is disconnected.
newbie
Activity: 33
Merit: 0
May 23, 2021, 11:22:36 AM
I am not too sure how to calculate this, if someone can help me.

We have at the Uni one NVIDIA DGX A100

It packs 5 petaFLOPS, eight A100 GPUs with 320GB of GPU memory.

Realistically, if we get permission to run it 24/7 (which I doubt lol) for the 120 key, how long would it take? Is it feasible? And more important, would the Kangaroo even work on it?

legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
May 22, 2021, 05:36:20 AM
Anybody else see this:

~

Damn it, I didn't get the DP size formatting correct on Windows either.  Sad

Yeah this is a known bug https://github.com/ZenulAbidin/Kangaroo-256/issues/3 which also appears to affect how speed is displayed too, I have to investigate this further when I have time.
newbie
Activity: 33
Merit: 0
May 22, 2021, 05:20:25 AM
The .exe from a.a works fine on a modest GPU, haven't tested yet on higher specs. Thanks again for compiling! Smiley

One question:

Any particular reason why the CPU usage jumps and stays to 100% as it runs further and further? This happens with Jean Luc's version too. The temp is normal btw. Maybe is just my machine but I was curious if it's something in the code that makes use of the CPU as well as GPU.
member
Activity: 406
Merit: 47
May 22, 2021, 12:19:42 AM
Anybody else see this:



if you not have GPU and small laptop

don't try with 265 bit range or 256bit key

Kangaroo-256 good for high performance PC with hi end space and GPU
many time I have problem with my small gpu with Kangaroo-256

Recommend to use Kangaroo.exe  JeanLucPons is better for laptop and low space PC

Kangaroo still have limited use with puzzle only success possible, Can not use real key success it 256bit

if you want to try , test setting with keyspace low than 2^70 may be can work

see on image
range too high
dp is high


try test use DP = 10


full member
Activity: 706
Merit: 111
May 21, 2021, 08:54:16 PM
Expected RAM is 135431276999271530496 MB

The Executable is running into OOM (out of memory) and silently fails?

So that's why the bits are shaved off that's causing the range to seem like its smaller? It doesn't fail, it does hash. It just the range is smaller.
full member
Activity: 706
Merit: 111
May 21, 2021, 08:53:51 PM
Anybody else see this:


What is problem detail?

try test compare with binary windows .exe release and you compile version Did both have problem?

I can only use the windows.exe, I can't compile because I don't have a gpu. I used 2 different laptops, 1 had reduced range and the other had doubled the range. On top of that I couldn't use my work files with the kangaroo 256.
a.a
member
Activity: 126
Merit: 36
May 21, 2021, 08:22:48 PM
Expected RAM is 135431276999271530496 MB

The Executable is running into OOM (out of memory) and silently fails?
member
Activity: 406
Merit: 47
May 21, 2021, 08:19:47 PM
Anybody else see this:


What is problem detail?

try test compare with binary windows .exe release and you compile version Did both have problem?
full member
Activity: 706
Merit: 111
May 21, 2021, 07:21:32 PM
Anybody else see this:

legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
May 21, 2021, 01:09:48 PM
if I remark this line , I can compile a EXE ~~
Code:
Int.cpp

void Int::Div(Int *a,Int *mod)

           qhat = _udiv128 (nh , nm , _dh , &qrem);


1>..\SECPK1\Int.cpp(1097): error C3861: '_udiv128':  identifier not found

Don't do that, if you comment that out you will break division and Kangaroo won't work properly.

Windows has a problem with 128-bits multiplication and division intrinsics, they have to be emulated as macros by Kangaroo because they don't natively exist in the compiler (at least not until 2019 apparently).
Pages:
Jump to: