The "one week before bit boundary" was exactly this. You can never know when you are "just one week before the bit boundary".

Interestingly, if Unknownhostname overdoes it, he will not be eligible for LBC Pot distribution himself.

If it were so, at the moment there would be only a few people currently active that could get the LBC Pot (at least in the top 30, from what I can see).

And besides, If we could mantain a 1.5 Gkeys/s speed for 1 year, we would find #54, #55 and #56 by the end of 2018.

EDIT: now we are almost at 2 Gkeys/s, #54 by the end of this year! And we will hit the next bit boundary in less than 4 days! At this speed, in the next 50 days we will generate as many addresses as we have been generating from the beginning of this project so far.

BOUNTY PORTALS

BLOG

WHEREBOUNTY MANAGEMENT

MEETSAUTOMATION

SIGNATURE CAMPAIGNS

TWITTER

FACEBOOK

MEDIA CAMPAIGNS

AND MORE!

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.

and also, I will let run the "Gkeys forfeiture reaper" script before the distribution script.While the Gkeys gained by the forfeiture of others will be recorded in a separate place, they will count for share computation.

edit:

And of course you need to have a BTC address set for payout, else cry (holy crap):

UnimatrixONE would be eligible by activity, but has no BTC address set!__ac0v__ would be eligible by activity, but has no BTC address set!__rico666__ would be eligible by activity, but has no BTC address set!amthenia would be eligible by activity, but has no BTC address set!kknd2017 would be eligible by activity, but has no BTC address set!Total blocks of eligible users: 562942816Satoshi in LBC Pot: 12274528Distribution as follows:

There are a lot of dead/dormant accounts, who seem to just have tested LBC and then stopped colliding. And this is perfectly ok.On the other hand, I don't think it makes sense to keep these accounts around indefinitely as most of them have some single-digit Gkeys, but everyone started out small, so an automated cleanup mechanism should not immediately reap small accounts.

This is what will happen:

Starting with 53bit search space (which is due in about a month given current speed), accounts that have been inactive for (7 + Gkeys_delivered) days will be reaped and their Gkeys will be added proportionally to the other active accounts. Consider it a kind of Proof of Stake.

e.g.

Account has delivered 5 Gkeys and is inactive. This account can be inactive for 12 days before it is reaped.Account has delivered 1000 Gkeys and is inactive. This account can be inactive for 1007 days before it is reaped.

It's clear that accounts that did some serious colliding in the past with several thousand Gkeys do not have to fear to be reaped anytime soon.But I should point out that as speed of colliding rates changes over time, we may change this rule at some point in the future. (Imagine if the hardware/software in 5 years can give you 1Gkey/s then probably 1 Gkey will buy you 1 hour idle time. Or something like that)

For now, 7 days idle time is ok for everyone, above that: 1Gkey = 1 day.

The 53bit search space is nearing completion, and see below for the current forfeiture list.So in probably less than 24 hours accounts worth ~1300 Gkeys are going to be reaped and redistributed.If anyone sees an old account of his and wants it to be merged, ping me (Discord).

Our family was terrorized by Homeland Security. Read all about it here: http://www.jmwagner.com/ and http://www.burtw.com/ Any donations to help us recover from the $300,000 in legal fees and forced donations to the Federal Asset Forfeiture slush fund are greatly appreciated!

I found the cause of the spam. I was using Amazon EC2 Container Service. With the service you configure how many containers you want running at a time. I think I had it set for 8 "desired tasks". The service will deploy 8 containers, execute their entrypoint file, when a container/task stops running, it will start a new one in its place.

I just ran the container locally by supplying "bash" as an override entrypoint.

We did test yesterday the first AVX512-enabled generator, seems to bring a slight speedup compared with avx2 binaries (Haswell, Syklake)I'm looking into some other issues of the client and will make one more update to offer a skylake-avx512 generator "soon(tm)".

Rico gave me a link to show the hooks documentation. It opened up a "secret manual" that I had never seen before!

Here is the problem with the website I am seeing. Steps to reproduce:1. Click https://lbc.cryptoguru.org/man/user#hooks2. Verify that you see the hooks information3. Click trophies from the left bar4. Click Manual from the left bar

Expected behavior: The hooks documentation is visibleActual behavior: The hooks documentation is not visible on the page

I was wondering if this will run on ARM cpus, I tried to set it up on a Raspberry Pi and I have an error during benchmarking:

ARM is not supported, only 64bit x86 compatible (x86_64 a.k.a. AMD64)

Quote

Code:

./kardashev-sandybridge: /usr/local/cuda-8.0/targets/x86_64-linux/lib/libOpenCL.so.1: no version information available (required by ./kardashev-sandybridge)

Still it is able to compute keys at 0.79 Mkeys/s (it's a AMD Athlon X2 340 ultra cheap cpu) but I guess it's complaining because the cpu is AMD?

No, it's complaining because your OpenCL installation is slightly broken.Reinstalling OpenCL helps. clinfo should work, if you have a Nvidia GPU, nvidia-smi should work, then you are probably good to go.

The performance you see is because you run a CPU-only generator.

In this project, you have to earn your merits and perks. One of them being to be allowed to use a GPU. Which comes after you delivered 3000 Gkeys CPU-only.

./kardashev-sandybridge: /usr/local/cuda-8.0/targets/x86_64-linux/lib/libOpenCL.so.1: no version information available (required by ./kardashev-sandybridge)

Still it is able to compute keys at 0.79 Mkeys/s (it's a AMD Athlon X2 340 ultra cheap cpu) but I guess it's complaining because the cpu is AMD?

No, it's complaining because your OpenCL installation is slightly broken.Reinstalling OpenCL helps. clinfo should work, if you have a Nvidia GPU, nvidia-smi should work, then you are probably good to go.

The performance you see is because you run a CPU-only generator.

In this project, you have to earn your merits and perks. One of them being to be allowed to use a GPU. Which comes after you delivered 3000 Gkeys CPU-only.

Oh ok I didn't realize it was complaining about OpenCL since it was running on CPU only mode. I will fix it when I get to enable the GPU. For the 3000 Gkeys I am working on it

Oh ok I didn't realize it was complaining about OpenCL since it was running on CPU only mode. I will fix it when I get to enable the GPU. For the 3000 Gkeys I am working on it

It's a tribute to the unified generators (earlier we had different generators for CPU and GPU, now the binary supports both), it needs to dynamically link against a OpenCL library - but you can install a dummy one: