So for those who do not monitor the
News link in my signature, here the "more important" news.
Claiming Finds:Tomorrow it will be 6 months since our 1st find (
https://lbc.cryptoguru.org/trophies) went into custody.
2016-10-11 03:00:34 GMT
The pool found a private key to f6cc30532dba44efe592733887f4f74c589c9602 (1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg) as 0x22306e3f1a72. At the time of the find, there were 0.007899 BTC on that address.The funds were transferred to custody at 16cFBcM27DGriyvz5i8SLmd8n5ai8hCTEE. See the announcement and the modalities of the return of the funds to their rightful owner here.
As no one came along to reclaim these funds,
they will be moved to the
LBC Pot adding some $13 to the currently present ~$195.
*crowd cheers*
New generators: KardashevIn the next few days, I will roll out our next generation of generators (sounds nice - eh?) called "Kardashev". The predecessor "
HRD-core" served us well, but in order to break new ground, we needed to make extensive changes which made the resulting generator not just a newer version of HRD-core:
Unified binaryMainly, the new generators will already have support for GPU computing, it will be on the client to evaluate "GPU-Auth" and start the generator with the appropriate options.
This will reduce the number of binaries we have to maintain/juggle (no +gpu versions anymore). You can see the generators already appearing on our
update URL.
In order to have a seamless upgrade, please make sure you run at least LBC client version 1.140. Because the new generators are all linked against libOpenCL, you have to make sure you do install OpenCL on your machine - even if you use only the CPU version or have a VM. If you were already running a GPU client, you do not need to do anything. If you are on a VM or even intend to run only CPU clients, you still have to install OpenCL. Luckily, you can install some dummy OpenCL package like
https://apps.ubuntu.com/cat/applications/ocl-icd-libopencl1/ or the Mesa OpenCL or whatever (feel free to install the Nvidia, AMD ones if you intend to use that Hardware later on) - just make sure a libOpenCL.so is on your system.
HW support:Reducing the number of binaries we have to juggle while improving the release cycle (testing & automation), allows us to extend the support for various other nice devices out there. Take for example Intel
Goldmont a.k.a. Apollo Lake a.k.a. Pentium/Celeron WTF. These nifty little CPUs
do have hardware support for SHA256! And some even niftier ARM CPUs
do also! So yeah - we intend to support that. Your little settop box may actually perform a formidable search for BTC keys while you are watching a movie (of course without disturbing the movie).
Speed:As of now, Kardashev generators are only slightly faster than HRD-core. While there is nothing spectacular as of now, make no mistake: We just left a
local optimum, went through some performance valley and are releasing the new generators while climbing up the next performance mountain, just about the height of the last peak. Understood?
In terms of efficiency, already the current versions of HRD-core are the best key generation (and checking) software out there. With Kardashev, we intend to take the game to a whole new level. Doubling the speed seems realistic now. We
do already have faster prototypes running here...
About:Oh - and about the
name. Kardashev is of course some tribute to our anglo-saxonian friends. I wouldn't mind to call the binary
Kardašov, or
Kardaschow or
Кapдaшёв, but some people might have trouble with their keyboard.
As for why this name has been chosen: It was an idea sketched out by Ryan Castellucci some months (~10) ago, in reference to the nice but pathetic
picture of the sun. Other than that, it should be self-explanatory why the name has been chosen.