mine is a founder edition and can hit 1,400,000,000 Mk/s with -b 4532 -t 32 -p 584."

Pool restored after failure due to weather anomalies in owner's areas.  The owner is on vacation so he only took care of the restoration after I gave him the information.  So go ahead: http://ttdsales.com/64bit

This is a general picture of the situation showing how many percent of what part of the entire range has already been scanned. The entire range of 64 is divided into 16 sub-ranges. The percentage indicator shows, for example, that the 16th part of the main range (i.e. F80000: FFFFFF) was scanned in almost 40%.

If you have the #64 space, ttd breaks it down into 2^32 ranges (I believe), so ranges are randomly selected and assigned to users; so it will take 2^32 searches to touch the entire 64 bit range. The other pool breaks the entire range down where users search 2^19 ranges (considered 1 round, spread out over the entire #64 range) and search 2^32 keys within each range. After the 2^19 ranges have been searched, the next start range is shifted by beginning range 8000000000000000 + 2^32. Next start range would be 8000000000000000 + 2^32 + 2^32, next start range, etc.. In this way, every space of #64 is touched, every round. It is merely a different concept versus ttd. I understand you have a lot invested with ttd's pool, so of course you will want people to join it where you have a large majority of ranges searched.