Large Bitcoin Collider (Collision Finders Pool)

[Real-Duke]

Game over ? from 30 bounties I found 21 on the servers with new blf ... and some on the old ... how many I found hell knows :> but I havent found anything for the past 30+ hours

I found only one last week and as far as I know another one was found by coinpiet so 23 until now?

[rico666]

I'm working on a table to account for everything we know so far from the SlarkBoy Bounty Galore: https://bitcointalk.org/index.php?topic=1877935.msg18672178#msg18672178

[Gleb Gamow]

Looks like rico666 got the mods to have some of my damaging posts deleted from this thread. 

[cagrund]

My first found! 

#52 of the puzzle transaction, today at 14:40.

36af659edbe94453f6344e920d143f1778653ae7:c:priv:000000000000000000000000000000000000000000000000000efae164cb9001 + 0xe3b


Best regards, Carsten.

[unknownhostname]

My first found! 

#52 of the puzzle transaction, today at 14:40.

36af659edbe94453f6344e920d143f1778653ae7:c:priv:000000000000000000000000000000000000000000000000000efae164cb9001 + 0xe3b


Best regards, Carsten.

GZ  .. road to 10k BTC started :>

[Gyrsur]

My first found! 

#52 of the puzzle transaction, today at 14:40.

36af659edbe94453f6344e920d143f1778653ae7:c:priv:000000000000000000000000000000000000000000000000000efae164cb9001 + 0xe3b


Best regards, Carsten.

GZ  .. road to 10k BTC started :>

LOL, just 52 bit of 256. waiting to see 53 bit in ?? weeks. effort will go up non-linear to crack more bits of such weak private keys.

[BurtW]

Please see my related thread here:  https://bitcointalk.org/index.php?topic=1895455.0

[ligor]

My first found! 

#52 of the puzzle transaction, today at 14:40.

36af659edbe94453f6344e920d143f1778653ae7:c:priv:000000000000000000000000000000000000000000000000000efae164cb9001 + 0xe3b


Best regards, Carsten.

You found the keys to this address. Did you withdraw all the money? This is stealing, are not you afraid that the owner will file a search? So does the entire Large Bitcoin Collider?

[Jude Austin]

My first found! 

#52 of the puzzle transaction, today at 14:40.

36af659edbe94453f6344e920d143f1778653ae7:c:priv:000000000000000000000000000000000000000000000000000efae164cb9001 + 0xe3b


Best regards, Carsten.

You found the keys to this address. Did you withdraw all the money? This is stealing, are not you afraid that the owner will file a search? So does the entire Large Bitcoin Collider?

You're dumb as shit, the person who put the funds on that address did it with intentions of people finding it.

See this thread: https://bitcointalk.org/index.php?topic=1306983.0

Get the fuck out of here with your assumptions.

Thanks,
Jude

[Gleb Gamow]

My first found! 

#52 of the puzzle transaction, today at 14:40.

36af659edbe94453f6344e920d143f1778653ae7:c:priv:000000000000000000000000000000000000000000000000000efae164cb9001 + 0xe3b


Best regards, Carsten.

You found the keys to this address. Did you withdraw all the money? This is stealing, are not you afraid that the owner will file a search? So does the entire Large Bitcoin Collider?

You're dumb as shit, the person who put the funds on that address did it with intentions of people finding it.

See this thread: https://bitcointalk.org/index.php?topic=1306983.0

Get the fuck out of here with your assumptions.

Thanks,
Jude

WOW! By using the Giant Goat Collider, I just found this address: https://blockchain.info/address/1NBC8uXJy1GiJ6drkiZa1WuKn51ps7EPTv

[ligor]

Get the fuck out of here with your assumptions.

Thanks,
Jude

Sorry, did not want to offend, maybe just Google translator did not translate my question correct.

[kknd]

win7 ultimate running:
vmware + ubuntu


1) first pases:

sudo apt-get update
sudo apt-get upgrade
sudo apt install perl bzip2 xdelta3 libgmp-dev libssl-dev gcc make
sudo cpan force install JSON
sudo cpan force install LWP
sudo cpan force install Net::SSLeay
sudo apt-get install libnet-ssleay-perl
sudo apt-get install libcrypt-ssleay-perl
sudo apt-get install LWP::Protocol::https
sudo apt-get install Parallel::ForkManager
sudo apt-get install Term::ReadKey
sudo apt install ocl-icd-opencl-dev

2) passe dor error:

Code:

ubuntu@ip:~/$ ./LBC
Will use 0 CPUs.
Benchmark info not found - benchmarking... failed to open bloom filter 'funds_h160.blf': No such file or directory
Generator validity check failed. Expected: 5, Got: 0
With output:
--
ubuntu@ip-:~/$

Download file:
http://ftp://ftp.cryptoguru.org/LBC/blf/170719-d6e6afe549f661770b8fb1e61a98fe06.blf.bz2
(<ewest dateYYMMDD>-<md5>.blf.bz2
bunzip2 it, rename to funds_hash160.blf and off you go.

3) set login and password:
./LBC -id "LOGIN" -secret "password:password"

[prakbit]

the link to the LBC Appliance is not working. can you pls post a new link so i can start contributing ?

[BitTrader1000]

the link to the LBC Appliance is not working. can you pls post a new link so i can start contributing ?

same for me. Cannot download with wget. Connection times out

[fiscorcle]

the link to the LBC Appliance is not working. can you pls post a new link so i can start contributing ?

same for me. Cannot download with wget. Connection times out

Triple same for me here

[User365]

Amazing work you are doing here but I think bitcoin needs a security update. This shouldn´t be possible. 

[arulbero]

the link to the LBC Appliance is not working. can you pls post a new link so i can start contributing ?

same for me. Cannot download with wget. Connection times out

Triple same for me here

Have you tried this ?

[BurtW]

This should not be possible.  

Your statement is illogical nonsense.  It is easy to calculate that everything being done by the LBC is mathematically possible, they are doing it, and, in fact, you can see with your own eyes that it is really happening.  Wishing something to be not possible when it is obviously possible is pathologically pointless.

All that the LBC and the puzzle transaction are showing/proving is that you should use full entropy private keys.  If you do that then your Bitcoins are totally safe.

I think bitcoin needs a security update

Agreed, but not for the reasons you think.  In certain cases there was a small hole in the fact that the Bitcoin address is only 160 bits instead of the full 256 bits but we now have an upgrade to fix that:

Increased security for multisig via pay-to-script-hash (P2SH)

Multisig payments currently use P2SH which is secured by the 160-bit HASH160 algorithm (RIPEMD of SHA256). However, if one of the signers wishes to steal all the funds, they can find a collision between a valid address as part of a multisig script and a script that simply pays them all the funds with only 80-bits (280) worth of work, which is already within the realm of possibility for an extremely well-resourced attacker. (For comparison, at a sustained 1 exahash/second, the Bitcoin mining network does 80-bits worth of work every two weeks)

Segwit resolves this by using HASH160 only for payments direct to a single public key (where this sort of attack is useless), while using 256-bit SHA256 hashes for payments to a script hash.

From:

https://bitcoincore.org/en/2016/01/26/segwit-benefits/

[fiscorcle]

Amazing work you are doing here but I think bitcoin needs a security update. This shouldn´t be possible. 

Do you know the basic rules behind Bitcoin? Lol

[rsalazarm]

Hello!!! Is there anybody out there??

Seems that LBC is scam... or, in other words, if you run LBC on your computer, your computer is running and working for this/these guy/s, and you will see no addresses with bitcoins:

    Seems that rico666 is trying to obtain a new "allbalance file" with the last addresses with bitcoins (https://github.com/znort987/blockparser/issues/65). In the meantime he continues using the same *.blf file, which has the 51, 52 and 53 puzzle addresses included.

Running brainflayer over the current blf file, it detects the addresses with bitcoins:
mmm@Proliant:~/brainflayer$ ./brainflayer -v -I 000000000000000000000000000000000000000000000000000efae164cb9e00 -b funds_h160.blf 36af659edbe94453f6344e920d143f1778653ae7:c:(hex)priv:000000000000000000000000000000000000000000000000000efae164cb9e3c Rate: 253812.80 p/s found: 1/1572864 elapsed: 7.217 s

mmm@Proliant:~/brainflayer$ ./brainflayer -v -I 00000000000000000000000000000000000000000000000000180788e47e3200 -b funds_h160.blf 2f4870ef54fa4b048c1365d42594cc7d3d269551:c:(hex)priv:00000000000000000000000000000000000000000000000000180788e47e326c Rate: 291779.34 p/s found: 1/1048576 elapsed: 3.578 s

mmm@Proliant:~/brainflayer$ ./brainflayer -v -I 00000000000000000000000000000000000000000000000000075070a1a00900 -b funds_h160.blf ef6419cffd7fad7027994354eb8efae223c2dbe7:c:(hex)priv:00000000000000000000000000000000000000000000000000075070a1a009d4 Rate: 345945.88 p/s found: 1/524288 elapsed: 1.732 s

But running LBC in the same address range, it does not detect something:

mmm@Proliant:~/LBC$ ./LBC --id XXX -s XXX -p '#xefae164cb9e00-#xefae164cbffff' Loop off! Work on blocks [4021163596-4021163596] (1 Mkeys) Will use 2 CPUs. (0.67 Mkeys/s) mmm@Proliant:~/LBC$ ./LBC --id XXX -s XXX -p '#x180788e47e3200-#x180788e47fffff' Loop off! Work on blocks [6450351687-6450351687] (1 Mkeys) Will use 2 CPUs. (0.69 Mkeys/s)

OPS!!! A bit strange, wright?


At the same time, you can detect a lot of network activity, so, from my understanding, you computer contacts with the server and sends it the information about the addresses found but nothing is communicated to you...

As I said, SCAM!!!

Btw, why the generator code is not published so in this way we can review it, and, if necessary, compile it at home?