A few days ago I checked this pool, but I didn't really understand the principle of operation and even the scoreboard itself. Back then I didn't have time to write more about it, and now that I have - the server of this field is not working, so apart from the unclear interface - the stability is poor. Nevertheless, I encourage you to join us at ttdsales.com/64bit
Not sure what was confusing about the interface. If you need help understanding, I am here to assist.
It is easy to understand.
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.
But it was setup this way so that users with 1 GPU could continually run their GPU and compete with people like you who bring online massive amount of work-related/server type GPUs, for periods of time. It was designed so even the slowest single GPU could complete a range in under a minute.
Another difference was the software. ttd's pool uses old bitcrack, single GPU only, unless you run multiple instances (pain in the neck) OR you can use the modified VS Bitcrack that your buddy wrote for you long ago and then you can use multiple GPUs. The other pool was using a far superior program, a different version of VS.
The other pool, had a bonus for the finder as well, built into the numbers.
When the pool was running and had users, the stability was not poor, it was up and running 24/7. Once users declined and I had 99% of searched ranges (took months to get to that point), I took it off-line but continue to work it, from time to time. Mining is too good right now ($$$) for most with GPU power to want to participate in any #64 pool, myself included.