Large Bitcoin Collider Thread 2.0

[Marcel555]

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

[HappyS]

Rico, can i ask you to enable a GPU script for my worker? i want to kompare 1080 w5100 and grid k2  

[anunnaki1202]

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 ?

[anunnaki1202]

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 <BTC address>
      Give a BTC address for rewards to this client. You set this
      and the server stores that info until you set another.

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

    --cpus <num>
      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 <float>
      Sleep between loops <float> seconds. Great for "pulsed" mode
      on e.g. Amazon instances that have CPU credits.

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

    --file <name>
      Use <name>.json instead of the default lbc.json

    --gpu
      Enable GPU acceleration if available and authorized.

    --gopt <options>
      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 <num>
      Will keep asking server for work <num> times. For one run, give
      0 or 1. Default: infinite

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

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

    --pages <from>-<to>|'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 <duration>
      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 ?

[snosj]

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!!

[arulbero]

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 )

[rico666]

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.

[snosj]

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?

[arulbero]

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

[itod]

...
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.

[arulbero]

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.

[rico666]

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.

[arulbero]

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.

[rico666]

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.

If all this proves to be true - we would look at a hash160 collision - yes?

[arulbero]

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.

If all this proves to be true - we would look at a hash160 collision - yes?

Yes, we would have a (sha256 + ripemd160) collision. That's why I hope he will post his public key.

[rico666]

By the way: the private key for https://www.blockchain.com/btc/address/1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa

is 000000000000000000000000000000000000000000000000006abe1f9b67e114

[anunnaki1202]

Now that's a clever move rico666 who can decode that key only you

 snosj do not have any privkey for that address he says he has .. because he needs to decompress the key what LBC find and he doesn't run LBC 

[anunnaki1202]

False alarm that address snosj posted is zero balance useless even if he has the key maybe watch only address wait trillions of trillions years to happen a transaction again

[anunnaki1202]

I think I have an idea what snosj is trying to do he maybe have them cards or even maybe is mining for bitcoin at the moment and is not so profitable for and wanting to switch to LBC

[rico666]

Now that's a clever move rico666 who can decode that key only you

Excuse me?

Don't be so ignorant - read the manual:
https://lbc.cryptoguru.org/man/user#found-

I also believe there are ready-made scripts to show you the private key in any format you are used to.