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

Let me try my luck and drop an answer when it's ready. Will take a lot of brainstorming but I will see it to the end. I love question of such.

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?

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.

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

Here's another 64 bit pool for puzzle #64

http://bitcoinchallenge.site/64-bit-user-stats/

https://github.com/WanderingPhilosopher/64-Bit-Random-Pool-2

https://discord.gg/Kv2sSFUX

My benefit is that the solution will be found faster, because the situation with my hardware capabilities is different [mostly I do not have access anymore than I have] so participation in this pool means that it does not make the chances of a solution dependent in any way. Handing over this bonus from the pool of my current share of the prize is still a small amount, but from the point of view of new willing participants - my result does not encourage to start - what this small part that I decided to add to the bonus pool - I hope will change. As for the warranty - I am not the owner of the pool, but from the very beginning I am in constant contact with its owner and I also archive all correspondence. Pool has already existed for a while, so its disappearance is impossible without a trace, and the act you are talking about would be a crime that would not be a problem to detect. I will not mention any other issues, such as the age of the ttdsales.com domain (it was created in 2004, so it was not just for the purpose of the pool). Moreover, my results from the scanned ranges - I decided to transfer to the pool several months ago, therefore I fully trust the owner as to his intentions and I am sure of them, bearing in mind the above. To sum up in a nutshell - all these factors force me to say that ONLY THIS POOL is able to find a solution # 64 together.



The owner of the field and channel on Telegram will accept your request to join, probably when he is at the computer.

What do you benefit from this?
Where is the guarantee that the owner of the pool will not take everything for himself?

Can you pull me into the telegram group? I used to join the btc cracking group, but now I can't get in?

For the pool, any piece of hardware is welcome... It always reduces the rest of the ranges that the correct key fits.
I would like to remind everyone - that the creator of the pool adds $500 from himself for the person who finds the solution (if the prize according to the result from the TOP15 is lower than a one thousand dollars).
Today - to encourage all to join and actively participate in looking for the key - I am adding another $500 from myself on the same terms, so the bonus is now guaranted $1000 if you find solution with us.
As a reminder, I will remind the url to the pool: ===> http://ttdsales.com/64bit/ <===

gpu is not usefull anymore. i was thinking of ACIC miners the hash power in those devices are insane.but is there even any way to give them cracking cod?

dude you have 520mk speed? i only have 16mk xD but still trying

hey.so i know there is way to convert base58 address to hash160 but is there any way to convert any of these to hex64 public key format?
i want to serch for my privet key with kangoroo but it won't accept base 58 addres 

I know it's February already ... but before that, I just didn't have the opportunity to look here to see what's going on in the subject. For my part, I temporarily have no spare resources to be able to use them for further operation, but I hope that it will return to its previous state soon and I can continue. For my part, I would just like to remind you that the search for the key to # 64 continues on the pool to which I decided some time ago to transfer my results in the form of scans that I have already carried out. I watch the pool almost every day and I am pleasantly surprised by the fact that the daily increase in activity is noticeable, which makes me think that solution # 64 is getting closer.
I encourage you:

POOL SITE: http://ttdsales.com/64bit

Oh, and to the point, because I broke the topic with which I started ... So I wish you all the best in the new year :-)

Wrong range, but interesting solving of something)

Hey, I have been lurking around here silently for around a year now, just made an account and wanted to say Happy New Year to everyone!
I am pretty sure a lot of people still have the script running in the background, and someone will eventually find #64. On my puny laptop 2060 with 520mkeys/s it's unlikely I will find anything compared to the rigs many have, but we gotta keep trying, I mean, who wouldn't want to say "Yeah, I wrote/downloaded some code, let my rig sit for a few months and got half a BTC easy peasy"... this #64 alone can literally change the life of many of us.
Don't give up people, even if the chance of finding anything is slimmer than your card after buying a GPU in the middle of the shortage!

I don't know

may be this year some one can

Happy new year!

Everybody gave up?
Where are the Heros?
Where are the Geniuses?
Let's solve that puzzle guys! #64!

Understood nothing.
Whole Range 64bit: 8000000000000000-FFFFFFFFFFFFFFFF
You have shortened to: 8AC7230489E80000-C249FDD327780000
This is still a very large range.

I think we can go a little deeper.
Just my observation. I'm not an expert in coding, I tried to create an alternative brute-force algorithm, but I could not achieve the required speed, but, nevertheless, maybe it will give something, or maybe I wrote nonsense.


We have Pk formula = 2^((n-1)+(x^(n-1))) where (x^(n-1)) is rem.
We know "n" and we can get "x" from previous outputs.
For example:



First of all, I want to draw your attention, I think that it was the "x" that was randomly generated, and here we need to look for an ace.
Even if not, then iterating over the "x" value itself, raising it into a formula, and then performing AES operations saves a lot of resources, because changing "x" by 1 part changes Decimal to millions.

I hope if this helps to find something you will not forget about me.
17HHd3M5ennd12CEUZXQ75W7gC6UgTkoUz

the key of puzzle # 64 is found

between 10000000000000000000 --- 14000000000000000000
hex
0000000000000000000000000000000000000000000000008AC7230489E80000 --- 000000000000000000000000000000000000000000000000C249FDD327780000


If the information helps you and you can solve it, if you want to thank, send here 3QWcjuY72EyouLmkRY4FbuoM1V7mA6tyqv