Pages:
Author

Topic: Large Bitcoin Collider (Collision Finders Pool) - page 9. (Read 193120 times)

legendary
Activity: 3431
Merit: 1233
It certainly must be, as the lower bound for an OpenCL implementation of key generation on my Notebook GPU (Quadro M2000M - 640 cores) is 15 Mkeys/s. (As I said, vanitygen does that - inefficiently - computing the compressed public key once you have computed the uncompressed is quite easy). My estimate is, that we should be able to squeeze 20 Mkeys/s out of the Quadro M2000M.

9 Months later...

Squeezing around 29 Mkeys/s with the current implementation.  Wink

9 Months later... No success.
9 Years later... Will be the same.

Happy burning of your money!
legendary
Activity: 1914
Merit: 2071
9 Months later...

Squeezing around 29 Mkeys/s with the current implementation.  Wink

And I think that now 5 Mkeys/s is possible with only cpus (Inter Xeon CPU E3-1505M v6 @ 3.00GHz, 4 cores).

...

I have an unpublishable GPU prototype based on vanitygen. It's basically half the speed of vanitygen (which has 15 MKeys/s on my notebook), as it uses 2 passes, one for compressed and one for uncompressed public keys. Also, it requires around 4GB RAM on startup until the AVL data structures are fiddled up. So on my notebook, the GPU prototype needs around 4GB memory on startup and 3.4 GB in GPU RAM and gives around 7MKeys/s.

Almost as fast as the first GPU prototype  Smiley  

It certainly must be, as the lower bound for an OpenCL implementation of key generation on my Notebook GPU (Quadro M2000M - 640 cores) is 15 Mkeys/s. (As I said, vanitygen does that - inefficiently - computing the compressed public key once you have computed the uncompressed is quite easy).

To make a comparison between vanitygen and our best cpu generator, look at this rate: MAddresses/s.
I made a program (with the last aecc library and the last sha256 and ripemd optimized functions, without any offset constraint on private keys) that generates only compressed keys via cpu without bloom check.

Vanitygen:     15 MAddresse/s (uncompressed keys, on your GPU)

My program: 13.67 MAddresses/s (compressed keys, on my cpus)
legendary
Activity: 1120
Merit: 1037
฿ → ∞
It certainly must be, as the lower bound for an OpenCL implementation of key generation on my Notebook GPU (Quadro M2000M - 640 cores) is 15 Mkeys/s. (As I said, vanitygen does that - inefficiently - computing the compressed public key once you have computed the uncompressed is quite easy). My estimate is, that we should be able to squeeze 20 Mkeys/s out of the Quadro M2000M.

9 Months later...

Squeezing around 29 Mkeys/s with the current implementation.  Wink
legendary
Activity: 1120
Merit: 1037
฿ → ∞
Hello ,

after downloading LBC client , runing first LBC -h , then LBC --update, I am not getting blf file. Can't proceed without it. Where I can download it ? Is LBC server under maintenance ?

This does not work as well http://ftp://ftp.cryptoguru.org/LBC/blf/171001-d6e6afe549f661770b8fb1e61a98fe06.blf.bz2

BLF files are under https://lbc.cryptoguru.org/static/blf/ now.

Yeah, the FTP server is borked. Will move everything to HTTPS eventually.

newbie
Activity: 4
Merit: 0
Hello ,

after downloading LBC client , runing first LBC -h , then LBC --update, I am not getting blf file. Can't proceed without it. Where I can download it ? Is LBC server under maintenance ?

This does not work as well http://ftp://ftp.cryptoguru.org/LBC/blf/171001-d6e6afe549f661770b8fb1e61a98fe06.blf.bz2

Any help appreciated .

e-mail : [email protected]

Regards,
Mar
legendary
Activity: 2646
Merit: 1129
All paid signature campaigns should be banned.
There are already too many out there. What is going to make yours different from theirs? The entire process is a losing proposition as there is nothing that makes it more successful than just mining and there has yet to be enough power put to the system and that is still a waste as the same power applies to mining would produce the same pay out.
Tell the truth.  You bought your Hero account, right?
sr. member
Activity: 434
Merit: 251
physics, mathematics and engineering
This should not be possible.  Shocked

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.

No, it is not.
I'm sorry if it is too complex for you.

This should not be possible means that I am fully aware that it is possible but I think it would be better if it was not possible. This means I would be in for a security update.

and NOW it is safe if you use full entropy keys  Wink

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

Do you know the basic rules behind Bitcoin? Lol

you man that upgrading would mean hardforking? Well yes
legendary
Activity: 3431
Merit: 1233
Hello!!! Is there anybody out there?Huh?

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:

This project is a scam from the very beginning. So, what? Bitcoin is the nowadays wild west. If you find enough scumbags to form a scam group you're free to participate in whatever scam you like.
full member
Activity: 706
Merit: 111
legendary
Activity: 2646
Merit: 1129
All paid signature campaigns should be banned.
Hello!!! Is there anybody out there?Huh?

...

OPS!!! A bit strange, wright?Huh [NOTE: spelling error, the word here should be "right?Huh"]

...

Great first and only post!  Keep up the good work and someday you will be a Legend in your own mind.
jr. member
Activity: 32
Merit: 11
Works Tongue LOL

KKND@lbc:~/KKND$ sudo ./LBC --id xxx-secret xxx-c 6 -gpu -gopt lws=256 -p 4021163596-4021164000
GPU authorized: yes
Loop off! Work on blocks [4021163596-4021164000] (424 Mkeys)
Estimated duration: 1m 39.57758075s
oooooooooooooooooooooooo
36af659edbe94453f6344e920d143f1778653ae7:c:priv:000000000000000000000000000000000000000000000000000efae164cb9001+0xe3b
 (10.13 Mkeys/s)
newbie
Activity: 1
Merit: 0
Hello!!! Is there anybody out there?Huh?

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?Huh


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?Huh
hero member
Activity: 994
Merit: 502
Amazing work you are doing here but I think bitcoin needs a security update. This shouldn´t be possible.  Shocked

Do you know the basic rules behind Bitcoin? Lol
legendary
Activity: 2646
Merit: 1129
All paid signature campaigns should be banned.
This should not be possible.  Shocked

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:

Quote
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/
legendary
Activity: 1914
Merit: 2071
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 ?
sr. member
Activity: 434
Merit: 251
physics, mathematics and engineering
Amazing work you are doing here but I think bitcoin needs a security update. This shouldn´t be possible.  Shocked
hero member
Activity: 994
Merit: 502
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
full member
Activity: 224
Merit: 102
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
newbie
Activity: 2
Merit: 0
the link to the LBC Appliance is not working. can you pls post a new link so i can start contributing ?
jr. member
Activity: 32
Merit: 11
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
(-.blf.bz2
bunzip2 it, rename to funds_hash160.blf and off you go.

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



Pages:
Jump to: