64 took so long to solve because a few people were trying to solve it, when you compare it to 63 which Zielar solved in 3 days, it must have been frustrating.
and now a whole army of people are cracking it
by the way 63 Zielar solved it with 3 graphics cards
Statistically speaking, there must be another puzzle within 0.7% of the starting range—specifically, between 71 and 160. But which one?  It will be resolved within a month No ... 160 will be not solved even in few years... |
|
|
|
the key was found after 0.7206% of the range.
So someone solved puzzle 69 using a modified Cyclone in 20 days?  Hi all! Modified version with jumps and partial match: https://github.com/Dookoo2/CycloneTry your luck:) It seems shady... The "updated" version of Dookoo2 Cyclone is only available as compiled Windows binary file (.exe) without source code available. The source code available on dookoo's github is old and it isn't probably the same code that was used to compile the new windows .exe file. I suggest to be very careful here ... |
|
|
|
I had to sign up to this forum today just to to say WOW! I was working on this little puzzle constantly and was bummed when I saw it was solved, and even more bummed when I saw someone stole it. Terrible. Can someone explain how this even happened? I didn't know you could rbf to a completely different address. What am I missing? It was explained here many times ... I can't believe someone was able to solve it but wasn't smart enough to let someone else steal it. |
|
|
|
caffeinated squirrel on a sugar rush.
Very dangerous being |
|
|
|
Let's get back to the puzzles guys.
Did anyone else notice that Puzzle 16 is fully contained in Puzzle 42?
And that's not all: the end of Puzzle 15, the entire Puzzle 16, and the first bits of Puzzle 17, they are fully contained in Puzzle 42. That's one long sequence: 22 continuous bits. Just sitting there in the middle of #42.
I'm framing this on the wall for future research.
No , it's not. Where did you see it ? Off by one error, sorry  Continuous unknown bits sequences:
Puzzle 16 100100100110110
Puzzle 17 0111011001001111
Puzzle 18 10000100000001101
Puzzle 43 101011110100111011001001111100010110010001
It's coincidence...IMO |
|
|
|
Let's get back to the puzzles guys.
Did anyone else notice that Puzzle 16 is fully contained in Puzzle 42?
And that's not all: the end of Puzzle 15, the entire Puzzle 16, and the first bits of Puzzle 17, they are fully contained in Puzzle 42. That's one long sequence: 22 continuous bits. Just sitting there in the middle of #42.
I'm framing this on the wall for future research.
No , it's not. Where did you see it ? |
|
|
|
SCAM coin, i will stay away !!
its not mining its a timer set on the background giving you a feel of mining. nothing is happening on the background. PI project is nothing but a data collection team, stay AWAY !!
Exactly. I was "mining" it back then and still don't want to sell it cause they require my ID documents (?!!). I don't want even think what for they need it... There is no mining here and never was. It's a giant pyramid scheme and data collecting operation for gullible newbies unaware of anything. I don't know who pumped the price but i will stay away no matter what. wtf are you talking about? my node running right here sounds like you missed out WTF you talking about ? I don't care about nodes... I'm talking about "mining" which not mining and cryptocurrency that require your ID to even move your coins is a mockery. Plus it's like pyramid scheme cause if you want more reward you must get other suckers into it... It's against everything cryptocurrency stands for... But some stupid kids may fall into it. |
|
|
|
SCAM coin, i will stay away !!
its not mining its a timer set on the background giving you a feel of mining. nothing is happening on the background. PI project is nothing but a data collection team, stay AWAY !!
Exactly. I was "mining" it back then and still don't want to sell it cause they require my ID documents (?!!). I don't want even think what for they need it... There is no mining here and never was. It's a giant pyramid scheme and data collecting operation for gullible newbies unaware of anything. I don't know who pumped the price but i will stay away no matter what. |
|
|
|
I've been less active on this forum for a while now, thats because I developed some health issues and they don't seem to go away, not knowing that what's causing the constant break down is in my home.
Since 2022 I've been mining Ethereum with some GPUs and when ETH mining stopped I switch to mineable platform and convert whatever I mine back to BTC, the whole set up is over 1GH and a S19 Asic miner that I connect to viabtc, this mining rig was installed in my room and the Asic miner down in a store, basement like room.
I can't put the two together because of higher heat detection.
I started noticing that I became so weak, to wake up in the morning becomes harder for me, I can't lift a big bucket of water like I used to normally, followed by cramps, headaches, nauseous and dizziness here and there, I went to the hospital and the doc recommended that I go through blood tests and so on.
The first question the doc asked me was if I work in a coal factory, my mind went straight to my mining rigs, I had to exposed it all to him, and he prescribed some drugs to me and warned me to stay away from my rigs, after sevarl weeks battling with fatigues and dizzy like feeling I finally start getting better, I had to build another block nearby brick by brick just to make sure I have my room to myself only.
If you are planning on sleeping in the same room as your miners make sure it is very limited, make sure the heat is very minimal, maybe I wouldn't have faced this if I stopped at my first 400MH mining rig. While BTC is your goal always look out for your well-being too.
Are you sure it was the heat ? Could be also constant fan noise and exposition to electric field. |
|
|
|
|
I don't want to smash anyone dreams but you will not hit a btc block with nerdhash or axe.
Not with current network hashrate.
Honestly it's just throwing away money and the devices are useless for anything else.
You have bigger chance a lightning will hit your house and it will burn to the ground than hitting a block with one of these small hashrate devices (toys).
People like delusion but this is the harsh truth.
And for all those who say "but you can try mining and educate yourself how it works" i can only say you can do the same with any PC without spending money.
|
|
|
|
I'm making one final exception.
I highly recommend you to do other things in life.
No, I can't apologize for your screw up code that works on 159-bit numbers.
Please stop acting like a snobby 7 year old kid who thinks he's the center of the Earth.
And I don't even care if you redact your majestic bit counting code to account for the missing 0 bit. It won't help any of us (you, me, or anyone else).
I didn't censor anything. Because the leading 0 was covered. I think the creator said this. Did you listen? Now I understand why you two are hated here, you're extremists. They're using probabilities, they're not claiming that from a prefix they know where another will be. It still seems not very useful to me, But perhaps it's the best way to try their luck.
You're right. I like soup salty. They say no, it's better without salt. What about you, you eat it without salt. I like it salty. lol They say soup is not made like that. You eat the soup you make. I say I eat the soup I make. Finally some useful information. Salty soup is better. I think i become a chef here. |
|
|
|
I wonder what one Believer would do if they stumble upon a 68-bit (or longer) prefix, or whatever has a less than 1 in 2**68 chances of being observed relative to their probability "rules". Queue up the whole range as the next best option, to find the next 68+ key, or...? Maybe skip it? =)) PS: I forgot, this definitely can't happen. Sorry guys, my bad. Oh quit it already, you verbalist This thread hits new low everyday |
|
|
|
I can't understand what is the purpose of collecting addresses with the same prefix within the same private key range.
Is there some sort of secret formula that would help in getting the private key of the puzzle?
Someone enlighten me please.
I can't understand why someone would create a brand new account, and out of all the questions to ask, ask that one, especially since all of it has been discussed...very recently. Enlighten yourself via reading the last 10 pages or so of this topic. Read, or don't. Collect addresses, or don't. But I will enlighten you. If you can find 2 prefixes where they match at least 53 bits of your target address, you can solve the private key using the Pythagorean theorem. In this case, "C" would be your target address! The question is : Is finding TWO 53bit prefixes really easier than solving the puzzle without them ? |
|
|
|
|
It seems like some people here wants to solve it so badly they become mental and starting to see things and connections that aren't really there...
|
|
|
|
I am silently watching and learning from all you guys that have been in this space for quite some long time and doing the puzzle, but again and again people say you need to find more than one or that. What exactly does that mean? Is it if someone has multiple addresses with private key in 69bit range that starts with 19vkiEajf, does it help to achieve goal faster
No it doesn't but some people don't like the truth cause it's too brutal for them. |
|
|
|
I wonder why none of the prefix believers fails to answer this simple question:
Assuming the prefix theory works, it automatically implies a weakness in the cryptographic guarantees of Bitcoin, and more generally automatically implies that the elliptic curve cryptographic assumptions are broken, and also the cryptographic security of SHA256 and/or RIPEMD-160 are also broken.
Yielding BTC as a 0$ asset. Hence, why would you try to solve the puzzle?
If so, why the hell aren't you guys publish a paper and wait for the academic gratitude? It would worth infinitely more than some stupid satoshis... RIGHT ?!?
Maybe because you know deep inside that you're simply just chasing ghosts of the statistical fluctuations of something that is not distinguishable from randomness? Or are you afraid that you'll need to call all the academic peers who'd dismiss your paper in 5 seconds, as people who obviously "don't understand probabilities" and have zero clues about math?
 |
|
|
|
All puzzle solvers must keep hope alive for us remaining solvers with terrible hardware. LOL!
That's the problem here. People count on "hopes" or "luck"... It doesn't work like that. Pure computing power is key factor here. The more gear you have the better for you. And it's important to realize what is real and what is not - solving a 69bit number on a single (or even few) CPU or GPU is not real (in a reasonable time) in my opinion. |
|
|
|
Bram = Doing something that everyone can do with 2200+ GPU is not a very high-level result.
What "high-level result" you are talking about ? There are three widely known methods for solving this puzzles: 1) For those with public keys available there is Kangaroo or BSGS 2) For the rest is just brute forcing (can be sequential, random or using those methods in certain ranges based on statistics/probability etc.) In both of them the key is how much computing power you have. That's all... |
|
|
|
Excellent. You just need to find the other 1 billion of them.
what does this have to do with a billion more keys, if the question was, if hashes160 have the same prefix - can they be in the same key range or not. and by the way, Bram also collects data on address prefixes at the beginning and end of the search range at the beginning of his full brute force. Well, that wasn't the question. Maybe you should read it again, it's exactly opposite to what you understood. Collecting prefixes is just meant to prove the range was scanned, since it's impossible to cheat and produce prefixes to your liking. That is the whole point of using statistics - checking if everything is alright, not defying the rules of nature and its randomness fluctuations. Besides, he's not even collecting prefixes of the target hash, but leading zero bits, which definitely do not help with anything whatsoever (except as proof of work). I have an insane amount of 44 bits prefixes for 68, but decided to not share them this time to not fuel the prefix fire. On 67 people still managed to read something into the proofs I published… It would be a good thing when someone who really solved a puzzle (like You) officially stated here that collecting prefixes isn't useful in solving puzzle and people doing it just wasting their time. Of course everyone can do whatever he wants but for new people here it would be a good indicator on how to not waste time. |
|
|
|
|
Show Posts
