Large Bitcoin Collider Thread 2.0 - page 8.

BurtW

legendary

Activity: 2646

Merit: 1129

All paid signature campaigns should be banned.

Quote from: bcoinmanager on December 20, 2017, 07:41:17 PM

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

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.

bigvito19

full member

Activity: 706

Merit: 111

Quote from: bcoinmanager on December 20, 2017, 07:41:17 PM

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?

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

bcoinmanager

newbie

Activity: 1

Merit: 0

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?

andreyyv

newbie

Activity: 23

Merit: 0

Hm... tested my RIG Cel G1840 and GTX 1060 3g and got from 1 core about 600k and 1 core with gpu about 2M.... Undecided

with GPU load about 50%...... what is wrong? slow CPU? Huh

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

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: holy_ship on December 18, 2017, 10:40:36 PM

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.

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.

smmintl

newbie

Activity: 3

Merit: 0

Quote from: holy_ship on December 18, 2017, 10:40:36 PM

Quote from: smmintl on December 18, 2017, 04:21:25 AM

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?

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

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!

holy_ship

jr. member

Activity: 109

Merit: 1

Quote from: smmintl on December 18, 2017, 04:21:25 AM

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?

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

SatoshíNackamoto

newbie

Activity: 42

Merit: 0

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

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

smmintl

newbie

Activity: 3

Merit: 0

Quote from: rico666 on December 18, 2017, 02:06:22 AM

Quote from: smmintl on December 17, 2017, 05:15:19 PM

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?

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

Code:

cat FOUND.txt

or

Code:

less FOUND.txt

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?

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: smmintl on December 17, 2017, 05:15:19 PM

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

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?

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

Code:

cat FOUND.txt

or

Code:

less FOUND.txt

smmintl

newbie

Activity: 3

Merit: 0

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?

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: andreyyv on December 17, 2017, 06:53:33 AM

Hi! what is the -c in process? why they are diferent? Huh

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

andreyyv

newbie

Activity: 23

Merit: 0

Hi! what is the -c in process? why they are diferent? Huh

http://c2n.me/3Qpu2Gr

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

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.

Quote from: arulbero on December 06, 2017, 09:52:00 AM

Then you can use this python script, called "lbc_output.py": https://www.dropbox.com/s/q1sgc4gbb26vc99/lbc_output.py?dl=0

Copy the line of FOUND.TXT you are interested of and you get the result:

Code:

$ ./lbc_output.py 2d17543d32448acc7a1c43c5f72cd5be459ab302:u:priv:0000000000000000000000000000000000000000000000000000000000000001+0x5e

Private key : 000000000000000000000000000000000000000000000000000000000000005f
Public  key :
          x : 15d9441254945064cf1a1c33bbd3b49f8966c5092171e699ef258dfab81c045c
          y : d56eb30b69463e7234f5137b73b84177434800bacebfc685fc37bbe9efe4070d
 
PrKey WIF u.: 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreMQiR4w7
Address u.  : 2d17543d32448acc7a1c43c5f72cd5be459ab302
Address u.  : 157RMZhbBLC1wucv3jxQqqHjbKezL1yy7g

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.

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: holy_ship on December 09, 2017, 06:43:48 AM

rico666 thanks for not sending me to GTFO Grin

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

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.

holy_ship

jr. member

Activity: 109

Merit: 1

rico666 thanks for not sending me to GTFO Grin

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

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: holy_ship on December 07, 2017, 12:32:59 AM

Quote from: rico666 on December 06, 2017, 09:10:54 AM

See https://lbc.cryptoguru.org/man/user#hooks
Not sure what you mean by the "too large sieve".

Thanks for the answer, rico666! English is not my native language.
It seems to me that LBC now has rather weak control of clients (correctness of their checks and return of results).
So the effect is: in list of Trophies we see far less records than it should be.

Also the main sense and benefit of pool is sharing award between all members (proportionally to contribution).
But now the single member takes everything (and can even not report the find!).

Actually, I do not see any advantages of being member of LBC versus solo mode.
Yeah, I've read the FAQ, but I totally disagree with the answer.
The range of LBC is known (and I think it is not best).
Solo "miner" can easily use another range without being a member of LBC.

The point of this message is not "hey, everyone, run from LBC", but to make LBC better and possibly more popular.

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.

holy_ship

jr. member

Activity: 109

Merit: 1

Quote from: rico666 on December 06, 2017, 09:10:54 AM

See https://lbc.cryptoguru.org/man/user#hooks
Not sure what you mean by the "too large sieve".

Thanks for the answer, rico666! English is not my native language.
It seems to me that LBC now has rather weak control of clients (correctness of their checks and return of results).
So the effect is: in list of Trophies we see far less records than it should be.

Also the main sense and benefit of pool is sharing award between all members (proportionally to contribution).
But now the single member takes everything (and can even not report the find!).

Actually, I do not see any advantages of being member of LBC versus solo mode.
Yeah, I've read the FAQ, but I totally disagree with the answer.
The range of LBC is known (and I think it is not best).
Solo "miner" can easily use another range without being a member of LBC.

The point of this message is not "hey, everyone, run from LBC", but to make LBC better and possibly more popular.

holy_ship

jr. member

Activity: 109

Merit: 1

By the way, don't you think that starting from very beginning is a bad idea?

I guess most of us are hoping to discover abandoned wallets from early 2010-s.
At that times harsh cryptofreaks didn't have fancy bitcoin-core software and generated private keys themselves.
So, they at least have seen the result of RNG.
And the secret key with 40 leading zeros looks very stupid.
Yeah, I understand that any value from RNG has the same probability to occur, but still...

Why not to move to middle of 256-bit range (or 2^160 - I'm not sure what exactly we are bruteforcing)?

arulbero

legendary

Activity: 1914

Merit: 2071

A number of people have raised this matter: how to read properly the FOUND.txt file?

I decided to share a little python script.

First we generate a FOUND.txt file to make a test:

Code:

$ ./LBC -x
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your speed is roughly ............ keys/s per CPU core.
o
Test ok. Your test results were stored in FOUND.txt.
Have a look and then you may want to remove the file.

$ ls
FOUND.txt
....

$ more FOUND.txt 
2d17543d32448acc7a1c43c5f72cd5be459ab302:u:priv:0000000000000000000000000000000000000000000000000000000000000001+0x5e
02e62151191a931d51cdc513a86d4bf5694f4e51:c:priv:0000000000000000000000000000000000000000000000000000000000000001+0x65
9d74ffdb31068ca2a1feb8e34830635c0647d714:u:priv:00000000000000000000000000000000000000000000000000000000000f9001+0xf8c
3d6871076780446bd46fc564b0c443e1fd415beb:c:priv:00000000000000000000000000000000000000000000000000000000000f9001+0xf8c

Then you can use this python script, called "lbc_output.py": https://www.dropbox.com/s/q1sgc4gbb26vc99/lbc_output.py?dl=0

Copy the line of FOUND.TXT you are interested of and you get the result:

Code:

$ ./lbc_output.py 2d17543d32448acc7a1c43c5f72cd5be459ab302:u:priv:0000000000000000000000000000000000000000000000000000000000000001+0x5e

Private key : 000000000000000000000000000000000000000000000000000000000000005f
Public  key :
          x : 15d9441254945064cf1a1c33bbd3b49f8966c5092171e699ef258dfab81c045c
          y : d56eb30b69463e7234f5137b73b84177434800bacebfc685fc37bbe9efe4070d
 
PrKey WIF u.: 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreMQiR4w7
Address u.  : 2d17543d32448acc7a1c43c5f72cd5be459ab302
Address u.  : 157RMZhbBLC1wucv3jxQqqHjbKezL1yy7g

What does the script?

First it reads and parses the line.
Then it computes the private key (it does the addition, in our example: 0000000000000000000000000000000000000000000000000000000000000001 + 0x5e) and using the ecc arithmetic it generates the public key. Then it generates the address (compressed or uncompressed) and checks if it matches with the address in FOUND.txt (in this case 2d17543d32448acc7a1c43c5f72cd5be459ab302).

Finally it provides the private key in WIF format and the address b58 encoded.

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