Client version 66.4 has been released on the pool. Main change is fixed network retry code. It was broken when I moved from c# .net to c++ in version 66.3. That was my fault. I never fully tested that feature but it is tested now. There are also a couple of minor cosmetic changes. Let me know if you have issues.

Hey everyone. We have been making great progress in the last month or so. With our DB being the most complete of any out there, the attempts to get 'fresh' ranges by nefarious entities is also increasing. Starting at 20% and on I am going to require clients to also have their bitcoin payout address be part of the line one in settings.ini so please be sure to update as soon as possible. I know it is short notice but I like to set deadlines at milestones and what better one then the big 20.

settings.ini Line 1:
Your username worker name and payout address
There should be a . between username and workername and a , between workername and payout address
workername is optional. In the case of no workername there should be a , between username and payout address
eg: Username.WorkerName,PayoutAddress
eg: Username,Payoutaddress

This does not require a client upgrade but I will be releasing a newer version to truncate the payout address when displayed in the cli to make it more visually appealing and to mask peoples addresses when screen shots are shared. So please refrain from sharing screen shots for the time being with the entire payout address being displayed with the current client software. As always feel free to reach out if you have any questions.

Just a reminder that sometime in the next 24 hours we will be crossing the 20% complete milestone and settings.ini files will need to be edited to now include the payout address from your accounts to better secure the server from abuse. See previous announcement for more details.

update complete be sure to update in order for it to continue working

OK so after a short stint with a little DDoS attack last night I now have implemented an auto ban script that will ban any IP that the script determines is being malicious. So if you are suddenly blocked from accessing the site at any given time and are not being malicious you should contact me so I can look into it for you. I am sure some of the initial variables will need to be tweaked. Happy key searching!

Congrats everyone for achieving 25% completion of the entire 66 bit key space!

I have just released version 66.6 of the clients for all platforms and hardware. Lots of new things in this release.
1. You can now make changes to the settings.ini file and they will take effect on the next range. You no longer need to close and run again to load new settings.
2. I have added 8 new sequential modes in addition to the existing mode: (see settings.ini for use)
Forward - default 'F'
Reverse - 'R'
Up - 'U'
Down - 'D'
Up and Forward - 'UF'
Up and Reverse - 'UR'
Down and Forward - 'DF'
Down and Reverse - 'DR'
Random direction - 'Random' (Like a snake slithering through the unchecked ranges)
The client will now indicate jump amount indicating when completed ranges are encountered for all sequential movement.
3. Auto -r calculation to squeeze more performance out of Nvidia GPUs (any -r values on line 2 of settings.ini will prevent the client from running) Thanks to Wandering Philosopher for finding this tweak.
4. the Vast script has been updated for the new features

As always feel free to ask any questions you might have.

Nvidia client and vanity software updated to 66.7 and 1.19.
Changes include:
Rekey improvements (previous rekey tweak was found to not be ideal so some changes in both client and vanity needed to be made)
Removal of CPU threads altogether (blocked in client with exit message)
Removal of multi GPU support (blocked in client with exit message)
Added more checkes to ensure line 2 is just a single gpuID.

These were removed due to poor performance and to simplify configuration.
Line 2 in settings.ini is now just a single GPU id as indicated in the instructions in the file.

I just reset the collision count since the values where not accurate because finding multiple collisions in a row was not realistic with the new modes of range selection. So I have reset it to zero and now the only modes that affect the collision stats are random and 1 range at a time. They should happen at a more realistic frequency now.

I realized today that with the newer sequential search modes that it was possible for the system to assign ranges outside of the bit 66 eligible range. And this happened about 55,000 times. The ranges have been deleted from the db and an audit of all user submitted ranges was done. So you may notice slight range count changes in your account. The problem has been fixed and It is no longer possible to run outside of the correct range. in the near future I am also going to be resetting the requested values in your accounts so that I can better monitor future bad actors.

As mentioned in the announcement yesterday. Today I have reset the requested ranges to 1.02 * the value of your submitted ranges. I did this so that I can deal with offending accounts going forward that are requesting a large number of ranges without performing the work afterwards. My view user code highlights possible offenders and it was highlighting past instances that I had already dealt with. I also reset users that have never submitted a range but have requested them to 0 requested which means in 30 days any of these users that do not have activity on there account will get auto deleted.

Big update in the vast and clore download sections. You can now create unprompted startup commands for Vast and Clore complete with a copy to memory button. Should be a nice time saver for everyone.

I just added caching on the day (ten minutes) and week (1 hour) charts.
Huge server load improvement

67 is now live for a soft opening with windows support only for now. I still have a bug in linux that Andrew and I are working on.
-Client and vanity now in one executable
-AES encryption on the distributed ranges
-RSA encryption on the submitted keys
-Separate request and submit operations
-CRC32 checking on request and submit to improve data integrity durring network transfers
-Only 1 range can be worked at a time now
-Range size is now 2^41 keys. 2x pool 66 this keeps the total ranges the same
-Big improvements in speed thanks to Andrew. Ran many threads on gpu now that take a bit to start but will yield very nice speed improvements.
-Reworked settings.ini (username workername and btcpayout on separate lines)
-added distinct start point for sequential modes
-added a message feature in the client to push notes from the server.
-3 total PoW keys. 4 keys submitted every time no matter what. PoWs and filler/winning key
-PoW count removed
-HTTPS
-No longer saves input or output files
I probably forgot some things but I am around to answer questions and help. I hope to see everyone back on the new pool. Linux should be around the corner hopefully. Please DM any errors you encounter.

All version of the Linux client are on the site now. Clore and Vast enabled. Let the BK/s fly.

Version 67.13 just released on all platforms. Thanks to Andrew it now has multithreaded GPU thread init making start up considerably faster.

Just updated all client versions to 67.14. Removed unused GPU functions resulting in slight speed increase and drastic file size reduction. I added more GPU support now since the file size was reduced. The client now supports Compute Capability (CCAP) 60, 61, 75, 80, 86, 89, & 90. Which basically covers all Nvidia GPUs from 10xx all they way to current commercial and enterprise. GPU improvements are credited to Andrew. I also have the program exiting when GPU errors occur instead of looping.

Just updated all client versions to 67.15. Now pressing 'q' while it is running will finish the current range workload and then exit gracefully with out requesting another range. I will update the ./finish script eventually to use this new feature. Until I do it will continue to work as it has been.
I also fixed the seqstart feature. It did not work like it should have prior to this release.

Congrats everyone on 2% your continued support is welcomed. I know there are other options out there but know that I have created everything here with a great deal of passion and as always I am available for any concerns or thoughts anyone might have. Thanks!

After a a nasty DDoS attack this morning brought the server to a crawl I finally pulled the trigger on configuring a cloudflare proxy. All traffic goes through them now. If you are having connection problems it is most likely due to DNS propagation delays. Refresh DNS or wait a while longer. Contact with any questions or concerns.