Version 1.2 of the ttdclient has been released in both windows and linux versions. The big change for this version is an updated settings.ini file that allows your client to work a range of your choosing. If the range completes or is already complete the server will detect that it is done and hand out traditional uncompleted random selections from the uncompleted ranges. Also there are several server side checks on the user selected ranges. If the range you enter does not seem to be working it is because there is an error in the way you entered it. The range your client checks is still randomly selected with this new feature but now it will be within the range you specify. As always I am available for assistance if you need any.

Ranges must fall between 0x8000000 and 0xFFFFFFF

End range must be larger then start range as you should have expected.

You can specify either a start range only or an end range only as well if you like.

Version 1.3 of the ttdclient has been released in both windows and linux versions. The big change for this version is an updated settings.ini file that allows your client to compute between 1 and 16 ranges. Lets say you have a 2080ti that can do 1280mk/s according to bitcrack but because of startup time your only getting 1020 mk/s according to ttdclient. If you set ranges to 8 you essentially reduce the time wasted on startup by 87.5%. As always I am available for assistance if you need any.

Over 1 million ranges checked on the pool.

Today I removed some of the older entries from the collision list so that only the newer entries remain with more details stored about the collision. Just wanted to let everyone know incase you noticed that the numbers got smaller in regards to collisions.

I removed 50 accounts that were bogus/old/unused/never contributed.
There are 19 accounts I am leaving for now that are older and have requested ranges but have submitted 0 that I might remove in the future.

The future came early the 19 are now gone too.

I was doing some testing with the solution notification settings and it might have stopped some of your clients. Sorry for the inconvenience.

We finally made it to 1% of the 64 bit range scanned.

Added a couple of solution finding odds. It is based off real time data and the key rate average for the last day. If anyone knows anyone that would be interested in contributing get them on the pool.

Over 100 Quadrillion keys checked.

Over 2 Million ranges checked.

First quad collision happened this morning. odds 1 in 15 million aproximately. Would love to see some other contributers on the pool.

We are over 1% on each of the 16 range divisions.

Also passed 150 quadrillion keys checked.

Week straight and I am the only contributor. Even in the beginning I had support. The solution gets found sooner the more keys we search. Lets do this.

Today I purged 120 accounts that where over 30 days old and have not requested any ranges.

7/400th of the entire range scanned :)

Now over 2% completed

Over 200 Quadrillion keys checked