Large Bitcoin Collider Thread 2.0

[pablito1989]

which company offer the best vps for lbc? (cost/effort)
What do you think about digitalocean high cpu droplets?

[1715426350]

1715426350

[1715426350]

1715426350

[1715426350]

1715426350

[holy_ship]

DigiOcean highCPU seems to be ordinary dedicated CPUs, price is $160 for 8core.

Probably google's "preemptible instance" for $40/month is the winner (8core). Speed differs from 3.1 to 3.4 megakeys.

[jhdscript]

Google cloud is the best but preemptive machines are killed when CPU rate is high :-(

[holy_ship]

That's a wrong statement. They are killed (with 30 seconds timeout) when there's demand from google itself.
So they live from several minutes to 24 hours.

[BurtW]

The other thread is depreciated?

So, being new here in general as well as this thread I may just be ignorant but I have to ask.

If the goal of this project is to find collisions and the best way to find one is if an "owner" comes forward claiming their wallet was stolen by LBC, then why is the LBC only searching addresses that have balances "up to 1 Satoshi"? Especially given that the average bitcoin holder has a balance of 2 bits (0.0002 btc)?

I get the whole "we are searching for collisions, not trying to crack wallets" but it seems to me that you get just as many abandoned wallets with small balances as you do with large balances and that the ideal search space should be in the average balance range of 2 bits. (For that matter I would crank the number up to the 20-150 bit range considering that a guy with $20 or more in it is a lot more likely to seek out why his btc have gone missing)

I have read the entire thread as well as have used the search box and Google, however I have yet to come to an answer for this seemingly obvious question.

Edit: According to the "trophies" page the balances are 0.1 to 79 bits (0.00001 to 0.0079 btc) not 1 Satoshi? Regardless the question remains the same.

You are confused.  The bits mentioned on the trophies page refer to the search space, not Bitcoin value.

Here is what you need to know:

1 Bitcoin = 1 BTC
1 Satoshi = 0.00000001 BTC
1 BTC = 100,000,000 Satoshi

On the statistics page here:  https://lbc.cryptoguru.org/stats

keys per day:   282.21 tn
total keys generated:   19498.14 tn
pages on directory.io   152329.19 bn
search space covered:   54.11 of 160 bits
search space in 1y:   56.77 bits

Means:

tn = trillion
bn = billion

search space covered of 54.11 bits means LBC has tried 2^54.11 private keys (about 19,441,647,535,076,223)

search space in 1y:   56.77 bits means at the current rate they will cover 2^56.77 private keys in the next year.

On the trophies page you mentioned that "bit" was used.  I only see one reference to the word "bit" and it is:

A manual revisit of the 38-42 bit search space revealed these private keys

Which simply means they were searching private keys with values from 2³⁸ through 2⁴²

Where are you getting your very confusing definition of "bit", trying to make it equal to 0.0001 BTC ?  I have never seen that in all my years.

There was a push to call one millionth of a BTC a "bit" in the distant past.  But that really is not what you are talking about here.

Are you trying to use the antiquated definition of 1 bit = $0.125 ?  That would be really strange.

[Jude Austin]

Just curious, can this https://github.com/basil00/pairgen contribute to LBC in a way?

Thanks,
Jude

[arulbero]

Just curious, can this https://github.com/basil00/pairgen contribute to LBC in a way?

That program uses the Pollard rho algorithm (a probabilistic algorithm) to find a collision between any 2 addresses.
LBC checks all the private keys from 1 to 2^134 to find a collision with an address with bitcoin.

The 2 ways are very different.

[18fdmtTHAS]

Guys, sorry for being noob, but what does this mean:

Code:

Ask for work... got blocks [18607002461-18607006172] (3892 Mkeys)

Does this mean my client will search in this range [18607002461-18607006172]? I believe this range is < 2^35; while LBC is already done with 2^54? I'm searching on the already searched space?

I run LBC with this command:

Code:

sudo ./LBC --address xxx --id xxx --secret xxx --cpus 8

Is there anything wrong? Thank you so much.

[holy_ship]

>Is there anything wrong

Megakeys means millions of keys. 18607006172-18607002461=3711

[18fdmtTHAS]

>Is there anything wrong

Megakeys means millions of keys. 18607006172-18607002461=3711

Thanks, but what is the relation between 3892 Mkeys and  3711 Mkeys? Did you mean the LBC client is searching in the range [18607002461x10^6-18607006172x10^6]?

Sorry for being ignorant

---
Edit:

Okay I got this: https://lbc.cryptoguru.org/man/user

pages/blocks
The parameter is called "pages", for historic reasons. A page (sometimes also called a "block") contains 2^20 (1048576) private keys. The history of LBC dates back to directory.io, where 128 private keys are listed on one page. As our "pages" do have 1048576 keys and therefore each represents "8192 directory.io pages", we started to call pages blocks. You remember: pages=blocks

3711 block, each contains 2^20 key (the output has oooooo.. but I don't understand why they are not fat block) -> 3892M keys

[bxmath]

It's easy, the difference is because you're assuming 1 Block = 1,000,000 but it's actually 1,048,576.

So 3711 blocks * 1,048,576 = 3,891,265,536

Basically 3892 MKeys.

Hope that helps.

[ZafotheNinja]

-Snip-

https://bitcointalk.org/index.php?topic=406312.0

Yes, I was referring to the value of the wallets in btc, not the difficulty of finding a working key for them. This is why I mentioned "balances" several times and specified 0.0001 btc whenever I used the somewhat uncommon term "bit" or "bits".

None of your rant actually answered my question?

[rud3boy]

Hey Rico,

could you pls enable --gpu auth for my ID 785872e03932a91cb17634861c6b6c31

THX in advance

[BurtW]

So, being new here in general as well as this thread I may just be ignorant but I have to ask.

If the goal of this project is to find collisions and the best way to find one is if an "owner" comes forward claiming their wallet was stolen by LBC, then why is the LBC only searching addresses that have balances "up to 1 Satoshi"? Especially given that the average bitcoin holder has a balance of 2 bits (0.0002 btc)?

I get the whole "we are searching for collisions, not trying to crack wallets" but it seems to me that you get just as many abandoned wallets with small balances as you do with large balances and that the ideal search space should be in the average balance range of 2 bits. (For that matter I would crank the number up to the 20-150 bit range considering that a guy with $20 or more in it is a lot more likely to seek out why his btc have gone missing)

I have read the entire thread as well as have used the search box and Google, however I have yet to come to an answer for this seemingly obvious question.

Edit: According to the "trophies" page the balances are 0.1 to 79 bits (0.00001 to 0.0079 btc) not 1 Satoshi? Regardless the question remains the same.

OK, so now that I know you are using the archaic term "bit" to mean $0.125 I can answer your question.

You are saying why not look at addresses that have a least a "bit" (at least $0.125) of money in them.

But LBC is searching for addresses that have "up to 1 Satoshi" (should be "at least 1 Satoshi") in them.  

Since by definition 1 Satoshi is 0.00000001 BTC, at today's price of about $10,000 USD/BTC 1 Satoshi is worth about $0.0001.

So there you have it.  

LBC is searching for addresses that contain at least $0.0001, you want to look for addresses with at least $0.125, therefore LBC is doing more than you are asking for.

Did I answer your question?

[Greko81]

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.

hi please specify after running the scrypt in phyton window where exactly to @Copy the line of FOUND.TXT you are interested of and you get the result@ please can you post more details photos on process? ps I am running phyton app under mac

[kranium5]

What the hell is that?

https://d.radikal.ru/d27/1801/b8/6fb4c957210f.png

[arulbero]

Curious though if the LBC lets you search for the private key of a specific address, namely, the one to which my coins were inadvertently sent. They are just sitting there.

If I know that the first 4 characters are the same as the address for which I have the privkey, does that do anything to narrow the scope or increase my chances?

No. Searching for a specific address is quite equivalent to search against all addresses with bitcoin.
If you know the first 4 characters, again you cannot take advantage from this fact.
You could use vanitygen and store all addresses that match with the first 4 characters. But your chances to find a private key for that specific address will remain always 1 over 2^160.

LBC software could be useful only if you would know a (consistent) part of a private key of a specific address. Informations only about the address are useless.

[therealbtcdave]

Is this code open source and how could I get access? In the first post you have a link to https://svn.cryptoguru.org/ which looks like an SVN server but it requires credentials as you mentioned.

Thanks

[ViperGuyMike]

Hey everyone, I have been following and studying the project for a couple weeks and finally finished my new Linux rig tonight and joined the pool. Although I am a long way from it, I had a question or two about the payout system. It seems as though I read somewhere that only members in the top30 would be included in the payouts, but I cant find anything about that now that I am searching for it? Is everyone included in the payout provided they haven't had a 2 hour window with 0 k/s in the previous week, and all their info is correct and updated? If anyone has a link or clarification, I would appreciate it. Working towards my 3000 keys now so I can point my mining rig at it for a while and see how much the CPU can handle with 6 cards behind it

[rosengold]

The Bitcoin Colider it's a great ideia. this is why i made my own: http://youtube.com/watch?v=VAo7qgrbAqw
I found some addresses with balance but the privkey ins't the real one 
I think it's because I'm using an old colision curve algo, I'll keep it updated. Long Life this New "pool" way