What are your thoughts...
For this Kangaroo ECDLP solver, if RAM was not an issue, what is the optimal DP setting?
Would lower always be better? Small DP means you have to find more DPs.
Expected group operations remains the same no matter how you adjust the DP, right?
So what is the optimal DP setting if RAM is not an issue?
Topic: Pollard's kangaroo ECDLP solver - page 106. (Read 59389 times)
Anybody think about using bsgs algo but with DP?
bsgs fast but have a problem due to memory usage. maybe using DP can solve this issues?
Extremely fast, it gets through a FFFFFFFFFFF range in 2 seconds total. Including step build time. Only uses 600Mb.bsgs fast but have a problem due to memory usage. maybe using DP can solve this issues?
I thought about how to implement it differently. Use DP or build the table on harddrive and when giants start stepping compare back to the saved table. After so long, save the giant file with previously created file, and continue with giant step.
How do you use DPs with BSGS?
Anybody think about using bsgs algo but with DP?
bsgs fast but have a problem due to memory usage. maybe using DP can solve this issues?
Extremely fast, it gets through a FFFFFFFFFFF range in 2 seconds total. Including step build time. Only uses 600Mb.bsgs fast but have a problem due to memory usage. maybe using DP can solve this issues?
I thought about how to implement it differently. Use DP or build the table on harddrive and when giants start stepping compare back to the saved table. After so long, save the giant file with previously created file, and continue with giant step.
How do you use DPs with BSGS?
Anybody think about using bsgs algo but with DP?
bsgs fast but have a problem due to memory usage. maybe using DP can solve this issues?
Extremely fast, it gets through a FFFFFFFFFFF range in 2 seconds total. Including step build time. Only uses 600Mb.bsgs fast but have a problem due to memory usage. maybe using DP can solve this issues?
I thought about how to implement it differently. Use DP or build the table on harddrive and when giants start stepping compare back to the saved table. After so long, save the giant file with previously created file, and continue with giant step.
Anybody think about using bsgs algo but with DP?
bsgs fast but have a problem due to memory usage. maybe using DP can solve this issues?
bsgs fast but have a problem due to memory usage. maybe using DP can solve this issues?
How long are your GPUs working on #115?
If #110 was solved for 2 days, so with the same speed and the same luck you need 2days * sqrt(2^5) = 2 days * 5.66 ~ 11.3 days for #115. So, yes, if you started on 1 June, the estimated completion date 11-12 June
For #110 you was very close to sqrt(n) operations, but not the average 2*sqrt(n). That means that probably you should wait another 11-12 days to be close to the average and 50% probability to find the key.
EDIT:
I doubt you will find the #115 key tomorrow. Much more likely at the end of June, or mid July. But not tomorrow.
We almost reached 50% probability yesterday (~8 days of run, ~2^33 DP, DP25) but unfortunately everything was shutdown due to a storm
Fortunately the workfiles has been preserved but we have to restart clients and servers to recover from crash.
As there was no kangaroo backup we will get a DP overhead by restarting the work.
I don't know if Zielar restarted the GPUs, yesterday he was a bit nervous
We also get lots of troubles handling large workfiles (above 200GB) so I created a partitioned work file system (available on github) , an integrity workfile checker. We manage to re-merge all worfiles in ~24H.
The current release is tagged 1.10(unstable) but should work.
Hope it will go better now...
If any of you are working on #115 or #120 or # any above that, by yourself, you're just wasting power.
Jean Luc's knowledge, with Zielar's unlimited GPUs through his work...YOU can't compete. Especially if Jean Luc is making changes to increase chances of Zielar finding the puzzle.
You can't compete. Not with Kangaroo. You'll have to get creative and try random other options.
It's like everyone has GPU power but no one wants to link up and send DPs to common server, or get together and agree on a specific DP to share work files, etc.
I'd rather have 10% of 1.15 BTC versus 0%.
I'm still in the chase, but not strictly with Kangaroo. I offered up my work files, at DP 30 or 31. They are just sitting in file, no longer being used. I'm down to DP 12, with creative works.
Jean Luc's knowledge, with Zielar's unlimited GPUs through his work...YOU can't compete. Especially if Jean Luc is making changes to increase chances of Zielar finding the puzzle.
You can't compete. Not with Kangaroo. You'll have to get creative and try random other options.
It's like everyone has GPU power but no one wants to link up and send DPs to common server, or get together and agree on a specific DP to share work files, etc.
I'd rather have 10% of 1.15 BTC versus 0%.
I'm still in the chase, but not strictly with Kangaroo. I offered up my work files, at DP 30 or 31. They are just sitting in file, no longer being used. I'm down to DP 12, with creative works.
Quote
We also get lots of troubles handling large workfiles (above 200GB) so I created a partitioned work file system (available on github) , an integrity workfile checker.
Told you
How long are your GPUs working on #115?
If #110 was solved for 2 days, so with the same speed and the same luck you need 2days * sqrt(2^5) = 2 days * 5.66 ~ 11.3 days for #115. So, yes, if you started on 1 June, the estimated completion date 11-12 June
For #110 you was very close to sqrt(n) operations, but not the average 2*sqrt(n). That means that probably you should wait another 11-12 days to be close to the average and 50% probability to find the key.
EDIT:
I doubt you will find the #115 key tomorrow. Much more likely at the end of June, or mid July. But not tomorrow.
We almost reached 50% probability yesterday (~8 days of run, ~2^33 DP, DP25) but unfortunately everything was shutdown due to a storm
Fortunately the workfiles has been preserved but we have to restart clients and servers to recover from crash.
As there was no kangaroo backup we will get a DP overhead by restarting the work.
I don't know if Zielar restarted the GPUs, yesterday he was a bit nervous
We also get lots of troubles handling large workfiles (above 200GB) so I created a partitioned work file system (available on github) , an integrity workfile checker. We manage to re-merge all worfiles in ~24H.
The current release is tagged 1.10(unstable) but should work.
Hope it will go better now...
Thank you very much for the help. I was able to finally run the program. Community tell me how to open a 65save answer file? The file does not have an extension, I open notepad there are hieroglyphs, squares. I tried to open Bred3.0.3, I didn’t open it. Thank you very much in advance.
HxD Hex Editor, Winhex, Cygnus Hex Editor, etc
Thank you very much for the help. I was able to finally run the program. Community tell me how to open a 65save answer file? The file does not have an extension, I open notepad there are hieroglyphs, squares. I tried to open Bred3.0.3, I didn’t open it. Thank you very much in advance.
Maybe totalcommander can help. TC file viewer support many codepages(ANSI,Unicode, etc...)
Thank you very much for the help. I was able to finally run the program. Community tell me how to open a 65save answer file? The file does not have an extension, I open notepad there are hieroglyphs, squares. I tried to open Bred3.0.3, I didn’t open it. Thank you very much in advance.
Together with the author of this work, we plan to have solution # 115 tomorrow and set a new record :-)
How long are your GPUs working on #115?
If #110 was solved for 2 days, so with the same speed and the same luck you need 2days * sqrt(2^5) = 2 days * 5.66 ~ 11.3 days for #115. So, yes, if you started on 1 June, the estimated completion date 11-12 June
For #110 you was very close to sqrt(n) operations, but not the average 2*sqrt(n). That means that probably you should wait another 11-12 days to be close to the average and 50% probability to find the key.
EDIT:
I doubt you will find the #115 key tomorrow. Much more likely at the end of June, or mid July. But not tomorrow.
In wikipedia wrighted - about max solved is 109 Bytes )))
Together with the author of this work, we plan to have solution # 115 tomorrow and set a new record :-)
How long are your GPUs working on #115?
If #110 was solved for 2 days, so with the same speed and the same luck you need 2days * sqrt(2^5) = 2 days * 5.66 ~ 11.3 days for #115. So, yes, if you started on 1 June, the estimated completion date 11-12 June
For #110 you was very close to sqrt(n) operations, but not the average 2*sqrt(n). That means that probably you should wait another 11-12 days to be close to the average and 50% probability to find the key.
EDIT:
I doubt you will find the #115 key tomorrow. Much more likely at the end of June, or mid July. But not tomorrow.
If any of you are working on #115 or #120 or # any above that, by yourself, you're just wasting power.
Jean Luc's knowledge, with Zielar's unlimited GPUs through his work...YOU can't compete. Especially if Jean Luc is making changes to increase chances of Zielar finding the puzzle.
You can't compete. Not with Kangaroo. You'll have to get creative and try random other options.
It's like everyone has GPU power but no one wants to link up and send DPs to common server, or get together and agree on a specific DP to share work files, etc.
I'd rather have 10% of 1.15 BTC versus 0%.
I'm still in the chase, but not strictly with Kangaroo. I offered up my work files, at DP 30 or 31. They are just sitting in file, no longer being used. I'm down to DP 12, with creative works.
Jean Luc's knowledge, with Zielar's unlimited GPUs through his work...YOU can't compete. Especially if Jean Luc is making changes to increase chances of Zielar finding the puzzle.
You can't compete. Not with Kangaroo. You'll have to get creative and try random other options.
It's like everyone has GPU power but no one wants to link up and send DPs to common server, or get together and agree on a specific DP to share work files, etc.
I'd rather have 10% of 1.15 BTC versus 0%.
I'm still in the chase, but not strictly with Kangaroo. I offered up my work files, at DP 30 or 31. They are just sitting in file, no longer being used. I'm down to DP 12, with creative works.
Together with the author of this work, we plan to have solution # 115 tomorrow and set a new record :-)
How long are your GPUs working on #115?
If #110 was solved for 2 days, so with the same speed and the same luck you need 2days * sqrt(2^5) = 2 days * 5.66 ~ 11.3 days for #115. So, yes, if you started on 1 June, the estimated completion date 11-12 June
For #110 you was very close to sqrt(n) operations, but not the average 2*sqrt(n). That means that probably you should wait another 11-12 days to be close to the average and 50% probability to find the key.
EDIT:
I doubt you will find the #115 key tomorrow. Much more likely at the end of June, or mid July. But not tomorrow.
the thing is i start with dp 24 after you found the 110 bit then i lost big file for dp 24
then i start with new one with dp 26 i run it for 6 days
this is my workfile
Loading: 115all
Version : 0
DP bits : 26
Start : 40000000000000000000000000000
Stop : 7FFFFFFFFFFFFFFFFFFFFFFFFFFFF
Key : 0248D313B0398D4923CDCA73B8CFA6532B91B96703902FC8B32FD438A3B7CD7F55
Count : 9743276691781672 2^53.113
Time : 68.7d
DP Size : 403.0/1183.5MB
DP Count : 13140929 2^23.648
HT Max : 89 [@ 021EC5]
HT Min : 22 [@ 00EAD0]
HT Avg : 50.13
HT SDev : 7.09
Kangaroos : 0 2^-inf
Kangaroo v1.8
Loading: 115all
Version : 0
DP bits : 24
Start : 40000000000000000000000000000
Stop : 7FFFFFFFFFFFFFFFFFFFFFFFFFFFF
Key : 0248D313B0398D4923CDCA73B8CFA6532B91B96703902FC8B32FD438A3B7CD7F55
Count : 11306564601638692 2^53.328
Time : 103.7d
DP Size : 655.4/1815.3MB
DP Count : 21411199 2^24.352
HT Max : 129 [@ 021EC5]
HT Min : 46 [@ 00BF14]
HT Avg : 81.68
HT SDev : 9.07
Kangaroos : 0 2^-inf
then i start with new one with dp 26 i run it for 6 days
this is my workfile
Loading: 115all
Version : 0
DP bits : 26
Start : 40000000000000000000000000000
Stop : 7FFFFFFFFFFFFFFFFFFFFFFFFFFFF
Key : 0248D313B0398D4923CDCA73B8CFA6532B91B96703902FC8B32FD438A3B7CD7F55
Count : 9743276691781672 2^53.113
Time : 68.7d
DP Size : 403.0/1183.5MB
DP Count : 13140929 2^23.648
HT Max : 89 [@ 021EC5]
HT Min : 22 [@ 00EAD0]
HT Avg : 50.13
HT SDev : 7.09
Kangaroos : 0 2^-inf
Kangaroo v1.8
Loading: 115all
Version : 0
DP bits : 24
Start : 40000000000000000000000000000
Stop : 7FFFFFFFFFFFFFFFFFFFFFFFFFFFF
Key : 0248D313B0398D4923CDCA73B8CFA6532B91B96703902FC8B32FD438A3B7CD7F55
Count : 11306564601638692 2^53.328
Time : 103.7d
DP Size : 655.4/1815.3MB
DP Count : 21411199 2^24.352
HT Max : 129 [@ 021EC5]
HT Min : 46 [@ 00BF14]
HT Avg : 81.68
HT SDev : 9.07
Kangaroos : 0 2^-inf
oww Zielar i run my engines so long now for 115 and you solve it tomorrow ? wht dp size you choose ?
i have dp 26 maybe i can share with you
i have dp 26 maybe i can share with you
Seems like #115 pazzle it is the latest pazzle to solve with kangaroo.
Next #120 need 160 days with 100x2080ti. With the same power even at not the best algorithm Ethash for this card this huge power get 1.6BTC for 160 days, it is much more then expected reward for solving key.
Next #120 need 160 days with 100x2080ti. With the same power even at not the best algorithm Ethash for this card this huge power get 1.6BTC for 160 days, it is much more then expected reward for solving key.
someone have workfile for share with dp26 ?
What setting I nedd to do for get 100% probability ?
Maximum patience
Oh, Good Lack Man !!! Be Be !!
You trust Santa ? So, what he say you about time then he came to you again ? ? ?
Jump to: