Could the user operating currently(!) under the Id "johnsnow" contact me ASAP?
#51??
Topic: Large Bitcoin Collider (Collision Finders Pool) - page 25. (Read 193404 times)
#51??
Could the user operating currently(!) under the Id "johnsnow" contact me ASAP?
It's to be expected that you get same keyrate on oclvanitygen independent of the CPU, as oclvanitygen (if you have no pcre matching) is GPU-only.
I get on my GPU only between 15-16 Mkeys/s from oclvanitygen, so your GPU should be about 5 times as fast, which seems consistent with the data in the comparison chart http://www.videocardbenchmark.net/compare.php?cmp%5B%5D=3502&cmp%5B%5D=3373
However I get 20 Mkeys/s on my notebook (skylake+M2000M) - which translates to 40 MAddresses/s (where oclvanitygen only does the compressed ones, thus for oclvanitygen 15Mkeys = 15Maddresses). Making LBC on my notebook about 2,7 times faster than oclvanitygen. As of now.
Not true for your system. :-( For you, the CPUs are still the bottleneck.
So you get 50-60 MAddresses/s from LBC, but 80 MAddresses from oclvanitygen. Your GPU load with LBC is around 50% I assume, where oclvanitygen shows 100%?
Rico
I get on my GPU only between 15-16 Mkeys/s from oclvanitygen, so your GPU should be about 5 times as fast, which seems consistent with the data in the comparison chart http://www.videocardbenchmark.net/compare.php?cmp%5B%5D=3502&cmp%5B%5D=3373
However I get 20 Mkeys/s on my notebook (skylake+M2000M) - which translates to 40 MAddresses/s (where oclvanitygen only does the compressed ones, thus for oclvanitygen 15Mkeys = 15Maddresses). Making LBC on my notebook about 2,7 times faster than oclvanitygen. As of now.
Not true for your system. :-( For you, the CPUs are still the bottleneck.
So you get 50-60 MAddresses/s from LBC, but 80 MAddresses from oclvanitygen. Your GPU load with LBC is around 50% I assume, where oclvanitygen shows 100%?
Rico
yeah.
avx2+gpu = 65% - 70%
skylake+gpu = around 77%
But I like this generator right now. Not really disappointed with the speed and not taking 100% usage. Because I still can watch youtube video and gambling. to pay this dedicated servers.
with oclvanitygen I was getting 150Mkeys with a 4x K80 GPU's
Highest block number for #51 is 2147483648
We are currently at 1541746271
=> 605737377 blocks to go
=> 635161675825152 keys to go
current keyrate 564310000 keys/s
=> 1125554 seconds = 13 days
Rico
PS: Of course, the numbers will be outdated when I press "Post"
PPS: As a reminder for why there is a difference: We "jumped" forward in search space by about 370 Mblocks, which we'll have to work after #51 is found.
We are currently at 1541746271
=> 605737377 blocks to go
=> 635161675825152 keys to go
current keyrate 564310000 keys/s
=> 1125554 seconds = 13 days
Rico
PS: Of course, the numbers will be outdated when I press "Post"
PPS: As a reminder for why there is a difference: We "jumped" forward in search space by about 370 Mblocks, which we'll have to work after #51 is found.
I get 80 Mkeys/s with oclvanitygen. both avx2 and skylake.
It's to be expected that you get same keyrate on oclvanitygen independent of the CPU, as oclvanitygen (if you have no pcre matching) is GPU-only.
I get on my GPU only between 15-16 Mkeys/s from oclvanitygen, so your GPU should be about 5 times as fast, which seems consistent with the data in the comparison chart http://www.videocardbenchmark.net/compare.php?cmp%5B%5D=3502&cmp%5B%5D=3373
However I get 20 Mkeys/s on my notebook (skylake+M2000M) - which translates to 40 MAddresses/s (where oclvanitygen only does the compressed ones, thus for oclvanitygen 15Mkeys = 15Maddresses). Making LBC on my notebook about 2,7 times faster than oclvanitygen. As of now.
Not true for your system. :-( For you, the CPUs are still the bottleneck.
So you get 50-60 MAddresses/s from LBC, but 80 MAddresses from oclvanitygen. Your GPU load with LBC is around 50% I assume, where oclvanitygen shows 100%?
Rico
I'd be interested what keyrate you get from oclvanitygen on that configuration. It should be less than 25 Mkeys/s with the GPU 100% load. But I could be wrong, so I'm interested in comparative numbers.
Rico
I get 80 Mkeys/s with oclvanitygen. both avx2 and skylake.
CPU: Intel® Core™ i7-6700 or Intel® Core™ i7-4790K
GPU: GTX 1080
on another machine with skylake CPU, speed increased 5 Mkeys/s.
--time 40 --delay 900
Code:
Ask for work... got blocks [1529011424-1529084767] (76906 Mkeys)
oooo......oooo (30.22 Mkeys/s)
Nice speed. new GPU generator
Code:
root@420vs69:~/LBC# ./LBC --id xxx --secret xxx --no_update --gpu --cpus 8
GPU authorized: yes
Ask for work... got blocks [1505284048-1505313999] (31406 Mkeys)
ooo..skip...ooo (25.37 Mkeys/s)
I'd be interested what keyrate you get from oclvanitygen on that configuration. It should be less than 25 Mkeys/s with the GPU 100% load. But I could be wrong, so I'm interested in comparative numbers.
Rico
Hi rico666, Sent you a PM re bootable iso image,
I can do some testing on NVidia and AMD (I have an Radeon R9 270 also on another machine). Would I need different ids to test a different hardware setup?
Also, may as well add a little customisation to it. Grub screen, hostname etc
I can do some testing on NVidia and AMD (I have an Radeon R9 270 also on another machine). Would I need different ids to test a different hardware setup?
Also, may as well add a little customisation to it. Grub screen, hostname etc
Will use 32 CPUs.
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your maximum speed is 719889 keys/s per CPU core.
need GPU GPU GPU GPU ^^
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your maximum speed is 719889 keys/s per CPU core.
need GPU GPU GPU GPU ^^
Nice speed. new GPU generator
Code:
root@420vs69:~/LBC# ./LBC --id xxx --secret xxx --no_update --gpu --cpus 8
GPU authorized: yes
Ask for work... got blocks [1505284048-1505313999] (31406 Mkeys)
ooo..skip...ooo (25.37 Mkeys/s)
This user manual must be titled something like "Stealing from Amateur Thieves" lol
LBC user manual is being used as reference in cyber investigations articles
This user manual must be titled something like "Stealing from Amateur Thieves" lol
read the news with 1000 trillion addresses more than on 10 websites ...you're going to be a star :>
...you're going to be a star :>Yeah - hooray.
In a burst of vanity attack, I checked mentions on the internet and found out, that the LBC user manual is being used as reference in cyber investigations articles: http://mccann-cyber.com/anonymity-cryptofraud-blockchain/
The theory part of the manual (see footnotes). Now the LBC has to run forever, else cyber investigators might get a 404.
Rico
I have almost finished a bootable iso image using arch, has lbcuser account and collider/LBC @ home dir. Currently booting with Nvidia drivers. I am just trying to work around a kernel hook that can determine the card you have and select a proprietary driver from either nvidia or amd/ati as currently its failing to boot using both. Currently this is working from an x64 version of arch.
Great progress. I will be happy to check it out.
Quote
I will also create i686 for 32-bit computers with GPU access.
Don't. Spare the energy - there will be no 32bit clients.
Rico
Hi,
I have almost finished a bootable iso image using arch, has lbcuser account and collider/LBC @ home dir. Currently booting with Nvidia drivers. I am just trying to work around a kernel hook that can determine the card you have and select a proprietary driver from either nvidia or amd/ati as currently its failing to boot using both. Currently this is working from an x64 version of arch.
I will also create i686 for 32-bit computers with GPU access.
I have almost finished a bootable iso image using arch, has lbcuser account and collider/LBC @ home dir. Currently booting with Nvidia drivers. I am just trying to work around a kernel hook that can determine the card you have and select a proprietary driver from either nvidia or amd/ati as currently its failing to boot using both. Currently this is working from an x64 version of arch.
I will also create i686 for 32-bit computers with GPU access.
Oh wow - someone has been reading Reddit:
https://cointelegraph.com/news/ultimate-white-hat-hacker-large-bitcoin-collider-passes-1000-trillion-addresses
"Ultimate white hat hacker" - take that becoin!
For da Germans:
https://www.btc-echo.de/der-large-bitcoin-collider-erreicht-eine-billiarde-adressen/
Rico
https://cointelegraph.com/news/ultimate-white-hat-hacker-large-bitcoin-collider-passes-1000-trillion-addresses
"Ultimate white hat hacker" - take that becoin!
For da Germans:
https://www.btc-echo.de/der-large-bitcoin-collider-erreicht-eine-billiarde-adressen/
Rico
read the news with 1000 trillion addresses more than on 10 websites
...you're going to be a star :>
Oh wow - someone has been reading Reddit:
https://cointelegraph.com/news/ultimate-white-hat-hacker-large-bitcoin-collider-passes-1000-trillion-addresses
"Ultimate white hat hacker" - take that becoin!
For da Germans:
https://www.btc-echo.de/der-large-bitcoin-collider-erreicht-eine-billiarde-adressen/
Rico
https://cointelegraph.com/news/ultimate-white-hat-hacker-large-bitcoin-collider-passes-1000-trillion-addresses
"Ultimate white hat hacker" - take that becoin!
For da Germans:
https://www.btc-echo.de/der-large-bitcoin-collider-erreicht-eine-billiarde-adressen/
Rico
output of free?
Yes. Something like this:
Code:
$ free
total used free shared buff/cache available
Mem: 16299924 1650300 12482160 1056560 2167464 13303548
Swap: 0 0 0
It happened after I upgraded it (calling LBC -u). Everything went fine, I even did the LBC -x and no problem. But when I called it for LBC -c 2 -id xxx -s xxx, it said ... Answer: too fast.
...
real 0m0.002s
user 0m0.004s
sys 0m0.000s
...
real 0m0.002s
user 0m0.004s
sys 0m0.000s
I doubt LBC -x went through without a problem. Because the benchmark claims your computer did 16M keys in 0.002s, so either your computer is from the future or something went wrong.
Code:
The result of the test:
time ./gen-hrdcore-sse42-linux64 -I 0000000000000000000000000000000000000000000000000000000000000001 -c 10000 -L 1
but the first key must be in the range:
1 - fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8ccf364141
Please retry with another key
Something went wrong. The generator failed internally somewhere. For diagnosis send me
The distro (name, version) you use
output of ls -al of the collider directory
output of cat /proc/cpuinfo
output of free
Rico
output of free?
Jump to: