nomachine
|
 |
May 01, 2025, 10:07:37 AM |
|
I wonder how many of them will come forward and say they've been robbed.  We're all robbed, don't you see?  Nah, nothing got stolen from me. All my fishing rods are still here. I’m good. 
|
BTC: bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
Bram24732
Member

Offline
Activity: 182
Merit: 18
|
 |
May 01, 2025, 10:13:24 AM |
|
Let’s talk more about this team of engineers, 12 of them but: No one to read the main thread on the topic. No one to read a bit of doc about how RBF works. Even if they are for real they kinda deserve the situation.
Wouldn’t want to work with those guys IRL 🤣
|
|
|
|
Akito S. M. Hosana
Jr. Member
Offline
Activity: 392
Merit: 8
|
 |
May 01, 2025, 10:15:37 AM |
|
I wonder how many of them will come forward and say they've been robbed.  We're all robbed, don't you see?  Nah, nothing got stolen from me. All my fishing rods are still here. I’m good.  You’re really out here making jokes about folks who got robbed? 
|
|
|
|
kTimesG
|
 |
May 01, 2025, 10:16:08 AM |
|
If you guys believe that 66 and 69 went through the mempool because the solver was an idiot that never revealed himself... oh well.
My bot was online. A well tested bot. A bot that actually worked this time, and fought for a higher fee.
The only problem? It retried pushing a new TX by increasing the fee with a fixed amount every 3 seconds, instead of refreshing from the most recent replacement. Since the fee went huge, by the time the increments reached it, the TX got mined. I literally noticed it in my terminal 2 minutes after the show ended. I could have fixed the problem in real-time. But do I feel sorry for this? No way - after all, one weekend of coding a bot last summer isn't really worth that much.
So congrats to the "stealer", though I believe there was nothing "stolen" from anyone.
|
Off the grid, training pigeons to broadcast signed messages.
|
|
|
Akito S. M. Hosana
Jr. Member
Offline
Activity: 392
Merit: 8
|
 |
May 01, 2025, 10:25:22 AM |
|
Wouldn’t want to work with those guys IRL 🤣
You are kidding just like nomachine. You actually enjoy the situation.  So congrats to the "stealer", though I believe there was nothing "stolen" from anyone.
And this dude even congratulates thieves? What a joke. This whole puzzle idea is a bust, just like this topic. 
|
|
|
|
Bram24732
Member

Offline
Activity: 182
Merit: 18
|
 |
May 01, 2025, 10:25:50 AM |
|
If you guys believe that 66 and 69 went through the mempool because the solver was an idiot that never revealed himself... oh well.
My bot was online. A well tested bot. A bot that actually worked this time, and fought for a higher fee.
The only problem? It retried pushing a new TX by increasing the fee with a fixed amount every 3 seconds, instead of refreshing from the most recent replacement. Since the fee went huge, by the time the increments reached it, the TX got mined. I literally noticed it in my terminal 2 minutes after the show ended. I could have fixed the problem in real-time. But do I feel sorry for this? No way - after all, one weekend of coding a bot last summer isn't really worth that much.
So congrats to the "stealer", though I believe there was nothing "stolen" from anyone.
What do you think happened ? I fail to see how things might have unfolded differently, even with my tinfoil hat on.
|
|
|
|
yxlm2003
Newbie
Offline
Activity: 8
Merit: 0
|
 |
May 01, 2025, 10:33:10 AM |
|
I should write a script to share it, monitor Private Key.txt, and automatically submit it to slipstream.mara.com, so that novices will not be stolen.
|
|
|
|
Akito S. M. Hosana
Jr. Member
Offline
Activity: 392
Merit: 8
|
 |
May 01, 2025, 10:35:21 AM |
|
I should write a script to share it, monitor Private Key.txt, and automatically submit it to slipstream.mara.com, so that novices will not be stolen.
Thank you very much in advance. Please help us 
|
|
|
|
Denevron
Newbie
Offline
Activity: 117
Merit: 0
|
 |
May 01, 2025, 10:38:05 AM |
|
I should write a script to share it, monitor Private Key.txt, and automatically submit it to slipstream.mara.com, so that novices will not be stolen.
To prevent this from happening again, people just need to read part of this forum thread before making transfers, and then none of them will lose their winnings.
|
|
|
|
nomachine
|
 |
May 01, 2025, 10:39:07 AM |
|
You actually enjoy the situation.  I’m not loving this situation, but I can’t stop laughing either. It’s just too much. Hahahaha! 
|
BTC: bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
kTimesG
|
 |
May 01, 2025, 10:48:00 AM |
|
What do you think happened ? I fail to see how things might have unfolded differently, even with my tinfoil hat on.
bc1qlp0z45ctphhz0kywpmw3x2kjy7umhyfawxctah has suspicious blockchain history. IDK what exactly happened here, there may be many scenarios, including automations hidden in software. But I doubt anyone who actually solves such a difficult puzzle on his own has zero clues on how to safely transfer funds.
|
Off the grid, training pigeons to broadcast signed messages.
|
|
|
Akito S. M. Hosana
Jr. Member
Offline
Activity: 392
Merit: 8
|
 |
May 01, 2025, 10:55:54 AM |
|
What do you think happened ? I fail to see how things might have unfolded differently, even with my tinfoil hat on.
bc1qlp0z45ctphhz0kywpmw3x2kjy7umhyfawxctah has suspicious blockchain history. IDK what exactly happened here, there may be many scenarios, including automations hidden in software. But I doubt anyone who actually solves such a difficult puzzle on his own has zero clues on how to safely transfer funds. Maybe someone hacked the puzzle creator. How could someone guess the private key so easily on such a high-level puzzle? Even after that, they don’t even know how to safely transfer the prize. Or did the puzzle creator hack themselves—like, maybe they messed up or something? And this ain’t a joke; it’s a serious problem here. 
|
|
|
|
Benjade
Jr. Member
Offline
Activity: 40
Merit: 1
|
 |
May 01, 2025, 11:04:26 AM |
|
What do you think happened ? I fail to see how things might have unfolded differently, even with my tinfoil hat on.
bc1qlp0z45ctphhz0kywpmw3x2kjy7umhyfawxctah has suspicious blockchain history. IDK what exactly happened here, there may be many scenarios, including automations hidden in software. But I doubt anyone who actually solves such a difficult puzzle on his own has zero clues on how to safely transfer funds. Of course it’s possible to have no clue even if you find a key. It’s like a newcomer to crypto who sets up a wallet, puts in a few dollars, lands on a shady site, clicks a link, and winds up with an empty balance. Same story here: someone fresh to the game learns how brute-forcing works, lets a script run, and mostly by luck hits a winning combo, then figures all that’s left is to sweep the funds. Honestly, I didn’t even know frontrunning or RBF attacks existed until I dug into this forum a few months back. A little honesty would go a long way online, but truly honest people are hard to come by on the internet.
|
|
|
|
nomachine
|
 |
May 01, 2025, 11:08:17 AM |
|
What do you think happened ? I fail to see how things might have unfolded differently, even with my tinfoil hat on.
bc1qlp0z45ctphhz0kywpmw3x2kjy7umhyfawxctah has suspicious blockchain history. IDK what exactly happened here, there may be many scenarios, including automations hidden in software. But I doubt anyone who actually solves such a difficult puzzle on his own has zero clues on how to safely transfer funds. Maybe someone hacked the puzzle creator. How could someone guess the private key so easily on such a high-level puzzle? Even after that, they don’t even know how to safely transfer the prize. Or did the puzzle creator hack themselves—like, maybe they messed up or something? And this ain’t a joke; it’s a serious problem here.  The probability that someone hacked the puzzle creator’s PC within 20 days is way higher than actually solving Puzzle 69—no cap. And forget about Puzzle 71; that’s just insane. Plus, if the creator really wanted his money back, he could get it back easily—no way he’d be playing games like this.
|
BTC: bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
kTimesG
|
 |
May 01, 2025, 11:14:11 AM |
|
My working theory: Key = 0x101d83275fb2bc7e0c Using the Scooby Doo: Origins method, the key was found after 0.7206% of the range. That's like, an investment of maybe $ 2000 or less  The Scooby Doo: Origins method proved its worth. I now wonder what the magic method would have accomplished. Maybe it founds the key faster. Maybe it skips it and you end up scanning some rest of 99% of the keyspace before going through the skipped ranges. Who knows? After all, it praises itself as "we save scanning vast amounts of the key space". Well, Scooby Doo: Origins saved 99.28% of this vast space. Now, how can the Scooby Doo method be put in practice? Oh no, so many cloud services to allow any n00b for scanning Puzzle 69, without having any idea what the software actually does. Sounds like a very good chance to get rich, right? Pay for renting some GPU, give 0 shits on whether it actually gets you anything in return.
|
Off the grid, training pigeons to broadcast signed messages.
|
|
|
Cricktor
Legendary
Offline
Activity: 1246
Merit: 2962
|
 |
May 01, 2025, 11:18:00 AM Last edit: May 01, 2025, 11:43:02 AM by Cricktor |
|
I think it is replaced  I hate the RBF option. There's a solution to avoid being robbed by default Full-RBF. OK. Thanks for re-iterating that you have zero credibility.
Why do you and others still interact with zero-value spammers here? Simply hit Ignore and never look back for dudes like bibilgin or Akito and some others who pollute this thread with their alarmingly frequent nonsense. We got robbed of Puzzle 69.
Hello, we are coming out to claim we are the group that solved puzzle 69. We are a group consisting of 12 software developers in Asia with interest in cryptography.
Prove it by signing a message with private key of public address bc1qlp0z45ctphhz0kywpmw3x2kjy7umhyfawxctah which you would need to be in control of, because it is the target output address of claiming puzzle #69. According to mempool.space this is the first transaction 651d171e1b103501f57563c2c12a9154e7659e2d9c72c87e92c6609d8213c07a of the RBF timeline that mempool.space got aware of. I would assume this is the solver's initial attempt to claim puzzle #69 and it failed spectacularly for obvious and known reasons, somewhat apparently not known to you if you are actually the first solver. Excuse me to be frank and blunt, but publishing the claiming transaction in public mempool is plain stupid and the reason why the solver has been robbed. Why didn't you use slipstream.mara.com as has been proven to be working as intended by the solver of puzzles #67 and #68 (Bram24732). We are aware of RBF attack so we used a wallet software (we prefer not to say which one) which does not enable RBF by default, to transfer the coins. But when we checked the transaction, before it was confirmed, another transaction was created.
If transaction 651d171e1b103501f57563c2c12a9154e7659e2d9c72c87e92c6609d8213c07a was yours, then why does it have RBF enabled? It's a contradiction to what you say. You clearly don't understand how unconditional Full-RBF works. Basically every miner or mining pool has that enabled because it gives them a financial incentive to do so. Miners don't give a shit if your super-secret wallet software (hilarious) flags RBF disabled. I'm puzzled, you don't know such details or didn't dare to inform yourself upfront properly. This has also been discussed in this thread extensively. Well, it's not easy to find in all the repetative no-brain-full-qote, no-value response bs that we see too much here. Now, our problem is how to pay our remaining GPU bill which amounts to $158,954.07. This is so frustrating! Why can't people play fair and square???
Blame yourself for not understanding how Full-RBF works. It seems you were aware that puzzle #66 was robbed, but #67 and #68 not. Why didn't you adapt the smarter strategy discussed here and likely elsewhere to safely claim puzzles with lower bitranges?
|
|
|
|
AlanJohnson
Member

Offline
Activity: 185
Merit: 11
|
 |
May 01, 2025, 11:21:48 AM |
|
|
|
|
|
Akito S. M. Hosana
Jr. Member
Offline
Activity: 392
Merit: 8
|
 |
May 01, 2025, 11:35:26 AM |
|
the key was found after 0.7206% of the range.
So someone solved puzzle 69 using a modified Cyclone in 20 days? 
|
|
|
|
FrozenThroneGuy
Member

Offline
Activity: 61
Merit: 43
|
 |
May 01, 2025, 11:44:07 AM |
|
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:)
|
|
|
|
fantom06
Jr. Member
Offline
Activity: 49
Merit: 1
|
 |
May 01, 2025, 11:53:19 AM |
|
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:) ./Cyclone -a f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8 -r 400000000000000000:7fffffffffffffffff -p 6 -j 10000000 terminate called after throwing an instance of 'std::invalid_argument' what(): ╨Э╨╡╨┤╨╛╨┐╤Г╤Б╤B╨╕╨╝╤Л╨╣ ╤Б╨╕╨╝╨▓╨╛╨╗ ╨▓ ╤Б╤B╤A╨╛╨║╨╡ Base58
|
|
|
|
|