Topic: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED== - page 38. (Read 56094 times)

https://imgur.com/JZzbBpn

probably not going to be the code that finds it, but i notice people have posted python here so..

https://github.com/barrystyle/b58

is currently hardcoded for #64,
on my 11th gen i7-1165g7 manages around 124,000 keys/sec.
matches using the hash160 rather than the full base58 address for speed.

james

Yes, Around 1.4 Billion peak. it fluctuates but not wildly.

Ok, that's 1,4 billion k/s.
Makes sense.

My guess is that he meant 1400Mkeys/s

Can you clarify this number?
You wrote 1,4 billion but used Mk/s (million keys per second).

Is this 1,4 billion keys per second or what?

I am happy to inform you that I spent quite a lot of time to refresh this topic and catch up with today's technology in terms of eliminating the problems that I was able to read or meet anywhere, and therefore - I added an extensive update to the main topic. I hope that for many people - the time I have devoted will be helpful and will solve most problems / questions / doubts. All the best!

---

If you want - you can send me a donation to my BTC wallet address 31hgbukdkehcuxcedchkdbsrygegyefbvd

I wish I had saved my 115 files. I didn't think they would ever be useful then, and their size didn't encourage me to keep them anyway. Well ... it's hard. If I still have time - I will definitely join the cooperation, but I promised myself that I would finish topic # 64 for good first, and then focus on Kangaroo. In any case, if I get it again - we will surely get along somehow, because I will be happy to join the cooperation again, rather than wanting something again myself.

Welcomed!

Used GPUs...if you can find one that is still under manufacturer's warranty, that is best. Usually a card has a 3 year warranty. I have purchased many used over the years with no issues.

For the puzzle, I am spending time each day on #120 via Kangaroo. I still mine most of the day but switch over to #120 for a bit each day until I find around 2^20.5 DPs. Another forum user has quite a few DPs saved and I am starting to send him my tame and wild points and he checks to see if we have a collision.

Zielar, if you want to join in the hunt, I can set up your own port on my server and you can point and run your GPUs . We should be at around 2^28 DPs needed out of 2^30.55 DPs by the end of this month (running DP 30). The thrill of the hunt continues...slow and steady!

1) Not a bad idea. This has no effect on performance. When buying a used one, it is worth knowing what the card was used for during its use (i.e. whether it was used as a graphics card in the computer or used for crypto mining). the same new.
2) The participants can decide on their own to what extent the parties they want to be allocated. For example - the VanitySearch configuration file consists of five lines, as in the example on my one machine:

which in turn means for the program: 1. my login 2. commands for vanitysearch for selected processors 0,1,2 and excluding CPU usage, 3. Lowest selected range, 4. Maximum selected range, 5. Number of simultaneously downloaded ranges (i.e. I download 16 ranges at once to eliminate connecting to the pool every single range)
3) The specific scanned ranges are not published for obvious reasons which, apart from their huge number, include issues that eliminate the support of people not participating in the pool. Working for a pool is about bringing their members closer to the correct key, not letting outsiders know which ranges are already checked and empty. Thanks to this also - the pool has an advantage over people who will try their luck [in the form of already such a large resource of proven ranges], and as a colleague wrote earlier - the full range is huge. This 16% consists of more than 21 million sub-ranges that the Pool has already scanned, while the full sub-range pool is 134,217,728.

However, you can see the estimated distribution of the scanned sub-ranges in the table after logging in, divided into 16 parts - from which you can see, for example, that the final (F80000-FFFFFF) range is already scanned in 45%, while the initial (80000-87FFFF) only in 4%. This information, however, is so useless for outsiders, because the correct key is only one and it can still lie in the still unchecked part of the last range, while the very percentage discrepancy from the beginning to the end results from the fact that I insisted on the second half of the range and as I wished, the system assigned me sub-ranges from the second half to be scanned.

P.S. As a curiosity, I will only mention that today I switched to the initial ranges, because my whim regarding the sub-ranges has changed

---

Thanks a lot. This is what I was looking for. This will be very helpful, as these results were created while the VanitySearch performance was the same as the current VanitySearch performance with the scoping option. Nevertheless - the values will be more or less very similar, and I have a base for possible development. Soon there will be a table in the main topic - which I will gladly supplement with the missing types of cards, if someone has one ... Then I ask for info in the post or in PW (i.e. what GPU, how many Mkeys / s achieves and any additional starting variables such such as -g which increase performance)

[EDIT]
I've already added the performance sections to the main topic.

yes I have been lurking around that pool for a while and up to date for the most part, I just never owned a gpu and would like to throw one or two at the pool for fun. 3 questions:

1) Would it be a bad idea to purchase a used gpu? risky efficiency/speed wise?

2) Do participants get to choose which specific range they would like to allocate their gpu's to on ttdsales?

3) Are the already scanned ranges publicly published somewhere?

thank you for your answer

VanitySearch benchmarks

https://bitcointalksearch.org/topic/m.50823897

However, the speed using ttd version will be slower since it is searching for keys in one specific range versus original vanity search that searches using inversions and such.

What are these cosmic parameters for bitrack?
I once stated exactly that -b is a parameter that should be equal to the number of "compute units" read with cuBitCrack -l, a -t parameter of 512 (or 256 if the newer card architecture doesn't let that big), and a floating parameter -p that it is necessary by trial and error to determine the most issued. Apart from the fact that you tire your GPU with the parameters you specify (not to mention the MKeys / s speed) - let me also remind you that VanitySearch has better performance when it comes to MKeys / s.
As for the right question of my predecessor - any not too old card will be good. At the current stage of development of all the above-mentioned applications - it is definitely worth paying attention to NVIDIA cards, because they are reliable on these cards, which cannot be mentioned about the OpenCL support that only BitCrack provides, and in addition with a different effect.
A colleague in front of me is somewhat misleading, because there was no question about how many cards he must have to find the key, but what card he must have in order to start participation, and these are two different issues. The same in terms of profitability. As you can see on the ttdsales.com/64bit/ pool, which is actively working to find the key to # 64 - apart from me, there is also a group of people who with little power, but still support the search, because each already proven range falls out of the pool of possibilities, and what a hence -> the number of possible ranges is constantly decreasing, but if in the end the correct key is found by these smaller participants (because the chance for this is greater with every moment when subsequent empty ranges fall off) - apart from the prize resulting from the score table - the participant will receive such a Pool owner bonus of $ 500 + from me another $ 500, so even entering the participation with little power -> you can get rich with a bit of luck by a minimum of $ 1000, and I will just mention that 16% of the range has already been checked.

As part of the development of this topic - I will gladly update the main post with the GPU performance charts in terms of speed achieved along with the best settings for both programs listed beside.
I remember that some time ago someone created something like that, taking into account the price of the GPU and the price-performance ratio, but I don't remember if it was in any of the previous topics on this challenge, such as VanitySearch, BitCrack or elsewhere, but if anyone remembers - I would be grateful for pointing to the link in order to be able to start developing the base version of this list. Creating it from scratch somehow I don't really want to go out :-)

You need to understand that is not the right question.
here is my previous post on this subject: https://bitcointalksearch.org/topic/m.59904434
or in summary: "you need 2724 2080ti approximately to do puzzle 64 in one month with bitcrack. 1362 if you correctly guess which half of the range it is in.
or in other words 1,830,035 optimal 2080ti hours for $24,000. mine is a founder edition and can hit 1,400,000,000 Mk/s with -b 4532 -t 32 -p 584."

running One 2080ti 24/7 is not really advisable.
running 2724 is not worth $24,000.

a 3070 might be similar to my 2080ti and according to some data I have ~954 3090s would do it in a month.

so to wrap it up
1. you have to first guess a lucky number and hope it's close.
2. get as efficient (modern NVIDIA for cuda) a card as you can
3. stick with it for months
...just for the slim chance of getting it.

some 'attempts' have been made at pooling resources but stick with it for months still applies

what would be the cheapest gpu's (but still acceptable speed) that I could purchase for participating in this puzzle?
 please any recommendations

Those "ghost" addresses are the PoW addresses. This is how the pool knows you searched the range you said you searched. If you search only 1 range at a time, there will be 1 PoW address and the target address in the .txt file.

These are NVIDIA Tesla series GPU cards.
I can use the resources available in the company as long as they are free (not in use).
The prices of these cards are so high that it is definitely not profitable to buy at least one for this type of workload.
Personally, if I had to invest in a GPU for such loads - I would choose the RTX3090 because:
a) it achieves a MUCH higher hashrate
b) you will buy MUCH more RTX3090 than this ONE Tesla.

Can you tell me which GPU you're using? Gotta check the price to see if it's worth getting one.

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

That's right ... I'm just an active participant.
I noticed that a few hours ago the server on which the pool was placed stopped working. I have already informed the owner by e-mail and via Telegram. I don't think this is a conscious step. I am of good cheer.