@Andzhing @Evillo I believe that the person who created this puzzle did not put much thought into it. They simply selected a random number in a very ordinary manner to create the puzzle, and we may be unnecessarily complicating it. My point is that we should also consider these aspects when attempting to solve it. below in lime green text.
I am the creator.
You are quite right, 161-256 are silly. I honestly just did not think of this. What is especially embarrassing, is this did not occur to me once, in two years. By way of excuse, I was not really thinking much about the puzzle at all.
I will make up for two years of stupidity. I will spend from 161-256 to the unsolved parts, as you suggest. In addition, I intend to add further funds. My aim is to boost the density by a factor of 10, from 0.001*length(key) to 0.01*length(key). Probably in the next few weeks. At any rate, when I next have an extended period of quiet and calm, to construct the new transaction carefully.
A few words about the puzzle. There is no pattern. It is just consecutive keys from a deterministic wallet (masked with leading 000...0001 to set difficulty). It is simply a crude measuring instrument, of the cracking strength of the community.
Finally, I wish to express appreciation of the efforts of all developers of new cracking tools and technology. The "large bitcoin collider" is especially innovative and interesting!
That's right, but we don't know what he specifically did and in what program. What entropy was used 128-256 bit. 128bit enropy 12 words, still get 256bit private key. Let's say we start iterating over the entire enropy of 128bit and, by derivation, generate 256 addresses and cut them off in front, as the creator of the puzzle did. We have to iterate over all 128bits (12 worlds, 2048^12).
https://github.com/Mizogg/python-mnemonic For each of 2048 to 2048^11 etc.But the generation itself (if he did not use the words brainwallets) 128bit number was caused by some data for seed() ("some garbage" > Mersenne twister 2^19937 bit > seed() > 128bit > address), what size of "some garbage" for the swirl was used. Maybe the size of the "some garbage" was less than 128bit, maybe more. If he manually cut 256 addresses for the deep puzzle, then how did he get addresses from them.