Bitcoin puzzle transaction ~32 BTC prize to who solves it

[COBRAS]

Seems there are 12 satoshi left to grab on the #66 address. Hurry up guys.

TX input:

Code:

1FuckUmT5yBAvozf6gT8GRQVbJ7iBDUnrH

TX outputs:

Code:

1Jvv4yWkE9MhbuwGU66666666669sugEF 0.00000001
1YouAreSoDumbLoL666666666667K5aR4 0.00000002
1WhatWereUThinking6666666662wkqq1 0.00000003
1YouDeserveNothing6666666665sbbBC 0.00000004
1YouEpicFaiLure66666666666688GSDA 0.00000005
1BitchAssLoser66666666666669dBUVg 0.00000006
1AndEveryoneELse666666666669Vnc8C 0.00000007
1ThisisALosingGame6666666667HAZdf 0.00000008
1JustGetAReaLJob666666666665vGKVD 0.00000009
1YoureWastingTimeAndMoney664CVExC 0.00000010
1AndCausingCLimateChange6666HK8Qc 0.00000011
13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so 0.00000012
1Jvv4yWkE9MhbuwGUoqFYzDjRVQHaLWuJd 0.00000013
1FK5PjPNARQmg94n2cNHTo9417kWfXUDBQ 0.00002125

I think whoever sent these sats stole the price from the real solver of puzzle 66.

Can sender of microsat know of balace move faster then others because  this microsathoshi ?


Probably we will seen transaction replace again.

[AndrewWeb]

I don't think anything wrong happened here.

5.94 BTC went to

bc1ql5lrt3y97djyu5k8ewmz87nnemxheycp6wdree
bc1qdplvug87leypur2a27xh64u8cu78e0td8edwv7
bc1qpa20zkg6kr55yl7gxnwh37aj8q00rt70k6q8ru

whereas 0.66 BTC (exactly 10% of the prize 6.60 BTC) went straight to Binance (for cash out ?)

Someone helped the finder with the transaction and got 10% of the prize ?

[masken]

https://github.com/nzengi/Dual-Vanity/blob/main/dual_vanity.py


Dual-Vanity new version v0.1

start_range = 0x40000000000000000
end_range = 0x7ffffffffffffffff


prefix = "1B"
suffix = "W9"

sample output :: C Address :: 1BxxxxxxxxxxxxxxxxxW9

[Kelvin555]

I don't think anything wrong happened here.

There were so many bots listening to that address at every moment, and not even one tried to replace the transaction ? I doubt it, if so then the person who sent those sats is mocking us..... I interpreted "you're so dumb, what were you thinking and you deserve nothing" as what were you thinking trying to send out the coins through the mempool(exposing the public key), you're so dumb, the coins have been stolen from you, you deserve nothing  OR  mocking us, what were you thinking playing a losing game, you're so dumb, you deserve nothing.

Can sender of microsat know of balace move faster then others because  this microsathoshi ?

I don't know.

[COBRAS]

https://github.com/nzengi/Dual-Vanity/blob/main/dual_vanity.py


Dual-Vanity new version v0.1

start_range = 0x40000000000000000
end_range = 0x7ffffffffffffffff


prefix = "1B"
suffix = "W9"

sample output :: C Address :: 1BxxxxxxxxxxxxxxxxxW9

thank you for the scrypt

[COBRAS]

vanity adresses like this , I read, what some of them more vulneranble then other.

1FuckUmT5yBAvozf6gT8GRQVbJ7iBDUnrH

because they generated not all time in 256 bit range, mach smaler

[nomachine]

There were so many bots listening to that address at every moment, and not even one tried to replace the transaction ? I doubt it, if so then the person who sent those sats is mocking us..... I interpreted "you're so dumb, what were you thinking and you deserve nothing" as what were you thinking trying to send out the coins through the mempool(exposing the public key), you're so dumb, the coins have been stolen from you, you deserve nothing  OR  mocking us, what were you thinking playing a losing game, you're so dumb, you deserve nothing.

I even turned off the bot, thinking that the winner would go through Mara's slipstream.

We’ll see next time if that person is mocking anyone. Next time, all my bots will be ON.

[Baskentliia]

The more private keys we have, the smaller the error would be....5% deviation on puzzle 130 is too big.

Hello, can you share the guess range or decimal number of puzzle 130

[nomachine]

The more private keys we have, the smaller the error would be....5% deviation on puzzle 130 is too big.

Hello, can you share the guess range or decimal number of puzzle 130

python3 predict.py 130
Puzzle 130 Predicted Value: 794791040024653568798270036743662075904.00

[gygy]

The more private keys we have, the smaller the error would be....5% deviation on puzzle 130 is too big.

Hello, can you share the guess range or decimal number of puzzle 130

python3 predict.py 130
Puzzle 130 Predicted Value: 794791040024653568798270036743662075904.00

🔮🔮🔮

[nomachine]

🔮🔮🔮

Exactly. However, if I happen to succeed in any way, I will donate to everyone in this thread. I will definitely not send any mocking messages in addresses.

[zhengxingshui123]

I am a fool, and the 66 puzzle seems to have been taken away by a robot. I have no idea why this happened. Please tell me how to avoid being snatched away by robots if I crack the private key.

[COBRAS]

I am a fool, and the 66 puzzle seems to have been taken away by a robot. I have no idea why this happened. Please tell me how to avoid being snatched away by robots if I crack the private key.

Make a transaction fee in 5% of 1btc and more ballance, for any of ballance transfer transactions ! Robot have no so many money for fee

The more private keys we have, the smaller the error would be....5% deviation on puzzle 130 is too big.

Hello, can you share the guess range or decimal number of puzzle 130

python3 predict.py 130
Puzzle 130 Predicted Value: 794791040024653568798270036743662075904.00

why all try gake 130, but not 110 for ex ? need only 2^20 pubketxs of 2^110 crack, or make a pool for crack 2^50 keys in 2^80.
 

[Baskentliia]

🔮🔮🔮

Exactly. However, if I happen to succeed in any way, I will donate to everyone in this thread. I will definitely not send any mocking messages in addresses.

It's a 100% successful prediction, rest assured. Thank you. Puzzle 130

[random3425]

Hey,

hypothetically i find the key, submit tx transaction with 0.1BTC going to my address and pay fee of 6.5 BTC. How do you steal my transaction ?

Thank you!

It is a lose-lose example in my case the bot will keep increment 1sat/vB more than your or anyone else TX.

In the final round in case to reach the limit of the input balance it will append an extra input to the TX and send 100% of the puzzle address as fee.

  cant understand is worth or not to try for puzzle 67,68,69??

[gygy]

I am a fool, and the 66 puzzle seems to have been taken away by a robot. I have no idea why this happened. Please tell me how to avoid being snatched away by robots if I crack the private key.

Yes, unfortunately it seems it has been snatched. At least https://privatekeys.pw/puzzles/bitcoin-puzzle-tx directly states that. I don't know if they have proofs. And based on that, the original address is one of that was the target of the mocking transaction.

To avoid this you need to keep the public key (of this low range keys) in secret. Unfortunately public key is designed to be public, so it is not so easy to transact without making them public.
Option 1: Mine your own block or have a deal with a mining pool.
Option 2: Mara Slipstream. But Mara still can stole it in this case.

[Kelvin555]

I even turned off the bot, thinking that the winner would go through Mara's slipstream.

We’ll see next time if that person is mocking anyone. Next time, all my bots will be ON.

Me too, I thought whoever found the private key would go through Mara's slipstream, that no one would dare go through mempool directly but how wrong I was.

The thief who stole the coins must have a nice setup, it took his bot 45 seconds to replace the transaction, I assume whether he used BSGS or Kangaroo, it took 30 seconds to find the private key and the remaining 15 seconds for opening and shutting down apps.

[mcdouglasx]

Me too, I thought whoever found the private key would go through Mara's slipstream, that no one would dare go through mempool directly but how wrong I was.

The thief who stole the coins must have a nice setup, it took his bot 45 seconds to replace the transaction, I assume whether he used BSGS or Kangaroo, it took 30 seconds to find the private key and the remaining 15 seconds for opening and shutting down apps.

kTimesG bragged about having a very fast setup and also started precalculating tames for 66bit, 67bit... Preparations you would only need if you plan to steal the transaction sitting in the mempool.
Every other user that took part in the stealing-bot-script discussions a few pages ago is suspicious.
The thief likely active here but would never confess because of repercussions...and well he would unmask as an asshole  .

Is it considered the one who uses bots as a thief? Very little ethical, yes, but they are the rules, I think RBF is poorly implemented, it should be an irrevocable choice of those who send the funds and not depend on the configuration of each node.

[COBRAS]

Me too, I thought whoever found the private key would go through Mara's slipstream, that no one would dare go through mempool directly but how wrong I was.

The thief who stole the coins must have a nice setup, it took his bot 45 seconds to replace the transaction, I assume whether he used BSGS or Kangaroo, it took 30 seconds to find the private key and the remaining 15 seconds for opening and shutting down apps.

kTimesG bragged about having a very fast setup and also started precalculating tames for 66bit, 67bit... Preparations you would only need if you plan to steal the transaction sitting in the mempool.
Every other user that took part in the stealing-bot-script discussions a few pages ago is suspicious.
The thief likely active here but would never confess because of repercussions...and well he would unmask as an asshole  .

Is it considered the one who uses bots as a thief? Very little ethical, yes, but they are the rules, I think RBF is poorly implemented, it should be an irrevocable choice of those who send the funds and not depend on the configuration of each node.

jiHe is steal 66

https://bitcointalk.org/index.php?topic=5218972.msg64536611#msg64536611

[CY4NiDE]

Me too, I thought whoever found the private key would go through Mara's slipstream, that no one would dare go through mempool directly but how wrong I was.

The thief who stole the coins must have a nice setup, it took his bot 45 seconds to replace the transaction, I assume whether he used BSGS or Kangaroo, it took 30 seconds to find the private key and the remaining 15 seconds for opening and shutting down apps.

kTimesG bragged about having a very fast setup and also started precalculating tames for 66bit, 67bit... Preparations you would only need if you plan to steal the transaction sitting in the mempool.
Every other user that took part in the stealing-bot-script discussions a few pages ago is suspicious.
The thief likely active here but would never confess because of repercussions...and well he would unmask as an asshole  .

I'm tending to think it wasn't any of the usuals in this thread 'cause we all thought the solver would go through MARA. For this very reason I didn't even bother to finish developing mine.

Also, I don't think anyone would bother to precompute against 66 in this scenario as the key can be cracked in mere seconds anyways.

If that was the case it would have taken much less than 45s to replace the original tx, as once you have the key it might take less than 1 second to relay the first replacement.

I was also thinking.... What if the creator himself triggered the first attempted withdraw?

Reason: To officially embed this event in the challenge's timeline at the cost of 6.6 BTC, as now "puzzle #66" will be notoriously known to have been hijacked by a bot in the proposed scenario.

The bot scenario is now undeniably part of this puzzle's history. Am I making any sense here or am I just hitting my bong too much?