Large Bitcoin Collider (Collision Finders Pool)

[adaseb]

This is a very interesting project. I have a few very old GPUs that can't mine ZEC/ETH/XMR so I modded the OCLVanitygen to try and find the 51st key from that "32BTC+ Contest" thread.

The problem I had was that if the GPUs are inside a 1x riser then the speed is 50% of what it should be. Only the GPUs in the 4x-8x-16x slots perform up to speed (~20-30MH/s per GPU).


With that speed it would probably take over 3 months just to find the 51st key.

I think the best proposal would be to try and dual mine kind of like the Claymore miner. Where you are mining ETH and with the unused GPU core you can mine to find the 51st key. Like that you wouldn't be losing any speed mining ETH. However running Vanitygen at the same time as ETH/ZEC/XMR greately slow down the mining speed.

[1714494172]

1714494172

[1714494172]

1714494172

[1714494172]

1714494172

[rico666]

This is a very interesting project. I have a few very old GPUs that can't mine ZEC/ETH/XMR so I modded the OCLVanitygen to try and find the 51st key from that "32BTC+ Contest" thread.

The problem I had was that if the GPUs are inside a 1x riser then the speed is 50% of what it should be. Only the GPUs in the 4x-8x-16x slots perform up to speed (~20-30MH/s per GPU).

With that speed it would probably take over 3 months just to find the 51st key.

Quote from https://lbc.cryptoguru.org/stats

at current speed - the pool will hit the private key to 1NpnQyZ7x24ud82b7WiRNvPm6N8bqGQnaS (#51 of the puzzle transaction) in 104 to 292 days.

(69.06 Mkeys/s)

LBC isn't specifically looking for #51. These puzzle transaction addresses are merely waypoints. We're looking at everything - including uncompressed addresses (which oclvanitygen does not). So the two addresses with funds we have found are in fact uncompressed ones.


Rico

[ImHash]

Can we use Golem super computer to find a collision? or design ASIC for doing it?
A bit off topic but since you seem like to know things about bitcoin, is it possible to have negative blocks in blockchain? like block 0,1,2 and -0,-1,-2.


Why is this 964MB to download?

[rico666]

Can we use Golem super computer to find a collision?

I had to look that up. Yes, at least certain nodes in that network would be suitable. Actually LBC would be a perfect application, because it is parallelizable so well. (Golem has high interconnectivity latencies, making it appear somewhat like the early Beowulf clusters).

or design ASIC for doing it?

One step after another. :-)
In fact, LBC clients will probably undergo a similar evolution like BTC miners did: CPU -> GPU -> FPGA -> ASIC.
We're at the transition phase between CPU and GPU.

But there are already things like "OpenCL for FPGAs" I am aware of. and should we bring the LBC client to a FPGA, I believe for a specialised company it should be technically no big deal to make an ASIC. Still I am not sure anyone would fork out like 3-4 M$ for such a development.

A bit off topic but since you seem like to know things about bitcoin, is it possible to have negative blocks in blockchain? like block 0,1,2 and -0,-1,-2.

Sort of. Except 0 and -0 :-) you could define -1 as being 110427941548649020598956093796432407238805355338168053038220561162489092
-2 being
110427941548649020598956093796432407238805355338168053038220561162489093
etc.

Why is this 964MB to download?

That's only the LBC appliance for windows users. These days you want to have a linux machine with some Nvidia or AMD GPU installed and then the download is somewhat around 205 MB. And the resulting client is faster.


Rico

[rico666]

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.

We're trying to show a private key collision. Actually SHA256 plays the least part in this.

We know because of the 256->160 bit reduction of RIPEMD160, that there are - on average - 2⁹⁶ private keys per address (if you look at both compressed and uncompressed addresses, there actually are 2⁹⁷, but that's just a fun fact)

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?

I don't know if it does prove a point. I don't think so. When I started it, I thought it would be very interesting to actually see a live collision.
Like we all know there must be many (2⁹⁷ is a quite big number) private keys for any address out there. If anything, my point is, that the private key to your bitcoin address does not provide true 256bit security, but thanks to RIPEMD160 only 160bit security - at best. Evidently, when the public key is known, the security of your private key drops to 128bit - at best.

So when you have a bitcoin address with funds on it, and even if you know it has some private key in the - say - 2²⁴⁰ numeric range, the LBC could basically hit an alternate key to it tomorrow - in the 2⁴⁹ numeric range. Probability is low, but not 0.  Also, there is no safe distance. more here: https://lbc.cryptoguru.org/man/theory

Another fun fact is that contrary to BTC mining, we started out with max difficulty and the difficulty is getting lower and lower (thus the probability higher and higher) every day. That's exceptional fun - isn't it? 


Rico

[becoin]

That's exceptional fun - isn't it? 

Yes, it is.  28 pages of exceptional blah-blah and not a single collision found.

[Jude Austin]

That's exceptional fun - isn't it? 

Yes, it is.  28 pages of exceptional blah-blah and not a single collision found.

Go away, you are like a gnat!

Buzz buzzing around the thread driving Rico nuts.

[Jude Austin]

That's exceptional fun - isn't it? 

Yes, it is.  28 pages of exceptional blah-blah and not a single collision found.

Go away, you are like a gnat!

Buzz buzzing around the thread driving Rico nuts.

Damn, it was that easy??

[rico666]

More on the technical side, I managed to get the Bloom filter check done on GPU.
Biggest problem was actually the printout in case of a hit.

This raised the keyrate of my notebook from 7.3 Mkeys/s to 8.2 Mkeys/s, while the GPU
is still at 34% usage with 4 CPU cores firing at it.

Needless to say, it works perfectly on my system (24h burn-in with no problems), but
raises a segmentation fault on AWS "hardware".  

Meanwhile, in ECC land, a potential 2.x speedup is on the horizon, which would translate
into a 16 - 24 Mkeys/s on my notebook with the GPU usage at around 70%. We'll see.

Also, I'm falling behind in the top30 from #5 to #7, but I think it's a good thing. 

Rico

[ylpkm]

I'd be down to test on windows 10, ive got a 1080 i could use too if you make a windows build with nvidia gpu support.

[Gyrsur]

let's proof the strength of BitCoin! LOL!

[rico666]

I have updated/extended the docs for maintenance-free auto-update and auto-notify LBC mode of operation:

How to let your LBC instance run and make sure it looks for updates and in case there are some,  does auto-update (itself, the generator, the BLF file)

https://lbc.cryptoguru.org/man/user#eternal-run

How to notify you in case of a find automatically either via email

https://lbc.cryptoguru.org/man/user#email-notification

or via HTTP request (as some people have LBC running on servers where TCP port 25 is blocked):

https://lbc.cryptoguru.org/man/user#http-request-notification

Have Fun.



Rico

[ylpkm]

Had some issues getting it running on 14.xx ubuntu, and this allowed it to run, if anyone had some trouble try this.
So of course ensure you have these installed:
use: sudo apt install  "the name of the items below without quotations"
perl (5.14 or newer) - probably preinstalled
bzip2 - most probably preinstalled
xdelta3 - look for a "xdelta3"-named package.
libgmp-dev      -The GNU Multiple Precision Arithmetic Library
gcc


----------------------------
Then in terminal use:
cpan install File::Spec
cpan install JSON                (dont remember if this one actually installed)
cpan install LWP::UserAgent
cpan install Net::SSLeay
cpan install LWP::Protocol::https
cpan install Parallel::ForkManager
cpan install Term::ReadKey
cpan install Win32::SystemInfo     (dont know if this one and the ones below it are necessary but i did it anyway)
cpan install Data::Dumper
cpan install Digest::MD5
cpan install File::Temp
cpan install Math::BigFloat
cpan install Getopt::Long
-------------------------------------
Then for opencl files:
sudo apt get install ocl-icd-opencl-dev
cpan install OpenCL
----------------------------
then you should be able to run lbc by using:
perl lbc -h
or any other parameter you want after the lbc like -x -gpu -id -s -a

(Dev I had a question, How much merit needs to be brought to the pool to have gpu enabled?  If this guide merits enough if you could pm me, id like to see what the hashrate of my gpu is. Thanks for your time.)

[rico666]

Had some issues getting it running on 14.xx ubuntu, and this allowed it to run, if anyone had some trouble try this.
So of course ensure you have these installed:
use: sudo apt install  "the name of the items below without quotations"
perl (5.14 or newer) - probably preinstalled
bzip2 - most probably preinstalled
xdelta3 - look for a "xdelta3"-named package.
libgmp-dev      -The GNU Multiple Precision Arithmetic Library
gcc


----------------------------
Then in terminal use:
cpan install File::Spec
cpan install JSON                (dont remember if this one actually installed)
cpan install LWP::UserAgent
cpan install Net::SSLeay
cpan install LWP::Protocol::https
cpan install Parallel::ForkManager
cpan install Term::ReadKey
cpan install Win32::SystemInfo     (dont know if this one and the ones below it are necessary but i did it anyway)
cpan install Data::Dumper
cpan install Digest::MD5
cpan install File::Temp
cpan install Math::BigFloat
cpan install Getopt::Long
-------------------------------------
Then for opencl files:
sudo apt get install ocl-icd-opencl-dev
cpan install OpenCL
----------------------------
then you should be able to run lbc by using:
perl lbc -h
or any other parameter you want after the lbc like -x -gpu -id -s -a

(Dev I had a question, How much merit needs to be brought to the pool to have gpu enabled?  If this guide merits enough if you could pm me, id like to see what the hashrate of my gpu is. Thanks for your time.)

May I ask why you just didn't

Code:

$ sudo apt install perl bzip2 xdelta3 libgmp-dev libssl-dev gcc make
$ wget ftp://ftp.cryptoguru.org/LBC/client/LBC
$ chmod a+x LBC
$ ./LBC -h

because ./LBC -h should do all the CPAN stuff already and for this to work, you definitely need the apt install before that.
You do not need Win32::Systeminfo on Linux - obviously. Quite some of the mentioned Perl modules are belonging to Perl core
i.e. are installed as soon as Perl is installed.

I think SlarkBoy has a very similar configuration to yours. You can see what performance to expect a couple threads up
https://bitcointalk.org/index.php?topic=1573035.msg17969538#msg17969538


Rico

[ylpkm]

May I ask why you just didn't

Code:

$ sudo apt install perl bzip2 xdelta3 libgmp-dev libssl-dev gcc make
$ wget ftp://ftp.cryptoguru.org/LBC/client/LBC
$ chmod a+x LBC
$ ./LBC -h

because ./LBC -h should do all the CPAN stuff already and for this to work, you definitely need the apt install before that.
You do not need Win32::Systeminfo on Linux - obviously. Quite some of the mentioned Perl modules are belonging to Perl core
i.e. are installed as soon as Perl is installed.


Rico

Cool cool thanks. I tried it that way and using chmod and it still wouldnt allow LBC to run. It would give me "JSON not found". So I opened up LBC in Gedit and just installed whatever it said it could call for. After that it worked for me. For me, the necessary Perl core modules were not installed so idk why I had to manually do it.

[rico666]

@DrTouchUrSon

Nice Id.  

If I may suggest - crank up the -t parameter. You seem to run quite some capacity with -t 1
As stated in the docs, this does cost you some keyrate. Try -t 10 and see what happens.

@ylpkm

It would give me "JSON not found".

looking at the source, the complete printout is

Code:

print "$module not found - installing it.\n";

then followed by a

Code:

qx{cpan force install $module};

LBC finds out what's missing and does install by itself.


Rico

[ylpkm]

It would say that "module not found, installing it", and nothing would happen, I waited 15 min, came back, closed the terminal and tried again and nothing. So thats why I manually did it. I'm not sure if the folder had permission issues, I set everything to be able to create and delete files, ran lbc as sudo, and yeah. Just posting so if anyone else had trouble they can fix it themselves quickly.
Thanks for the tip, I just tested a low t to see the keyrate, ill put it back to 10.

[rico666]

It would say that "module not found, installing it", and nothing would happen, I waited 15 min,

Yeah, it's necessary to hold the "Return"-key for a while (like 5 seconds), which auto-answers some "Shall I install xyz?" CPAN questions that unfortunately are not seen on the screen. It may be a little bit counter-intuitive.  I'll see if I can fix this nicely.

Rico

[rico666]

Only the server providing the FTP services will be unavailable for 20 minutes, LBC server will operate without interruption.

Rico

[Jude Austin]

It would say that "module not found, installing it", and nothing would happen, I waited 15 min,

Yeah, it's necessary to hold the "Return"-key for a while (like 5 seconds), which auto-answers some "Shall I install xyz?" CPAN questions that unfortunately are not seen on the screen. It may be a little bit counter-intuitive.  I'll see if I can fix this nicely.

Rico

It only happens on the cpan install of JSON.

I always manually run cpan install JSON prior to running LBC for the first time.

Then after JSON installs I run the LBC client and everything except xdelta3 will install.

I then install xdelta3 using apt-get.