Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 45. (Read 230559 times)

Clown music here


There is a lot of bitcoin holders that are just waiting to see their holdings increase the value..

showing an address is not evidence of anything.

I can't prove the the puzzle creator not move that balance.
You can't prova the puzzle creator move it...

anything that we write here is pure speculation, is just an opinion of what you or me personally believe.

Even thats founder of the puzzle we cannot say anything..
Its attracting more people to join the bruteforce party.

He also didn't even claim the Bitcoin Cash and others on that addresses... Very suspicious   

Maybe because the person who is supposed to complain is dead, we have seen some people complain in this thread how they have lost their jobs and families because they have dedicated all their time to this puzzle challenge, some have even spent a huge amount of money on this puzzle challenge and the only hope  they are hanging on to is that they will find the private key.... when they finally find it and someone steals it from them and even mock them, what do you think will happen ?



This defeats the main reason the creator had in mind when he created the challenge in the beginning, how can he know that the community is able to crack 66bits range wallet in 3years time if he scheduled the withdrawal in 2 years time.

So can we confirm now puzzle #66 was solved and casually emptied by a normal transaction without any "bot war" taking place?
I'm personally not affected by #66 being solved because even though I've been at it for a year or so, I looked through all my theories, all my notes, all my scripts, and not one of them were even close to the solved keyspace/binary/hex/decimal.

Theoretically, which puzzle is now "easier" to solve for a normal person with standard resources? puzzle #67 with all kids of trash scripts, or #130 with kangaroo? 

3Emiwzxme7Mrj4d89uqohXNncnRM15YESs https://www.blockchain.com/explorer/addresses/BTC/3Emiwzxme7Mrj4d89uqohXNncnRM15YESs
Because, likely, he wanted to make the community work on the lower bits, but without the private key. Maybe the solution provided by Kangaroo answered all the questions related to the vulnerability when revealing the pubkey... The funds from those wallets were transferred by one person to a single address. Do you really think that someone wealthy enough, who can afford not to touch the prize money from 120 and 125 bits, would bother solving the puzzle at all, let alone succeed twice?! It's nonsense to think otherwise in this case.

For a while I thought along these same lines. But RBF is effective, and the network works securely as designed, because nobody is transacting bitcoins using wallet addresses with private keys in the low bit range. Puzzle 66's private key is at 0.00000000000000000000000000000000000000000000000000000000040025374665586730511 0971121712095050954258 x 100 percent of the keyspace.

In other words, if the keyspace was the distance between earth and the sun (147m km), 66's private key is not even a nanometer off the ground.

My math is probably off by a bit but just trying to help visualize the issue.

Where do you get that? Without any proof this is bullshit...

Just ask your self why the author of this challenge will move 1.2 and 12.5 bitcoins, when he increase all other puzzles in x10 factor? it wen from some 100 btc to near 1000

 

why the founder of Puzzle was transfered coins from 120 and from 125?

What odds would there be if during solving we could check for a known address?
For example, i have a locked multibit wallet since 2016-ish, could all combinations be checked against this address should i decide to solve a puzzle?

I would shit my pants if someone sent me 6.69 BTC by mistake 

It looks like this is because I sent an unsigned transaction to Mara, because https://coinb.in/#sign does not sign the raw transaction with the wrong private key, but simply returns the raw transaction unchanged in the field where the signed transaction should be.

You would have to check the balance of each private key.  It would slow down the brute forcing to a crawl.  I highly doubt there are any funded wallets in the keyspace, except for some dust in some test wallets that people made to test their bots.

So out of curiousity, did anyone ever hit a non-related funded wallet during puzzle solving?

It is not free. Those coins are burned. If you have "024ee2be2d4e9f92d2f5a4a03058617dc45befe22938feed5b7a6b7282dd74cbdd" as a Script, which is hashed into "20d45a6a762535700ce9e0b216e31994335db8a5", then it means, that it is invalid.

Thank you, this looks like what will be needed when the private key is found.

---

something is wrong when I send a transaction from address 67 signed by any privatekey through this service (https://slipstream.mara.com/), it says that:

"Transaction already exists in mempool, add a higher fee."

does this mean that if you sign a transaction with the correct private key, the service will respond with the same message?

If you find the private key to 67 and you want to send it through mara I think this is the way.  Someone please correct me if i am wrong.

bitcoin-cli createrawtransaction '[{"txid":"12f34b58b04dfb0233ce889f674781c0e0c7ba95482cca469125af41a78d13b3","vout":2},{"txid":"5d45587cfd1d5b0fb826805541da7d94c61fe432259e68ee26f4a04544384164","vout":15},{"txid":"08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15","vout":66}]' '{"bc1q0pju92kh0qyaygvnm074mpdhdg28qa357w7usd":6.69}'

The bitcoin address at the end should be replaced with your address otherwise you will send me 6.69BTC.

The output gives you this.

0200000003b3138da741af259146ca2c4895bac7e0c08147679f88ce3302fb4db0584bf31202000 00000fdffffff6441384445a0f426ee689e2532e41fc6947dda41558026b80f5b1dfd7c58455d0f 00000000fdffffff15cda65f1e46982fc082b15c8dbb60985d12a7e60b0c742263608cc9349f380 84200000000fdffffff014021e027000000001600147865c2aad77809d22193dbfd5d85b76a1470 763400000000

After you get the private key you need to sign it.

bitcoin-cli signrawtransactionwithkey "0200000003b3138da741af259146ca2c4895bac7e0c08147679f88ce3302fb4db0584bf31202000 00000fdffffff6441384445a0f426ee689e2532e41fc6947dda41558026b80f5b1dfd7c58455d0f 00000000fdffffff15cda65f1e46982fc082b15c8dbb60985d12a7e60b0c742263608cc9349f380 84200000000fdffffff014021e027000000001600147865c2aad77809d22193dbfd5d85b76a1470 763400000000" '["PRIVATE KEY WIF"]'

The result is what you put into mara slipstream. 

free 8$  btc

addrss compress P2PSH : 34gbwEu34QBz7bozafSyStRqw9f6Jw7cTt

privkey hex : 2832ed74f2b5e35ee
privkey wif : KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZfFoWMiwBt943V7CQeX

could someone show how to make a raw transaction for 67? it can be created without privatekey, are there any services for creating raw transactions, or using bitcoincore? to spend all outputs on one address with the required commission. so that I can then sign it and send it via MARA

ps: I haven't found the private key yet, but if I do I'll thank you for this tip))

Coincidence...   BTW What you mean "scheduled long time ago" ? By scripts ?  It would be visible.

There is better way to mess with such transacions (i don't know if it's true):

"RBF is optional and works by setting the nSequence flag in the transaction. If a transaction has the nSequence parameter set to an appropriate value, it is marked as replaceable. However, if nSequence is set to the maximum value (0xFFFFFFFF or 4294967295), such a transaction is not marked as replaceable - it is then "finalized" immediately and is not subject to the RBF mechanism."