rico666 (OP)
Legendary
Offline
Activity: 1120
Merit: 1037
฿ → ∞
|
|
February 22, 2017, 06:35:46 AM |
|
I just used Ubuntu 14.04.4 and installed fglrx.
Then the normal LBC install.
As for the GPU client: Can you write more about hardware you use and keyrate you get out of it? I'm adding some overview of speed for complete system configurations https://lbc.cryptoguru.org/man/admin#generator-speedRico
|
|
|
|
rico666 (OP)
Legendary
Offline
Activity: 1120
Merit: 1037
฿ → ∞
|
|
February 22, 2017, 12:27:03 PM |
|
There is a new version, which fixes the rogue "Death Kiss" events.
Please update as follows:
End your LBC client Do a LBC -u (you should have a 1.031 or newer) Start your LBC as usual
If you haven't updated yet (I see clients as old as 0.993), you are also missing out quite some keyrate. There are reports of 1.6 Mkeys -> 2.1 Mkeys for CPU clients on VMs
Rico
|
|
|
|
Jude Austin
Legendary
Offline
Activity: 1140
Merit: 1000
The Real Jude Austin
|
|
February 22, 2017, 02:12:22 PM Last edit: February 23, 2017, 04:58:14 AM by Jude Austin |
|
I just used Ubuntu 14.04.4 and installed fglrx.
Then the normal LBC install.
As for the GPU client: Can you write more about hardware you use and keyrate you get out of it? I'm adding some overview of speed for complete system configurations https://lbc.cryptoguru.org/man/admin#generator-speedRico Yep, I will do that after work. It's after work: processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 16 model name : AMD A8-5500 APU with Radeon(tm) HD Graphics stepping : 1 microcode : 0x6001116 cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legac y svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pst ate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists p ausefilter pfthreshold vmmcall bmi1 bugs : fxsave_leak sysret_ss_attrs bogomips : 6388.03 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro
processor : 1 vendor_id : AuthenticAMD cpu family : 21 model : 16 model name : AMD A8-5500 APU with Radeon(tm) HD Graphics stepping : 1 microcode : 0x6001116 cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 17 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legac y svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pst ate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists p ausefilter pfthreshold vmmcall bmi1 bugs : fxsave_leak sysret_ss_attrs bogomips : 6388.03 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro
processor : 2 vendor_id : AuthenticAMD cpu family : 21 model : 16 model name : AMD A8-5500 APU with Radeon(tm) HD Graphics stepping : 1 cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings : 4 core id : 2 cpu cores : 2 apicid : 18 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legac y svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pst ate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists p ausefilter pfthreshold vmmcall bmi1 bugs : fxsave_leak sysret_ss_attrs bogomips : 6388.03 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro
processor : 3 vendor_id : AuthenticAMD cpu family : 21 model : 16 model name : AMD A8-5500 APU with Radeon(tm) HD Graphics stepping : 1 cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings : 4 core id : 3 cpu cores : 2 apicid : 19 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legac y svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pst ate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists p ausefilter pfthreshold vmmcall bmi1 bugs : fxsave_leak sysret_ss_attrs bogomips : 6388.03 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro Key rate: Your maximum speed is 578988 keys/s per CPU core. Averaging around 2.18Mkeys using a Sapphire 7970 reference card to assist 4 cores (-c 4). As for OS, I used Ubuntu 14.04.4 because that is the last known version to work well with OpenCL. So fresh Ubuntu install, then I sudo apt-get update && sudo apt-get install fglrx, RESTART PC, install LBC, profit. Thanks, Jude
|
Buy or sell $100 of Crypto and get $10!
|
|
|
rico666 (OP)
Legendary
Offline
Activity: 1120
Merit: 1037
฿ → ∞
|
|
February 23, 2017, 08:09:41 AM |
|
model name : AMD A8-5500 APU with Radeon(tm) HD Graphics
Key rate: Your maximum speed is 578988 keys/s per CPU core. Averaging around 2.18Mkeys using a Sapphire 7970 reference card to assist 4 cores (-c 4). As for OS, I used Ubuntu 14.04.4 because that is the last known version to work well with OpenCL. So fresh Ubuntu install, then I sudo apt-get update && sudo apt-get install fglrx, RESTART PC, install LBC, profit. Very, VERY interesting because of several reasons: 1) I'm still unable to get my AMD GPU working root@rico666-desktop:/home/rico666/collider# time ./gen-hrdcore-sse42+gpu-linux64 -I 0000000000000000000000000000000000000000000000000000000000000001 -c 10000 Couldn't create a command queue: Out of host memory Tried Arch, ditched that after half a day of error messages and install woes, Installed Ubuntu 16.04 with AMDGPU Pro on a USB stick -> same result. Aaargh. So you beat me there. I cannot run my own program, but you can. 2) I do have a R9 280X which is pretty near to your 7970, however when I look up the specs for the AMD A8-5500 APU, it says there's a Radeon 7560D built in there somewhere. So just to be clear. You have a system with that AMD APU + 7970? So you have 2 GPUs? And you are sure LBC takes the 7970 to assist and not the 7560D? Because when I look at the diagnostics-OpenCL you sent me, there are - in fact - two Tahiti devices lurking there, and the 1st one is the 7560D. So unless you are starting LBC with -gdev 2, you are using the 7560D to assist. Might want to cross check that. 3) Your AMD APU reminded me, I have something similar here sitting in my Kodi box: AMD A6-5400K APU with Radeon(tm) HD Graphics - it claims to have a 7540D, I might try that. Rico
|
|
|
|
Jude Austin
Legendary
Offline
Activity: 1140
Merit: 1000
The Real Jude Austin
|
|
February 23, 2017, 01:40:07 PM |
|
model name : AMD A8-5500 APU with Radeon(tm) HD Graphics
Key rate: Your maximum speed is 578988 keys/s per CPU core. Averaging around 2.18Mkeys using a Sapphire 7970 reference card to assist 4 cores (-c 4). As for OS, I used Ubuntu 14.04.4 because that is the last known version to work well with OpenCL. So fresh Ubuntu install, then I sudo apt-get update && sudo apt-get install fglrx, RESTART PC, install LBC, profit. Very, VERY interesting because of several reasons: 1) I'm still unable to get my AMD GPU working root@rico666-desktop:/home/rico666/collider# time ./gen-hrdcore-sse42+gpu-linux64 -I 0000000000000000000000000000000000000000000000000000000000000001 -c 10000 Couldn't create a command queue: Out of host memory Tried Arch, ditched that after half a day of error messages and install woes, Installed Ubuntu 16.04 with AMDGPU Pro on a USB stick -> same result. Aaargh. So you beat me there. I cannot run my own program, but you can. 2) I do have a R9 280X which is pretty near to your 7970, however when I look up the specs for the AMD A8-5500 APU, it says there's a Radeon 7560D built in there somewhere. So just to be clear. You have a system with that AMD APU + 7970? So you have 2 GPUs? And you are sure LBC takes the 7970 to assist and not the 7560D? Because when I look at the diagnostics-OpenCL you sent me, there are - in fact - two Tahiti devices lurking there, and the 1st one is the 7560D. So unless you are starting LBC with -gdev 2, you are using the 7560D to assist. Might want to cross check that. 3) Your AMD APU reminded me, I have something similar here sitting in my Kodi box: AMD A6-5400K APU with Radeon(tm) HD Graphics - it claims to have a 7540D, I might try that. Rico 1. Hmm, try setting environment variables for the GPU. 2. I tried using all the devices on my rig and got the same hash rate for each one. I have 2 7970s and one 7950 on my rig, I went through devices 1-4 and achieved the same rate. Thanks, Jude
|
Buy or sell $100 of Crypto and get $10!
|
|
|
|
rico666 (OP)
Legendary
Offline
Activity: 1120
Merit: 1037
฿ → ∞
|
|
February 23, 2017, 02:38:22 PM Last edit: February 24, 2017, 01:15:12 PM by rico666 |
|
SHA1 ... bah. That's like beating up a grown up MD5. 6500 CPU-years & 100 GPU years Rico
|
|
|
|
rico666 (OP)
Legendary
Offline
Activity: 1120
Merit: 1037
฿ → ∞
|
|
February 24, 2017, 09:29:46 PM |
|
I managed to get the Bloom Filter check done on GPU also.
with some more optimizations total time for 16M keys went down about 0.2 secs on my machine. Tested with -L 5 (generating 5 x 16M consecutive keys but just 1 startup cost), the time went down 0.5s per 16M keys so I'm at about 2396745 keys/s per core now.
Did some benchmarking and my M2000M Quadro - a midrange notebook GPU - does 60M of my BTC-optimized hash160 code + bloom-check per second. That's enough horsepower to check 30 Mkeys (uncompressed + compressed) per second.
If they are provided fast enough...
So how do I get from my current 7 Mkeys/s to 30 Mkeys/s?
I'd like to pursue some of the ideas arulbero threw in on ECC pubkey generation, but after having looked at his code and also at things like "supervanitygen" (which is now officially less than half the speed of LBC), It's pretty clear I will have to come up with something on my own. And also that I will have to move ECC to the GPU.
Rico
|
|
|
|
freemanjackal
|
|
February 25, 2017, 12:44:59 AM |
|
lets see if i understand the idea, are you trying to find another private key that should exists by a given public key(in this case public addresses), if i am not wrong this mathematically should take thouthands or millions of years, is that the idea behind the project? what about quantic processing that is actually working, i think that 's why this should be unfeasible at least for the moment, more processing capabilities needed.
|
|
|
|
Jude Austin
Legendary
Offline
Activity: 1140
Merit: 1000
The Real Jude Austin
|
|
February 25, 2017, 12:57:31 AM |
|
I managed to get the Bloom Filter check done on GPU also.
with some more optimizations total time for 16M keys went down about 0.2 secs on my machine. Tested with -L 5 (generating 5 x 16M consecutive keys but just 1 startup cost), the time went down 0.5s per 16M keys so I'm at about 2396745 keys/s per core now.
Did some benchmarking and my M2000M Quadro - a midrange notebook GPU - does 60M of my BTC-optimized hash160 code + bloom-check per second. That's enough horsepower to check 30 Mkeys (uncompressed + compressed) per second.
If they are provided fast enough...
So how do I get from my current 7 Mkeys/s to 30 Mkeys/s?
I'd like to pursue some of the ideas arulbero threw in on ECC pubkey generation, but after having looked at his code and also at things like "supervanitygen" (which is now officially less than half the speed of LBC), It's pretty clear I will have to come up with something on my own. And also that I will have to move ECC to the GPU.
Rico
This may be of some use: https://pdfs.semanticscholar.org/e1b1/1b509ac7c4f049ebab19caf57fcd0622b3c0.pdf
|
Buy or sell $100 of Crypto and get $10!
|
|
|
SlarkBoy
Member
Offline
Activity: 114
Merit: 11
|
|
February 25, 2017, 03:22:16 AM |
|
Congrats! And ... what? ... better keyrate than me? I have to o.p.t.i.m.i.z.e. more I'm getting more and more feedback about GPU clients finally working with some heart-lung machine work. I'll publish a new client soon which wraps up all the fixes, so GPU experience will be smooth. Rico Why isn't using all resources? Only 25% +-----------------------------------------------------------------------------+ | NVIDIA-SMI 375.26 Driver Version: 375.26 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===============================+======================+======================| | 0 GeForce GTX 1080 Off | 0000:01:00.0 On | N/A | | 29% 54C P2 49W / 200W | 1217MiB / 8113MiB | 25% Default | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=============================================================================| | 0 1162 G /usr/lib/xorg/Xorg 181MiB | | 0 2889 G compiz 114MiB | | 0 10005 C ./gen-hrdcore-avx2+gpu-linux64 115MiB | | 0 10008 C ./gen-hrdcore-avx2+gpu-linux64 115MiB | | 0 10011 C ./gen-hrdcore-avx2+gpu-linux64 115MiB | | 0 10012 C ./gen-hrdcore-avx2+gpu-linux64 115MiB | | 0 10013 C ./gen-hrdcore-avx2+gpu-linux64 115MiB | | 0 10014 C ./gen-hrdcore-avx2+gpu-linux64 115MiB | | 0 10015 C ./gen-hrdcore-avx2+gpu-linux64 115MiB | | 0 10016 C ./gen-hrdcore-avx2+gpu-linux64 115MiB | +-----------------------------------------------------------------------------+
|
|
|
|
rico666 (OP)
Legendary
Offline
Activity: 1120
Merit: 1037
฿ → ∞
|
|
February 25, 2017, 06:27:51 AM |
|
Why isn't using all resources? Only 25%
Because your GPU is too fast. Or your CPU too slow. Pick one of the explanations ;-) My CPU-GPU combo uses 34% of the GPU On Amazon machines, around 8-10 CPU cores are able to saturate a K80 GPU (that's because both their CPU and GPU are slow) So yes, there is a HUGE discrepancy between CPU and GPU computational power, so I'm trying to shift more and more load to the GPU. @freemanjackal lets see if i understand the idea, are you trying to find another private key that should exists by a given public key(in this case public addresses), if i am not wrong this mathematically should take thouthands or millions of years, is that the idea behind the project? what about quantic processing that is actually working, i think that 's why this should be unfeasible at least for the moment,...
Yes, we are trying to find "for any of the ~9 mio BTC addresses with unspent outputs one of the other 296-1 private keys that should exist. https://lbc.cryptoguru.org/stats shows the probability to find something within the next 24 hours. https://lbc.cryptoguru.org/trophies shows what we have found so far more processing capabilities needed. Yes. https://lbc.cryptoguru.org/download Rico
|
|
|
|
Jude Austin
Legendary
Offline
Activity: 1140
Merit: 1000
The Real Jude Austin
|
|
February 25, 2017, 08:45:36 AM |
|
Sweet:
|
Buy or sell $100 of Crypto and get $10!
|
|
|
arulbero
Legendary
Offline
Activity: 1915
Merit: 2074
|
|
February 25, 2017, 01:09:54 PM |
|
Did some benchmarking and my M2000M Quadro - a midrange notebook GPU - does 60M of my BTC-optimized hash160 code + bloom-check per second. That's enough horsepower to check 30 Mkeys (uncompressed + compressed) per second. So how do I get from my current 7 Mkeys/s to 30 Mkeys/s?
I'd like to pursue some of the ideas arulbero threw in on ECC pubkey generation, but after having looked at his code and also at things like "supervanitygen" (which is now officially less than half the speed of LBC), It's pretty clear I will have to come up with something on my own. And also that I will have to move ECC to the GPU.
Rico
Cpu + GMP library: on your pc you could get 16,7M / 4s or 16,7/ 2s with complement or 16M / 1s with endomorphism. My function "double_add" now takes 6s on my cpu (on your pc I guess it takes less than 3s), then 4s is a reasonable estimate. If the goal is 15Mkeys/s, CPU + GMP library are enough, otherwise you have to implement an efficient representation of field's elements (like secp256k1 library does) and/or use GPU. About GPU and multiprecision library: https://pdfs.semanticscholar.org/d807/b453c7f10bc547971a9344e81a88af934ad0.pdfIn this paper, we present our design and implementation of a multiple-precision integer library for GPUs which is implemented by CUDA. We report our experimental results which show that a significant speedup can be achieved by GPUs as compared with the GNU MP library on CPUs
|
|
|
|
DiamondCardz
Legendary
Offline
Activity: 1134
Merit: 1118
|
|
February 25, 2017, 03:06:39 PM |
|
Is this just a regular pooled brute force attack? If it is I don't see how it really adds anything to Bitcoin's development or tells us something we don't already know, unless it's trying to use some new novel method of finding collisions: in which case it is less of an attack on Bitcoin, and more of an attack on SHA256 in an attempt to prove it obsolete.
|
BA Computer Science, University of Oxford Dissertation was about threat modelling on distributed ledgers.
|
|
|
rico666 (OP)
Legendary
Offline
Activity: 1120
Merit: 1037
฿ → ∞
|
|
February 25, 2017, 04:11:44 PM |
|
Is this just a regular pooled brute force attack? If it is I don't see how it really adds anything to Bitcoin's development or tells us something we don't already know, unless it's trying to use some new novel method of finding collisions: in which case it is less of an attack on Bitcoin, and more of an attack on SHA256 in an attempt to prove it obsolete.
Please define "regular" and "us" Also, would you care to lay out "what we already know" and finally why you think this is an attack on SHA256. If you don't know what it adds to BTC development, you probably haven't read anything of the thread in which case it's hard to discuss the matter. Fun fact: BTC mining is a regular pooled brute force attack. Rico
|
|
|
|
rico666 (OP)
Legendary
Offline
Activity: 1120
Merit: 1037
฿ → ∞
|
|
February 25, 2017, 04:19:25 PM |
|
Also fun fact: Time since inception: 6 months Number of keys generated: 250 trillion Number of unspents found: 2 (genuine, no bounties etc.) Total collisions confirmed: 0 Current generation speed: 23.71 Mkeys/s (*) Time since 250 tn: 38 days. Rico
|
|
|
|
Jude Austin
Legendary
Offline
Activity: 1140
Merit: 1000
The Real Jude Austin
|
|
February 25, 2017, 06:35:24 PM |
|
Someone should buy that new 1800x Ryzen chip and run LBC with it...
|
Buy or sell $100 of Crypto and get $10!
|
|
|
|
DiamondCardz
Legendary
Offline
Activity: 1134
Merit: 1118
|
|
February 25, 2017, 10:51:01 PM |
|
Is this just a regular pooled brute force attack? If it is I don't see how it really adds anything to Bitcoin's development or tells us something we don't already know, unless it's trying to use some new novel method of finding collisions: in which case it is less of an attack on Bitcoin, and more of an attack on SHA256 in an attempt to prove it obsolete.
Please define "regular" and "us" Also, would you care to lay out "what we already know" and finally why you think this is an attack on SHA256. If you don't know what it adds to BTC development, you probably haven't read anything of the thread in which case it's hard to discuss the matter. Fun fact: BTC mining is a regular pooled brute force attack. Rico You might have misinterpreted what I said, the phrase "attack" was in no way supposed to be an attack on your project, I actually think a successful attack on Bitcoin/SHA256 would be very important and noble of the person showing it in proving that the protocol is no longer effective. However the project is literally an attempt to find collisions, no? Does it prove a point, and if it does, is it any different to, say, finding a collision in SHA256 using a birthday attack?
|
BA Computer Science, University of Oxford Dissertation was about threat modelling on distributed ledgers.
|
|
|
|