Large Bitcoin Collider (Collision Finders Pool)

[KnightShift]

I'm new to Linux, so please forgive my stupid questions. Ive installed the required programs listed in your manual, but when I try to run the script, I get the "command not found" error. I'm running it with sudo.

I also tried using "sudo perl LBC.pl -h" after searching for a while, but it returns a BIGNUM error and says that JSON isn't installed.

I installed the necessary programs and downloaded your script to my desktop. Am I missing something obvious?

[1713926332]

1713926332

[1713926332]

1713926332

[1713926332]

1713926332

[rico666]

I'm new to Linux, so please forgive my stupid questions. Ive installed the required programs listed in your manual, but when I try to run the script, I get the "command not found" error. I'm running it with sudo.

I also tried using "sudo perl LBC.pl -h" after searching for a while, but it returns a BIGNUM error and says that JSON isn't installed.

I installed the necessary programs and downloaded your script to my desktop. Am I missing something obvious?

It does not need the .pl extension, but you may need to invoke it like that

Code:

sudo ./LBC -h

the ./ is necessary, because . (the current PATH) is often not in the $PATH environment variable.
The messages upon 1st invocation are plenty and may look quite disturbing.

(the program is mentioning what is not installed and will install the required modules. During that installation, it shows the output of the installation, which is terse.)

Let the program vomit and wait for a while, eventually all will settle and the help will appear.


Rico

[KnightShift]

I gave up and decided to just run it in a VM. Seems to be working well so far. Still trying to remember all the commands. Earlier I ran ./LBC -q to see my status, and it quit. Going to have to reread the thread to work everything out.

On another note, after installing the VM, it gave me the MD5 doesn't match error. I solved this by doing as someone else in the thread suggested and using

Code:

rm funds*

Code:

rm 4a*

It took a minute to redownload the necessary files, but it worked fine after that.

[rico666]

Earlier I ran ./LBC -q to see my status, and it quit. Going to have to reread the thread to work everything out.

Which happens if you query the status before having delivered a single block.

Before rereading the thread, I'd suggest the manual: http://lbc.cryptoguru.org:5000/man/user
where I try to have the distilled information from the thread.

RIco

[str4wm4n]

cool project, good luck!!!

[rico666]

Sunday evening (UTC) the LBC server will move to newer greener pastures and there will be a downtime of about 30 minutes.
Because this is longer than the retry-time of the clients, they need to be restarted after that.

I'd suggest to start your clients with "-t 30" so in any case there would not be much work lost.
I'll probably PING here shortly before we shutdown and move the server.


Rico

[KnightShift]

Earlier I ran ./LBC -q to see my status, and it quit. Going to have to reread the thread to work everything out.

Which happens if you query the status before having delivered a single block.

Before rereading the thread, I'd suggest the manual: http://lbc.cryptoguru.org:5000/man/user
where I try to have the distilled information from the thread.

RIco

http://imgur.com/x4kmUC7

I let it run overnight and tried running it again. This is the result.

[rico666]

I let it run overnight and tried running it again. This is the result.

LOL.

By typing something which belongs on the command line as input to the LBC itself, all it got was "q" which it interprets as QUIT.
Try to input the query command on the commad line. In your case like this:

Code:

[osboxes@osboxes collider]$ ./LBC -q

And you should actually see an output similar to this:

Code:

Server answer to 'query' is:
{
"lastsee" : 1479426435,
"ips" : {
"111.222.111.222" : 3104,
"192.65.33.65" : 234
},
"done" : 2817168
}
'done' means we have delivered   2954.015 valid Gkeys.

You have to distinguish between "when the program runs" (then it listens to the keys "e" - end and "q" - quit)
and "when you are on command line" (then you basically are starting LBC)

Rico

[rico666]

LBC going down around 20:00 UTC, downtime about 30 minutes. (= should be up 20:30 UTC)

New IP will be 185.157.21.48, should the DNS not catch up soon enough, you could enter that in your /etc/hosts
for lbc.cryptoguru.org


Rico

edit:

Server up since 20:40, clients pouring in again. :-) Thanks for the patience.

[Jude Austin]

Is this project losing steam?

Come on colliders!

[becoin]

Is this project losing steam?

Yes, every project based on free electricity is nonsense.

I hate to see so much talent wasted on nonsensical projects.

[rico666]

Is this project losing steam?

Come on colliders!

I guess for many clients, it seems pointless to always look at

Code:

...
Ask for work... got blocks [177666153-177668392] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Ask for work... got blocks [177674889-177677128] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Ask for work... got blocks [177684009-177686248] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Ask for work... got blocks [177690281-177692520] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Ask for work... got blocks [177699049-177701288] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Ask for work... got blocks [177707497-177709736] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Ask for work... got blocks [177714681-177716920] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Ask for work... got blocks [177722425-177724664] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Ask for work... got blocks [177729081-177731320] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Ask for work... got blocks [177737817-177740056] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Ask for work... got blocks [177746777-177749016] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Ask for work... got blocks [177753401-177755640] (2348 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
...
yadda yadda - you get the idea

If I didn't know, that between each two 'o' all of a sudden a "FOUND: ..." message may appear and the probability of the hash160 found containing 0.0001 BTC being as high as finding e.g. "bcadb700c24da04b17feb9aa9bd71e368a4b623c", I would miss the motivation too. Maybe it's a good thing, because everyone who participated because he hoped "to make a quick buck" is gone now.

Right now, the pool has had only one true find after searching 35 trillion keys. We have now searched almost 187 trillion keys without another find, so yeah it may be getting boring for some. The attention span of the general population nowadays seems way too short without augmenting medication. 

I had lots of other things to do in the past time, but when time allowed it, I looked into the OpenCL generator. I also have a 6% faster CPU generator running here on my notebook from time to time doing janitoring work, but 6% was not worth it to release it yet.

I incspected hashcat for their SHA256 and RIPEMD160 OpenCL code and contrary to vanitygen which has around 15 MKeys/s on my notebook GPU, the hashcat code suggests way more should be possible (RIPEMD160 does 400 Mhash/s, SHA256 does 200MHash/s). I believe with the EC arithmetics and the bloom filter lookup both on GPU, I should be able to squeeze almost 100 MKeys/s out of my GPU.

That is again almost 13 times speedup to my current Pleiades prototype (a hacked vanitygen).

While I do not know exactly when I will be able to spend how much time hacking that, one thing I am pretty sure about: No matter what the stats say,
the pool will hit the private key to 1NpnQyZ7x24ud82b7WiRNvPm6N8bqGQnaS in 2017.


Rico

[rico666]

Yes, every project based on free electricity is nonsense.

I hate to see so much talent wasted on nonsensical projects.

You are in no position to make any judgement about talent.


Rico

[rico666]

Before I forget

https://lbc.cryptoguru.org/trophies

#48 - almost a week ago.


Rico

[arulbero]

My test is ok:

Code:

antonio@ubuntu:~/collider$ sudo ./LBC -x
Will use 0 CPUs.
Best generator chosen: gen-hrdcore-sse41-linux64
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your maximum speed is 204516 keys/s per CPU core.
PAGE-TO: 0 PAGE-FROM: 0

Test ok. Your test results were stored in FOUND.txt.
Have a look and then you may want to remove the file.
o2d17543d32448acc7a1c43c5f72cd5be459ab302:u:(hex)priv:000000000000000000000000000000000000000000000000000000000000005f
02e62151191a931d51cdc513a86d4bf5694f4e51:c:(hex)priv:0000000000000000000000000000000000000000000000000000000000000066
9d74ffdb31068ca2a1feb8e34830635c0647d714:u:(hex)priv:00000000000000000000000000000000000000000000000000000000000f9f8d
3d6871076780446bd46fc564b0c443e1fd415beb:c:(hex)priv:00000000000000000000000000000000000000000000000000000000000f9f8d
Ending test run.


antonio@ubuntu:~/collider$ ls
bench.pst  FOUND.txt  funds_h160.blf  gen-hrdcore-sse41-linux64  LBC

but then:

Code:

sudo ./LBC 
Best generator chosen: gen-hrdcore-sse41-linux64
PAGE-TO: 0 PAGE-FROM: 0
Ask for work... Server doesn't like us. Answer: perm withdrawn.

antonio@ubuntu:~/collider$ sudo ./LBC -c 1 -t 1
Best generator chosen: gen-hrdcore-sse41-linux64
PAGE-TO: 0 PAGE-FROM: 0
Ask for work... Server doesn't like us. Answer: perm withdrawn.

antonio@ubuntu:~/collider$ sudo ./LBC -l 0 -c 1 -t 1:0
Best generator chosen: gen-hrdcore-sse41-linux64
PAGE-TO: 0 PAGE-FROM: 0
Ask for work... Server doesn't like us. Answer: malformed request.

antonio@ubuntu:~/collider$ sudo ./LBC -p 1000-1001 
Loop off! Work on blocks [1000-1001] (2 Mkeys)
Will use 0 CPUs.
Best generator chosen: gen-hrdcore-sse41-linux64
PAGE-TO: 1001 PAGE-FROM: 1000
Estimated duration: infd NaNh NaNm NaNs
Too many requested pages [1000,1001]. Limiting work per iteration to 1 day.
New range: [1000, 1000].
oServer doesn't like us. Answer: perm withdrawn.

antonio@ubuntu:~/collider$ sudo ./LBC -q
Server answer to 'query' is:
{
"nil" : "malformed request"
}
'done' means we have delivered      0.000 valid Gkeys.

What is the problem?

[rico666]

Hi,

My test is ok:

Ok.

Ask for work... Server doesn't like us. Answer: malformed request.

what does ./LBC -v say? You should have version 0.899

If you do have version 0.899, then the messages simply say you have tampered with the LBC source code.
If you haven't - which is the better alternative - the file "bench.pst" is simply not readable to LBC.
In that case, it should be sufficient to do a "sudo chown antonio *" on the files.

Rico

[arulbero]

Code:

antonio@ubuntu:~/collider$ sudo ./LBC -V
[sudo] password di antonio: 
0.899

antonio@ubuntu:~/collider$ sudo chown antonio *

antonio@ubuntu:~/collider$ ls -al *
-rw-r--r-- 1 antonio root          114 dic 19 22:41 bench.pst
-rw-r--r-- 1 antonio root          472 dic 19 22:43 FOUND.txt
-rw-r--r-- 1 antonio antonio 536870912 dic 19 17:36 funds_h160.blf
-rwxr-xr-x 1 antonio antonio   1074624 dic 19 17:10 gen-hrdcore-sse41-linux64
-rwxr-xr-x 1 antonio antonio     34671 dic 18 16:06 LBC
-rw-r--r-- 1 antonio root        50166 dic 18 18:56 LBCdiag.txt

antonio@ubuntu:~/collider$ sudo ./LBC  -c 1 -t 1:0
Best generator chosen: gen-hrdcore-sse41-linux64
PAGE-TO: 0 PAGE-FROM: 0
Ask for work... Server doesn't like us. Answer: error 0x567.

Another error...

[rico666]

Code:

-rwxr-xr-x 1 antonio antonio     34671 dic 18 16:06 LBC

antonio@ubuntu:~/collider$ sudo ./LBC  -c 1 -t 1:0
Best generator chosen: gen-hrdcore-sse41-linux64
PAGE-TO: 0 PAGE-FROM: 0
Ask for work... Server doesn't like us. Answer: error 0x567.

Another error...

Then we are back at the "you have tampered with the LBC source code" hypothesis.

Code:

$ wget ftp://ftp.cryptoguru.org/LBC/client/LBC
$ ll LBC 
-rwxr-xr-x 1 rico rico 34675 Dec 20 13:30 LBC

LBC should be 34675 bytes long - not 34671

Rico

[arulbero]

Ok, now it works!!!  Thanks!!

Code:

antonio@ubuntu:~/collider$ rm LBC

antonio@ubuntu:~/collider$ wget ftp://ftp.cryptoguru.org/LBC/client/LBC
--2016-12-20 14:05:35--  ftp://ftp.cryptoguru.org/LBC/client/LBC
           => "LBC"
Risoluzione di ftp.cryptoguru.org (ftp.cryptoguru.org)... 92.43.104.60
Connessione a ftp.cryptoguru.org (ftp.cryptoguru.org)|92.43.104.60|:21... connesso.
Accesso come utente anonymous ... Accesso eseguito.
==> SYST ... fatto.    ==> PWD ... fatto.
==> TYPE I ... fatto.  ==> CWD (1) /LBC/client ... fatto.
==> SIZE LBC ... 34675
==> PASV ... fatto.    ==> RETR LBC ... fatto.
Lunghezza: 34675 (34K) (non autorevole)

LBC                       100%[====================================>]  33,86K  --.-KB/s    in 0,05s   

2016-12-20 14:05:35 (671 KB/s) - "LBC" salvato [34675]


antonio@ubuntu:~/collider$ ls -al *
-rw-r--r-- 1 antonio root          114 dic 19 22:41 bench.pst
-rw-r--r-- 1 antonio root          472 dic 19 22:43 FOUND.txt
-rw-r--r-- 1 antonio antonio 536870912 dic 19 17:36 funds_h160.blf
-rwxr-xr-x 1 antonio antonio   1074624 dic 19 17:10 gen-hrdcore-sse41-linux64
-rw-r--r-- 1 antonio antonio     34675 dic 20 14:05 LBC
-rw-r--r-- 1 antonio root        50166 dic 18 18:56 LBCdiag.txt


antonio@ubuntu:~/collider$ sudo ./LBC  -c 1 -t 1:0
Best generator chosen: gen-hrdcore-sse41-linux64
PAGE-TO: 0 PAGE-FROM: 0
Ask for work... got blocks [200617417-200618024] (637 Mkeys)
oo

[Haze]

Right now, the pool has had only one true find after searching 35 trillion keys.

How do we know? Is it on the stats page?