Pages:
Author

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

legendary
Activity: 1932
Merit: 2077
September 07, 2018, 07:06:53 AM

It is different public key.
Is this  first real collision?


If you look here you can see that who signed that transaction has used the public key 02b009e153bd0df7fd2856ffbcbb71020bd69fbea49b20f7cd0b40e0ae98ff2486.

You claim that you found a different public key, that means nobody has stolen your private key.
legendary
Activity: 1120
Merit: 1037
฿ → ∞
September 07, 2018, 07:06:21 AM
Guys, there are no collisions. ... Until you have any kind of proof please do not use the "collision" word, you just make yourself look bad.

I believe the use of the word collision with a question mark after it is allowed - if you're kind enough to allow it sir.

Of course there are collisions we just have no definitive proof (2 different privkeys resulting in 1 pubkey).

Mathematically there must be collisions because you are not able to map a 2^256 bit space onto a 2^160bit space collision-free.
That is impossible and in this light your skepticism makes you look bad.

Because there must be - in fact - for every single public key around 2^96 private keys resolving in that public key.

All this results in 2^256 - 2^160 "superfluous" private keys and we "just" need to find one colliding pair.

Summary: There are collisions and everyone claiming otherwise simply doesn't understand the math behind this.
The legit question may be if/how to find these efficiently or if that is possible at all, but doesn't change the fact about their existence.
legendary
Activity: 1932
Merit: 2077
September 07, 2018, 06:56:46 AM
Guys, there are no collisions. There never was, if there were Bitcoin would go to the ground. How long do you need to understand this fact?

There are about 2^96 different public keys for each address.

2^160 addresses times 2^96 public keys = 2^256 public keys.
legendary
Activity: 1974
Merit: 1077
^ Will code for Bitcoins
September 07, 2018, 06:03:16 AM
...
Or did you find just a collision (different public key <--> same address) ?
...

It is different public key.
Is this  first real collision?


Same address and different public key? Yes. Could you post only your public key?

...

Guys, there are no collisions. There never was, if there were Bitcoin would go to the ground. How long do you need to understand this fact? Never assume a collision, always assume you are doing something wrong without understanding what you are talking about. The point of this whole thing is to prove this fact, and it has been proven over and over again. Until you have any kind of proof please do not use the "collision" word, you just make yourself look bad.
legendary
Activity: 1932
Merit: 2077
September 07, 2018, 02:39:05 AM
From the blockchain I see that the address 1CuSHEw7nerhLSwc4guXXdEvwLim58QnZ3 has the public key

Code:
compress format: 02b009e153bd0df7fd2856ffbcbb71020bd69fbea49b20f7cd0b40e0ae98ff2486

uncompress format:
x = b009e153bd0df7fd2856ffbcbb71020bd69fbea49b20f7cd0b40e0ae98ff2486
y = 9a0f84d2862d23c4f576046ccba404586609646e8df5f59ec89e4c0bb9c58d7a

Did you find the private key relative to the public key "02b009e153bd0df7fd2856ffbcbb71020bd69fbea49b20f7cd0b40e0ae98ff2486"?

Or did you find just a collision (different public key <--> same address) ?

To check this fact, you can run my script https://www.dropbox.com/s/q1sgc4gbb26vc99/lbc_output.py?dl=0

(see here how to run it )

It is different public key.
Is this  first real collision?


Same address and different public key? Yes. Could you post only your public key?

Anyway my guess is that someone accessed to your "FOUND.txt" file (it is not encrypted). Probably your PC is not safe. LBC has nothing to do with this. it is not possible, see -> this post
newbie
Activity: 2
Merit: 0
September 07, 2018, 02:10:49 AM
From the blockchain I see that the address 1CuSHEw7nerhLSwc4guXXdEvwLim58QnZ3 has the public key

Code:
compress format: 02b009e153bd0df7fd2856ffbcbb71020bd69fbea49b20f7cd0b40e0ae98ff2486

uncompress format:
x = b009e153bd0df7fd2856ffbcbb71020bd69fbea49b20f7cd0b40e0ae98ff2486
y = 9a0f84d2862d23c4f576046ccba404586609646e8df5f59ec89e4c0bb9c58d7a

Did you find the private key relative to the public key "02b009e153bd0df7fd2856ffbcbb71020bd69fbea49b20f7cd0b40e0ae98ff2486"?

Or did you find just a collision (different public key <--> same address) ?

To check this fact, you can run my script https://www.dropbox.com/s/q1sgc4gbb26vc99/lbc_output.py?dl=0

(see here how to run it )

It is different public key.
Is this  first real collision?
legendary
Activity: 1120
Merit: 1037
฿ → ∞
September 07, 2018, 01:41:24 AM
Please expplain to me:

- I run LBC on approx 150 nvidia 1050 cards, at work
- I have custom way of selecting the range to scan using lbc parameters
- I am running for over a year now
- Today my equippement found key for 1CuSHEw7nerhLSwc4guXXdEvwLim58QnZ3. Big address!
- I checked but everything moved half hour after my LBC found it???

Is LBC a scam? How is this possible. So much coinsidence.
Half an hour later it is emptied!!


If you use LBC on 150 nvidia 1050 cards, you should have a keyrate of at least 3.75 GKeys/s
which is more than 10 times what the whole LBC pool has now (~ 300Mkeys/s):
https://lbc.cryptoguru.org/stats

Given the fact that the LBC sees nothing of your keyrate, your clients - however you may operate them - do not even communicate with the server.

So as far as I am concerned, whatever it is you do it is completely unrelated to LBC.

On a personal note, I find it slightly asocial to take the software and not to contribute to the pool, so feel free to think of LBC being a scam and stop using the software.
legendary
Activity: 1932
Merit: 2077
September 06, 2018, 11:38:32 AM
Please expplain to me:

- I run LBC on approx 150 nvidia 1050 cards, at work
- I have custom way of selecting the range to scan using lbc parameters
- I am running for over a year now
- Today my equippement found key for 1CuSHEw7nerhLSwc4guXXdEvwLim58QnZ3. Big address!
- I checked but everything moved half hour after my LBC found it???


From the blockchain I see that the address 1CuSHEw7nerhLSwc4guXXdEvwLim58QnZ3 has the public key

Code:
compress format: 02b009e153bd0df7fd2856ffbcbb71020bd69fbea49b20f7cd0b40e0ae98ff2486

uncompress format:
x = b009e153bd0df7fd2856ffbcbb71020bd69fbea49b20f7cd0b40e0ae98ff2486
y = 9a0f84d2862d23c4f576046ccba404586609646e8df5f59ec89e4c0bb9c58d7a

Did you find the private key relative to the public key "02b009e153bd0df7fd2856ffbcbb71020bd69fbea49b20f7cd0b40e0ae98ff2486"?

Or did you find just a collision (different public key <--> same address) ?

To check this fact, you can run my script https://www.dropbox.com/s/q1sgc4gbb26vc99/lbc_output.py?dl=0

(see here how to run it )
newbie
Activity: 2
Merit: 0
September 06, 2018, 06:42:50 AM
Please expplain to me:

- I run LBC on approx 150 nvidia 1050 cards, at work
- I have custom way of selecting the range to scan using lbc parameters
- I am running for over a year now
- Today my equippement found key for 1CuSHEw7nerhLSwc4guXXdEvwLim58QnZ3. Big address!
- I checked but everything moved half hour after my LBC found it???

Is LBC a scam? How is this possible. So much coinsidence.
Half an hour later it is emptied!!
jr. member
Activity: 78
Merit: 1
September 01, 2018, 05:04:39 AM
I think I got it open with the command ./LCB -h  but not accepting any more commands

Code:
anunnaki1202@Anunnaki:~$ ./LBC -h

         LBC - Large Bitcoin Collider v. 1.195
    client fingerprint: b313bf5169f0453c8fee26a7af399b1a

 Usage:
    LBC [options]

 Options:
    --address
      Give a BTC address for rewards to this client. You set this
      and the server stores that info until you set another.

    --blocks
      Allows to process individual blocks stored in file .
      One block (number) per line. Only one CPU is used in this case.

    --cpus
      Set the number of CPUs to delegate address generation to. By
      default only one CPU is used. If you set 0 here, the number of
      CPUs to use is set to half of all found, which should get only
      physical cores.

    --delay
      Sleep between loops seconds. Great for "pulsed" mode
      on e.g. Amazon instances that have CPU credits.

    --email
      Give a email address for notifications. You set this and the
      server stores that info until you set another. NYI

    --file
      Use .json instead of the default lbc.json

    --gpu
      Enable GPU acceleration if available and authorized.

    --gopt
      You can give complex options to alter/adjust GPU behavior.
      Please see the manual for a detailed documentation.

    --help/-?
      This help. Options may be abbreviated as long as they are unique.

    --id <8-32 chars string>
      Register your desired id with the server

    --info
      Will print out diagnostic information and also create a file
      "LBCdiag.txt" with the same info. You will need this only if the
      developer asks for it to hunt down some bug.

    --loop
      Will keep asking server for work times. For one run, give
      0 or 1. Default: infinite

    --no_update
      Prevent the client from auto-updating (itself, generator, blf)

    --override |?
      Override the LBC generator choice. You get a list of valid
      generators when giving '?' as argument.

    --pages -|'auto'
      Give the interval to work on. 'auto' will let the server assign
      an interval. That's the default - you do not need to enter that.

    --secret <[oldpassword:]password>
      Set or change password to protect your client-id. (and the attached
      BTC address). When setting for the first time, use an arbitrary
      string for oldpassword!

    --time
      Time constraint in case client is in pages 'auto' mode. This
      puts an upper limit on the client runtime. Format is h:m You are
      free to enter '60' for an hour instead of '1:0' If you specify a
      pages interval, this option has no effect.

    --update
      Perform only the update run. LBC will check for updates of
      itself, the generator and balance data.

    --version
      Prints the version of the LBC client and exits.

    --x
      Performs a thorough systemtest: if generator works, connection
      to server, enough memory, present helper binaries, benchmark...
      If this runs ok, your system will work.

then any of commands i give to register my username with this ./LBC -id annunaki1202 then reply with
Code:
anunnaki1202@Anunnaki:~$ ./LBC -id anunnaki1202
Will use 2 CPUs.
Ask for work... Server doesn't like us. Answer: wrong secret.

or any other command will give different error
please help if anyone knows what is going on

actually I got a test going on fine look below on ./LBC -x command

Code:
anunnaki1202@Anunnaki:~$ ./LBC -x
Will use 2 CPUs.
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your speed is roughly 402766 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.
2d17543d32448acc7a1c43c5f72cd5be459ab302:u:priv:0000000000000000000000000000000000000000000000000000000000000001 + 0x5e
02e62151191a931d51cdc513a86d4bf5694f4e51:c:priv:0000000000000000000000000000000000000000000000000000000000000001 + 0x65
9d74ffdb31068ca2a1feb8e34830635c0647d714:u:priv:00000000000000000000000000000000000000000000000000000000000f9001 + 0xf8c
3d6871076780446bd46fc564b0c443e1fd415beb:c:priv:00000000000000000000000000000000000000000000000000000000000f9001 + 0xf8c

now when i give the command perl LBC -x I get reply as another error see below please

Code:
anunnaki1202@Anunnaki:~$ perl LBC -x
This script must run under the name 'LBC'.

any suggestions what options I got left to try ?


jr. member
Activity: 78
Merit: 1
August 30, 2018, 01:08:58 PM
Am trying to run the LBC and got stuck on see below please

$ wget http://ftp://ftp.cryptoguru.org/LBC/client/LBC
--2018-08-30 17:30:44--  http://ftp://ftp.cryptoguru.org/LBC/client/LBC
           => ‘LBC.1’
Resolving ftp.cryptoguru.org (ftp.cryptoguru.org)... 92.43.104.60
Connecting to ftp.cryptoguru.org (ftp.cryptoguru.org)|92.43.104.60|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /LBC/client ... done.
==> SIZE LBC ... 63819
==> PASV ... couldn't connect to 192.168.1.200 port 59530: No route to host

And I want to set it to search alone as random
And I want settings for pool as well please
And the keys conversion to WIF how we do ?
legendary
Activity: 1568
Merit: 1008
May 06, 2018, 04:09:17 AM
Rico, can i ask you to enable a GPU script for my worker? i want to kompare 1080 w5100 and grid k2  Cheesy
jr. member
Activity: 252
Merit: 4
April 07, 2018, 05:13:08 AM
By the way, don't you think that starting from the beginning is not a good 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)?
jr. member
Activity: 149
Merit: 7
April 06, 2018, 01:42:56 PM
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  Tongue
I think it's because I'm using an old colision curve algo, I'll keep it updated. Long Life this New "pool" way  Grin
jr. member
Activity: 126
Merit: 2
March 04, 2018, 12:59:00 AM
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 Grin
newbie
Activity: 12
Merit: 3
February 09, 2018, 01:53:55 PM
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
legendary
Activity: 1932
Merit: 2077
February 09, 2018, 11:40:04 AM
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.
newbie
Activity: 9
Merit: 0
newbie
Activity: 6
Merit: 0
January 28, 2018, 10:29:39 AM
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@ Huh Smiley Smiley please can you post more details photos on process? ps I am running phyton app under mac
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
January 17, 2018, 03:04:57 PM
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?
Pages:
Jump to: