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.
My only suggestion was that the Pool is not available all the time (for whatever reasons) which makes participating [or creating a competitive] unattractive. That's right - I put a lot of strength into ttd and that's why I'm going to work for this pool, but not only because I put a lot of effort into looking for it, but also because regardless of the situation - the pool has a 100% uptime, so who wants to be clear conditions to join and continue your work or even start, where the same regardless of when it started - if you find the right key (and the chance is greater because the range where the key is missing is already eliminated) - me and the author have a $ 500 bonus . After all, it would be obvious that no one would start working seeing how many scans I have already scanned without a bonus :-)
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.
Do you know what the data below "Distribution for each 16th of the entire 64 - 63 bit range" means?
Is that how many keys where tried in each key range?
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%.
I am having to do a string search versus full address search because a few of those cards are the RTX 3070 cards. But at least I can still use them with VBC. But as you can see, I set the range from 8000000000000000 to FFFFFFFFFFFFFFFF and the program spreads out over entire range. I was hoping to hit close to address and find it before 2^50 but no such luck. I'll let it ride for at least another 6-8 hours and see what happens.
I do search by string too
I just try do experiment about look a pattern
problem all puzzle is not create by pattern all is absolute random
problem on rank 2*63-2*64 prefix is distribution all keyspace by variable difference
conclusion no pattern
16454495722324959939 16jY7qK5oW1wnfKRN6uj1ASVdds6aouxDX 3ee4133d41444731cd7beb48b26d3a501fc744ce 359043673673754458109913579780954779489629848782 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ4hn8W4n7yeaG9rram8 000000000000000000000000000000000000000000000000E45A1CAE075D22C3
15356914462326594163 16jY7qK6wNNFqnR4k1UGUmfv7TFvTrfUbd 3ee4133d42ac12d331b91511632880f5413f9a53 359043673675622622798033731761492103220271487571 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ3SCCx52gr4araCbtaR 000000000000000000000000000000000000000000000000D51EB856CD091A73
14084089149906511880 16jY7qK9UeLf4rFYrQsoqQnYbuNpSU9si6 3ee4133d45d08b8400891186f72ccbc24cfdd40b 359043673679799677369610125758950696635980436491 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ1xrrHCkz9TeKqnueyf 000000000000000000000000000000000000000000000000C374BC760D1C6808
10957366083765617198 16jY7qKJTia8qA2HRyCH8ttkDK48ynC1qW 3ee4133d50eed586e09a754d9cea64bd8a8e99cf 359043673694578455355112905559483281244005767631 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYxMEeazeLdb25mbUBw9 0000000000000000000000000000000000000000000000009810626608C3422E
15338467798463623790 16jY7qKXvAbWydkoECFnvC4B6tjBrEKWhN 3ee4133d6195ed5c8e3a8d5403e938cf0f43ca84 359043673716713700287800823551761138585853741700 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ3QxUe4KUp4Qyb5bTtR 000000000000000000000000000000000000000000000000D4DD2F322E31326E
12018053845398380115 16jY7qKYE8yqVeeo2BQ2GEuxzccLtrXruQ 3ee4133d61f818fbacb8d98050673320fb5d9f8b 359043673717223430130265268114148103754155401099 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYyaM7UjWXwrcJJnbQe2 000000000000000000000000000000000000000000000000A6C8B44C4A7CDE53
15919540175014676452 16jY7qKq9YFpbNv7hE9rAegbnzQxThjb9y 3ee4133d76e8ddd9249feed6118b39026ca024b6 359043673745058134190826254367550950173015286966 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ45uxygmUpuWfLF3Yys 000000000000000000000000000000000000000000000000DCED91719F4F47E4
14960309530126404974 16jY7qL3Lk1F6doZRESLuyL1K5jQ4eqx6A 3ee4133d85ffdce51ba9dc109c8ab8b18507a68a 359043673765115957620901275540833771579488315018 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ2yc1u6yhHBLx5U9MV5 000000000000000000000000000000000000000000000000CF9DB24129134D6E
15163223678565228562 16jY7qL53WH9mqfiGnDVNu4E5cmpaTt2uJ 3ee4133d881b5811bdba44b047547989c0ed3f6e 359043673767917103900228355891329549583627665262 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ3DD3WJbyCwwmeMLipV 000000000000000000000000000000000000000000000000D26E9798F2AC2012
17690427578206221414 16jY7qL5MmbBuUPN3pjLgLyCKNCAnMyuPL 3ee4133d887f1bc6b3762a22de2bdca6e91ae941 359043673768435110696216248540087649519577786689 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ68e2XDu8T3FmYF4H64 000000000000000000000000000000000000000000000000F58106278BC17466
14130206010662142352 16jY7qLBfZwny9vSBX1G45XkLFB1jAzqZ7 3ee4133d904d3c7a19809acc9ee368e5ac76fef7 359043673778809983070097333345067472077834354423 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ21xB6s78CZR1uPt36f 000000000000000000000000000000000000000000000000C41893806C9B4190
13355442818363142526 16jY7qLED7wcq3mw3gWq3PqwtnmoZcQYBk 3ee4133d93733783fef9051366cb7392af95097a 359043673782994873710099489007655791452168194426 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ181XK3xsR9gWHUgvez 000000000000000000000000000000000000000000000000B958107BAE93B17E
16943334460982138399 16jY7qLGAvZw8JXVeDe6dKz2mdQfgDLyME 3ee4133d95e0dadc9e7043138d4236e8d8aaf03f 359043673786222603113445584966135603418991620159 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ5GYyDTyLjCLEii1f7k 000000000000000000000000000000000000000000000000EB22D0EC3179961F
17625864068125699820 16jY7qLK8rBoKkAEfdQMMZDX2yogfjZinv 3ee4133d998bf7eff1f284ea13c3f0277b2753a3 359043673791098759584668108861628840569146397603 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ64JyPjsWtcpdWfBdvm 000000000000000000000000000000000000000000000000F49BA5FBEFF42EEC
15753519546411984270 16jY7qLKagtc9cypcLj3Ui3QhcQgndY29t 3ee4133d9a191d487e39da0068db61a2a21a7765 359043673791831630906369292845610890857495033701 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ3tnQ32KETDrkAXS8b4 000000000000000000000000000000000000000000000000DA9FBE8FCE0F258E
10985036183770518811 16jY7qLU3rWzA5WzpV4BuDW6yh7Xv8wbn4 3ee4133da4940a6c8157683f58ce3924288c90dc 359043673805762180865213802119997989261188829404 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYxP6F5Nmpm3UswAqn9p 0000000000000000000000000000000000000000000000009872B0353A74551B
11114163388052541195 16jY7qLXbTXPSciC46crGHs4DqH3EaSdHe 3ee4133da8f71f2df32e42748ecdb7d3e49aa303 359043673811593551211807398525934563932772147971 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYxXkMNkX743SmHrYB2P 0000000000000000000000000000000000000000000000009A3D70B750860F0B
12811263834395200302 16jY7qLYUz7iQLiAWpCvSFDmgYB5638mMR 3ee4133daa10955629e2f547c710dff740908428 359043673813054983139446058212669508452736861224 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYzVXVcJ9Fv937ruhXMy 000000000000000000000000000000000000000000000000B1CAC09494EF4B2E
Questin; what number of same characters of address would be needed to get 9/10 missing characters of priv. key so you can brute force it than?
The ratio of the characters of the address (or the initial prefix) to the value of the characters of the private key or the general distribution throughout the entire range of the pool is completely random, so whatever you write about - it probably doesn't lead to anything :-)
