Topic: Large Bitcoin Collider Thread 2.0 - page 8. (Read 57423 times)

The donation pot cannot collect couple of BTC for GPU development  

ASIC development costs around $10-100MLN.

The worst thing is - even if you get an investor with 100 megabucks, the chinese will steal your tech and start flooding the market with cheap clones.

I guess, LBC (or it's clone projects) should go the BTC way - CPU-GPU-FPGA-ASIC... GPU is still immature, no FPGA. You want too much.

Interesting project. Any wallet miner asics work in progress yet?

Once this attracts real size io/hashpower, could get interesting rather quick lol

One way to make it happen, how about a bounty pot bitcoiners/donors can donate to - would maybe motivate to mine it

Salve! Do you have instructions for new setting GPU? On i7-4820K 3.7GHz I had 3.9 million keys. Plugged gf 1050ti and now have speed 22 million.
nvidia-smi shows 6 processes with 561MiB and 4 with 49MiB. Changing --cpus from 6 to 20 doesn't matter, speed is around 21-22 millions keys.
Shouldn't be 35?

nvidia-smi -pm 1 did nothing.
With --cpus 6 I have
GPU-Utilization 60% and CPU utilization 80%. So what is bottleneck?

Temp is low (40C).

The number of possible words for each of the 12 words is 2048 so the total number of 12 word combinations is:

2048¹² = 5.44452 x 10³⁹

That is for the weaker 12 word seeds.  I use the Trezor wallet which uses a 24 word seed so for my wallet the number of possible ways to select the 24 words is:

2048²⁴ = 2.96428 x 10⁷⁹

Compare these numbers to the total number of Bitcoin addresses:

2¹⁶⁰ = 1.46150 x 10⁴⁸

and the total number of private/public key pairs:

2²⁵⁶ = 1.15792 x 10⁷⁷

First, you see that you should really be using a 24 word seed and not a 12 word seed.

Next, I believe the amount of work to go from the seed words to the xPriv then to the xPub then to the generated Bitcoin addresses is more than the amount of work LBC does to calculate the next private key [just a simple increment], the next public key [just add G to the previous public key], then to the Bitcoin address.

So, going through all the possible 12 word seeds is "harder" than going through all the Bitcoin addresses on a Bitcoin addresses / second basis.

Plus, after going through all the possible 12 word seeds you will only hit about 2048¹² / 2¹⁶⁰ = 0.00000037253 % of all Bitcoin addresses.

ASIC miners are only used for mining bitcoins and that's it, not cracking private keys.

Could you make a software or other transformer to allow the use of bitcoin mining ASIC for the LBC? Things would really speed up with couple of antminers.

On the other hand, could one search for wallets by brute forcing the 12 phrase keywords?

Hm... tested  my RIG Cel G1840 and GTX 1060 3g and got from 1 core about 600k and 1 core with gpu about 2M.... with GPU load about 50%...... what is wrong? slow CPU?

and got 4.5M from 1  core laptop CPU i7-7500 with GTX 940m ....

If you were on the Discord, you'd know by now, that the best cost-efficient GPU is a 1050Ti, where you can get for 150 bucks (or less) as much as 40 Mkeys/s with the right CPU.

user glatzer44 is also doing some work to get more out of the higher-end cards which behave not as good in price/performance category.

A small WX4100 also tops somewhere at 30 Mkeys/s, but costs double the 1050Ti.

New ATI Vega64 ... are at the moment a monumental drama of misery. But there it's the software, the hardware should be great, so we wait.

Thanks for the advice! I actually have a decent GPU but I can't use it as I'm not auth yet I think since I only started a couple days ago and my average speed is 1,8 Mkeys/s. I'll take a look at what Google has to offer, thanks again!

Google offers $300 "credit" for newcomers to their cloud services. The most efficient hardware is 8core/7.2GB will make 3.0-3.3 megakeys a second. One server costs $150 a month. So you'll have a free server for 2 months.

I guess, buying a videocard to your own PC is much more funds-efficient.

Actually, this project lacks a reasonable comparison of different cards.
I'm not ready to buy a $1000 card like nvidia 2000, but it's totally unclear how would cheaper aftermarket cards behave.
Also, ATI cards were always much stronger for mining, is it the same for LBC?  

There is always someone who has to try and break the stuff you make..

But, respect.. This is a very interesting project.

Thank you very much! I'm currently looking for a vps to run this 24/7 with a better speed and should be around $50/month. Any suggestions?

You started the collider and you are searching with 1 800 000 keys/second.

you can see the file FOUND.txt in the same directory as the LBC client and look at is in a text editor, by doing or

Total newb here when it comes to linux but please take a look at the attached image and let me know if I actually started the collider

https://i.imgur.com/BLSDMjc.png

If it's started how can I see the FOUND.txt file in case something is found? Any suggestion is much appreciated.

edit: also, does 1,8 Mkeys/s mean that I'm searching through 1,800,000 keys per second?

Client -> Generator challenge. To make sure the client is talking to a legit generator.

Hi! what is the -c in process? why they are diferent? 
http://c2n.me/3Qpu2Gr

We have now our own directory.io, clone as the original site seems to have gone.

Clicking on the directory.io in https://lbc.cryptoguru.org/stats leads to https://lbc.cryptoguru.org/dio/101091723026432 (or whatever the page at the time of the click is)

I've enabled a rate limiter for all my beloved leechers out there, who still haven't understood how the page works.


With the above, the reverse way is possible too:

https://lbc.cryptoguru.org/dio/priv/5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreMQiR4w7

will take you to the page containing that privkey and the address.

ASICs - as the "Application-Specific" part suggests - are of use only for a very narrow usage case. Bitcoin miners have scrapyard value beyond BTC* mining.

I asked http://www.orsoc.se/ what the cost of ASIC development might be about 2 months after launching the pool.
ORSoC is/was the technology development company behind KnC and I thought it would be a good address to ask.

Unfortunately never got any answer. I might try again.

Bitcoin miners do a SHA256d essentially.
The LBC does  ECC, followed by hash160, followed by bloom filter lookup

Now the hash160 is actually less demanding than SHA256d and if it was only for that, I'm pretty sure that hash160 ASICs could deliver more performance than SHA256d ASICs.
The ECC however, requires 256bit multiplications and that is serious stuff taking up whole FPGA circuits. (at least until a few years ago)

At the moment we do these ECC things on CPU and hash160 on GPU

An ASIC doing hash160 and Bloom-filter lookup (512MB chips containing the BLF connected directly to the ASIC) I can imagine, but I can't imagine how to feed it with ECC data.
ECC on ASIC I can't imagine, but then again, I am a VHDL, Verilog, FPGA, ASIC noob.

It would certainly be good if we managed to establish at least some informal smalltalk with ORSoC (or similar) engineers about this.

rico666 thanks for not sending me to GTFO  Tried to read "What We Do" more attentive.

One question still remains: did you estimate required funds to make FPGA or ASIC clients for LBC? I guess ordinary bitcoin mining ASICs wouldn't be effective (or suitable at all)?

No hard feelings, but I think you have still a lot to read and learn about the project and the concept and tech behind it.

Most of your "suggestions" are result of being badly informed - really.