No I haven't. I have sworn to myself to pull this project off without any thinking at all.


Rico

My CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz

I was thinking, if sha256/ripemd160 is too fast compared to CPU pk generation, you could search for P2SH "addresses" too.

For example, with only 3 pubkeys, you could generate about 20 addresses (probably more):

6

+6

+3

Sorry, noob here. This doesn't look like a private key and when put into bitcoin address it says invalid. What am I missing?

In the trophies section, it is all well prepared. If you put the hash160 in the blockchain.info search, you end up on

https://blockchain.info/address/12CiUhYVTTH33w3SPUBqcpMoqnApAV4WCF
which is the same page as
https://blockchain.info/de/address/0d2f533966c6578e1111978ca698f8add7fffdf3

and if you convert the private key to a WIF, its 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEXxDuJBiUbiVA9e

I don't see an "invalid" anywhere.

More info: https://lbc.cryptoguru.org/man/user#found-

Rico

it works

I have feedback, that at least one user got his AMD GPU to run with LBC and the sse42+gpu generator.
Which makes him the 1st, because I was not lucky so far. May he come forth and bath in glory (and answer questions/give support  )

The new generators have a new parameter -L you may see in the process table. In case you're wondering what that is:


So if you e.g. see -L 25, this means, the generator will startup and run from a certain offset a search of 25 x 16M keys, which means only 1 startup cost for 400M keys instead of 25 startups.
There is a drawback to this - unfortunately. If you want to end LBC by pressing "e", it will take longer. Namely at the end of the next ask-for-work-block.


So max. time from "e" to end is twice the time given in -t

---

Also, you may see a -d 1 parameter in the process table with the GPU generators.


When does one use that? Again, as a LBC user, most of the time you do not need to take care of this, but in case you have a really big iron (say 32 physical CPUs and 4 GPUs), the LBC parameter is called "gdev" aka "GPU device".


Howto - you open 4 windows/terminals:

terminal1: ./LBC --gpu -c 8 -gdev 1
terminal2: ./LBC --gpu -c 8 -gdev 2
terminal3: ./LBC --gpu -c 8 -gdev 3
terminal4: ./LBC --gpu -c 8 -gdev 4

=> you should have 4 LBCs running, each taming 8 generators (8 CPUs + 1 GPU)
used if e.g. 8 CPUs are right to saturate 1 GPU


Rico

Of course my answer was sarcasto-ironic (which I often do to stimulate thinking in my discussion counterpart, but it almost never works).
So full verbatim, my answer translates to this:

There are currently P2PKH and P2SH addresses. We search only P2PKH, but we may extend our search to P2SH.

This "If you find collisions BTC will die/will be worth nothing" is FUD. Bitcoin is an evolving system. And yes, LBC may put evolutionary pressure on the P2PKH part right now.
If you look at https://github.com/bitcoin/bips/blob/master/README.mediawiki, you will see that there are other address formats already proposed.

E.g. the now deferred BIP142 defining a P2WPKH format.

Others may follow (I'd propose a true-512bit address format in a BIP myself, but am lacking the time atm. Also I prefer to interact with core devs as few as possible).

In other words: There are so many levels between LBC finding collisions and BTC dying, one can safely assume these two events are not connected. Also I do not believe in the 2nd one.


Rico

New client 1.029 - upon restart your LBC should auto-update.

Also, most generators (except generic and sse41) have been updated to accept the -L option.
These too, should auto update.

Everyone who is GPU auth, should now be plug and play via --gpu.

The names of the generators are now in a more canonical form.

gen-hrdcore-skylake-linux64  (CPU)
gen-hrdcore-skylake+gpu-linux64 (CPU+GPU)
gen-hrdcore-avx2-linux64  (CPU)
gen-hrdcore-avx2+gpu-linux64 (CPU+GPU)
...etc. - you get the idea

So basically if you had a gen-hrdcore-avx2-linux64 generator up to now, with --gpu LBC would fetch the gen-hrdcore-avx2+gpu-linux64 counterpart and use that.

Even if you are CPU only, an update makes sense, as the -L will lower the generator startup overhead and should give you some more keys/s

Rico